Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

SSIS package failing while executing as Agent job Expand / Collapse
Author
Message
Posted Wednesday, March 20, 2013 11:25 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, November 14, 2014 8:28 AM
Points: 301, Visits: 597
Welsh Corgi (3/20/2013)
Right Click on the Project and Select Properties,

On the left click the debugging tab.

Make sure that Run64bitRuntime is set to false.


If it is set to TRUE even while debugging it will not run at all, it looks like he got past that...However the last time this happened to me, it was package encryption, just sayin, doesn't hurt to look at all avenues...


MCSA SQL Server 2012
Post #1433362
Posted Wednesday, March 20, 2013 11:38 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Thursday, December 11, 2014 1:06 PM
Points: 4,253, Visits: 4,295
I had 64 bit set to true on many occassions and it still ran in debug but failed when running as a job.

I just ran a package with 64 bit set to true and it sucessfully completed.

Is the OP connecting to Oracle, DB2, etc or are they only using SQL Server Authenication?

If they are only using SQL Server Authenication specifying EncyptSensitiveWithPassword is not going to do anything.

The error that the OP is getting is not the type of error you would expect if there was an issue with the password.


For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1433371
Posted Thursday, March 21, 2013 7:27 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, November 26, 2014 3:45 AM
Points: 42, Visits: 1,079
Thanks Welsh for your help.

When I set the job to run package as 32 bit then it started working fine.

this package connecting to remote MYSQL Server to pull the data.

Thanks John and every one.
Post #1433778
Posted Thursday, March 21, 2013 7:30 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, November 14, 2014 8:28 AM
Points: 301, Visits: 597
lazy writer (3/21/2013)
Thanks Welsh for your help.

When I set the job to run package as 32 bit then it started working fine.

Thanks John and every one.


Glad that was it, it is always something like that, that gets me all the time! When ever I create a new package this is one of my first steps! Good luck! and don't forget to encrypt it if you are saving a user name and password or you will end up in the same boat!



MCSA SQL Server 2012
Post #1433779
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse