October 26, 2016 at 10:41 am
I have a table of ssisconfig table where I stored all the connection strings with a type column.
In the package I took execute sql task and queried with ssis config table where type = ....
after that I took for each loop contained where it does truncate stage table and loads data from DOW database to main table.. there I faced this error..
I created a var called user:connstring and passed the first connection by default..
[Connection manager "Source Database Connection - DOW"] Error: The connection string format is not valid. It must
consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string with zero
components is set on database connection manager.
Error: The result of the expression "@[User::ConnString]" on property "\Package.Connections[Source Database Connection - DOW].
Properties[ConnectionString]" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
October 26, 2016 at 10:59 am
mcfarlandparkway (10/26/2016)
I have a table of ssisconfig table where I stored all the connection strings with a type column.In the package I took execute sql task and queried with ssis config table where type = ....
after that I took for each loop contained where it does truncate stage table and loads data from DOW database to main table.. there I faced this error..
I created a var called user:connstring and passed the first connection by default..
[Connection manager "Source Database Connection - DOW"] Error: The connection string format is not valid. It must
consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string with zero
components is set on database connection manager.
Error: The result of the expression "@[User::ConnString]" on property "\Package.Connections[Source Database Connection - DOW].
Properties[ConnectionString]" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
This sounds annoying, but I'm not sure what help we can be if you do not tell us what the problematic connection string is. Are you looking for a solution? An explanation? Sympathy? 🙂
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 26, 2016 at 11:10 am
Solution
October 26, 2016 at 11:29 am
mcfarlandparkway (10/26/2016)
Solution
Good luck with that, as you've given us neither the text nor the expression.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 26, 2016 at 4:42 pm
mcfarlandparkway (10/26/2016)
I have a table of ssisconfig table where I stored all the connection strings with a type column.In the package I took execute sql task and queried with ssis config table where type = ....
after that I took for each loop contained where it does truncate stage table and loads data from DOW database to main table.. there I faced this error..
I created a var called user:connstring and passed the first connection by default..
[Connection manager "Source Database Connection - DOW"] Error: The connection string format is not valid. It must
consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string with zero
components is set on database connection manager.
Error: The result of the expression "@[User::ConnString]" on property "\Package.Connections[Source Database Connection - DOW].
Properties[ConnectionString]" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
Let's make this clear as to what we need...we know you created a var called user:connstring. But that isn't the issue, there seem to be two issues and we need the data/string/whatever that created the errors:
1. The connection string format is not valid
-what is the connection string? Then we may be able to tell you why it isn't valid
2. Properties[ConnectionString]" cannot be written to the property.
-again, the connection string has an issue and cannot be used. Knowing what the connection string is will help troubleshoot this.
We can't see your data and we aren't mind readers, so we really need you to provide us the needed information.
-SQLBill
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply