asked
ssis package job failing
Hi I have an ssis package which runs fine when a developer runs from visual studio. But when we create a job for it its failing. What might be the cause. I dont have the exact error message.. The job was created by a developer with his credentials and as he left the comapny and his credentials expired then job started failing. From then we are running from visual studio. are there any workarounds...
You can try to navigate to this job from SSMS and change the **owner** of the job (under general tab). In the worst case scenario when for whatever reason SSMS will not let you to even view it, you can re-enable AD account in question, change its password, login to SSMS with his new credentials, change the owner, and then disable AD account again. Oleg
In that case, open the dtsx file on the server. From the file menu choose Save Copy of Package. This will enable you to change the security settings. Change the package protection level to: Do not save sensitive data.
Are the connections all windows based? If they are then create Credentials and a proxy account, and then run the SSIS package as the proxy account. See this link for info on how to create credentials and run as a proxy account
http://www.sqlservercentral.com/articles/Integration+Services+(SSIS)/69441/
Re-import the job and chose to use the server for the sensitive data, its the last option in the list. That should do the trick.
1st thing, please check dtexec is enabled or not 2nd thing, some pakages will run based on the system variables (like 32 bit or 64 bit environmrnt). If the package is is configured to run under 64 bit environment and operating sytem is 32 bit environemtn then you need to disable 62 environment on ssis configurations.
Thanks all for your quick response !! I did dtexec it's failed.
Did you try any of the other things that folks listed? p.s. This is also why I don't allow Developers to promote code to any production system. ;)
1 Person is following this question.
