September 3, 2014 at 10:30 am
I have a package where I have an oledb connection manager, I'll call it "SQLConn" that is used to access a configuration table in SQL Server. I have 2 configurations in the pkg. The first one (located in the config window first) sets the connection manager SQLConn to use a config file in a directory....the DTS/Packages folder in SQL Server folder. The 2nd is a sql server config using the SQLConn connection to set the rest of the connection managers. When I deployed this pkg to our dev server it worked fine when running from a job (I did not have to paste the directory of the config file in the job step config tab). But whe I deployed to our QA and ran from a job it was not reading the new connection string from the file and had a login failure because it was still trying to connect to tghe SQL Server config table in dev. I added the directory and config file to the configurations tab of the job on QA and it then read the new connection string and ran successfully. Why did it not run without placing the directory in the config tab? It should have ran shouldn't it?
This QA server also never updates values from Enviroment variables either. Dev server reads them fine but the QA never does.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply