Warning NTDS ISAM Event ID 507 and Event id 508

Discussion:

(too old to reply)

RizFra

2006-09-05 08:37:02 UTC

Hi,
i have a problem with my active directory (with 2 domain controller): some
time appears this warning in the event viewer (Directory Service Log):

------------------------------------------------------------------------------------
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 507
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
Description:
NTDS (500) NTDSA: A request to read from the file "C:\WINDOWS\NTDS\ntds.dit"
at offset 15908864 (0x0000000000f2c000) for 8192 (0x00002000) bytes
succeeded, but took an abnormally long time (87 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.
------------------------------------------------------------------------------------

and then

------------------------------------------------------------------------------------
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
Description:
NTDS (500) NTDSA: A request to write to the file "C:\WINDOWS\NTDS\edb.log"
at offset 1230848 (0x000000000012c800) for 512 (0x00000200) bytes succeeded,
but took an abnormally long time (95 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.
--------------------------------------------------------------------------------------

Can anyone help me? any idea?

many thanks
Francesco

Jorge Silva

2006-09-05 11:09:07 UTC

Permalink

Hi
Start by checking 2 things:
-Antivirus is looking at your NTDS Folder.
-Disk performance is bad or disk is starting to crash or having other
performance problems.
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

Post by RizFra
Hi,
i have a problem with my active directory (with 2 domain controller): some
------------------------------------------------------------------------------------
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 507
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
NTDS (500) NTDSA: A request to read from the file
"C:\WINDOWS\NTDS\ntds.dit"
at offset 15908864 (0x0000000000f2c000) for 8192 (0x00002000) bytes
succeeded, but took an abnormally long time (87 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.
------------------------------------------------------------------------------------
and then
------------------------------------------------------------------------------------
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
NTDS (500) NTDSA: A request to write to the file "C:\WINDOWS\NTDS\edb.log"
at offset 1230848 (0x000000000012c800) for 512 (0x00000200) bytes succeeded,
but took an abnormally long time (95 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.
--------------------------------------------------------------------------------------
Can anyone help me? any idea?
many thanks
Francesco

RizFra

2006-09-07 09:38:01 UTC

Permalink

hi Jorge,
i had installad another DC and replicated AD information on this server
all roles and AD objects. Then the first server was sutting down and off.

Now AD is ok.

I think it was a hw problem (like say you).

thanks
francesco

Post by Jorge Silva
Hi
-Antivirus is looking at your NTDS Folder.
-Disk performance is bad or disk is starting to crash or having other
performance problems.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator

Jorge Silva

2006-09-07 10:02:04 UTC

Permalink

Glad to help
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

Post by RizFra
hi Jorge,
i had installad another DC and replicated AD information on this server
all roles and AD objects. Then the first server was sutting down and off.
Now AD is ok.
I think it was a hw problem (like say you).
thanks
francesco

Post by RizFra
Hi,
i have a problem with my active directory (with 2 domain controller): some
------------------------------------------------------------------------------------
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 507
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
NTDS (500) NTDSA: A request to read from the file
"C:\WINDOWS\NTDS\ntds.dit"
at offset 15908864 (0x0000000000f2c000) for 8192 (0x00002000) bytes
succeeded, but took an abnormally long time (87 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.
------------------------------------------------------------------------------------
and then
------------------------------------------------------------------------------------
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 05/09/2006
Time: 9.25.07
User: N/A
Computer: ERACLE
NTDS (500) NTDSA: A request to write to the file
"C:\WINDOWS\NTDS\edb.log"
at offset 1230848 (0x000000000012c800) for 512 (0x00000200) bytes succeeded,
but took an abnormally long time (95 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.
--------------------------------------------------------------------------------------
Can anyone help me? any idea?
many thanks
Francesco

gmeng

2007-06-06 17:35:35 UTC

Permalink

I have the same problem on 2 DCs. It started happening at the same tim
so I don't think it is related to hardware. I can reproduce the proble
every time I try to copy a large file (> 1GB).

Has anyone found a solution to the problem that is *not* hardwar
related? I have no AV running.

NTDS (400) NTDSA: A request to read from the fil
"C:\WINDOWS\NTDS\ntds.dit" at offset 25772032 (0x0000000001894000) fo
8192 (0x00002000) bytes succeeded, but took an abnormally long tim
(146 seconds) to be serviced by the OS. This problem is likely due t
faulty hardware. Please contact your hardware vendor for furthe
assistance diagnosing the problem

--
gmen
-----------------------------------------------------------------------
gmeng's Profile: http://forums.techarena.in/member.php?userid=2644
View this thread: http://forums.techarena.in/showthread.php?t=58112

http://forums.techarena.i

erb

2007-06-12 03:25:50 UTC

Permalink

I have this problem as well.

I just recently turned my member server in a Domain Controller.
My problem is NOT related to a hardware fault.

MS doesn't help with this error.

NTDS (576) NTDSA: A request to read from the file
"C:\WINDOWS\NTDS\ntds.dit" at offset 303104 (0x000000000004a000) for
8192 (0x00002000) bytes succeeded, but took an abnormally long time
(119 seconds) to be serviced by the OS. In addition, 0 other I/O
requests to this file have also taken an abnormally long time to be
serviced since the last message regarding this problem was posted 12433
seconds ago. This problem is likely due to faulty hardware. Please
contact your hardware vendor for further assistance diagnosing the
problem.

Both servers are 2k3 and very active Terminal Servers. If I'm in remote
desktop and this occurs, the screen freezes but not all at once. My only
solution is to wait it out.
This is causing problems with the client workstations. Main issue is
because My Documents is redirected to the server, makes the
workstations freeze up till the problem goes away.

I cannot reproduce this error.

I'm anxious to troubleshoot but I'm not sure where to start...
denouncing it as a domain controller might be a start.

(by the way, I just joined this site to reply to this)

--
erb
------------------------------------------------------------------------
erb's Profile: http://forums.techarena.in/member.php?userid=26609
View this thread: http://forums.techarena.in/showthread.php?t=581125

http://forums.techarena.in

JustinGSEIWI

2009-04-22 19:52:26 UTC

Permalink

I just noticed that I have this event logged as well. Did anybody find
an answer to this? It is possible that mine is hardware related since it
is a server that is at least five years old. Here is a copy of my
error.

Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 4/21/2009
Time: 10:13:30 PM
User: N/A
Computer: -server-
Description:
NTDS (416) NTDSA: A request to write to the file
"C:\WINDOWS\NTDS\edb.chk" at offset 0 (0x0000000000000000) for 4096
(0x00001000) bytes succeeded, but took an abnormally long time (123
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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Thanks,

Justin

--
JustinGSEIWI
------------------------------------------------------------------------
JustinGSEIWI's Profile: http://forums.techarena.in/members/92673.htm
View this thread: http://forums.techarena.in/active-directory/581125.htm

http://forums.techarena.in

Marcin

2009-04-23 00:42:42 UTC

Permalink

Justin,
assuming this is recurring error, other than the checking th eobvious
(hardware problem), you might want to verify firmware/drivers for your disk
controller and monitor disk performance to determine if these do not come
into play...

hth
Marcin

Post by JustinGSEIWI
I just noticed that I have this event logged as well. Did anybody find
an answer to this? It is possible that mine is hardware related since it
is a server that is at least five years old. Here is a copy of my
error.
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 508
Date: 4/21/2009
Time: 10:13:30 PM
User: N/A
Computer: -server-
NTDS (416) NTDSA: A request to write to the file
"C:\WINDOWS\NTDS\edb.chk" at offset 0 (0x0000000000000000) for 4096
(0x00001000) bytes succeeded, but took an abnormally long time (123
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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Thanks,
Justin
--
JustinGSEIWI
------------------------------------------------------------------------
JustinGSEIWI's Profile: http://forums.techarena.in/members/92673.htm
View this thread: http://forums.techarena.in/active-directory/581125.htm
http://forums.techarena.in

Meinolf Weber [MVP-DS]

2009-04-26 18:58:19 UTC

Permalink

Hello JustinGSEIWI,

Check that Antivirus software excludes that directory during scans. Additional
check hardware drivers and run diagnostic test for hardware. Maybe the hardware
is going to crash.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm