We are having 2 node (active-passive) SQL server 2005 cluster with SP2. From last some days we are facing issue that SQL server cluster group not coming online on passive node(sql server services & agent remain in stop state even after several retries.). All other resources other then SQL server are coming online sucessfully.
We are getting below error messages : -
1) SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: xx.xx.xx.xx]
2) The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15.
3) [sqsrvres] checkODBCConnectError: sqlstate = 08S01; native error = e9; message = [Microsoft][SQL Native Client]Named Pipes Provider: No process is on the other end of the pipe.
4) [sqsrvres] ODBC sqldriverconnect failed
5) [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 0; message = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
6) [sqsrvres] checkODBCConnectError: sqlstate = 08S01; native error = e9; message = [Microsoft][SQL Native Client]Communication link failure
7) EXCEPTION: Error 6144854: T8240 C6144854 The following SQL Server error or errors occurred: 18452,"28000",[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'xxxx'. The user is not associated with a trusted SQL Server connection.
Findings & Actions taken:-
1) Registry entries are already updated 2) Browser services are activated & started 3) upgarde SP3 on both nodes but issue not resolved 4) Window sevrer hardning done
Your error 2 (0x2098) is that the SQL Server doesn't have sufficient rights to register the named pipe. The errors 3 and 6 are results of error 2.
I believe you need to assign the 'read service' and 'write service' rights to the domain account under which SQL Server is running in Active Directory. For more information, see Step 3 on this page.
answered Apr 04 '10 at 09:17 AM
Matt Whitfield ♦♦
I dont have any experience of clusters but this looks like a security issue. What machine is the IP that you have XX'd out in step 1? Is it using an account that doesnt have permission to connect? What does the error log contain? I would try to investigate the security issues mentioned in 1) and 7) combined.
answered Apr 04 '10 at 06:46 AM