Link to home
Start Free TrialLog in
Avatar of Markieboy1
Markieboy1Flag for United Kingdom of Great Britain and Northern Ireland

asked on

NTDS ISAM, Event ID: 508, A request to write to the file "C:\Windows\NTDS\edb.log" succeeded, but took an abnormally long time.

I have a customer with a Server running Server 2012 R2 Essentials. The company has just the one server running as a Domain controller and file server.

The server is a Dell PowerEdge R320, just over a year old and has 3 x 2TB Hard Drives running Raid 5.

Emails are dealt with by Exchange online.

There have been no particular problems noted with the server and all users are happy.

Over the last couple of weeks, however, I have received the following error on the daily report most days:

 NTDS ISAM      Event ID: 508
NTDS (592) NTDSA: A request to write to the file "C:\Windows\NTDS\edb.log" at offset 4431872 (0x000000000043a000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (16 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

It is always the same error and always the edb.log file. When it happens varies considerably.

I have looked into this problem via Google and Experts Exchange and it most likely reason for the error boils down to hard disk problems.
I have therefore:

1.      Checked the installed Dell Openmanage software for potential errors on the hard disks. All signs show everything is OK.
2.      I have run consistency checks on the drives every other month since installed and since the errors started and they have always been fine.
3.      Checked the Antivirus running on the server and all the areas of NTDS etc. are excluded from scanning. ( Real time and scheduled scanning )

I have checked the logs in Event Viewer and can’t see any other errors that may suggest problems with Active Directory etc.

I am going to contact Dell and see if they have any advice and I intend to visit the site soon and check Active Directory.

I would, however, like advice on what to check when it comes to Active Directory – considering the error - and any other ideas on what may cause this issue apart from potential hard disk problems.

Thanks in advance for any help.
ASKER CERTIFIED SOLUTION
Avatar of Satish Auti
Satish Auti
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Markieboy1

ASKER

I have got Dell on the case.

I will leave the question open for now just in case they don't come back with anything useful.
Dell are looking into it. They have found no hardware issues although they are trying to update the firmware of the hard drives and it is causing them problems

I have left it it their hands for the moment. The error, however, is still being registered.

I will close this for now but may bring it back in another question if it isn't sorted by Dell