SAM Error 12294 on SBS 2003 DC

I have been receiving the following Event log error for a while now:

Event Type:      Error
Event Source:      SAM
Event Category:      None
Event ID:      12294
Date:            8/13/2012
Time:            6:12:35 AM
User:            <local domain name>\Administrator
Computer:      <server name>
Description:
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: a5 02 00 c0               ¥..À  

I have checked the error code and it reads the following:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator\Desktop\Err>err c00002a5
# for hex 0xc00002a5 / decimal -1073741147 :
  STATUS_DS_BUSY                                                ntstatus.h
# The directory service is busy.
# 1 matches found for "c00002a5"

I've used lockoutstatus.exe to confirm that the account hasn't been locked and I can also see that there hasn't been a bad password associated with the event (that is reported).

I haven't been able to determine the source of this error and would like any assistance you may be able to offer.
telefunkenAsked:
Who is Participating?
 
Jeffrey Kane - TechSoEasyConnect With a Mentor Principal ConsultantCommented:
FYI, troubleshooting for this error is here:
http://support.microsoft.com/kb/306091

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Do you have any other servers in your network?  Or have you recently changed the Domain Administrator password?

Jeff
TechSoEasy
0
 
telefunkenAuthor Commented:
Jeff,

Other than the DC (the server we're having the issue with) we have a terminal server, that's it. No, the administrator password has not been changed recently.

Nate
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Then you can either troubleshoot the root cause, or safely ignore it as the article I linked above suggests.

Jeff
TechSoEasy
0
 
telefunkenAuthor Commented:
Jeff,

I am off for the next two days...but I will review and get back to you sometime Monday. After browsing the article I think there might be a collision happening. What do you think of the following senario:

I routinely use RDC to connect to the DC and to the Terminal Server. Many times I will be logged in to both at the same time. It is also not unusual for me to leave both of these connections active, sometimes even overnight. Could this be the cause of my error?

Nate

PS Thanks again for your assistance
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Are you logging in with the Administrator account?  If so, stop doing that and see if the problem subsides.

Use your own account or create a separate admin account for logging into your server.

Jeff
TechSoEasy
0
 
telefunkenAuthor Commented:
Jeff,

Yes I have been logging in using the admin account using RDC. I will do as you suggest and try making another account with admin privilages and see if that helps.

Nate
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.