|
Hi I have a SSIS package created by a developer who left the company now. It used to run with his domain active but now it is not running. As a DBA I tried to run the job but now it is not executing. What might be the reason and how to resolve this...This is very urgent Thanks Munna
(comments are locked)
|
|
Take a look on the Job History for error returned by the SSIS package... From the error message you can see what is wrong. Or if you do not understand the error message, then post it here a we can probably help you.
(comments are locked)
|
|
I'm no SSIS expert but chances are he created the package using the default SSIS protection level setting "encrypt sensitive with user key". This setting ties the package directly to the user account so if his account is no longer active then the package won't work. To fix this I suggest converting the package to "don't save sensitive" and then implementing a package configuration. However, if that is out of your comfort zone I think you could also convert the protection level to "encrypt sensitive with password" and then specify a custom password instead. This option requires the password to be supplied when the package is executed so it's tricky (to say the least) to automate packages but it should at least allow you to run it manually.
(comments are locked)
|
