Hi, I have no idea why I am receiving such an error. I just installed Server 2003 Eval for some testing, and whenever I transfer large files (4gigs+), the server keeps on freezing. I don't think there is anything wrong with the hardware because I had windows 2000 server previously installed on this machine and it ran perfectly for 1+ years.
I updated my linksys NIC drivers and Promise IDE controller, so i am not sure what the problem could be.
OO yeah, I downloaded all windows updates.
any ideas?
thanks in advance
---ERROR---
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 509
Date: 7/30/2004
Time: 12:08:42 AM
User: N/A
Computer: 2003SERVER
Description:
NTDS (516) NTDSA: A request to read from the file "C:\WINDOWS\NTDS\ntds.dit" at offset 2490368 (0x0000000000260000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 1 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 92 seconds ago. 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.
I updated my linksys NIC drivers and Promise IDE controller, so i am not sure what the problem could be.
OO yeah, I downloaded all windows updates.
any ideas?
thanks in advance
---ERROR---
Event Type: Warning
Event Source: NTDS ISAM
Event Category: Performance
Event ID: 509
Date: 7/30/2004
Time: 12:08:42 AM
User: N/A
Computer: 2003SERVER
Description:
NTDS (516) NTDSA: A request to read from the file "C:\WINDOWS\NTDS\ntds.dit" at offset 2490368 (0x0000000000260000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (69 seconds) to be serviced by the OS. In addition, 1 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 92 seconds ago. 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.