none
ESENT problem on WS2012 DC RRS feed

  • Question

  • Hi,

    I now install new Domain controller for existing domain (with two DC on WS2008R2).

    I use hardware Dell M620 with H710 RAID controller and two HDD SAS 10kRPM. Systém log is OK, but in application log is many warnings about ESENT:

    1)

    Log Name:      Application

    Source:        ESENT

    Date:          24. 5. 2013 12:48:55

    Event ID:      533

    Task Category: General

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      xxxxxxxxxxxxxxxxxxxxx

    Description:

    svchost (2536) A request to write to the file "C:\Windows\system32\LogFiles\Sum\Svc.log" at offset 4112384 (0x00000000003ec000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    2)

    Log Name:      Application

    Source:        ESENT

    Date:          24. 5. 2013 12:48:58

    Event ID:      508

    Task Category: Performance

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      xxxxxxxxxxxxxxxxxxx

    Description:

    svchost (2536) A request to write to the file "C:\Windows\system32\LogFiles\Sum\Svc.log" at offset 4112384 (0x00000000003ec000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (41 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.

    3)

    Log Name:      Application

    Source:        ESENT

    Date:          24. 5. 2013 12:55:42

    Event ID:      510

    Task Category: Performance

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      xxxxxxxxxxxxxxxxxx

    Description:

    svchost (2536) A request to write to the file "C:\Windows\system32\LogFiles\Sum\Svc.log" at offset 4141056 (0x00000000003f3000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (24 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 403 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    4)

    Log Name:      Application

    Source:        ESENT

    Date:          24. 5. 2013 13:15:15

    Event ID:      531

    Task Category: Database Page Cache

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      xxxxxxxxxxxxxxxxxxxx

    Description:

    lsass (640) The database engine attempted a clean write operation on page 8911 of database C:\Windows\NTDS\ntds.dit. This action was performed in an attempt to correct a previous problem reading from the page.

    This is realy hardware problem ? Server is tested with WS2012 (without DC) and working without any problém (all firmwares and drivers is up to date).

    Thanks,

    SnakeAG

    Saturday, May 25, 2013 1:06 PM

All replies

  • Hi,

    I cannot find information about the file C:\Windows\system32\LogFiles\Sum\Svc.log. As it is a log file, try to rename it to svc.old and see if the errors related to the file still exists after reboot.

    If the last error still exists, you can have a try with steps provided in this article to :

    How to complete a semantic database analysis for the Active Directory database by using Ntdsutil.exe

    http://support.microsoft.com/kb/315136/en-us

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

    Monday, May 27, 2013 12:06 PM
    Moderator
  • Hi,

    I try your fir step - rename log file svc.log and ESENT warning with this: svchost (2536) A request to write to the file "C:\Windows\system32\LogFiles\Sum\Svc.log" now not found in application log.

    But this warrnings is found:

    1)

    Log Name:      Directory Service
    Source:        NTDS ISAM
    Date:          27. 5. 2013 16:36:34
    Event ID:      507
    Task Category: Performance
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxxxxxxx
    Description:
    NTDS (700) NTDSA: A request to read from the file "C:\Windows\NTDS\ntds.dit" at offset 52797440 (0x000000000325a000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (32 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.

    2)

    Log Name:      Directory Service
    Source:        NTDS ISAM
    Date:          27. 5. 2013 16:36:34
    Event ID:      509
    Task Category: Performance
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxxxxxxxx
    Description:
    NTDS (700) NTDSA: A request to read from the file "C:\Windows\NTDS\ntds.dit" at offset 69984256 (0x00000000042be000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (23 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 0 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    3)

    Log Name:      Directory Service
    Source:        NTDS ISAM
    Date:          27. 5. 2013 16:36:34
    Event ID:      508
    Task Category: Performance
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxxxxxxxxxxx
    Description:
    NTDS (700) NTDSA: A request to write to the file "C:\Windows\NTDS\edb.log" at offset 8294400 (0x00000000007e9000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (32 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.

    4)

    Log Name:      Application
    Source:        ESENT
    Date:          27. 5. 2013 16:50:02
    Event ID:      531
    Task Category: Database Page Cache
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxxxxxxxxxxxxxx
    Description:
    lsass (700) The database engine attempted a clean write operation on page 8542 of database C:\Windows\NTDS\ntds.dit. This action was performed in an attempt to correct a previous problem reading from the page.

    I try now sematic database analysis and send result about few minutes.


    • Edited by SnakeAG Tuesday, May 28, 2013 4:30 AM
    Monday, May 27, 2013 2:59 PM
  • Hi,

    semantic database  analysis results:

    C:\sysadmin>ntdsutil
    ntdsutil: activate instance ntds
    Active instance set to "ntds".
    ntdsutil: semantic database analysis
    semantic checker: go
    Fixup mode is turned off
    ......Done.

    Writing summary into log file dsdit.dmp.1
    SDs scanned:           1565
    Records scanned:      49010
    Processing records..Done. Elapsed time 8 seconds.

    Monday, May 27, 2013 3:19 PM
  • Hi,

    aftter restart and about 30 minutes, all warnings back includes this:

    Log Name:      Application
    Source:        ESENT
    Date:          28. 5. 2013 6:24:33
    Event ID:      508
    Task Category: Performance
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxx
    Description:
    svchost (2624) A request to write to the file "C:\Windows\system32\LogFiles\Sum\Svc.log" at offset 1433600 (0x000000000015e000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (15 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.


    • Edited by SnakeAG Tuesday, May 28, 2013 4:29 AM
    Tuesday, May 28, 2013 4:29 AM
  • Any news?

    I am experiencing the same problem here, many esent 507/531 warnings on my 2012 vDC...

    F

    Tuesday, July 9, 2013 11:48 AM