Error: Could not find any IP address that this SQL Server instance depends upon.

Problem:

We had a requirement to change the SQL Server Fail over cluster group Virtual server name. We did that change through the cluster administrator. That SQL Server was 2008 Enterprise running on  Windows 2008 Enterprise cluster. The change was successfully made from one node and the SQL server came online after that. But when we did fail over testing, we noticed that the SQL Server service is not coming online on the other node. The SQL Server error-log gave below errors while trying to start-up.

  • 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: 0x103.
  • Error: 17182, Severity: 16, State: 1.
  • TDSSNIClient initialization failed with error 0x103, status code 0xa. Reason: Unable to initialize the TCP/IP listener. No more data is available.
  • Error: 17182, Severity: 16, State: 1.
  • TDSSNIClient initialization failed with error 0x103, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. No more data is available.
  • 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.
  • Error: 17120, Severity: 16, State: 1.
  • SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Resolution:

Check the Registry entry shown below on the node in which the SQL Server cluster was not coming online. If the key is not updated with the new Virtual network name, update the same and try to bring SQL Server resource online. Yeah !. It comes online Successfully.

Registry Key Screenshot
Registry Key Screenshot

Still Facing Issue?

Check the SQL Server Configuration manager on the failing node and see if the TCP/IP is enabled and VIA is disabled. At least this should fix that issue. If you still have problem, Please send me your complete error-log. I will try my best to find the solution. Thank You.


Author: Sherbaz

Being a gadget enthusiast, He always felt good to try new programming languages and techniques. But never goes in-depth anywhere. www.SplitExpense.in was found when he tried php, html, javascript and mysql. Being an electronics engineer, he is also interested to build small gadgets and tools in embedded and digital electronics. As a profession, he handles microsoft sql server database and calls himself a database administrator

Leave a Reply