Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/252641

From BetaArchive Wiki
Knowledge Base


Resolving MSDTC Conflicts During NTOP Installation on Cluster Server

Article ID: 252641

Article Last Modified on 1/5/2006



APPLIES TO

  • Microsoft Internet Information Server 4.0



This article was previously published under Q252641

We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:

SYMPTOMS

When you install the Windows NT Option Pack (NTOP) on a clustered server with newer versions of the Microsoft Distributed Transaction Coordinator (MSDTC) present, the following MSDTC event may occur:

Source: Service Control Manager Event ID: 7024 Description: The MSDTC service terminated with service-specific error 3221229574.


CAUSE

MSDTC version conflicts can occur during the NTOP installation on a clustered server. The NTOP installs an older version of the MSDTC. If the clustered server has Windows NT Service Pack 4 or later, the NTOP installation may fail and the MSDTC may not function correctly after the installation. When SQL Server is installed prior to the NTOP, similar problems with the MSDTC may occur.

If one of the following situations describes your problem, use the steps in the "Workaround" section of this article.

  • The NTOP cannot be installed because Windows NT SP4 or later is installed on the system.
  • The NTOP is installed, but the MSDTC resources fail under Cluster Administrator.
  • SQL Server and the NTOP are both installed on a clustered server and the MSDTC is the only resource failing.


WORKAROUND

  1. Remove the MSDTC resource group from cluster server.
  2. Delete the following registry keys on the MSDTC:

    HKLM\software\Microsoft\MSDTC

    and

    HKLM\SYSTEM\CurrentControlSet\Services\MSDTC

  3. Remove the shared MSDTCLog folder on the shared drive.
  4. Install the standalone version of the MSDTC from the following location:
  5. Stop and restart the cluster services on both nodes in the following order:
    1. Stop CLSSVC on node B
    2. Stop CLSSVC on node A
    3. Start CLSSVC on node A
    4. Start CLSSVC on node B
  6. Test failover of the MSDTC group. If it works, the workaround was successful.
  7. If the errors persist, use the DTCremove utility (not supported), and then run DTCSetup.exe again as described above.
  8. If SQL Server is installed, you may need to remove SQL Server first.For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

    192708 INF: Installation Order: Cluster Server Support for SQL or MSMQ

    219264 INF: Order of Installation for SQL Server 7.0 Clustering Setup

Note: For servers with SP5 installed prior to the NTOP installation, a fix for the MSDTC installation is provided. For additional information on MSDTC installation instructions, click the article number below to view the article in the Microsoft Knowledge Base:

241573 How To Install IIS 4.0 onto a Single Node of MSCS 1.0


Note: Update both nodes on the cluster.


Additional query words: MSCS, cluster, MSDTC, NTOP server cluster

Keywords: kbprb kbpending KB252641