Active Directory Weird Error

[drewmaztech]

At EXACTLY 10am, every day, I get in my event log:

Event ID: 12294
"The SAM Database was unable to lockout the account of [] 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."

Trouble is - I have no user account "[]". (it's a little box) I've searched AD with no results. It happens on all my domain controllers at the same time, so I doubt its a hardware problem.

I am having NO luck finding a decent resolution to this error. I can provide the Hex error data if you're interested.
Any help would be greatly appreciated!

[Matridom]

At EXACTLY 10am, every day, I get in my event log:

Event ID: 12294
"The SAM Database was unable to lockout the account of [] 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."

Trouble is - I have no user account "[]". (it's a little box) I've searched AD with no results. It happens on all my domain controllers at the same time, so I doubt its a hardware problem.

I am having NO luck finding a decent resolution to this error. I can provide the Hex error data if you're interested.
Any help would be greatly appreciated!

In the support pack on the OS cd, there are a few utilities that will scan AD for anomolies and possibly correct them. Not positive if it will help, but worth a shot

[drewmaztech]

Ran a few utils and they say everything in hunky-dorey...

[futuretech]

This from eventid.net points to two M$ knowledge base articles.
http://www.eventid.net/display.asp?e...=12294&source=

[confus-ed]

This from eventid.net points to two M$ knowledge base articles.
http://www.eventid.net/display.asp?e...=12294&source=

They look most plausible ! worth investigation

So it says its a mismatch in your administrator accounts.

one of our servers has a different Local Administrator password, compared to Domain Administrator, because all services on that server use the local Admin account. I don't know what services require the domain wide account, but setting them the same has fixed all problems

in his case.