Top 25 SQL Server Engine Errors Based on support case volumes Documented
Published Feb 27 2023 03:02 PM 13.6K Views
Microsoft

About 6 months ago we decided to look at what SQL Server engine error messages are most commonly generating support cases to Microsoft. The end goal was to update the documentation for those error messages to allow our customers to find answers for themselves before they have to call Microsoft for technical assistance.

The task, as we suspected from previous experience, was not easy because we had to mine cases for error numbers and a relatively small number of support cases get reported with error messages when they are opened. Still, we were able to find the trends even from the small percentages because were looking for the top 20 or so most common errors, based on case count, and we needed relative information - which error is reported more than another.

 

As a result, over the past 6 months or so we have been updating and creating SQL Server engine errors (MSSQLSERVER_XXXX) or for some of them validated the content was relevant. Many of these errors did not have any documentation at all and some were updated with more detailed instructions and insights. With over 14,000 error messages in SQL Server engine alone, the realistic approach is to focus on documenting the common ones.

 

Here is the list of errors that we created or updated to help with your troubleshooting efforts and, we hope, complete resolution:

 

Error ID Document
18456 MSSQLSERVER_18456 - SQL Server | Microsoft Learn
19407 MSSQLSERVER_19407 - SQL Server | Microsoft Learn
OS errors 665 and 1450  Operating System errors 665 and 1450 are reported for database files - SQL Server | Microsoft Learn
3417 MSSQLSERVER_3417 - SQL Server | Microsoft Learn
912 MSSQLSERVER_912 - SQL Server | Microsoft Learn
3013 MSSQLSERVER_3013 - SQL Server | Microsoft Learn
19421 MSSQLSERVER_19421 - SQL Server | Microsoft Learn
824 MSSQLSERVER_824 - SQL Server | Microsoft Learn
17182 MSSQLSERVER_17182 - SQL Server | Microsoft Learn
Timeout expired when connecting Timeout expired messages when connecting to SQL Server - SQL Server | Microsoft Learn
Network-related error A network-related or instance-specific error occurred - SQL Server | Microsoft Learn
19419 MSSQLSERVER_19419 - SQL Server | Microsoft Learn
10054 An existing connection was forcibly closed (OS error 10054) - SQL Server | Microsoft Learn
18210 with OS 995

MSSQLSERVER_18210 - SQL Server | Microsoft Learn

17053 MSSQLSERVER_17053 - SQL Server | Microsoft Learn
17120 MSSQLSERVER_17120 - SQL Server | Microsoft Learn
3624 MSSQLSERVER_3624 - SQL Server | Microsoft Learn
17826 MSSQLSERVER_17826 - SQL Server | Microsoft Learn
9001 MSSQLSERVER_9001 - SQL Server | Microsoft Learn
3313 MSSQLSERVER_3313 - SQL Server | Microsoft Learn
9002 Troubleshoot full transaction log error 9002 - SQL Server | Microsoft Learn
MSSQLSERVER_9002 - SQL Server | Microsoft Learn
823 MSSQLSERVER error 823 - SQL Server | Microsoft Learn
17066 MSSQLSERVER_17066 - SQL Server | Microsoft Learn
3314 MSSQLSERVER_3314 - SQL Server | Microsoft Learn
35267 MSSQLSERVER_35267 - SQL Server | Microsoft Learn

 

 

There are multiple contributors to this project, but special thanks go to Siresh Peesa for mining the data and discovering the trends, Ramu Konidena a Content Project Manager for driving the project and contribution to the content, Suresh Kandoth for providing guidance and ideas, and James Ferebee for contribution to the content.

 

You can help!

 

We are committed to creating documentation that helps us all. Please consider contributing to these efforts by doing the following:

JosephPilov_0-1677521201732.png

  • Report full error messages when creating support cases with Microsoft.
  • Comment blogs posts like this one!

 

Stay tuned to this channel for additional updates on our progress in this space!

 

 

Thank you

 

Co-Authors
Version history
Last update:
‎Mar 11 2023 05:49 PM
Updated by: