FME 2024.1 SharePoint Reader

Do you use the sharepoint online connector in your workspace? I think I can remember having problems with this transformer but not necessarily in FME 2024. If this is the transformer you are using can you remove the transformer from your workspace, save, open an empty workspace, uninstall the sharepoint library (tools>FME Options>FME Packages), open your broken workspace and add the transformer again and check if it's working now?

Thanks for the reply. I tried your suggestion but it made no difference.

It’s a Feature Reader in a brand new workspace trying to read in an Excel from a SharePoint library. The SharePointOnlineConnector transformer works fine. There’s nothing else in it at all.

Hi @jacintasomers have you tried re-authenticating your SharePoint connection? Has anything else in your environment changed since the upgrade? (permissions, security settings, SharePoint admin settings, etc.?)
If this issue persists, perhaps you can submit a support ticket with us so that we may investigate further. https://support.safe.com/hc/en-us/p/Support

@evieatsafe thanks for your reply. Yes I re-authenticated but had no joy. Everything is the same and the connectors continue to function in previous versions of FME. I can see the preview of the Excel sheets when setting up the transformer and also open it with no issues in the Inspector.

There seems to be a successful translation with the error coming afterward.  I’ll log a ticket thank you. 

Did you upgrade your reader, writers and/or transformers when moving to v2024.1?
Do you still have the problem when running it with a non-upgraded workbench, i.e. still using the 2023 readers, writers and transformers?

I am seeing the exact same thing. Before upgrading to 2024.1, a workflow that I use frequently functioned without issue. Since the upgrade, I too see a Python-related error when reading from an XLSX file that is stored on SharePoint. 

Even with a vanilla workflow that contains only the reader, it still fails to run. 

Traceback (most recent call last):
  File "weakref.py", line 590, in __call__
  File "C:\Program Files\FME\python\urllib3\connectionpool.py", line 1135, in _close_pool_connections
    conn.close()
  File "http\client.py", line 1020, in close
  File "socket.py", line 505, in close
  File "ssl.py", line 1311, in _real_close
  File "socket.py", line 499, in _real_close
OSError: [WinError 10093] Either the application has not called WSAStartup, or WSAStartup failed
Exception ignored in: <finalize object at 0x10bf8ae0; dead>
Traceback (most recent call last):
  File "weakref.py", line 590, in __call__
  File "C:\Program Files\FME\python\urllib3\connectionpool.py", line 1135, in _close_pool_connections
    conn.close()
  File "http\client.py", line 1020, in close
  File "socket.py", line 505, in close
  File "ssl.py", line 1311, in _real_close
  File "socket.py", line 499, in _real_close
OSError: [WinError 10093] Either the application has not called WSAStartup, or WSAStartup failed
Error running translation.
 

I've been in contact with SAFE and if you upgrade the connector then your workspace might work, it didn't for me. I'm still in contact with them though and hopefully will get to sort it soon in my case. 

Strangely I have found that even though you don't use a SharePoint online connector in your workspace, of you add one to the workspace or a bookmark in the workspace where the reader is, if you're running it in pieces, then the reader works. Something to do with how the connection works in the backend if I remember correctly. 

of note is that I have the same issue with FME Form 2024.1 but in FME 2020.1 the SharePoint reader works. 

@vincentochiel it works even in 2023, it’s very strange. SAFE are looking into it though. 

Hi, 

I presume this issue hasn’t been resolved? We are experiencing this same behaviour whilst testing FME Form 2024.2.2. We receive the identical error ‘OSError:(WinError 1093)’ when using a FeatureReader to connect to an Excel file hosted on SharePoint, features are read in from the excel file and passed downstream, but the error message is still generated.

As suggested above, using the SharePointOnlineConnector before the FeatureReader, enables the FeatureReader to function correctly. The SharePointOnline connector can reference any SharePoint site.

We have tried re-authenticating the SharePoint connections using multiple domain accounts, that all have full permissions to the source files on SharePoint, to no avail. 

We have the latest SharePoint package installed v 1.2.2

However reading from excel files using the FeatureReader, where the files are hosted on a ‘Teams’ SharePoint sites, is successful? I’m not sure what the significance of this is, other than the URL containing the word ‘teams’

https://ourdomain.sharepoint.com/Teams/DataShare 

vs

https://ourdomain.sharepoint.com/Sites/DataShare

