locked
event id 12294 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    i am getiing below error message  in bulk. i am using Windows server 2003

    The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.


    regards,
    Balwan Singh

    Thursday, November 5, 2009 8:00 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Balwin,

    this error probably means that some service or someone/some pc is trying to use the Administrator account. If you changed the password lately, make sure that -if any services are running as the Administrator - services use the appropriate password.

    Try turning on security auditing on the server and monitor the security eventlog for failed audits.


    Regards,

    Ruben
    • Proposed as answer by Wilson Jia Thursday, November 5, 2009 10:08 AM
    • Marked as answer by Wilson Jia Monday, November 9, 2009 2:47 AM
    Thursday, November 5, 2009 8:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Balwan,

    Ruben is correct. Please perform his suggestion to verify whether there is some service running under administrator account.

    You can also perform the following actions to see if it resolves the issue.

    1.Keep the server's security patches up to date

    2.Change administrator password and the password on all administrative level accounts

    3.Rename administrator account (and possible other admin accounts)

    4. please also run a complete virus scan on your network using the latest availabe virus definitions.

    You may refer to this KB article:

    User accounts are unexpectedly locked, and event ID 12294 is logged in Windows Server 2003

    http://support.microsoft.com/kb/887433

    Hope it helps.

    Best Regards,
    Wilson Jia
    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed as answer by Wilson Jia Thursday, November 5, 2009 10:08 AM
    • Marked as answer by Wilson Jia Monday, November 9, 2009 2:48 AM
    Thursday, November 5, 2009 10:08 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Balwin,

    this error probably means that some service or someone/some pc is trying to use the Administrator account. If you changed the password lately, make sure that -if any services are running as the Administrator - services use the appropriate password.

    Try turning on security auditing on the server and monitor the security eventlog for failed audits.


    Regards,

    Ruben
    • Proposed as answer by Wilson Jia Thursday, November 5, 2009 10:08 AM
    • Marked as answer by Wilson Jia Monday, November 9, 2009 2:47 AM
    Thursday, November 5, 2009 8:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Balwan,

    Ruben is correct. Please perform his suggestion to verify whether there is some service running under administrator account.

    You can also perform the following actions to see if it resolves the issue.

    1.Keep the server's security patches up to date

    2.Change administrator password and the password on all administrative level accounts

    3.Rename administrator account (and possible other admin accounts)

    4. please also run a complete virus scan on your network using the latest availabe virus definitions.

    You may refer to this KB article:

    User accounts are unexpectedly locked, and event ID 12294 is logged in Windows Server 2003

    http://support.microsoft.com/kb/887433

    Hope it helps.

    Best Regards,
    Wilson Jia
    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed as answer by Wilson Jia Thursday, November 5, 2009 10:08 AM
    • Marked as answer by Wilson Jia Monday, November 9, 2009 2:48 AM
    Thursday, November 5, 2009 10:08 AM