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

Clustered instance will not start on node 4 anymore Expand / Collapse
Author
Message
Posted Monday, October 21, 2013 5:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, October 20, 2014 1:12 AM
Points: 34, Visits: 207
Hi

We have a 4 note active cluster for our SQL server production environment.

A few weeks ago we had a maintenance window for windows updates, so i updated SQL4 first, then i movewd all our instances to that host, and updated SQL3 - reboot - SQL2 - reboot - SQL 1 - reboot and then redistributed all the instances again.

now it seems that 1 of our instances no longer want to start on node 4, it will infact only run on node 1...

that is not even close to high availability, so it must be corrected, but how?

all the disks go online, the networkname too, aswell as the cluster share service, but the SQL server just says "Failed"

Any ideas?
Post #1506637
Posted Monday, October 21, 2013 9:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, October 20, 2014 9:59 AM
Points: 304, Visits: 574
It could be the service failing to start due to a login \ password error. Have you checked event viewer? If its a service issue the error will be logged in the event viewer.

You should also have a copy of the error in the SQL server log, which you can find via windows explorer.


MCITP SQL 2005, MCSA SQL 2012
Post #1506715
Posted Tuesday, October 22, 2013 3:11 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, October 20, 2014 1:12 AM
Points: 34, Visits: 207
Well... that is what made me post this in the first place, it really didnt say much in the event log and nothing in the SQL Server errorlog...

but the miracle of a good nights sleep (and no kids in the bed to kick me in the groin every 15 mins) and i looked at the errormessage with fresh eyes this morning:

initerrlog: Could not open error log file 'E:\MSSQL10.BI\MSSQL\Log\ERRORLOG'. Operating system error = 5(failed to retrieve text for this error. Reason: 15105).

and i learned a new trick:
net helpmsg 5
returned :"Access is denied"

so i had a closer look at the permissions on the disks, and it appear that some permissions where missing!

probably a result of the disk change we made a few weeks back, so i set the permissions for the SQLserver and Agent on the proper folders, looking at another instance as a souce and now the failover to another node works great!

but why did it work in the previous node then?

it looks like someone has but this perticular SQL server service account in the local administrators group...

Thanks for the help, it got me thinking in the right direction!
Post #1507023
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse