August 13, 2007 at 3:21 pm
I have the following problem and I'm hoping someone knows the answer.
I have several jobs scheduled that are all failing. The jobs are all executing DTS packages. Manually executing the packages works fine.
The error I get is login failed and the account name given is the domain account used for running the sql agent service.
The owner of the jobs is a user that was originally not part of the sysadmin role. So originally I was getting the non-sysadmins error about not being able to run cmdexec. So I started off by creating a credential and proxy account but that wasn't working so I resorted to granting the sysadmin role to the owner of the jobs and the domain account that runs the sql agent service. I also made the sql sgent service domain account part of the local admin group. However I still get this login failed message for the domain account of the sql sgent service.
My environment is sql server 2005 , service pack 2, and windows 2003 server sp2.
What am I missing?
Thank you for any input you may have,
MaryAnn
August 13, 2007 at 9:08 pm
Microsoft have changed a few things the package owner and the Agent Proxy must be both Admin level accounts. Try the link below for details.
http://support.microsoft.com/kb/918760
Kind regards,
Gift Peddie
August 15, 2007 at 1:10 pm
My work around was to make the owner of the package the same as the account running the package. I have Admin level rights and so did the agent but it would sporaticly fail when I was the owner. Since I changed the owner to be the same as the agent, problem solved. Not ideal but gets the job done.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply