Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using a proxy to run several SQL Server agent jobs.
Essentially the jobs copy data from Excel spreadsheets into a dbs via a network shared drive. The jobs have been failing for several weeks with the following error:

"Unable to start execution of step 1 (reason: Error authenticating proxy SERVERNAME\sharename, system error: ConnGetProxyPassword). The step failed."

when I run it under the proxy account, if I run it under the SQL Server Agent then I don't have permission errors.

I've recreated the proxy accounts but this has made no difference. The password for the proxy is correct.

Banging my head against this - any suggestions? It's not password length which I've seen suggested online.

share|improve this question
I suspect now, after two solid days of investigation that our dba changed the account that the SQL Server Agent runs under and as a result, the account can no longer use the proxy account I've set up. – alimack Jul 26 '11 at 8:11

Change the SQL Server Agent account back!

share|improve this answer
If this resolved the issue, please be sure to mark your answer as "accepted" when you are able. – jscott Jul 16 '12 at 15:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.