Cannot deploy SSIS via Integration Services to SQL Server 2012: Current transaction canot be committed. Error:3930

Question

I have a SSIS that has been working for over a year, and just in a couple of days I made a bunch of changes. When I try to deploy, it returns me an error saying

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

It doesn't tell me what or which package is causing this issue.

Is there any way to trouble shoot this?

I appreciate any recommendation!!

Answer 1

I got the same error message when I tried to deploy a new version of an SSIS package.

I saw that the SSISDB was using a lot of disk space:

So I opened the properties of the SSISDB integration service catalog and lowered the retention period:

And then I ran the job SSIS Server Maintenance Job:

After having done that, I was able to deploy the SSIS package. So take a look and see how much space the SSISDB is using and if you can clean it.

Answer 2

Just deploy the whole project rather than SSIS Package.

Answer 3

I changed the name of my Solution and Project but wanted to deploy to the same location in the SSISDB Catalog. I was getting this specific error because of the name change (it was failing on deployment step when it called the internal.preparedeploy procedure). I ended up deleting the Project that existed on the Target Server and re-deploying the new Project to the same location. It deployed successfully.

Answer 4

In my case, the reason of the error was trigger on SSISDB DB for DDL_DATABASE_LEVEL_EVENTS, wich tried to write info in another DB.

Answer 5

I just solve it, the partitionw as running out of free space, I just cleaned the log, and it's back to normal!