I'm looking for a bit of help with regard to a problem I'm looking at when failing a SQL Server 2008 R2 Enterprise instance over from one node of an active/active cluster to the other node.
One of the instances, normally on node #2, is at RTM. And when failing over to node #1 there is a time-out bringing the SQL Server service on-line, however once the time-out has, er, 'timed out', the service can actually be brought on-line OK manually. And looking at the Log there are errors of the form ‘Login failed ..... Reason: Server is in script upgrade mode…..’. This is similar to some other posts I've read regarding problems bringing SQL Server back on-line after a service pack however is slightly different in that the service is able to be brought on-line OK, albeit manually. Furthermore, when failing back to its original (and preferred) node, the service come back on-line OK so the problem only affects failing over from node #2 to node #1.
At first I thought this was the result of a failed attempt at installing SP1 however I'm now not so sure. SP1 has definitely been installed on the other instance on both nodes and this is able to be failed over between nodes without a problem. This instance's
preferred node is node #1 so.
It's difficult to tell which script is causing the problem here. It does look like SP1 was started and cancelled several times before completing however I'm finding it difficulty to interpret the log files with regard to what might be happening to the problem
instance and I can't see any out-and-out failure message anywhere relating the the problem instance. I've also applied trace flag -T902 and, whilst it inhibits script from running, it doesn't prevent the fail-over time-out, although naturally there could be
something else happening here. Curiously though, if I just re-start the service rather than failing it over to a different node, those 'Script upgrade mode' errors don't appear. These would only seem to appear when failing over.
I'm happy to try re-installing SP1 however I rather understand the problem and the error messages first before I do that.
Regards,
Gordon.