Quantcast
Channel: WSUS forum
Viewing all articles
Browse latest Browse all 12874

Windows Server 2012R2 DC with MSSQL$Microsoft##WID errors

$
0
0

My DC is intermittently showing errors:

Error: 701, Severity: 17, State: 107. (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.
SQL Server is terminating a system or background task HADR Task due to errors in starting up the task (setup state 1).
AppDomain 3181 (<appdomain>) is marked for unload due to memory pressure.
AppDomain 3181 (<appdomain>) unloaded.
Error: 9602, Severity: 16, State: 1.
Failed to start a system task with error code 28709, state 19.
Error: 17300, Severity: 16, State: 1.
SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
Error: 17312, Severity: 16, State: 1.
SQL Server is terminating a system or background task HADR Task due to errors in starting up the task (setup state 1).
Error: 18054, Severity: 16, State: 1.

These errors have a Microsoft HotFix - see https://support.microsoft.com/en-us/kb/2769594

BUT- the hotfix for SQL server and my DC does not have a stand alone copy of SQL - the SQL server that the DC uses is bundled into the OS.  So my question is how to I apply this fix to the DC when there is no real instance of SQL on the DC?

Is Microsoft aware that this same memory allocation error can occur on a Windows Server DC?   What is the recommended method for repair?


Viewing all articles
Browse latest Browse all 12874

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>