Skip to main content

I have created a workspace to push files into Sharepoint.

I've created a web connection via FME Options into Sharepoint. I've signed in and tested this connection.

 

When I bring in the SharepointOnlineConnector transformer, I can find the Authentication account. It's when I got to the "..."s to the right of Site and click on that that I get this warning.

imageimageI am connected to the internet. I don't think I have firewall issues.

 

I am signed into Sharepoint in my web browser too to this specific account. I do work with multiple Sharepoint/Microsoft accounts though on this laptop if that makes a difference?

 

I was unable to get Sharepoint to work in the workspace, however I have a colleague who can write into this Sharepoint account using my Sharepoint login/password (he writes through FME Server) and write into Sharepoint successfully. As a result he exported a .xml for me and told me to import it.

imageI have tried that, but am still getting this warning. I notice in the last three lines of the .xml it refers back to his ownername. Do I need to change this?

 

I wrote the workspace in FME 2022.1, but have since updated to 2022.2.1 which is the same version as my colleague who can write into Sharepoint.

Hi, when you created the web connection account "Sharepoint-test" I can see you used the web service template provided by Safe = safe.microsoft-sharepoint.Microsoft SharePoint Online

 

For production use, we recommend users obtain their own client id and client secret from the web service provider.

 

The steps may involve getting you're IT to register an app in Azure. If you are having trouble configuring the safe.microsoft-sharepoint.Microsoft SharePoint Online Web Service please refer to one of these articles depending on your App Registration settings. 

 

Hi, when you created the web connection account "Sharepoint-test" I can see you used the web service template provided by Safe = safe.microsoft-sharepoint.Microsoft SharePoint Online

 

For production use, we recommend users obtain their own client id and client secret from the web service provider.

 

The steps may involve getting you're IT to register an app in Azure. If you are having trouble configuring the safe.microsoft-sharepoint.Microsoft SharePoint Online Web Service please refer to one of these articles depending on your App Registration settings. 

 

Hi @jamesb16otterill​ ,

 

Thank you for your reply.

 

I've followed the steps multitenant and followed the article closely. I am still getting the same message.

image 

I did notice though when I switched to sharepoint-test I got a different warning message.

imageAre there any other troubleshooting or steps I can take before asking IT or give him some really easy to follow instructions? The IT guy works remotely and is hesitant to let any systems he is unfamiliar with into the system, so I'd like to try and figure this out myself if possible.

I'm not sure why the webservice provided by Safe for MicrosoftOnline is failing. Perhaps you could get it working after sending this to your IT to whitelist/trust these URLS

URLs Used by FME and Safe Software

 

Each web connection has a web service template

These templates can be found in 'Manage Services' in the bottom right corner of web connections window

Did the 4. 'Test the web service' work

 

If you still have problems with the above service (created from MS Sharepoint online safe.microsoft.sharepoint), then use the Production method recommended

Find out from IT if you are single or multi tenant

  • Single-tenant apps are only available in the tenant they were registered in, also known as their home tenant.
  • Multi-tenant apps are available to users in both their home tenant and other tenants

Then follow all the steps

 

Unfortunately oAuth authentication can be convoluted... but follow every step!

Hi @epro_admin​ : I am having the exact same issue as you had. I also followed a Multitenant web connection for Sharepoint Online Connector on Server. Were you able to resolve to issue? Could you please share the insights?

Hi @epro_admin​ : I am having the exact same issue as you had. I also followed a Multitenant web connection for Sharepoint Online Connector on Server. Were you able to resolve to issue? Could you please share the insights?

Hi @jaygrg111_​ , I ended up logging a case with support. We weren't able to solve it per se, but they did offer me a work around while they investigate further - install Fiddler Classic and have it open before you open your workspace, then run the workspace. That worked for me. Support said for them sometimes it works with Fiddler Classic installed, but not open. That's not the case for me. I suggest you log a support case too so they know other people are experiencing this issue too.

Hi @jaygrg111_​ , I ended up logging a case with support. We weren't able to solve it per se, but they did offer me a work around while they investigate further - install Fiddler Classic and have it open before you open your workspace, then run the workspace. That worked for me. Support said for them sometimes it works with Fiddler Classic installed, but not open. That's not the case for me. I suggest you log a support case too so they know other people are experiencing this issue too.

@epro_admin​  thank you so much for your response. Sounds good. I will reach out to them.

Community Stats

32,030
Posts
121,648
Replies
39,655
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.