Nov 03 2020 10:57 PM
Nov 03 2020 10:57 PM
Our file server (windows 2016 ) frequently becomes non responsive and needs to reboot to get it working again
When i checked event viewer i found in application log that
svchost((636)SoftwareUsageMetrics-Svc:An attempt to write the file C:\Windows\system32\LogFIles\Sum\Current.mdb at offset 921600(0x00000000000e1000) for 4096 bytes failed after 0.034 seconds with systemerror 1453: Insufficient quota to complete the requested service. The write operation will fail with error 1011
Nov 04 2020 09:23 AM
The file may be corrupt. You could stop the User Access Logging Service (UALSVC) delete all the files in;
start the service back up.
Nov 04 2020 03:09 PM
@Dave Patrick thanks for the suggestion.. I will try it and update how it goes
Nov 04 2020 04:52 PM
@Dave Patrick Unfortunately the issue came back with the event id 481 and 482 logged for SystemIdentity.mdb andcurrent.mdb
Nov 04 2020 05:05 PM
Maybe the User Access Logging service is not required?
Nov 09 2020 08:24 PM
@Dave Patrick As suggested disabled UAL service, Windows update service as well but still no luck.
Symptoms: The memory usage increases and the server becomes non responsive finally. The CPU usage spikes. Once rebooted the memory usage comes down but it increases again...
BUt when I checked if the memory usage for any process increases as well , I couldnot find any significant increase in the memory usage of any process but the total memory usage is increasing..
Its the VM in VMware..
Nov 10 2020 07:18 AM
but it increases again...
Seems you'll need to get to the bottom of the process responsible as first step. ProcMon may help you to that end.
Nov 11 2020 09:33 PM
Nov 12 2020 06:22 AM
I'd start a case here with product support.
Sep 14 2021 04:56 AM
Arrrgggg... this is our TSE VM... no drive problem...
We will do that in last time...
Sep 14 2021 05:23 AM
Our file server was also VM but we had extra Data drive as well.
Since it was mainly due to nonpaged pool memory growing and only option to release the memory was to restart the machine,
IF you have not checked yet please check the process consuming the memory
in our case it was ntfs.sys