Re: W2K SQL Cluster MSDTC cannot failover

From: Dave V (varmint243_at_bogus.adelphia.net)
Date: 06/26/04


Date: Fri, 25 Jun 2004 21:57:17 -0400

I have had a similar problem when comclust.exe was incompletely installed.
The DBA had attempted to do it and messed up the cluster after I built it
and installed SQL for him.

You havent done the comclust.exe install correctly on node B. There are very
specific instructions to do this including keeping the cmd window open on
node A until completely finished on node B. You also need to stop SQL and
SQL agent during the comclust.exe install or it will just hang.

Redo comclust.exe on node A and B

There are also specific instructions for how to get MSDTC in the group you
want it in

A quick google search should turn up everything you need. If you cant find
it I will look thru my old notes and see if I can find the white papers

        thanks,
                   DaveV

"HJI" <happy_haidong@RemoveThis.yahoo.com> wrote in message
news:210fb01c45a0e$2ec0dd50$a501280a@phx.gbl...
> 1. This is a different cluster with 2 nodes. I was not
> involved whatsoever during the setup and install.
> Therefore I have no idea what Server Admin did;
>
> 2. Win2k Advanced, SQL2kEnterprise SP3, 2 Nodes, SQL
> Default instance;
>
> 3. There are 2 groups configured under Cluster Admin:
>
> Cluster Group: Cluster IP Address, Cluster Name, Disk Q:
> (Note: Quorum Disk)
>
> SQL Cluster: Disk L: (Note: disk for db logs), Disk S:
> (Note: disk for db data files), MSDTC, SQL IP Address1
> (CMSLDADB), SQL Network Name(CMSLDADB), SQL Server, SQL
> Server Agent, SQL Server Fulltext;
>
> 4. When I try to failover SQL Cluster from Node A to Node
> B, e.g. Right click on "SQL Cluster" group and pick "Move
> Group", MSDTC always fails. This forces SQL Cluster to
> failback to Node A. In other words, failover is not
> working;
>
> 5. I talked to PSS. PSS had me try changing SQL Server
> startup account to MSCS Service startup account, which I
> did. The same problem persisted;
>
> 6. PSS then had me try changing the property of MSDTC by
> un-checking "Affect the Group" in Advanced Tab. I was able
> to failover back and forth with this unchecked. It appears
> MSDTC only works on Node A. However, because we use linked
> server between the clusters we have, having MSDTC disabled
> is NOT an option;
>
> 7. This is the error message from system log every time I
> try the failover:
> The Microsoft Clustering Service failed restore a registry
> key for resource SQL Server when it was brought online.
> This error code was 2. Some changes may be lost.
> Category: (64)
>
> Event ID: 1082
>
> Any help would be greatly appreciated.
>
> HJI



Relevant Pages

  • Re: Setup cluster SQL server in SAN due to task scheduler
    ... Dell PV220S (Cluster Mode, PERC 3/DC) ... SQL Database Engine ... Microsoft SQL Server 2005 Setup ... To install all SQL Server features, install IIS from Add or Remove Programs ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)
  • RE: Clustering Question
    ... if you want to install SQL cluster on both node at the same time. ... you could also install it on one node and then add another node. ... Microsoft SQL Server 2000, if Microsoft SQL Server 2000 is clustered. ...
    (microsoft.public.sqlserver.setup)
  • Re: Create SQL cluster on 2003
    ... Since you are in a cluster configuration, ... Microsoft SQL Server MVP ... We only about about 20 databases - all ... Move Databases Between Computers That Are Running SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: I Surrender.....Help?
    ... Name resolution is critical to cluster ... Verify the Edition of SQL you are installing. ... Install the SQL client tools only on your primary install node. ... account is a domain account with local admin rights on each node. ...
    (microsoft.public.sqlserver.clustering)

Loading