Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Can't Connect To Cluster Expand / Collapse
Author
Message
Posted Tuesday, August 28, 2012 10:20 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 8:48 AM
Points: 63, Visits: 360
Hi guys,

I had a fully functional SQL 2008 R2 Failover Cluster up and running. Without getting into the heavy details I ran a Repair on the cluster of all shared services (this was in the hope to resolve another issue I was having in being able to view some of the legacy components). Once the repair completed, I tried to log onto any of the instances afterwards and they all failed.
I've tried restarting the instances but they fail to come back online.
Any suggestions at all would be helpful, I'm trying to find any log files but can't find anything of use.
I did see in Event Viewer some errors but they're all fairly ambiguous:
1. [sqsrvres] OnlineThread:Error connecting to SQL Server
2. [sqsrvres] ODBC sqldriverconnect failed

The other errors on the system logs:
The Cluster service failed to bring clustered service or application 'SQL Server (XXX)' completely online or offline. One or more resources my be in a failed state.

I'm not sure what resources exactly are in a failed state so I'm having trouble trying to pin point what exactly is failing.

Any help would be appreciated

Thanks
Post #1351092
Posted Tuesday, August 28, 2012 10:44 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 8:48 AM
Points: 63, Visits: 360
Some more detail from the SQL logs

2012-08-28 17:36:17.97 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

2012-08-28 17:36:17.97 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

2012-08-28 17:36:18.00 spid29s The Service Broker protocol transport is disabled or not configured.

2012-08-28 17:36:18.00 spid29s The Database Mirroring protocol transport is disabled or not configured.

2012-08-28 17:36:18.02 spid29s Service Broker manager has started.



2012-08-28 17:36:22.37 spid7s Error: 8355, Severity: 16, State: 1.

2012-08-28 17:36:22.37 spid7s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.


Post #1351109
Posted Wednesday, August 29, 2012 5:47 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 8:48 AM
Points: 63, Visits: 360
Also, just to mention that the install of SQL 2008 R2 was done with a slipstream version with SP2 applied. The Repair I ran would have been from the same install.
Post #1351530
Posted Wednesday, August 29, 2012 6:58 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 8:48 AM
Points: 63, Visits: 360
Sorted it myself, SQL Browser had not come back up online after the repair.
Post #1351585
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse