svchost (4332,D,0) SoftwareUsageMetrics-Svc: An attempt to write to the file "C:\Windows\system32\LogFiles\Sum\SystemIdentity.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad):

Question

We have a VM that seems to randomly reboot and it is related to underlying either OS Corruption or Azure Disk corruption on the OS disk. Everything is fine, then once ever 1 to 4 hours we start getting errors about memory / disk corruption.

svchost (4332,D,0) SoftwareUsageMetrics-Svc: An attempt to write to the file "C:\Windows\system32\LogFiles\Sum\SystemIdentity.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) 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.

svchost (4332,D,51) SoftwareUsageMetrics-Svc: Database C:\Windows\system32\LogFiles\Sum\SystemIdentity.mdb was partially detached. Error -1011 encountered updating database headers.

Session "" failed to start with the following error: 0xC00000A1

The Microsoft Monitoring Agent service terminated with the following service-specific error:

Not enough memory resources are available to process this command.

We have upgraded the box with 40GB more of memory.
We have run sfc and chkdsk
We have resized the VM

We have redeployed the VM

Any ideas?

Answer

@Aaron Elder Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

This issue needs deeper investigation. resolution I would recommend you to contact support, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email to AzCommunity[at]Microsoft[dot]com referencing this thread as well as your subscription ID. Please mention "ATTN subm" in the subject field. Thank you for your cooperation on this matter and look forward to your reply.

Additional information: Based on the error messages you provided, it's possible that the issue is related to disk corruption on the OS disk. Specifically, the error message "An attempt to write to the file 'C:\Windows\system32\LogFiles\Sum\SystemIdentity.jfm' at offset 0...failed with system error 1453" suggests that there may be an issue with the file system on the OS disk.

To troubleshoot this issue further, I would recommend the following steps:

Check the health of the OS disk using Azure Disk Health. This service can help identify any issues with the disk, such as disk corruption or other errors.
Check the system event logs on the VM for any additional error messages that may provide more information about the cause of the reboots and disk corruption.
Consider creating a new VM and attaching the existing OS disk to the new VM to see if the issue persists. This can help determine if the issue is related to the VM itself or the OS disk.
If the issue persists, consider restoring the OS disk from a previous backup to see if that resolves the issue.
Explore Virtual Network Configuration & Performance Monitoring(Use performance monitoring tools to track the behavior of the VM over time and identify any patterns leading up to reboots)

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Share via

svchost (4332,D,0) SoftwareUsageMetrics-Svc: An attempt to write to the file "C:\Windows\system32\LogFiles\Sum\SystemIdentity.jfm" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad):

1 answer

Your answer