SSIS packages not executing when run from Visual Studio

Question

I have an SSIS project that I've been working on. I've moved to a new workstation, and when I try and run the SSIS packages from VS 2015 on this new workstation, they immediately complete with out doing any work. The progress log remains blank, and the output log only shows two lines:

SSIS package "C:\MyFolder\MyPackage.dtsx" starting.
SSIS package "C:\MyFolder\MyPackage.dtsx" finished: Canceled.

I can deploy the packages to SQL Server, and they run fine. Other SSIS projects on this workstation run without issue, and running these problem packages from other workstations also work without issue.

Anyone have any idea what might be the issue, and/or tips for how I can troubleshoot this?

Answer 1

Definitely sounds like an environmental issue. Works when targeting 2016, not when targeting 2012. New workstation, new problems.

Does the version number of SSDT match between machines? What is your current version? And the version on the old machine? Check here on how to find SSDT version numbers.

I ask because this sound similar to MS Connect 755959 that was resolved with a service pack update.

If your version numbers match, then this blog has great info about troubleshooting package cancellation errors.

Good luck!

Answer 2

Final solution ended up being mis-matched versions of the Attunity Connector for Oracle.

On the new workstation, I had only installed version 4.0. Once I installed versions 3.0 and 2.0 as well, the packages began to run without issue. This is even though most of the packages I was testing didn't user the Attunity connector. Just having an MSORA connection manager in my project was enough to bring the whole thing crashing down.

Moral of the story: Even though v4.0 is required to be installed to allow the designer in VS2015 to access and use the connector/Sources/Destinations, you still need the version specific to the SSIS TargetServerVersion that you're using installed as well.

Answer 3

I decided to add a comment as I had similar problem. I started the package by execute package command and no progress was visible. I checked the connections - everything fine. But still no gear icons and no progress. For me the solution was to remove the objects from /obj/Development (I created a backup in case of the problems) After that it worked fine.

Answer 4

I had a problem similar to this in VS Data tools 2012 when executing the package did not show that anything was happening. There were no gear icons showing a task has started or green tick when a task had completed. Later I found out that the packages were actually running and data was being extracted and loaded. To correct this I found that if I opened the connection managers and test the connections before executing then all of execution icons worked as expected. Thanks

Answer 5

Mine was fixed by changing the project Debug Option - Run64BitRuntime to False.

Right click project -> Property -> Configuration Properties -> Debugging -> Debug Option -> Run64BitRuntime