Post reply

Can't remove instance from clustered server

  • June 27, 2010 at 11:10 am

    #223333

    Hi ,

    I'm using SQL Server 2008 and I have on Active-Active Cluster on

    a Windows Server2008.

    I have one SQL instance on that Server. The other node I had SSAs wich I want to uninstall and be with another instance of SQL.

    I had SSIS has a clsutered here also.

    I unistalled the SSAS and made Prepare SQL to Cluster intallation on Node 1 (that already had one SQL instance).

    When I tried to Complete the SQL Failover clustered installation I cannot reach the instance and after a few atteps I cannot connect with SSIS on this clustered.

    I cannot remove the SQL instance from ADD/Remove Programs because it gives me the error that this instance is used has a cluster.

    So this is what I want to do:

    -Remove the instancethat says that is clustered but I can't see the cluster on Failover Clustered Administration.

    -Setup SSIS as a clustered service on the instance that was previous installed(I can reach the SSIS editing SQL Agent Job but I can't connect through Database Engine.Through the Agent all the packages are unreacheable but visible.)

    I already See that I can't add features to a clustered installation but I read that it's possible to Add SSis if I stop both nodes. How can I stop both nodes to install SSIS.

    Thanks.

  • June 27, 2010 at 7:08 pm

    #1185472

    Hey There, try using the command line to remove the nodes form the SQL isntallation, this will probably be the easiest.

    setup.exe /ACTION=RemoveNode /INSTANCENAME="<Insert Instance Name>"

    As for SSIS, this is not a cluster aware application and it is not recommended to install it on a cluster and try to make it cluster aware, so if I were you keep SSIS off the cluster and find a dedicated box for it. If that is not an option, then install it on the cluster but do not try to make it resource of the cluster

  • June 28, 2010 at 7:08 am

    #1185699

    Thanks for your help.

    I have only the instance in one node and I cannot install the instance on Node two.

    I cannot complete the installation of the cluster on Node 1 because gives me the error that Network name already exists. When I try to remove the instance gives me the error that is a clustered intance and in the properties of that instance Clustered is with the value of Yes.

    Through the setups and from the uninstall on ADD/remove programs I cannot remove instance or Network ID.

    I guess I have to delete instance and the Cluster Network through registry because it isn't available on Failover CLuster Administrator.

    How can I delete this?

  • June 29, 2010 at 5:55 am

    #1186289

    Don't delete it from the registry, you'll just get yourself into more trouble.

    A clustered instance cannot be removed through add/remove programs. You must use the installation media. Once you start it up, choose installation -> remove node from sql server failover cluster. (i think that's the correct path)

    This will uninstall the clustered instance, even though it's an incomplete single node cluster. Give this a shot before going into the registry.

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • June 29, 2010 at 9:40 am

    #1186470

    I already tried that. But the instance doesn't appear when trying to remove the node.

  • June 29, 2010 at 5:44 pm

    #1186782

    I have encountered this before. How I resolved it was the following

    You cant remove a node of SQL if it is not running. On the node you have SQL installed try to get it running. By the sounds of things you use the incorrect network name when installing SQL, you need SQL to use this name so wherever the contention is try to remove it. Perhaps shutdown he server that is using the network name and start SQL.

    If SQL starts try to uninstall it through the command line. If you get a failure on that. Install another instance on both nodes, then try to remove your broken instance.

  • June 30, 2010 at 7:13 am

    #1187040

    Hi , thanks for your help.

    I can't start SQL for that instance gives the error:

    The configuration of the NP protocol in the SQL instance is not valid.

    The Network name doesn't exist in the AD. I already have another intance and it's clustered and is working, but I don't want to stay wiith a corrupt instance.

  • July 1, 2010 at 5:19 am

    #1187587

    If the network name doesn't exist in ad create it so you can start the instance. You should be able to start it then.

  • July 2, 2010 at 5:05 am

    #1188108

    The name was removed from AD after this problem. It was because of this problem that we removed the name from AD.

    This problem ocurred and we removed it from the AD, 3 days after this problem start.

    We're going to put it again and try to start the service, but is something that we've tried already.

    Thanks.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply