Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all articles
Browse latest Browse all 7740

Cluster will not come online: Could not find any IP address that this SQL Server instance depends upon.

$
0
0

Hi,

I set up a new cluster the other day, after doing two others successfully. This particular cluster on windows 2012 R2 is a SQL 2014 installation that has been patched to SP2 CU10. The cluster also hosts 9 other instances and a file share we use for backups for all the instances. 

It will not come online and has the error - "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."

I verified that dependencies were set up like the other clustered instance on this cluster, took the IP & Network name offline and then tried to ping it - no response. I put the IP/NetName online and was able to ping it. I changed the IP to a new IP provided by my network team and also known to be available. I have read through several similar threads here that mention validating registry entries and looked at those entries. I've tried bringing it up on both nodes.  The same error has occurred after all these steps.

System Log:

The SQL Server (INST10) service terminated with the following service-specific error: 
Access is denied.

SQL Log:

2018-07-05 11:41:11.59 spid16s     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: 0x5.
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17826, Severity: 18, State: 3.
2018-07-05 11:41:11.59 spid16s     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.
2018-07-05 11:41:11.59 spid16s     Error: 17120, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Thanks for your review and suggestions.

Sam


Viewing all articles
Browse latest Browse all 7740

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>