3

I have a two node sql server 2008 r2 cluster that we just did an OS upgrade from windows 2008 r2 to windows 2012 r2, the OS upgrade was done in place so the SQL Server Installation stayed in tack. The cluster role won't come back online saying it's couldn't find any IP address that this instance depends on.

Everything comes on line except SQL Server resource and looking in the sql server log file it shows that error sql server is starting up as I can see master and model get started up.

From the sql log:

Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x5.

Are there additional steps that need to be taken with Windows Server 2012 r2 that need to be done to get SQL Server 2008 r2 to be able to run in a failover cluster?

  • Are cluster services actually installed? – Randolph West Jul 6 '17 at 23:20
  • Yes all of the clustering services are installed. In the logs it shows it trying to start sql server but when it attempts to bind the IP address it fails then shuts down. – Aaron Jul 7 '17 at 0:06
4

Prior to Windows Server 2012 R2, doing an in-place upgrade of Windows for an FCI is not supported. Per Microsoft's documentation:

Upgrading the Windows operating system of a failover cluster is not supported for operating systems before Windows Server 2012 R2. To upgrade a cluster node running on Windows Server 2012 R2, see Cluster Operating System Rolling Upgrade.

Because your starting OS was Windows Server 2008 R2, you are unable to do an in-place upgrade to Windows Server 2012 R2. Instead, you will need to build a new Windows Cluster, do a fresh SQL install for a new FCI, then migrate to that new FCI.

You can do this using existing hardware by removing a node from the cluster, doing the fresh install of both Windows & SQL, then repeating the process one node at a time to move servers from the old cluster to the new cluster.

Once you are upgraded to Windows Server 2012 R2, you will be able to do in-place OS upgrades in the future.

Given that you've already upgraded the OS, your best bet is going to be to uninstall SQL Server, and re-install the FCI from scratch.

  • We are trying a fresh install tomorrow. Initially the role started up after importing it from the other node but I wasn't able to connect to the engine so I recreated the role and this is when all of the trouble started. My take on the reinstall of sql is that we should wipe the OS and do a clean install of windows plus sql. Never been much of a fan of an in-place upgrade to much left over stuff. Thoughts? – Aaron Jul 7 '17 at 2:15
  • I prefer a clean install for a number of reasons. The biggest is that the cutover & rollback processes are way easier if you can build a new machine and test it while your existing server is still online. – AMtwo Jul 7 '17 at 2:26
  • Decided to go with a clean install of everything. – Aaron Jul 7 '17 at 21:36
0

A couple of possibilities, one is due to cluster dependencies, did any name changes happen in the upgrade check and make sure they are aligned. The other is a permissions issue being at the centre of the problem have a look at this post for a solution https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ac756875-eee4-422e-8701-780d519d01c0/sql-20052008-on-windows-server-2008-r2-cluster-service-only-starts-when-account-is-local-admin?forum=sqlsecurity. Due to changes in security in 2012 that might lead to the answer

  • No luck with that. Still is giving me the same error. – Aaron Jul 6 '17 at 23:33
-1

Upgrading the Windows operating system of a failover cluster is not supported for operating systems before Windows Server 2012 R2. To upgrade a cluster node running on Windows Server 2012 R2

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.