Error :
Argument "ETL" for option "connection" is not valid.
The command line parameters are invalid. The step failed.
While executing the Job in SQL Server Agent.
-
2what are you trying to do and with what ssis tools? what is the connections you are using? If you could explain the setup it would give a better indication.Inus C– Inus C2013-05-06 10:07:30 +00:00Commented May 6, 2013 at 10:07
Add a comment
|
4 Answers
This is often a problem with parameter configuration, see e.g. here.
When you run from inside BIDS, you are in an environment where your parameters are available. When you schedule an SSIS package as a SQL Server job, those parameters have to come from somewhere. You can reference them in a configuration file, and you can override them in the configuration tab for the job.
Comments
Today I faced exactly same issue and I fixed it. What I did is, renamed connection name (without space, dots,hyphen) in my SSIS package. Previously I had default connection name so it showed error as
Argument "****" for option "connection" is not valid. The command line parameters are invalid. The step failed.
later I changed both source and destination connection names(without space) and used those packages while scheduling Job in SQL Server Agent and tried Start Jot at Step and succeeded.
1 Comment
2tone_tony
this helped to I removed the underscore from my parameter then deleted and recreated the job. For some reason the sql server agent doesn't like it for some ssis packages
I had a similar issue where the paramater value ended in a backslash. I just removed it and appended it back in an expression within the SSIS package.
Comments
I also had a similar problem, I made a change deployed and it stop working, I tried to remove spaces and hyphens as suggested above (I have 2 connections at fault) and still nothing, well it did make an effect as in the error message switched from one connection to the other - arrrgh, after pulling all my hair out all day. I just had a thought to delete the job and recreate and it worked! Also BIDs I definitely think there is some kind of configuration bug in that after you deploy and try to manually change the connection manager it fails, so my workaround is to configure first, then deploy, (delete existing job if present) then create the job, so repeat for each environment u need to deploy to.
