I encountered this issue too when trying to deploy an individual package. The solution for me was to deploy the entire project and not an individual package.
visual studio 2019 deploy ssis to azure or local ssms fails
Hi Up to about 3 weeks ago I was able to deploy my package to Azure or locally to my SSMS but now I keep gettign this error message: =================================== The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. (.Net SqlClient Data Provider) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.00.2000&EvtSrc=MSSQLServer&EvtID=3930&LinkId=20476 ------------------------------ Server Name: strategy.database.windows.net Error Number: 3930 Severity: 16 State: 1 Procedure: internal.prepare_packages_deploy Line Number: 182 Im unable to resolve this - I even created a blank ssis package and tried to deploy that and it gave the same error. Please can someone assist its quite urgent now. ps: microsoft your help link is useless it goes nowhere ? For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.00.2000&EvtSrc=MSSQLServer&EvtID=3930&LinkId=20476 thanks w
2 answers
Sort by: Most helpful
-
-
Monalv-MSFT 5,891 Reputation points
2020-11-02T06:47:56.053+00:00 Hi @Wayne ,
Please use try, catch to get the detailed error messages .
Hope the following links will be helpful:
- TRY...CATCH (Transact-SQL)
- Deploy an SSIS project from SSMS with Transact-SQL
- Deploy Integration Services (SSIS) Projects and Packages
- Tutorial: Deploy and run a SQL Server Integration Services (SSIS) package in Azure
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.
Hot issues in October--Users always get connection timeout problem when using multi subnet AG via listener. Especially after failover to another subnet.