January 8, 2019 at 11:55 am
ERROR: svchost (1052) An attempt to read from the file "C:\Windows\system32\LogFiles\Sum\Current.mdb" at offset 135168 (0x0000000000021000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad): "Insufficient quota to complete the requested service. ". The read 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.
Hi All,
Sql was locked up and reboot helped to come out of it. There was only a regular job running at that point as per sql error log. Now, the windows application log shows lot of errors similar to ABOVE right before the sql become unresponsive and after that as well. I can see them now as well. What might be the issue? is it mem pressure or something else.
I am checking few other things as well, but could be the reason? Please advise if you have faced similar situation or share thoughts.
January 8, 2019 at 2:42 pm
sizal0234 - Tuesday, January 8, 2019 11:55 AMERROR: svchost (1052) An attempt to read from the file "C:\Windows\system32\LogFiles\Sum\Current.mdb" at offset 135168 (0x0000000000021000) for 4096 (0x00001000) bytes failed after 0.000 seconds with system error 1453 (0x000005ad): "Insufficient quota to complete the requested service. ". The read 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.Hi All,
Sql was locked up and reboot helped to come out of it. There was only a regular job running at that point as per sql error log. Now, the windows application logs shows lot of errors similar to ABOVE right before the sql become unresponsive and after that as well. I can see them now as well. What might be the issue? is it mem pressure or something else.
I am checking few other things as well but would this could be the reason? Please advise if you have faced similar situation.
I saw a similar message with insufficient quota before on a VM that wasn't allocated enough memory but none of it is really a SQL Server issue.
I believe that the files in that directory (C:\Windows\system32\LogFiles\Sum) are used by User Access Logging service.You probably need to go through the Windows event logs to try to figure out the issue - especially with having some type of similar errors in the event logs. You could try restarting the UAL service as well.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply