December 19, 2008 at 9:38 am
Hello folks - this one is driving me potty, been at it for hours. DTExec script setting some global variables...
This one with 2 variables works fine.
dtexec /FILE "D:\AirCharter\Migration\NewProject\Migration\Migration\ParentMigrate.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTINArgument ""\Package.Variables[User::vParentProdConn].Value;Data Source=LOCALHOST
;Initial Catalog=ACS_Production;Provider=SQLNCLI.1;Integrated Security=SSPI;"" f
or option "set" is not valid.G OFF /REPORTING EW /set \Package.Variables[User::vDummy].Value;"HELLO2" /set \Package.Variables[User::vDummy2].Value;"HELLO"
-----------
If I add a connection string parameter:
/set \Package.Variables[User::vParentProdConn].Value;"Data Source=LOCALHOST;Initial Catalog=ACS_Production;Provider=SQLNCLI.1;Integrated Security=SSPI;"
I get the error:
Argument ""\Package.Variables[User::vParentProdConn].Value;Data Source=LOCALHOST
;Initial Catalog=ACS_Production;Provider=SQLNCLI.1;Integrated Security=SSPI;"" f
or option "set" is not valid.
-----------
I've checked for carriage returns and the usual and all seems to be kosher. If i plug the value in directly to the project, it works fine. I don't think SSIS cant resolve some of the characters in the text string into a parameter.
Any ideas? Thanks...Jon
December 19, 2008 at 10:13 am
Sorry, sorted it. I plugged it into the DTExecUI and resolved it this way. It just needed the backslashes:
"\"Data Source=LOCALHOST;Initial Catalog=ACS_Production;Provider=SQLNCLI.1;Integrated Security=SSPI;\""
Have a good w/end!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply