Avatar of GordonAluminum
GordonAluminum
 asked on

Errors on Active Directory Server on Windows Server 2003

This morning no one was able to login to the domain until Restarted our Active Directory Server.  In the Event viewer I found the following Errors:

NTDS (400) NTDSA: An attempt to write to the file "C:\WINDOWS\NTDS\edb.log" at offset 696832 (0x00000000000aa200) for 512 (0x00000200) bytes failed after 1 seconds with system error 1784 (0x000006f8): "The supplied user buffer is not valid for the requested operation. ".  The write operation will fail with error -1011 (0xfffffc0d).  If this error persists then the file may be damaged and may need to be restored from a previous backup.


NTDS (400) NTDSA: Unable to write to section 0 while flushing logfile C:\WINDOWS\NTDS\edb.log. Error -1011 (0xfffffc0d).

NTDS (400) NTDSA: The logfile sequence in "C:\WINDOWS\NTDS\" has been halted due to a fatal error.  No further updates are possible for the databases that use this logfile sequence.  Please correct the problem and restart or restore from backup.

Then I got several of these:

Active Directory was unable to establish a connection with the global catalog.
 
Additional Data
Error value:
4294966206 []
Internal ID:
208017f

Once I rebooted the errors ceased but not sure why I would be getting these errors.  Please help.
Active DirectoryWindows Server 2003

Avatar of undefined
Last Comment
GordonAluminum

8/22/2022 - Mon
SOLUTION
Brian B

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
ASKER CERTIFIED SOLUTION
Awinish

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
GordonAluminum

ASKER
I do not see any error messages about it being corrupted just an issue with the log.  Not sure why that would lead to these messages.

Also it is currently up and checking the integrity involves bringing it down.

Brian B

At this point better to bring it down in a controlled way at a time of your chosing then have it crash due to corruption.
GordonAluminum

ASKER
I checked it last nite.  It is not corrupted.  We are running vmware and I guess the driver that handles file sync for it can cause problems so I disabled on our Active Directory Server.

This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23