ESENT Event ID 508 warnings in Event Viewer on Server 2012 R2

%3CLINGO-SUB%20id%3D%22lingo-sub-1548852%22%20slang%3D%22en-US%22%3ERe%3A%20ESENT%20Event%20ID%20508%20warnings%20in%20Event%20Viewer%20on%20Server%202012%20R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1548852%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20of%20the%20files%20may%20be%20corrupt%20in%20which%20case%20you%20can%20delete%20them.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwindows-update-resources%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwindows-update-resources%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1547158%22%20slang%3D%22en-US%22%3EESENT%20Event%20ID%20508%20warnings%20in%20Event%20Viewer%20on%20Server%202012%20R2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1547158%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22contentStandard%20x-hidden-focus%22%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22contentStandard%22%3EI'm%20running%20a%20Win%202012%20R2%20on%20a%20VMware%20platform%2C%20I%20few%20days%20I%20noticed%20some%20instabilities%20and%20when%20I%20check%20the%20logs%20I%20saw%20the%20messages%20below%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E(%3C%2FSPAN%3E%3CSPAN%20class%3D%22x-hidden-focus%22%3Ewuaueng.dll%20(920)%20SUS20ClientDataStore%3A%20A%20request%20to%20write%20to%20the%20file%20%22C%3A%5CWindows%5CSoftwareDistribution%5CDataStore%5CLogs%5Cedb.log%22%20at%20offset%20405504%20(0x0000000000063000)%20for%204096%20(0x00001000)%20bytes%20succeeded%2C%20but%20took%20an%20abnormally%20long%20time%20(28%20seconds)%20to%20be%20serviced%20by%20the%20OS.%20This%20problem%20is%20likely%20due%20to%20faulty%20hardware.%20Please%20contact%20your%20hardware%20vendor%20for%20further%20assistance%20diagnosing%20the%20problem.%3C%2FSPAN%3E%3CSPAN%3E)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ewuaueng.dll%20(920)%20SUS20ClientDataStore%3A%20A%20request%20to%20write%20to%20the%20file%20%22C%3A%5CWindows%5CSoftwareDistribution%5CDataStore%5CLogs%5Cedb.log%22%20at%20offset%20692224%20(0x00000000000a9000)%20for%204096%20(0x00001000)%20bytes%20succeeded%2C%20but%20took%20an%20abnormally%20long%20time%20(33%20seconds)%20to%20be%20serviced%20by%20the%20OS.%20This%20problem%20is%20likely%20due%20to%20faulty%20hardware.%20Please%20contact%20your%20hardware%20vendor%20for%20further%20assistance%20diagnosing%20the%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Esvchost%20(728)%20A%20request%20to%20write%20to%20the%20file%20%22C%3A%5CWindows%5Csystem32%5CLogFiles%5CSum%5CSvc.log%22%20at%20offset%20524288%20(0x0000000000080000)%20for%204096%20(0x00001000)%20bytes%20succeeded%2C%20but%20took%20an%20abnormally%20long%20time%20(19%20seconds)%20to%20be%20serviced%20by%20the%20OS.%20This%20problem%20is%20likely%20due%20to%20faulty%20hardware.%20Please%20contact%20your%20hardware%20vendor%20for%20further%20assistance%20diagnosing%20the%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Esvchost%20(728)%20A%20request%20to%20write%20to%20the%20file%20%22C%3A%5CWindows%5Csystem32%5CLogFiles%5CSum%5CSvc.chk%22%20at%20offset%200%20(0x0000000000000000)%20for%204096%20(0x00001000)%20bytes%20succeeded%2C%20but%20took%20an%20abnormally%20long%20time%20(17%20seconds)%20to%20be%20serviced%20by%20the%20OS.%20This%20problem%20is%20likely%20due%20to%20faulty%20hardware.%20Please%20contact%20your%20hardware%20vendor%20for%20further%20assistance%20diagnosing%20the%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22x-hidden-focus%22%3Ewuaueng.dll%20(920)%20SUS20ClientDataStore%3A%20A%20request%20to%20write%20to%20the%20file%20%22C%3A%5CWindows%5CSoftwareDistribution%5CDataStore%5CLogs%5Cedb.chk%22%20at%20offset%204096%20(0x0000000000001000)%20for%204096%20(0x00001000)%20bytes%20succeeded%2C%20but%20took%20an%20abnormally%20long%20time%20(19%20seconds)%20to%20be%20serviced%20by%20the%20OS.%20This%20problem%20is%20likely%20due%20to%20faulty%20hardware.%20Please%20contact%20your%20hardware%20vendor%20for%20further%20assistance%20diagnosing%20the%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22x-hidden-focus%22%3Ewuaueng.dll%20(920)%20SUS20ClientDataStore%3A%20A%20request%20to%20write%20to%20the%20file%20%22C%3A%5CWindows%5CSoftwareDistribution%5CDataStore%5CLogs%5Cedb.log%22%20at%20offset%20344064%20(0x0000000000054000)%20for%204096%20(0x00001000)%20bytes%20succeeded%2C%20but%20took%20an%20abnormally%20long%20time%20(21%20seconds)%20to%20be%20serviced%20by%20the%20OS.%20This%20problem%20is%20likely%20due%20to%20faulty%20hardware.%20Please%20contact%20your%20hardware%20vendor%20for%20further%20assistance%20diagnosing%20the%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22contentStandard%22%3E%3CSPAN%3Eis%20there%20Anything%26nbsp%3BI%20can%20on%20the%20system%20to%20fix%20this%20%26nbsp%3B%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1547158%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hi,

 

I'm running a Win 2012 R2 on a VMware platform, I few days I noticed some instabilities and when I check the logs I saw the messages below:

 

(wuaueng.dll (920) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 405504 (0x0000000000063000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (28 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.)

 

wuaueng.dll (920) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 692224 (0x00000000000a9000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (33 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.

 

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

 

 

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

 

wuaueng.dll (920) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.chk" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (19 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.

 

wuaueng.dll (920) SUS20ClientDataStore: A request to write to the file "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" at offset 344064 (0x0000000000054000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (21 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.

 

is there Anything I can on the system to fix this  ?

1 Reply
Highlighted

Some of the files may be corrupt in which case you can delete them.  

 

https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-resources