SQL Server fails to start if NIC has multiple IP address

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptom



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:


322756How to back up and restore the registry in Windows XP and Windows Vista


 



 




SQL Server service will not start after installing a cumulative update if the server has a NIC that is configured with multiple IP addresses.  You receive the following error in the SQL Server log:


 


Error: 17182, Severity: 16, State: 1.                                                                                                                                


TDSSNIClient initialization failed with error 0x34, status code 0x1e.                                                                                                


Error: 17182, Severity: 16, State: 1.                                                                                                                                 


TDSSNIClient initialization failed with error 0x34, status code 0x1.                                                                                                 


Error: 17826, Severity: 18, State: 3.                                                                                                                                 


Could not start the network library because of an internal error in the network library.


To determine the cause, review the errors immediately preceding this one in the error log.       


 


You will also see an indication in the Event Viewer log and the Setup logs that SQL Server could not start due to multiple IP addresses in conflict.

Cause



Cumulative update has registered all the IP address onto the SQL Server instance in the registry.

Resolution



Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.




Delete the registry keys that point to the extra IP addresses:


 


HKLM\Software\Microsoft\Microsoft SQL Server\ --> filter through the instance --> MSSQLServer\SuperSocketNetLib\TCP


 

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Eigenschappen

Artikel-id: 968759 - Laatst bijgewerkt: 9 mrt. 2009 - Revisie: 1

Feedback