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

Please Help Solve Why SSIS Package Fails When Run as SQL Agent Job Expand / Collapse
Author
Message
Posted Wednesday, January 19, 2011 10:50 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, June 1, 2013 8:05 AM
Points: 8, Visits: 70
Thanks, Grasshopper. I'd forgotten about this post. I'll keep your solution in mind for the future. What I discovered a few weeks ago was that we'd been copying existing working packages and then modifying them for the new server. SSIS really does not like this copying and modifying. When we finally gave that up and rebuilt the packages from scratch, all the problems we were having vanished.
Post #1050215
Posted Wednesday, September 12, 2012 6:25 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, November 14, 2014 5:18 PM
Points: 248, Visits: 1,052
Hope this link helps you

http://sqlism.blogspot.com/2012/08/ssis-package-in-sql-server-agent-job.html




SSIS Package in SQL Server Agent Job Fails
Error:
Argument "xyz" for option "connection" is not valid. The command line parameters are invalid. The step failed.


Solution:

If your SQL Server is 64 bit

In SQL Server JOB-->Properties-->Steps--->


In the Execution Option Tab -- Check "Use 32 bit runtime"
In the Data Sources Tab -- Uncheck the checkboxes of the connection managers if already checked.
Schedule the Job and run it
Post #1358277
Posted Tuesday, October 2, 2012 11:25 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, December 10, 2013 12:03 AM
Points: 125, Visits: 408
Hi all

Not sure if any one is still having this issue but the one change below seemed to resolve the problem for me.



*** NOTE - I did not have to make any changes to the job properties etc ****



Follow below steps :

1. Right click Solution

2. Select properties

3. Go to Debugging tab

4. Set 64 Bit Run Time to False

5. click Ok and close out

6. Save package

7. Deploy / run package as per normal

Web site address if needed for above steps

http://social.msdn.microsoft.com/Forums/en-NZ/sqlintegrationservices/thread/71cd55a0-b32d-4b2f-99c8-52d5e3d8cd7c

Cheers
Vani
Post #1367406
Posted Tuesday, September 30, 2014 3:26 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, November 14, 2014 5:18 PM
Points: 248, Visits: 1,052
Try this

http://sqlism.blogspot.com/2012/08/ssis-package-in-sql-server-agent-job.html
Post #1621385
Posted Wednesday, October 1, 2014 7:37 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, November 14, 2014 10:55 AM
Points: 346, Visits: 310
Does it make a difference if you load this into Integration services on the server and secure it with a password?
Most likely Visual studio is taking care of the security of sensitive data (connection strings) for you.
I have run into this issue before even when using Native security etc...
Post #1621553
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse