Sounds like when you run it as yourself, you have appropriate permissions on Server1, but the account SQL Agent runs on may not have appropriate permissions on Server1. Agent must be a domain user account also...
When you run the job, it runs under the SQL Agent login account, not the Windows login (Administrator). That account must have login permissions on the remote SQL Server. Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.
I found in propreties of "sql server agent" of server2 that the user "domain/administrator" who is starting the sql agent.
By asking the netwokrk administartor he said that he changed the password of "domain\administrator" on the domain controler server win2000 so the old password was not changed for sql server agent of server2.
After I changed the passowrd to be match each other I was be able to start the sql server agent of server2.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.