Any suggestions, ideas welcome as this is preventing us from upgrading FME Server 2022.2 to FME Flow 2024.2.2

Hi ​@sean.bullock 

Are you still seeing this error after upgrading the SharepointOnlineConnector package to version 1.2.1? 

Hi ​@clang 

Can you submit a support ticket with us so we can look into this issue: https://support.safe.com/hc/en-us/p/Support 
Please reference this development ticket number (FMEENGINE-84641) so we can link it to your support ticket. 
Thank you! 

Hi ​@crystalatsafe, raised a ticket as requested. 

Thanks,

Chris

Hello, 

We are facing the same problem, is there a solution ?

FME FORM 2024.1.3

Thanks.

​@topotoma I have been sent a possible fix but I haven’t tested it yet. I’m hoping to get to it today or tomorrow. I have found that if you put a SharePointOnlineConnector between the Creator and the FeatureReader that the workspace will run. 

Hi ​@topotoma and ​@jacintasomers,

I’ve had a call open with Safe for the past few months testing various settings, SharePoint packages, FME installations and reconfiguring the FME app registration on the Azure Portal. 

Ultimately there’s no quick fix and requires significant effort for the Development Team to upgrade one of the Python libraries. No timescales have been provided.

The work around as identified, involves using a SharePointOnlineConnector OR PythonCaller (Script provided by Safe) before the Feature Reader. Please let me know if you need the script. 

Kind Regards,

Chris  

Hi Chris,

Thanks for your reply, updating the SharePoint connector to the latest version did the trick in the end. 

I had exactly the same situation than you, a workspace that was working well which suddenly shows this python error after the execution resulting in translation error.

Nevertheless I would still be interested in having a copy of the script you got that solved the problem on your side. 

Have a great day.

Best regards.

Thomas

Hi jacintasomers,

Thanks for your message, interesting to see the solution you got.

I tried a direct excel reader with web data surce set to SharePoint and also creator plus feature reader, both didn't work until I upgraded the sharepointonlineconnector transformer to the latest version. Only then it was all right.

Best regards.

Thomas

Hi ​@topotoma 

I'm glad to hear that updating the SharePoint package resolved the error for you. Since the upgrade worked for you, I don't anticipate that you will need to use the PythonCaller workaround, but I can share the script.

This script resolved that error in the case where updating the SharePoint package did not.

import urllib3



urllib3.disable_warnings()

http = urllib3.PoolManager()

http.clear()

Copy and paste the code into a PythonCaller directly under "import fmeobjects". Place this PythonCaller after the creator and before the FeatureReader. 

I also wanted to share a feature on the PythonCaller, (and other transformers) in case it's helpful. There is a feature called Parameter Presets, which lets you save parameters and reuse them.

• In the PythonCaller (at the bottom left) select Presets -> Save as -> New Preset
• Give it a name and save it 
• Now in a new workspace, when you click on a PythonCaller, you can select Presents -> Load 'name' to load the saved parameters. 

This will allow you to save different versions of the PythonCaller (or other transformers) and you won't have to copy/paste anything over when you open a new workspace.

crystalatsafe wrote:

Hi ​@topotoma 

I'm glad to hear that updating the SharePoint package resolved the error for you. Since the upgrade worked for you, I don't anticipate that you will need to use the PythonCaller workaround, but I can share the script.

This script resolved that error in the case where updating the SharePoint package did not.

import urllib3



urllib3.disable_warnings()

http = urllib3.PoolManager()

http.clear()

Copy and paste the code into a PythonCaller directly under "import fmeobjects". Place this PythonCaller after the creator and before the FeatureReader. 

 

I also wanted to share a feature on the PythonCaller, (and other transformers) in case it's helpful. There is a feature called Parameter Presets, which lets you save parameters and reuse them.

• In the PythonCaller (at the bottom left) select Presents -> Save as -> New Present
• Give it a name and save it 
• Now in a new workspace, when you click on a PythonCaller, you can select Presents -> Load 'name' to load the saved parameters. 

This will allow you to save different versions of the PythonCaller (or other transformers) and you won't have to copy/paste anything over when you open a new workspace.

Hello Crystal,

Many thanks for your reply. Well, I couldn’t have guessed myself the solution you proposed nor updating the connector. I thank the contributors of the forum, this is an invaluable ressource.

Have a great day.

Hi ​@topotoma 

Happy to help!