Groups | Blog | Home
all groups > sql server clustering > august 2005 >

sql server clustering : Setting up MSDTC Resource on Clustered Server


Benjamin
8/25/2005 8:30:13 AM
I am trying to setup a MSDTC on Windows 2003 Cluster.
I have done the steps in Q301600 and KB 817064.

However the MSDTC Resource will start on one of the cluster nodes but not on
the other. (2 node cluster). I have checked that both nodes have access to
the disk that is used for the MSDTC files etc...

I get the following error message:

Event Type: Error
Event Source: MSDTC
Event Category: Cluster
Event ID: 4385
Date: 25/08/2005
Time: 14:06:33
User: N/A
Computer: SAN-EIGHT
Description:
MS DTC cannot start on this cluster node because the MS DTC resource is
currently owned by another node in the cluster. Error Specifics:
d:\nt\com\complus\dtc\shared\mtxclu\mtxclusetuphelper.cpp:583, CmdLine:
C:\WINDOWS\system32\msdtc.exe, Pid: 3472


Please can someone help ??

--
Ben.
England.
--
Ben.
Geoff N. Hiten
8/25/2005 1:02:01 PM
Do not use the services applet to control clustered resources. Use the
cluster management tool (or the CLUSTER.EXE command-line tool) to manage
clustered resources. Try and use the cluster tool to move the MSDTC
resource group to the other node.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

[quoted text, click to view]

Benjamin
8/26/2005 12:52:01 AM
Yes I am using the Cluster Administrator to control this. WHen I fail the
resource over to the other node it simly fails back to the original node
----- help ?
--
Ben.
England.


[quoted text, click to view]
Geoff N. Hiten
8/26/2005 5:27:56 AM
The Application event log should have an indication as to why the service
failed to start. Look on BOTH nodes. The SQL Server logs may also have
information.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

[quoted text, click to view]

CJ
10/28/2005 2:07:12 PM
I had the sam exact symptoms on my (2 node cluster). I am also using Vertias
Storage Foundation Works 4.1 RP1 for disk and path management. When creating
the MSDTC resource on the node that orignally owned all the resources the
MSDTC came online. But when I tried to fail-over the MSDTC resource to the
secondary node, the MSDTC resource timed out and failed back over to the
primary node. After noticing that Cluster Admin had showed the Q: Quorum
resource online, but the logical Q: drive wasn't showing up in My Computer, I
realized I had a problem.

Solution: I launched Veritas Enterpise Administrator (VEA) in your case this
would be MS Disk Manager and selected Q: as the disk letter. Once I did
this, logical Q: drive (Which is the Quorum drive) was populated in My
Computer. I accessed the Q: drive letter and noticed that the MSCS directory
wasn't present. I have to launch cluster admin, right click the cluster
name, select properties, click on the "Quorum" tab, and select any drive
other then Q:, then reselect Q:, select Apply and OK. Then Walla! the MSCS
directory for the Quorum database appeared on the Q: Drive. At this point I
recreated the MSDTC resource on my primary cluster, brought online and
noticed that the MSDTC directory was created on the Quorum drive. Test
fail-over and it worked!!!!

Hope this helps someone.

[quoted text, click to view]
AddThis Social Bookmark Button