Thursday, January 27, 2011

SQL Server 2005 Failover Cluster Setup issues

I was installing 2005 failover cluster y'day and have gone through some troubles.

1) During the setup, we need to enter the sql server virtual name and the virtual ip but I when I was trying to enter the name, it says it already exists.
Then I found that my windowns admin has laready created the "sql cluster name" and "sql server IP" in the sql server resource group in the cluster administrator.

2) So I deleted both of them and then entered those details, what sql server does is that it creates the virtual name and the IP in the domain so the name and ip should be unique and shouldn't be used anywhere else.

3) Then again before the installation was started, I was repeatedly getting the below strange error:
"setup failed to start on the remote machine. check the task scheduler event log on the remote machine"
I checked the sql server setup log as indicated in the path but couldn't find anything.
I've gone mad for some time as tried to install repeatedly for 3 unsuccessful times and later with the help of google found that you shouldn't be logging into the other node when you are installing sql server
I had logged off and then proceeded with the installation and it went fine.

4) There is another option you need to give after you give your sql server virtual name
it says something like this.
"add your domain admin group under which your cluster service account runs".
This name you'll get from your windows admin.
I've mentioned a domain group under which all service accounts in your organization are part of.

5) After installation, I checked the sql server resource group and could see "sql server IP" , "sql server cluster name", sql server, sql server full text search, sql server agent.

6) I've tested the failover and all seems good but there was one more issue coming through when I tried to restore the database

Msg 5184, Level 16, State 2, Line 2
Cannot use file 'g:\Microsoft SQL Server\MSSQL\DATA\test_data.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.
Then I verified the dependencies for the resource "sql server" in the cluster and found only F drive added.
So I quickly added my remaining two cluster drives G and H and then was able to restore it successfully.

7) One more error you would face if setup fails once and you are trying to re install.
Below is the error:

Product: Microsoft SQL Server Native Client -- Error 1706. An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.

This is because, once the setup fails once and you are trying to do the installation again, it fails as it tries to re install the client components. The solution is that you should remove the sql server client components from add remove programs and then start the setup all over again.

It was overall  a good experience.

No comments:

Post a Comment