Microsoft Knowledge Base Email Alertz

KBAlertz.com: After you install Cluster Server on Windows 2000 Advanced Server and configure Internet Information Services (IIS) or SQL Server, you may need to manually install Microsoft Distributed Transaction Coordinator (MSDTC) as a cluster instance.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 290624 - Last Review: April 7, 2006 - Revision: 4.2

How to configure MSDTC in a Windows 2000 cluster environment

This article was previously published under Q290624

SUMMARY

After you install Cluster Server on Windows 2000 Advanced Server and configure Internet Information Services (IIS) or SQL Server, you may have to manually install Microsoft Distributed Transaction Coordinator (MSDTC) as a cluster instance. By default, Microsoft Windows installs MSDTC in the first group going alphabetically ordered in the Cluster Administrator that contains an IP address resource, Network Name Resource and a Disk Resource. Note This article assumes that the cluster has more than one shared disk.

SQL Server users must use the following SQL Server specific Microsoft Knowledge Base article:
294209  (http://kbalertz.com/Feedback.aspx?kbNumber=294209/ ) Rebuilding or moving MSDTC used with a failover Clustered SQL Server

MORE INFORMATION

To configure MSDTC in a Windows 2000 cluster, follow these steps.

Microsoft only supports the running of MSDTC on cluster nodes as a clustered resource. MSDTC running in stand-alone mode on a cluster is not a recommended or a supported configuration. Using MSDTC in as a non-clustered resource on a MSCS cluster is a problematic configuration because transactions might be orphaned, and data corruption might occur in the event of a cluster failover.
  1. If the cluster group is the first group in Cluster Administrator, and you do not want to install MSDTC in this group, then open the Cluster Administrator on node A, and click to select the cluster group.
  2. In the Cluster Administrator, create a group and name it Temp Group. Right-click the quorum disk resource, click Change Group, and then click Temp Group. A warning dialog box appears. Click Yes to dismiss the warning, and then click Yes in the Move Resource dialog box.

    Note Make sure that you note the disk letter before you move the disk resource. If you want to install MSDTC in the cluster group, see step 7.
  3. If you have any other groups in Cluster Administrator other than the one in which you want to install MSDTC, and they have three resources that contain an IP address resource, Network Name Resource and a Disk Resource, then you must also move the disk from that specific group to the Temp Group. Now, there is only one group left in the Cluster Administrator that meets the IP, Network Name and Disk requirements. That is where Windows will install MSDTC.
  4. Close Cluster Administrator.
  5. At a command prompt on node A, type

    comclust

    and then press ENTER. After Comclust completes, the program returns you to the DOS command prompt.
  6. Do not close the DOS command prompt. Move to node B.
  7. At a command prompt on node B, type

    comclust

    and then press ENTER. After Comclust completes, the program returns you to the DOS command prompt.
  8. Close the command prompt on node B first, and then close the command prompt on node A.
  9. Click to select the Temp Group to which you moved the quorum disk and other disks (step 4), and then move the disks back to their original groups.
  10. Right-click the quorum disk resource, click Change Group, and then click Cluster Group. A warning dialog box appears. Click Yes to dismiss the warning, and then click Yes in the Move Resource dialog box.
  11. Click to select your Web or your SQL Server group.
  12. Bring the MSDTC instance online.
  13. Move your Web or your SQL Server group to node B, and back, to test whether MSDTC is configured correctly on both nodes. You should have an active MSDTC instance in your Web or your SQL Server group.

REFERENCES

For additional information about configuring MSDTC in a Windows Server 2003 cluster, click the following article number to view the article in the Microsoft Knowledge Base:
301600  (http://kbalertz.com/Feedback.aspx?kbNumber=301600/ ) How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 Cluster

APPLIES TO
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Cluster Server 1.1
  • Microsoft SQL Server 7.0 Enterprise Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
Keywords: 
kbsql2005cluster kbinfo KB290624
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please