December 23, 2010 at 9:48 am
I am in cluster install hell with a standard edition sql server 2008 active /passive install in a virtual environment. Been chasing my tail forever, but it looks like it may be related to issues with sql agent and cluster. The agent is up on the first node and service looks ok but still saw something odd. When I was going to do an uninstall I noticed one of the components that did not show up is SQL Agent which the blogs keep referencing as an issue. In the unistall components shouldn't sql agent show up
December 29, 2010 at 2:43 pm
Hi,
Did you received a Successful install message or Failed message? If there's an error and you click OK, it will shows like it completed but it has a big red X on the SQL Server Installation icon.
If the install failed, then I might be able to help. I've seen this issue before. In my case, the Service Account for the SQL Server resources does not have Domain Admins rights in the AD. The service account needs this right to create its Service Principal Name or SPN. Use the following command to see if the SPN for the cluster has been created
setspn -l <service-acc-name>
Ex. setspn -l sa-sqlcluster
Output will list the spn that registered to the service name.
You might need a Windows Admin to grant the Service Account with Domain Admin privileges to allow it to create its own spn. Make sure after the SPN is created to revoke the rights. See the following page for SPN info: http://msdn.microsoft.com/en-us/library/ms191153(v=SQL.100).aspx.
You might have to uninstall SQL and reinstall it before doing this.
Hope this helps,
Harry Chandra
December 30, 2010 at 8:21 am
I don't know if this problem still exists with SQL 2008, but we had multiple issues when we installed SQL 2005 onto a Windows 2008 Server cluster. We discovered that the node names must be all upper case characters when the Windows Cluster is built. If your node names are entered with any lower case characters you may want to rebuild the Windows Cluster (it's okay to use numbers in the node names too).
Good luck
January 10, 2011 at 8:22 am
This may or may not be your issue but check here just in case:
This happened to me on two 2008 R2 clusters I built in the last few weeks. One had all upper case node names and the other did not so it's not clear to me that case on node names is actually the cause.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply