Hi,
I've just added a second node to a w2k3 / SQL2005 cluster. I got through the install of SQL onto the new node but when I tried to fail over SQL would not start. Now it won't run on either node. I get the following error messages in the SQL log. My research indicates this is related to named pipes (possibly having an extra space in the config but I could not see one. I have alsotried to start the node with this disabled and enabled and neither work.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x2, status code 0x35.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x2, 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.
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.
This is my test setup running on VMWare Server but I need to do this twice on a mission critical production server soon, replacing the hardware of both nodes, so
View Complete Post