I have a Windows 2008R2 box with SQL Server 2012 Express. The problem is that randomly (sometimes twice a day, sometimes once a month) the SQL Server dies leaving those messages in error log:
Error: 49910, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
When I try to start the service again, it says:
Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 33086, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
After reboot of the machine it starts working again. How can I fix this problem?
Best Answer
ERROR 17300 is caused by SQL Server not being able to execute one of the system tasks. It points to insufficient memory: http://technet.microsoft.com/en-us/library/cc280564.aspx
As that resource explains, it could also be caused by a setting, but insufficient memory is more likely the cause.
ERROR 17312 is directly related.
This could be caused by another process eating up all the available memory. For example Windows explorer file copy operations are known to reserve memory and not release it.
Make sure you have adequate memory installed on the system and monitor how much of it is reserved.