InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 19:00:40 GMT20http://www.sqlservercentral.com/Forums/Topic1229483-148-1.aspxThis did the trick! Thank you so much for posting this solution!Unfortunately I wasted a whole day playing with different settings to try to resolve this... wish I had googled this error message first :-( I would have never thought of this in a million years.Thu, 20 Dec 2012 16:50:46 GMTwroberts 45638http://www.sqlservercentral.com/Forums/Topic1229483-148-1.aspx[url=http://sqlism.blogspot.com/2012/08/ssis-package-in-sql-server-agent-job.html]http://sqlism.blogspot.com/2012/08/ssis-package-in-sql-server-agent-job.html[/url]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 bitIn 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. Mon, 20 Aug 2012 17:40:27 GMTSQListichttp://www.sqlservercentral.com/Forums/Topic1229483-148-1.aspxin Set Values tab,I set I set Properties Path to:\Package001.Variables[User::ConnectionString001].Properties[Value]and Vaule is the actual connection string.but still got the same error. Tue, 03 Jan 2012 11:57:38 GMTw.w.http://www.sqlservercentral.com/Forums/Topic1229483-148-1.aspxI have a SSIS package run fine in BID, but when run as a sql agent job, it failed at the error:Argument "Server1" for option "connection" is not valid. The command line parameters are invalid. The step failed.In Job Step Properties, Configuration, Command files, Execution options, Logging, Set Values, Verification tabs do not have anything set. The only change made is in Data Source tab, the server name is changed to server2 ,so is in Command Line tab changed accordingly. But, somehow, it still points to the connection inside of the package. If I change the connection in the package, then create a new job point to the changed package, then it runs fine. Why changing DataSouce in the job properties will not take effect?Here is what is Command Line tab:/FILE "C:\ Conv_01.dtsx" /CONNECTION "Connection001";"\"Data Source=server2\SQL2008;Initial Catalog=FO;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;Application Name=SSIS-Package-{849C75AD-4693-4DF2-9EC7-73C347FEE10C}HEC_1.US-Iv2.5;\"" /CONNECTION " Connection002";"\"Data Source=server2\SQL2008;Initial Catalog=ULL;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;Application Name=SSIS-Package-{D399B84F-1467-41C3-A292-5B27789B66A3}HEC_EL1.ULL;\"" /CHECKPOINTING OFF /REPORTING ETue, 03 Jan 2012 11:54:09 GMTw.w.