SSIS Error: ADO NET Source has failed to acquire the connection with the following error message: "Could not create a managed connection

Khan, Nasif 0

Hello

I am getting this error when trying to connect Dynamics CDS.

[ADO NET Source [2]] Error: ADO NET Source has failed to acquire the connection {6F23C652-54D5-487B-AF3D-3354FD263841} with the following error message:

"Could not create a managed connection manager.".

I am using Visual Studio 2022. Can someone assist?

I am using KingswaySoft CDS Tool. –

I tried reinstalled Visual Studio 2022 and SQL Data Tools as well. But nothing is solving the issue.

2 answers

Yitzhak Khabinsky 25,721 Reputation points

2023-08-23T13:12:26.3266667+00:00
Hi @Khan, Nasif,

Please make sure that you are using the following software:

VS2022 any edition.

SQL Server Integration Services Projects 2022 extension v.1.1 for VS2022.
Download link: https://marketplace.visualstudio.com/items?itemName=SSIS.MicrosoftDataToolsIntegrationServices

IMHO, the VS2022 is not ready for a prime time due to too many bugs. It is better to stay with VS2019.

UPDATE

Please try to follow the following step-by-step tutorial: https://www.youtube.com/watch?v=vR_hVPR8kZo
Please sign in to rate this answer.

1 person found this answer helpful.
Khan, Nasif 0 Reputation points

2023-08-23T16:33:53.4066667+00:00

@Yitzhak Khabinsky . I tried install VS2019 but when I try to created a new ADO.Net Connect, I don't see the "Microsoft.Data.SqlClient " provider. I am trying to connect to Dynamics CDS. Do you know how can I connect to Dynamics CDS in VS2019. I tried with "System.Data.SqlClient" but I cannot connect.

Yitzhak Khabinsky 25,721 Reputation points

2023-08-23T17:26:40.7366667+00:00

@Khan, Nasif,

I updated the answer. Check it out.
Sign in to comment
ZoeHui-MSFT 34,836 Reputation points

2023-08-23T01:27:56.3966667+00:00

Hi @Khan, Nasif,

I am using KingswaySoft CDS Tool.

KingswaySoft is a 3rd party software, I'd like to suggest that you may raise the issue to KingswaySoft support.

https://www.kingswaysoft.com/support

Regards，

Zoe Hui

If the answer is helpful, please click "Accept Answer" and upvote it.
Please sign in to rate this answer.
Khan, Nasif 0 Reputation points

2023-08-23T12:42:05.44+00:00

Hi @ZoeHui-MSFT , I am getting the error when I am not using any KingswaySoft components as well. When I use the native ADO NET Source, I get the same error. I am able to test the connection and can preview the data. Can you please assist? Is it something to do with the SQL Data Client Driver?

Shah, Ankit 5 Reputation points

2024-01-05T20:22:05.8133333+00:00

I am receiving the same error when trying to use .Net Providers\Microsoft SqlClient Data Provider. I am able to preview the data of my table correctly but when executing the task or package in VS 2022 version 17.8.3 I get [ADO NET Source [2]] Error: ADO NET Source has failed to acquire the connection {DF7AFAE3-2B46-4F97-980A-FBA747C9885E} with the following error message: "Could not create a managed connection manager.". is Microsoft SqlClient Data Provider ready to be using with SSIS? seems like there are bugs in the driver. We want to leverage Managed Identities with SSIS.

Joanna Shen 0 Reputation points

2024-03-26T19:39:59.12+00:00

I have the exact same use case - we need to connect to the Dynamics SQL data source via an ADO NET Source component. KingswaySoft is not the root cause here.

The only viable authentication for our organization is MFA. Microsoft SqlClient Data Provider works just fine in design mode. I'm able to preview the results of my SQL query against database.

The error is reported when package is executed. An error occurred with the following error message: "Could not create a managed connection manager.".

I agree with Shah, Ankit. Is Microsoft SqlClient Data Provider ready to be using with SSIS? Why would the authentication fail at run time, but works just fine in design mode or SSMS?
Sign in to comment

Share via

SSIS Error: ADO NET Source has failed to acquire the connection with the following error message: "Could not create a managed connection

2 answers