|
Hi, Just recently we have begun to experience an issue with our connection managers in debug. I am using ssis 2005 BIDS. I can open the connection manager in the package, enter the password and click "Test Connection" with success. But when I execute the task, I get an error indicating the connection was not successful. I have a package config file enabled. When I disable the config file it executes properly. The config file has ConnectionString, Server name, user name and Password in it. However, I am trying to test the passing of a variable from the config file to the package, so I need the config file enabled. Can you tell me how the config file comes into play regarding debug? Am I doing something incorrectly? Thanks! paws27284
(comments are locked)
|
|
Hi , I guess the problem is more of an access issue or invalid credentials set in the config. Quick suggestions. Try to recreate the config file again after entering the values in the package connection string. Try to check if the config connection string matches the connection string in package. I guess it is enough you condfigure only the connection string since that holds all the required parameters. Thanks, Kannan
(comments are locked)
|
|
Overall it looks like all of my connection managers at some point in time become corrupt. It doesn't matter which package, whether there is a config file associated or not, whethter in debug or executing the package from the SQL job agent. Any ideas or suggestions regarding the whole idea of connection managers?
(comments are locked)
|
