OData Service to Sharepoint - Cannot acquire a managed connection from the run-time connection manager.

Vasantha Vasantha 16

Hello,

I am trying to get the sharepoint list using oData Source service using Basic Authentication. The connection test okay and i can preview the data.

Connection String

https://XXXXXXXXXXXXXXXX/_vti_bin/listdata.svc/

But when i run the package, it will error with following error message

Information: 0x4004300A at LoadData, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC020801F at LoadData, OData Source [23]: Cannot acquire a managed connection from the run-time connection manager.
Error: 0xC0047017 at LoadData, SSIS.Pipeline: OData Source failed validation and returned error code 0xC020801F.
Error: 0xC004700C at LoadData, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at LoadData: There were errors during task validation.

Any help is greatly appreciated!

Monalv-MSFT 5,891 Reputation points

2021-02-02T02:44:27.923+00:00

Hi @Vasantha Vasantha ,

1.May I know if you set expression for the connection string in OData Source Connection?

2.Could you please share the screenshots of your OData Source and OData Source Connection?

3.Please refer to How to configure OData SSIS Connection for SharePoint Online.

Best Regards,
Mona

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

8 answers

Rastogi, Aditya [ICG-IT] 1 Reputation point

2021-04-09T17:16:24.843+00:00

Hi @Vasantha Vasantha , Did you manger the solve the issue. I am facing the same issue. OData Connection was working in past and now suddenly it stopped working. I am getting same error as yours. Manual connection check works fine but when i try to run the package i get error.

Thanks,
Aditya
Please sign in to rate this answer.
Vasantha Vasantha 16 Reputation points

2021-04-09T17:47:20.78+00:00

Aditya,

I was not able to fix the issue. Looking for export advice from the community!

Thanks

RiaanJ 6 Reputation points

2021-05-09T21:54:46.247+00:00

Hi @Vasantha Vasantha ,

I have been experiencing the same issue since about mid April, with no resolution from our Internal IT or Microsoft.

However, this morning without any changes made to the solution, it started working again.

Have you experienced the same, or did Microsoft perhaps give you an answer/solution to manually fix this?

Do you have a Microsoft Incident number for this issue, as we could raise a Severity 1 call with them if multiple people complain about the same issue?

Austin Daily 1 Reputation point

2021-05-11T18:11:21.907+00:00

We are also having the exact same issue since mid-April.

rdkn 41 Reputation points

2021-05-11T23:39:50.137+00:00

same exact issue for us - have you guys got anywhere with the resolution?

rdkn 41 Reputation points

2021-05-12T00:50:39.963+00:00

same exact issue for us - have you guys got anywhere with the resolution?

RiaanJ 6 Reputation points

2021-05-12T01:14:19.457+00:00

ragavanrajan posted a solution below. He works with me and investigated the issue as it was solved for us this week.

Please have a look at his proposed solution, then reply here whether it worked for you.

Thanks

Rockell, Jill M 1 Reputation point

2021-05-25T14:00:20.48+00:00

I am still having this issue. Data last updated on 5/17/21 and hasn't worked since. Read through several threads all no help! :(
Sign in to comment
ragavanrajan 1 Reputation point MVP

2021-05-11T22:22:09.457+00:00
Hello Folks,

We were facing the same issue as @RiaanJ mentioned. I have created many new tenants but every single SharePoint site has ODATA issue. After serious research, I figured out this issue is either due to "Azure Security default settings" or "Conditional Access policy" has been created.

Solution:

Pre: Make sure you have proper Azure Active Directory access, if not contact your Azure Administrator or IT helpdesk.

Log in to https://portal.azure.com/#home

Select "Azure Active Directory"

Click Properties > Manage Security Defaults

Turn off the Enable Security Defaults > and Choose "Other" and add some appropriate comments or choose any other relevant option

Press save and wait for few minutes to sync.

Alternatively, if someone has created Conditional access policy to prevent SharePoint OData access. This error can occur.

Now your SSIS can fetch data and it will also solve if you have any connection error.

Hope it helps
Please sign in to rate this answer.
Hamada Abdulmonsif 21 Reputation points

2021-05-18T10:36:48.677+00:00

I'm suddenly facing this issue since 3 days and I have tried all proposed workaround with no luck, however my jobs were running without any issue since 2 years

Randy R 1 Reputation point

2021-07-08T16:27:28.41+00:00

@Hamada Abdulmonsif did you every figure out a solution? To the job failure due to the SharePoint Odata connection? My jobs started failing mid May as well. I haven't had much success getting our SharePoint group to investigate and I can't make any changes to the Azure portal as previously suggested.
Sign in to comment
rdkn 41 Reputation points

2021-05-12T05:20:22.283+00:00

Ah, I just see the above solution indeed worked for you. I will keep this article bookmarked for sure :)
Please sign in to rate this answer.

0 comments No comments
Sign in to comment