Error: 26054, Severity: 16, State: 1

Imagine if your SQL Server resource is not coming up and you are getting something like this in the errorlog:

2007-11-29 00:10:03.00 Server Error: 26054, Severity: 16, State: 1.
2007-11-29 00:10:03.00 Server 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.
2007-11-29 00:10:03.00 Server Error: 17182, Severity: 16, State: 1.
2007-11-29 00:10:03.00 Server TDSSNIClient initialization failed with error 0x103, status code 0xa.
2007-11-29 00:10:03.00 Server Error: 17182, Severity: 16, State: 1.
2007-11-29 00:10:03.00 Server TDSSNIClient initialization failed with error 0x103, status code 0x1.
2007-11-29 00:10:03.00 Server Error: 17826, Severity: 18, State: 3.
2007-11-29 00:10:03.00 Server 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.
2007-11-29 00:10:03.00 Server Error: 17120, Severity: 16, State: 1.
2007-11-29 00:10:03.00 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

all these errors are very different .But we need to see the first error ...
lets check the following registry key for all the instances we have on the cluster :
HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.1\Cluster(MSSQLSERVER)

Check the virtual server name ......it has to be different for all the instances ........right ..
In my case we had 2 instances and both had same virtual server names ( dont ask why ) not sure what the other person had done in the past .

Change the name of the virtual server on all nodes as needed and run the checkpoint on registry or