Esent Errors before critical shutdown of Server

Question

For last few months I have a server that stops responding. Right before the issue I see Esent errors in the logs.

System setup

Windows 2022 (fully updated)

SQL 2022 (fully updated)

128gigs ram

Event ID 482 is the majority of the errors here:

Log Name: Application Source: ESENT Date: 2/26/2024 11:09:01 PM Event ID: 482 Task Category: General Level: Error Keywords: Classic User: N/A Computer: Soyuz.2000domain.hscast.com Description: taskhostw (4720,D,0) WebCacheLocal: An attempt to write to the file "C:\Users\administrator.2000DOMAIN\AppData\Local\Microsoft\Windows\WebCache\V01.log" at offset 57344 (0x000000000000e000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad): "Insufficient quota to complete the requested service. ". The write operation will fail with error -1011 (0xfffffc0d). If this error persists then the file may be damaged and may need to be restored from a previous backup. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 482 0 2 1 0 0x80000000000000 111162 Application Soyuz.2000domain.hscast.com taskhostw 4720,D,0 WebCacheLocal: C:\Users\administrator.2000DOMAIN\AppData\Local\Microsoft\Windows\WebCache\V01.log 57344 (0x000000000000e000) 4096 (0x00001000) -1011 (0xfffffc0d) 1453 (0x000005ad) Insufficient quota to complete the requested service. 0.000

But I see these as well

Log Name: Application Source: ESENT Date: 2/26/2024 11:09:01 PM Event ID: 416 Task Category: Logging/Recovery Level: Error Keywords: Classic User: N/A Computer: Soyuz.2000domain.hscast.com Description: taskhostw (4720,D,10) WebCacheLocal: Unable to write to section 2 while flushing logfile C:\Users\administrator.2000DOMAIN\AppData\Local\Microsoft\Windows\WebCache\V01.log. Error -1011 (0xfffffc0d). Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 416 0 2 3 0 0x80000000000000 111163 Application Soyuz.2000domain.hscast.com taskhostw 4720,D,10 WebCacheLocal: C:\Users\administrator.2000DOMAIN\AppData\Local\Microsoft\Windows\WebCache\V01.log -1011 (0xfffffc0d)

Log Name: Application Source: ESENT Date: 2/26/2024 11:09:01 PM Event ID: 492 Task Category: Logging/Recovery Level: Error Keywords: Classic User: N/A Computer: Soyuz.2000domain.hscast.com Description: taskhostw (4720,D,10) WebCacheLocal: The logfile sequence in "C:\Users\administrator.2000DOMAIN\AppData\Local\Microsoft\Windows\WebCache" has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 492 0 2 3 0 0x80000000000000 111164 Application Soyuz.2000domain.hscast.com taskhostw 4720,D,10 WebCacheLocal: C:\Users\administrator.2000DOMAIN\AppData\Local\Microsoft\Windows\WebCache\

Log Name: Application Source: ESENT Date: 2/26/2024 11:13:33 PM Event ID: 104 Task Category: General Level: Error Keywords: Classic User: N/A Computer: Soyuz.2000domain.hscast.com Description: taskhostw (4720,T,97) WebCacheLocal: The database engine stopped the instance (0) with error (-1011). Internal Timing Sequence: [1] 0.000007 +J(0) [2] 0.000030 +J(0) [3] 0.000055 +J(0) +M(C:0K, Fs:0, WS:-36K # 0K, PF:-116K # 0K, P:-116K) [4] 0.000011 +J(0) [5] 0.002453 -0.002117 (3) WT +J(0) +M(C:0K, Fs:4, WS:16K # 0K, PF:4K # 0K, P:4K) [6] 0.000742 +J(0) +M(C:0K, Fs:0, WS:-1016K # 0K, PF:-1368K # 0K, P:-1368K) [7] 0.000006 +J(0) [8] 0.000707 +J(0) +M(C:0K, Fs:1, WS:-56K # 0K, PF:-60K # 0K, P:-60K) [9] - [10] 0.000015 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:0K # 0K, P:0K) [11] - [12] 0.000026 +J(0) +M(C:0K, Fs:0, WS:-4K # 0K, PF:-4K # 0K, P:-4K) [13] 0.000219 +J(0) [14] 0.000020 +J(0) +M(C:0K, Fs:0, WS:-12K # 0K, PF:-12K # 0K, P:-12K) [15] 0.000003 +J(0). Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 104 0 2 1 0 0x80000000000000 111168 Application Soyuz.2000domain.hscast.com taskhostw 4720,T,97 WebCacheLocal: 0 -1011 [1] 0.000007 +J(0) [2] 0.000030 +J(0) [3] 0.000055 +J(0) +M(C:0K, Fs:0, WS:-36K # 0K, PF:-116K # 0K, P:-116K) [4] 0.000011 +J(0) [5] 0.002453 -0.002117 (3) WT +J(0) +M(C:0K, Fs:4, WS:16K # 0K, PF:4K # 0K, P:4K) [6] 0.000742 +J(0) +M(C:0K, Fs:0, WS:-1016K # 0K, PF:-1368K # 0K, P:-1368K) [7] 0.000006 +J(0) [8] 0.000707 +J(0) +M(C:0K, Fs:1, WS:-56K # 0K, PF:-60K # 0K, P:-60K) [9] - [10] 0.000015 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:0K # 0K, P:0K) [11] - [12] 0.000026 +J(0) +M(C:0K, Fs:0, WS:-4K # 0K, PF:-4K # 0K, P:-4K) [13] 0.000219 +J(0) [14] 0.000020 +J(0) +M(C:0K, Fs:0, WS:-12K # 0K, PF:-12K # 0K, P:-12K) [15] 0.000003 +J(0).

Log Name: Application

Source: ESENT Date: 2/26/2024 11:14:24 PM Event ID: 439 Task Category: Logging/Recovery Level: Error Keywords: Classic User: N/A Computer: Soyuz.2000domain.hscast.com Description: qmgr.dll (15284,T,97) QmgrDatabaseInstance: Unable to write a shadowed header for file C:\ProgramData\Microsoft\Network\Downloader\qmgr.db. Error -1011. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 439 0 2 3 0 0x80000000000000 111172 Application Soyuz.2000domain.hscast.com qmgr.dll 15284,T,97 QmgrDatabaseInstance: C:\ProgramData\Microsoft\Network\Downloader\qmgr.db -1011

I've been trying to figure this out for what seems like for ever. This happens ever week or so right now and I have to restart the server to get it back up and running. I've updated all drivers, patched all versions of software. Still get these errors.

Anyone have any idea?

Shane

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

Based on the error messages you provided, it seems that the issue is related to the WebCacheLocal and QmgrDatabaseInstance. These errors indicate that the server is having trouble writing to the log files, which can cause the server to become unresponsive and require a restart.

To resolve this issue, you can try the following steps:

1. Check the disk space on the server and ensure that there is enough free space available.
2. Run a disk check to ensure that there are no disk errors.
3. Disable any antivirus software temporarily to see if it is causing the issue.
4. Try resetting the Windows Update components by running the following commands in an elevated command prompt:

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

5. If the issue persists, you may need to contact Microsoft Support for further assistance.

I hope this helps!

Best Regards,

Zack Lu

Answer 2

What is best way to contact support then? I do have MS MPSA licensing for all products.

Thank you,

Shane