Errors 26000 - 26999

Error

Severity

Event logged

Description (message text)

26010

10

Yes

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

Yes

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

Yes

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

Yes

The certificate [Cert Hash(sha1) "%hs"] was successfully loaded for encryption.

26014

16

Yes

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

Yes

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

Yes

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

Yes

A self-generated certificate was successfully loaded for encryption.

26022

10

Yes

Server is listening on [ %hs <%hs> %d].

26023

16

Yes

Server TCP provider failed to listen on [ %hs <%hs> %d]. Tcp port is already in use.

26024

16

Yes

Server failed to listen on %hs <%hs> %d. Error: %#x. To proceed, notify your system administrator.

26025

10

Yes

HTTP authentication succeeded for user '%.*ls'.%.*ls

26026

14

Yes

HTTP authentication failed.%.*ls

26027

10

Yes

Virtual Interface Architecture protocol is not supported for this particular edition of SQL Server.

26028

10

Yes

Server named pipe provider is ready to accept connection on [ %hs ].

26029

16

Yes

Server named pipe provider failed to listen on [ %hs ]. Error: %#x

26030

10

Yes

Server shared memory provider is ready for clients to connect to [ %hs ].

26031

16

Yes

Server shared memory provider failed to initialize. Error: %#x

26032

10

Yes

Server VIA provider is ready for clients to connect to [ %hs:%d ].

26033

16

Yes

Server VIA provider failed to initialize. Error: %#x

26034

10

Yes

The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination.

26035

16

Yes

The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x.

26036

10

Yes

Server named pipe connections are restricted to local access only. This is an informational message only. No user action is required.

26037

10

Yes

The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: %#x, state: %d. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

26038

10

Yes

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

Yes

The SQL Server Network Interface library was unable to load SPN related library. Error: %#x.

26040

17

Yes

Server TCP provider has stopped listening on port [ %d ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.

26041

10

Yes

Server TCP provider has successfully reestablished listening on port [ %d ].

26042

17

Yes

Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.

26043

10

Yes

Server HTTP provider has successfully reestablished listening.

26044

17

Yes

Server named pipe provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.

26045

10

Yes

Server named pipe provider has successfully reestablished listening on [ %hs ].

26046

17

Yes

Server shared memory provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.

26047

10

Yes

Server shared memory provider has successfully reestablished listening.

26048

10

Yes

Server local connection provider is ready to accept connection on [ %hs ].

26049

16

Yes

Server local connection provider failed to listen on [ %hs ]. Error: %#x

26050

17

Yes

Server local connection provider has stopped listening on [ %hs ] due to a failure. Error: %#x, state: %d. The server will automatically attempt to re-establish listening.

26051

10

Yes

Server local connection provider has successfully re-established listening on [ %hs ].

26052

10

Yes

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

Yes

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

Yes

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.

26055

16

Yes

The SQL Server failed to initialize VIA support library [%hs]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: %#x.

26056

10

Yes

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

Yes

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

Yes

A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections.

26059

10

Yes

The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.

26060

10

Yes

The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.

26061

10

Yes

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

Yes

Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support.

Community Additions

ADD
Show: