Cluster Install gives false MSDTC warning on check - by Allan Hirt

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


0
0
Sign in
to vote
ID 332357 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/10/2008 9:01:46 AM
Access Restriction Public

Description

For a clustered implementation, when the System Configuration Check is run and the node running the install does not own the clustered DTC resource, a warning is generated. This should not be the case since the clustered DTC is a shared resource in the cluster and it doesn't matter which node it's running on.
Sign in to post a comment.
Posted by Microsoft on 4/23/2008 at 4:45 PM
Hi Allan,

We already have a work item to revise this message. We will change the MSDTC message as follows.

(If MSDTC Is not running on current node (for example NODE1), set the negative message to read:)


The Distributed Transaction Coordinator service is not running on machine NODE1. Some of the features of SQL Server will fail to work when clustered if the MSDTC service is not running. Please check to see if MSDTC is clustered. If MSDTC is clustered, please make sure it is up and running on another node of the cluster. If MSDTC is not clustered, you can start the MSDTC service through the Services MMC snap-in or run "net start msdtc' from the command prompt.


Thanks for your feedback,

Max Verun
SQL Server
Posted by Microsoft on 3/26/2008 at 7:30 PM
Hi Allan,

We already have a work item to revise this message. We will change the MSDTC message as follows.

(If MSDTC Is not running on current node (for example NODE1), set the negative message to read:)


The Distributed Transaction Coordinator service is not running on machine NODE1. Some of the features of SQL Server will fail to work when clustered if the MSDTC service is not running. Please check to see if MSDTC is clustered. If MSDTC is clustered, please make sure it is up and running on another node of the cluster. If MSDTC is not clustered, you can start the MSDTC service through the Services MMC snap-in or run "net start msdtc' from the command prompt.


Thanks for your feedback,

Max Verun
SQL Server