You cannot bring a Microsoft Distributed Transaction Coordinator resource online after you create it on a Windows Server 2003-based server cluster (890634)
The information in this article applies to:
- Microsoft Windows Server 2003, Enterprise Edition
SYMPTOMSAfter you create a Microsoft Distributed Transaction Coordinator
(MSDTC) resource on a Microsoft Windows Server 2003-based server cluster, the resource
is created successfully. However, when you try to bring this resource online,
you are not successful. In this scenario, the MSDTC resource remains offline with a status of "Failed."CAUSEThis problem occurs if the local Administrator account does
not have the SE_SECURITY_NAME user right. This problem occurs if the Administrators
group has been removed from the Manage auditing and security log setting in the local security settings of the cluster
node. To view this setting, follow these steps:
- Click Start, point to
Administrative Tools, and then click Local Security
Policy.
- Expand Local Policies, and then click
User Rights Assignments.
- In the right pane, double-click Manage auditing and
security log.
The MSDTC resource startup code
does not verify whether the Administrator has the SE_SECURITY_NAME user right
assigned. RESOLUTIONTo resolve this problem, follow these steps:
- Install the Windows Server 2003 COM+ 1.5 Rollup Package 3 on each cluster node.
For additional information about how to obtain this rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
883955
Availability of Windows Server 2003 COM+ 1.5 Rollup Package
3
This rollup package contains a hotfix to cause the MSDTC resource to verify the permission level that it runs under when it starts. Without this hotfix applied, you must remove and then reinstall the MSDTC service to pick up a change in permissions. For additional information about how to do this, see the "Workaround" section. - Remove the MSDTC resource
from the cluster. To do this, follow these steps:
- Start the Cluster Administrator tool.
- Expand your cluster, expand Groups, and then click the group that contains the MSDTC resource.
- In the right pane, right-click MSDTC, and then click Delete.
- When you receive the following message, click Yes:Are you sure resource 'MSDTC' should be deleted?
- Stop the Cluster Service. To do this, follow these steps:
- Click Start, click
Run, type cmd, and then click
OK.
- At the command prompt, type net stop
clussvc, and then press ENTER.
- Add the Administrators group to the Manage auditing
and security log local security setting. To do this, follow these
steps:
- Click Start, point to
Administrative Tools, and then click Local Security
Policy.
- Expand Local Policies, and then click
User Rights Assignments.
- In the right pane, double-click Manage auditing
and security log.
- Click Add User or Group, type
Administrators in the Enter the object names to
select box, click Check Names, and then click
OK.
- Click OK, and then quit the Local
Security Settings tool.
- Start the Cluster Service. To do this, follow these steps:
- Click Start, click
Run, type cmd, and then click
OK.
- At the command prompt, type net start
clussvc, and then press ENTER.
- Follow steps 3 through 5 for each cluster node.
- Create a new MSDTC
resource.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301600
How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 cluster
- Right-click the new MSDTC
resource that you created, and then click Bring
Online.
WORKAROUNDTo work around this problem, follow these steps:
- Remove the MSDTC resource
from the cluster. To do this, follow these steps:
- Start the Cluster Administrator tool.
- Expand your cluster, expand Groups, and then click the group that contains the MSDTC resource.
- In the right pane, right-click MSDTC, and then click Delete.
- When you receive the following message, click Yes:Are you sure resource 'MSDTC' should be deleted?
- On each cluster node, stop the MSDTC service. To do this, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Type net stop msdtc, and then press ENTER.
- Remove the MSDTC service from each cluster node. To do this, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Type msdtc -uninstall, and then press ENTER.
- Verify that the MSDTC service no longer appears in the Services Microsoft Management Console (MMC) snap-in. To view the Services MMC snap-in, click Start, click Run, type services.msc, and then click OK.
- Stop the Cluster Service. To do this, follow these steps:
- Click Start, click
Run, type cmd, and then click
OK.
- At the command prompt, type net stop
clussvc, and then press ENTER.
- Add the Administrators group to the Manage auditing
and security log local security setting. To do this, follow these
steps:
- Click Start, point to
Administrative Tools, and then click Local Security
Policy.
- Expand Local Policies, and then click
User Rights Assignments.
- In the right pane, double-click Manage auditing
and security log.
- Click Add User or Group, type
Administrators in the Enter the object names to
select box, click Check Names, and then click
OK.
- Click OK, and then quit the Local
Security Settings tool.
- Start the Cluster Service. To do this, follow these steps:
- Click Start, click
Run, type cmd, and then click
OK.
- At the command prompt, type net start
clussvc, and then press ENTER.
- Install the MSDTC service. To do this, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Type msdtc -install, and then press ENTER.
- Verify that the MSDTC service appears in the Services MMC snap-in.
- Create a new MSDTC resource.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301600
How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 cluster
- Right-click the new Distributed Transaction Coordinator
resource that you created, and then click Bring
Online.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 3/4/2005 |
---|
Keywords: | kbpending kbBug kbClustering kbtshoot kbprb KB890634 kbAudDeveloper kbAudITPRO |
---|
|