0

I have two SQL servers, each running on their own Windows server. The versions of both Windows and SQL Server are the same, they are on the same domain, they're virtually identical.

On these servers, I have set up credentials for a domain service account (sa_abc), I've added sa_abc as a CmdExec proxy in the SQL Agent, I've created a job with one step (a CmdExec step with time /t > d:\temp.txt ).

On one server this job runs fine and the result is what I'd expect: a txt file on the root of the D; drive with the time of running printed in it. On the second server this job fails with the error:

Unable to start execution of step 1 (reason: Error authenticating proxy Domain\sa_abc, system error: The user name or password is incorrect.). The step failed.

I've validated that the domain account is indeed valid; I have a Powershell script that takes a username/password and validates it against the Active Directory. This seems to rule out any conflict with the DC.

  • You may have already done this but, from the docs, verify The user specified in the credential must have "Access this computer from the network" permission (SeNetworkLogonRight) on the computer on which SQL Server is running. – Scott Hodgin Oct 16 at 12:33
  • @ScottHodgin just checked: settings are equal between machines, and include everyone and users, so I'd say that's sufficient. – steenbergh Oct 16 at 13:20
  • Does anything in this post help? Also, some good stuff here – Scott Hodgin Oct 23 at 11:45
  • What do the Windows Event Security Logs show at the time of the job failure? Are you seeing a NT Authority/Anonymous Login event or are you seeing an error stating the Domain\sa_abc account has a bad password, etc.? – John Eisbrener Oct 23 at 14:34
  • How are you confirming the password is correct? Have you dropped and recreated the credential to be sure? – HandyD Oct 24 at 6:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.