How to know when not using the config file?
Is there a way to tell if an SSIS package isn't able to read the config file for some reason? We have had situation recently (which we are correcting) where our SSIS package ran against a different environment and didn't use the values in the config file because DTSX didn't have permissions to the config file. It took us a while to figure it out. When this happened we didn't receive a clear error message the config file couldn't be read and I'd like to work in some sort of routine to test reading the config file so we can write that to a log and be sure which environment it is using. I wasn't able to find anything searching the web. Thanks
October 4th, 2012 5:12pm

Check this: a post answers your question, please click "Mark As Answer" on that post or "Vote as Helpful".
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2012 2:57am

Hi, You can insert the value of the variable or any connection string that you pass through configurations, to any Custom log file, or log table(sysdtslog90). Rajkumar
October 5th, 2012 3:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics