Why does it appear as though SSIS is not reading a connection string properly?
2
votes
0
answers
1111
views
I am executing an SSIS package on a db server and receiving an error. I can execute it just fine on my local machine but when I try to execute it via a SQL Job I get the following:
Executed as user: \.
Microsoft (R) SQL Server Execute Package Utility Version 11.0.6020.0 for 64-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Argument ""CM.BackUpDB.ConnectionString";"Data "Source=;Initial" "Catalog=;
Provider=SQLNCLI11.1;Integrated" Security=SSPI;"" for option "parameter" is not valid.
The command line parameters are invalid.
The step failed.
It appears to me as though SSIS is splitting the connection string at the spaces instead of the semicolons. Why would it be doing that?
I am running SQL Server 2012. I do not have configuration files, nor am I dynamically generating the connection strings. They get configured in the SQL Job.
Asked by Wayne E. Pfeffer
(395 rep)
May 10, 2017, 07:19 PM
Last activity: Mar 31, 2024, 05:23 AM
Last activity: Mar 31, 2024, 05:23 AM