skosanabv (11/19/2013)
I found the solutionI experienced the same Issue with my packages, and tried all these solutions posted here, but none of them worked for me.
What I then did:
1. SQL Server Configuration Manager
2. SQL Services
3. Select SQL Server Agent, right click, select properties.
4. Under log on tab, select 'this account' radio button, and select the user who created the package.
Remember the user can be changed in the Solution Explorer in visual studio/SQL Server Data tools of the package in case there is a need to do that. HOW: Right Click the Project, Properties, Common properties, Project, CreatorName, Change it to whatever name you will configure the SQL Server agent to logon using.
Redeploy your package but not necessary. Start job at Step to test execution. Hurrraaaaayyy... Your Job is up and running.
I trust that this helps. Please give me feedback if this has helped you. Thank you.
Bongani
Are you suggesting that the SQL Agent service needs to run with the same account as created a package?
And therefore that every deployed package needs to be created by the same account?
🙂
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.