SQL Server Errors or Failures from Error: 26015 to Error: 26044

SQLServerF1

 

Error: 26015, Severity: 16, 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 Boo
Error: 26017, Severity: 10, Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
Error: 26018, Severity: 10, A self-generated certificate was successfully loaded for encryption.

Error: 26022, Severity: 10, Server is listening on [ %hs <%hs> %d].
Error: 26023, Severity: 16, Server TCP provider failed to listen on [ %hs <%hs> %d]. Tcp port is already in use.
Error: 26024, Severity: 16, Server failed to listen on %hs <%hs> %d. Error: %#x. To proceed, notify your system administrator.
Error: 26025, Severity: 10, HTTP authentication succeeded for user ‘%.*ls’.%.*ls
Error: 26026, Severity: 14, HTTP authentication failed.%.*ls

Error: 26028, Severity: 10, Server named pipe provider is ready to accept connection on [ %hs ].
Error: 26029, Severity: 16, Server named pipe provider failed to listen on [ %hs ]. Error: %#x
Error: 26034, Severity: 10, The SQL Server Network Interface library was unable to execute polite termination due to outstanding connections. It will proceed with immediate termination.
Error: 26035, Severity: 16, The SQL Server Network Interface library was unable to close socket handle due to a closesocket failure under memory pressure. Winsock error code: %#x.
Error: 26037, Severity: 10, 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.
Error: 26038, Severity: 10, 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.
Error: 26039, Severity: 16, The SQL Server Network Interface library was unable to load SPN related library. Error: %#x.
Error: 26040, Severity: 17, 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.
Error: 26041, Severity: 10, Server TCP provider has successfully reestablished listening on port [ %d ].
Error: 26042, Severity: 17, Server HTTP provider has stopped listening due to a failure. Error: %#x, state: %d. The server will automatically attempt to reestablish listening.
Error: 26043, Severity: 10, Server HTTP provider has successfully reestablished listening.
Error: 26044, Severity: 17, 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.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *