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

Argument "Server1" for option "connection" is not valid. The command line parameters are invalid. The step failed. Expand / Collapse
Author
Message
Posted Tuesday, January 3, 2012 11:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, September 11, 2012 8:03 AM
Points: 6, Visits: 62
I 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 E
Post #1229483
Posted Tuesday, January 3, 2012 11:57 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, September 11, 2012 8:03 AM
Points: 6, Visits: 62
in 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.

Post #1229484
Posted Monday, August 20, 2012 5:40 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 10:04 AM
Points: 235, Visits: 976
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 #1347515
Posted Thursday, December 20, 2012 4:50 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, February 28, 2014 10:00 AM
Points: 1, Visits: 22
This 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.

Post #1399133
Posted Thursday, May 30, 2013 10:11 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 23, 2014 10:24 AM
Points: 1, Visits: 20
Thank you so much. I have been loosing my hair since yesterday trying to find a solution and finally your solution just worked like magic!!!
Post #1458311
Posted Monday, July 15, 2013 9:53 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 7:36 AM
Points: 1,832, Visits: 1,367
+1 this did the trick for me too!



Everything is awesome!
Post #1473743
Posted Friday, September 6, 2013 8:32 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, May 29, 2014 12:41 AM
Points: 5, Visits: 59
hi, the solution didn't work for me though I had the same error. What I found was that the SQL Connections (in BIDS) can not contain spaces when processed via the SQL Agent.

- Leon
Post #1492277
Posted Thursday, October 3, 2013 4:09 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 17, 2014 7:00 AM
Points: 9, Visits: 88
Lightly resurrecting this just to note that I had the same problem.

Forcing it to use the 32-bit executable didn't work, but I did find out that the job had been altered in SSMS 2008 when it's a 2005 database.

Recreating the steps through SSMS 2005 fixed the issue for me. Thanks for the pointers though!
Post #1501101
Posted Tuesday, May 20, 2014 2:23 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, May 20, 2014 2:22 AM
Points: 22, Visits: 292
Actually the problem was that in my SSIS package I had the connection names as "server.domain.com". If the connection name contains dots and dashes, then the SQL Agent will fail to execute the package, since these connection names end up in the command line of the dtexec executable.

Make everything as simple as possible, but not simpler.
Albert Einstein
Post #1572524
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse