SQL Server Errors or Failures from Error: 26045 to Error: 26068

SQLServerF1

Error: 26045, Severity: 10, Server named pipe provider has successfully reestablished listening on [ %hs ].

Error: 26048, Severity: 10, Server local connection provider is ready to accept connection on [ %hs ].
Error: 26049, Severity: 16, Server local connection provider failed to listen on [ %hs ]. Error: %#x
Error: 26050, Severity: 17, 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.

Error: 26051, Severity: 10, Server local connection provider has successfully re-established listening on [ %hs ].
Error: 26052, Severity: 10, 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.
Error: 26053, Severity: 16, 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 th

Error: 26054, Severity: 16, 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 SQ
Error: 26056, Severity: 10, 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.
Error: 26057, Severity: 16, 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.
Error: 26058, Severity: 16, A TCP provider is enabled, but there are no TCP listening ports configured. The server cannot accept TCP connections.
Error: 26059, Severity: 10, The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
Error: 26060, Severity: 10, The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ %ls ] for the SQL Server service.
Error: 26061, Severity: 10, 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.
Error: 26062, Severity: 16, Invalid parameter detected while initializing TCP listening port. Error: %#x, state: %d. Contact Technical Support.
Error: 26064, Severity: 10, 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
Error: 26065, Severity: 16, 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
Error: 26066, Severity: 16, An error occurred while configuring cluster virtual IP addresses for Extended Protection. Connection attempts using Windows Authentication might fail. Error: %d.
Error: 26067, Severity: 10, 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 Ke
Error: 26068, Severity: 10, 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.

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 *