17066
SQL Server Assertion: File: <"filename">, line=
Failed Assertion = ''. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted
17067
SQL Server Assertion: File: <"filename">, line= Failed Assertion = ''. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted
17311
SQL Server is terminating because of fatal exception . This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
17884
New queries assigned to process on Node have not been picked up by a worker thread in the last seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: %. System Idle: %
The cause for these errors is specific to the error. In many cases, assertions and exceptions are caused by a problem with the SQL Server code. Scheduler yielding problems (or hangs) may be a problem with the SQL Server code but can also be a problem with an external module or a thread delayed when calling a Windows API call.
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)
Server Exception or Hang detected on server
The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect if any of the events listed in the Symptoms section are found in the Windows Application Event Log. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2.
If you run the BPA tool and encounter an Error with the title of Engine - Server Exception or Hang detected on server, then you have one of the EventID values as listed in the Symptoms section of this article in your Windows Application Event Log. BPA does not filter on any date/time so it will report the number of occurrences of these events in your current Event Log.
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)
Server Exception or Hang detected on server
The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect if any of the events listed in the Symptoms section are found in the Windows Application Event Log.
If you run the BPA tool and encounter an Error with the title of Engine - Server Exception or Hang detected on server, then you have one of the EventID values as listed in the Symptoms section of this article in your Windows Application Event Log. BPA does not filter on any date/time so it will report the number of occurrences of these events in your current Event Log.
SQL Server 2012
