AlexSQLForums (10/18/2006)

---

This is what i see in the error log of sql server.

I still can't start sql server from cnfogi manager or bring online from cluster admin.

2006-10-17 13:10:19.44 Server Error: 26054, Severity: 16, State: 1.

2006-10-17 13:10:19.44 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.

2006-10-17 13:10:19.44 Server Error: 17182, Severity: 16, State: 1.

2006-10-17 13:10:19.44 Server TDSSNIClient initialization failed with error 0x103, status code 0xa.

2006-10-17 13:10:19.44 Server Error: 17182, Severity: 16, State: 1.

2006-10-17 13:10:19.44 Server TDSSNIClient initialization failed with error 0x103, status code 0x1.

2006-10-17 13:10:19.44 Server Error: 17826, Severity: 18, State: 3.

2006-10-17 13:10:19.44 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.

2006-10-17 13:10:19.44 Server Error: 17120, Severity: 16, State: 1.

2006-10-17 13:10:19.44 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.