SQL Server System Errors: 26000 - 26999
List of error messages between 26000 and 26999 in SQL Server 2017.
These error messages are all available by querying the sys.messages catalog view on the master database.
| message_id | severity | is_event_logged | text |
|---|---|---|---|
| 26010 | 10 | 1 | The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: %#x. Check certificates to make sure they are valid. |
| 26011 | 16 | 1 | The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system. |
| 26012 | 16 | 1 | The server has attempted to initialize SSL encryption when it has already been initialized. This indicates a problem with SQL Server. Contact Technical Support. |
| 26013 | 10 | 1 | The certificate [Cert Hash(sha1) "%hs"] was successfully loaded for encryption. |
| 26014 | 16 | 1 | Unable to load user-specified certificate [Cert Hash(sha1) "%hs"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. |
| 26015 | 16 | 1 | Unable to load user-specified certificate. Because connection encryption is required, the server will not be able to accept any connections. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. |
| 26017 | 10 | 1 | Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. |
| 26018 | 10 | 1 | A self-generated certificate was successfully loaded for encryption. |
| 26022 | 10 | 1 | Server is listening on [ %s <%s> %d]. |
| 26023 | 16 | 1 | Server TCP provider failed to listen on [ %s <%s> %d]. Tcp port is already in use. |
| 26024 | 16 | 1 | Server failed to listen on %s <%s> %d. Error: %#x. To proceed, notify your system administrator. |
| 26025 | 10 | 1 | HTTP authentication succeeded for user '%.*ls'.%.*ls |
| 26026 | 14 | 1 | HTTP authentication failed.%.*ls |
| 26028 | 10 | 1 | Server named pipe provider is ready to accept connection on [ %s ]. |
| 26029 | 16 | 1 | Server named pipe provider failed to listen on [ %s ]. Error: %#x |
| 26034 | 10 | 1 | The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination. |
| 26035 | 16 | 1 | The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x. |
| 26037 | 10 | 1 | The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: %#x, state: %d. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. |
| 26038 | 10 | 1 | The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Administrator should deregister this SPN manually to avoid client authentication errors. |
| 26039 | 16 | 1 | The SQL Server Network Interface library was unable to load SPN related library. Error: %#x. |
| 26040 | 17 | 1 | Server TCP provider has stopped listening on port [ %d ] due to an AcceptEx failure. Socket error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
| 26041 | 10 | 1 | Server TCP provider has successfully reestablished listening on port [ %d ]. |
| 26042 | 17 | 1 | Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
| 26043 | 10 | 1 | Server HTTP provider has successfully reestablished listening. |
| 26044 | 17 | 1 | Server named pipe provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening. |
| 26045 | 10 | 1 | Server named pipe provider has successfully reestablished listening on [ %s ]. |
| 26048 | 10 | 1 | Server local connection provider is ready to accept connection on [ %s ]. |
| 26049 | 16 | 1 | Server local connection provider failed to listen on [ %s ]. Error: %#x |
| 26050 | 17 | 1 | Server local connection provider has stopped listening on [ %s ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening. |
| 26051 | 10 | 1 | Server local connection provider has successfully re-established listening on [ %s ]. |
| 26052 | 10 | 1 | SQL Server Network Interfaces initialized listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. This is an informational message only. No user action is required. |
| 26053 | 16 | 1 | SQL Server Network Interfaces failed to initialize listeners on node %ld of a multi-node (NUMA) server configuration with node affinity mask 0x%0*I64x. There may be insufficient memory. Free up additional memory, then turn the node off and on again. If the failure persists repeat this multiple times or restart the SQL Server. |
| 26054 | 16 | 1 | Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: %#x. |
| 26056 | 10 | 1 | Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover the correct DAC port through the SQL Server Browser Service. Error: %#x. |
| 26057 | 16 | 1 | Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a problem with the network configuration of the computer. Error: %#x. |
| 26058 | 16 | 1 | A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections. |
| 26059 | 10 | 1 | The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. |
| 26060 | 10 | 1 | The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service. |
| 26061 | 10 | 1 | Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This might indicate a problem with the network configuration of the computer. Error: %#x. |
| 26062 | 16 | 1 | Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support. |
| 26064 | 10 | 1 | SQL Server could not listen on IP address [%s] because the cluster resource '%s' is not online (state = %d). This is an informational message and may indicate that resource '%s' has OR type of dependency on several IP addresses some of which are currently offline or in a failed state. Further action is only required if it is generally possible to bind the IP address of the cluster resource '%s' to a network segment on the current hosting node. |
| 26065 | 16 | 1 | Extended Protection for the SQL Server Database Engine is enabled, but the operating system does not support Extended Protection. Connection attempts using Windows Authentication might fail. Check for an operating system service pack to allow for Extended Protection through Service Binding and Channel Binding, or disable Extended Protection for the Database Engine. |
| 26066 | 16 | 1 | An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Integrated Authentication might fail. Error: %d. |
| 26067 | 10 | 1 | The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Windows return code: %#x, state: %d. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. |
| 26068 | 10 | 1 | The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ %ls ] for the SQL Server service. Error: %#x, state: %d. Administrator should deregister this SPN manually to avoid client authentication errors. |
| 26069 | 10 | 1 | Started listening on virtual network name '%ls'. No user action is required. |
| 26070 | 10 | 1 | Stopped listening on virtual network name '%ls'. No user action is required. |
| 26071 | 16 | 1 | Failed to load the Cluster Resource Libraries: clusapi.dll and resutils.dll. SQL Server will be unable to accept TCP connections on clustered listeners. |
| 26072 | 10 | 1 | Found multiple dependent virtual network names for the Windows Failover Cluster Resource '%ls'. SQL Server will only listen on the first virtual network name resource: '%ls'. This may indicate that there is an incorrect configuration of the Windows Failover Cluster Resources for SQL Server. |
| 26073 | 16 | 1 | Failed to clean up event associated with TCP connection, this is most likely because the server was under heavy load. Operating system return code: %#x |
| 26075 | 16 | 1 | Failed to start a listener for virtual network name '%ls'. Error: %d. |
| 26076 | 10 | 1 | SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. |
| 26077 | 20 | 0 | An asynchronous read has timed out |
| 26078 | 20 | 0 | Client disconnected during login |
| 26079 | 17 | 1 | Server TCP provider has stopped listening on port [ %d ] due to a CreateSocket failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening. |