@MDD ,
The issue you have described pertains more to the SQL Server and hence we would suggest you to post the query on the SQL Server Forum for better assistance.
UNABLE TO RUN SSIS PACKAGE THROUGH SQL SERVER AGENT FOR AZURE MANAGED INSTANCES
Hi,
I created a SSIS package in Visual Studio 2017 to load data from one of the tables in Azure Managed Instances to another database, and it worked fine.
But, when I create a job for that SSIS package in SQL SERVER AGENT in SSMS v.2018 and run that job, it throws me the following error:
Description: ADO NET Source has failed to acquire the connection {********-****-****-****-************} with the following error message: "Unable to load adalsql.dll (Authentication=ActiveDirectoryIntegrated). Error code: 0x2. For more information, see http://go.microsoft.com/fwlink/?LinkID=513072".
I visited that website and re-installed adalsql.ddl, but it still gives me that same error.
What could be the possible solution?
Thank you
4 answers
Sort by: Most helpful
-
neray-MSFT 26 Reputation points
2020-03-12T15:09:02.757+00:00 -
Uri Dimant 206 Reputation points
2020-06-11T04:53:59.593+00:00 Hi
Where you deployed the package to? You can more detailed error message under SSISDB catalog -
louis esangbedo 1 Reputation point
2020-06-19T12:29:02.073+00:00 I got a similar issue. ADO.Net connection within an active directory context .Package failing in SSIS_DB integration services catalog however when i test the package itself before deployment I realize that the connection is failing with the error message below.
TITLE: Connection Manager
Test connection failed because of an error in initializing provider. One or more errors occurred.
BUTTONS:
OK
-
MDD 6 Reputation points
2020-06-19T16:08:15.813+00:00 Hi everyone,
my apologies for not being active in this QNA.I already found the solution.
The issue was, even though I installed adasql.ddl and correct version of ADO.NET in my pc, those library and framework were still missing in our work server (sql server agent Jobs run in our office server).
After DBA installed them in the server side too, the job ran successfully.
I did not use SSISDB but deployed the SSIS package in the SQL Server Agent using the
Type - SQL Server Integration Services Package Package source - File SystemThank you!