Pages

Tuesday, March 8, 2011

Logon failure: unknown user name or bad password

This is one of the very often faced error for job failure.

Exact error goes as follows:
Unable to start execution of step (reason: Error authenticating proxy , system error: Logon failure: unknown user name or bad password.). The step failed.

This happens when the secret word(password) you provided while creating a credential for a proxy has got expired. Exact scenario may be, you have used a domain account which enforces password expiration policy and you have changed you password. This happens because sql server resolves your changed password when you authentication mode is set to accept mixed mode, but the credentials which you have created does not accept this or resolve the change. Now you if you have to make this proxy work you need to delete the credential and again create it with new password and map to proxy. This sometime may again hit your jobs. So better way is to alter the credential and provide the new password. This can easily be achieved by below script by replacing the values according as per your needs:

Script:
USE [master]
GO
ALTER CREDENTIAL [ProxyCredentialsName] WITH IDENTITY = N'DOMAIN\ACCOUNTNAME', SECRET = N'NewPasswordchanged'
GO

4 comments:

  1. The suggestions above, and all the other ones I've tried, have yet to resolve my issue. I opened a remote desktop session using the login the proxy uses. Then I opened Management Studio and started the job. It failed with "Logon failure: unknown user name or bad password."
    The error log says: [298] SQLServer Error: 22046, Impersonation error. [SQLSTATE 42000]

    It looks like I may have to completely uninstall and reinstall the SQL Server.

    ReplyDelete
    Replies
    1. Hi Chris,

      Did you go through below link?
      It has some useful information.

      Are you running SSIS Package inside Job, What is the nature of the Job etc. Can share some more details

      Delete
    2. http://www.sqlservercentral.com/Forums/Topic527449-150-1.aspx

      Delete
  2. This comment has been removed by the author.

    ReplyDelete