How to create SQL Server 2005 Clustering with Virtual Server 2005 (Part 4)

In previous parts(Part 1, Part 2 and Part 3), we have completed windows clustering. Now, before installing SQL Cluster we have to configure MSDTC. We also need to make some shared drive which we would use to keep SQL Server databases and MSDTC. We are going to use Disk M for MSDTC and Disk X for SQL Server. We have already done the steps for Disk Q in part 2 (Create Quorum Disk section). I will reproduce the steps for Disk M and X here.

Configure Shared Disks

1. Turn off MyNode1 and MyNode2

2.  Choose Virtual Disks > Create > Fixed Size Virtual Hard Disks

Create Virtual Disk(M Drive)

3. Provide Details for M Drive (250 MB) and hit "Create" button

Create Virtual Disk(M Drive) Details

4. Same way we would create X drive (2 GB) and Hit "Create" button.

Create Virtual Disk(X Drive) Details

Create Virtual Disk(Y Drive) Details

5. Below is what you would see in Windows Explorer

All Disks

6. Lets attach the disks to MyNode1 and MyNode2 (They are off at this moment) I am showing for MyNode1. Please follow same for MyNode2 also.

MyNode1_Edit Configuration

 MyNode1 Edit hard disk

Click on Hard Disks

MyNode1 HardDisks Properties

Hit OK and it would attach the disks to MyNode1. Follow the same for MyNode2

7. Turn on ONLY MyNode1.

8. Login to MyNode1 and Start > Run > DiskMgmt.msc. Cancel on the screen if you get any.

9. You should see two new Disks which are Not Initialized. Right Click and choose Initialize Disk.  Then you create partition by Right Click New Partition. Below is final screen shot which you should see.

MyNode1 Disk management

10. Now Turn Off MyNode1 and Turn On MyNode2

11. Go to DiskMgmt.msc on MyNode2 and assign drive letters (M for 250 MB drive and X for 2 GB Drive)

12. Open Cluster Administrator (Start > Run > CluAdmin)

13. Create New Group called MSDTC (File > New > Group) and provide details

New Group MSDTC

14. Choose Both Nodes as preferred owner. You might get an error at last screen but that's OK because MyNode1 is offline.

15. Create a new "Disk" resource under MSDTC Group (File > New > Resource) Choose details as below screen shot.

New Resource M Drive

17. Choose M Drive in "Disk Parameters" screen. and finish.

Disk Parameters

18.  Now you should see a Disk resource under MSDTC Group. Right click and choose "Bring Online"

19. Follow 13 to 18 again to Create new groups called "SQL Group" and add "Disk X"

SQL Group Online

20. Up to here we have completed shared disk configuration for MyNode1 and MyNode2. Let's start MyNode1 and test fail over for new groups.

21. Before we install SQL Server, we have to configure MSDTC

Configure MSDTC as Resource

  1. On MyNode1 and MyNode2 follow below steps

    • Open Control Panel on the cluster node
    • Double-click Add/Remove Programs
    • On the left side of the screen, double click Add/Remove Windows Components
    • Under Components, highlight Application Server and click Details
    • Select Enable network DTC access, and then click OK
    • Click Next
    • Click Finish

  2. Add "MSDTC IP Address resource" in MSDTC Group

    • Right click MSDTC Group and select New > Resource
    • Type a some name such as MSDTC IP Address
    • In Resource Type, choose IP Address
    • Click Next
    • Click Next on Possible Owners screen
    • Click Next on Dependencies Screen
    • Give IP Address as
    • Click Finish
    • Right click the MSDTC IP Address resource and select Bring Online.

  3. Add "MSDTC Network Name" resource in MSDTC Group

    • Right click MSDTC Group and select New > Resource
    • Type a some name such as MSDTC NN
    • In Resource Type, choose Network Name
    • Click Next
    • Click Next on Possible Owners screen
    • On Dependencies Screen, move MSDTC IP Address and click on Add to bring on Right window. Now hit Next.
    • Give Name as MSDTC
    • Click Finish
    • Right click the MSDTC NN resource and select Bring Online.

  4. Add "MSDTC" resource in MSDTC Group

    • Right click MSDTC Group and select New > Resource
    • Type a some name such as MSDTC
    • In Resource Type, choose Distributed Transaction Coordinator
    • Click Next
    • Click Next on Possible Owners screen
    • On Dependencies Screen, choose "MSDTC NN" and "M Drive" and click on Add to bring on Right window.

                        MSDTC Dependencies

    • Click Finish
    • Right click the MSDTC resource and select Bring Online.

MSDTC Group Online

Above is the screen shot of "MSDTC group". Make sure you have matching "Resource Type" as shown in the screen.

Test fail over for MSDTC group. This finishes all Prerequisites to install SQL Server on Cluster. Get ready to install SQL Server in last part of the series.

You can follow to make changes to MSDTC Services.

Lets move on to last part of the series

Comments (20)
  1. Sameer Dhoot says:

    After step 11 you need to start up Node 1. I am not sure if this is coorect but worked for me. When i first did it node 1 was shut down. after creating groups and resources, i bought up node 1 and then to simulate failover i disconnect both the networks from node 2. I cluadmin on node 1 there was an error to bring M Drive online, but S drive though was online. So i again connected the newtowrk on node 2 and then restarted the cluster service on node 2. Delete the resource M Drive and then recreated when both node were online. Now i again disconnected network on node 1 and then M drive was up on node but now the S Drive failed (i used S instead of X), i again repetead the step to delelte the resource and then recreate it. After doing so i could simulate failover and all the resources were online.

    Please let me know if you think the process is not correct.

  2. Balmukund says:

    Sorry, but I could not understand your explaination…

  3. Thanga says:

    As u said in the first part about to download virtual hard disk, the link having the following three downloads which one is need to be downloaded.


    700.0 MB



    700.0 MB



    495.1 MB

  4. Balmukund says:

    Hi Thanga,

    Thanks for the comments.

    You have to download all the files in same folder. Once you run part1.exe, it automatically use rest two and extract vhd. hope this answers your question. Feel free to add commments.

    I have modified Part 1 to make it clear.

    • Balmukund
  5. Eric Twilegar says:

    I see a lot of mention in this part and part 5 of virutal names. MSDTC requires it’s own name and IP. So does SQL server.

    The cluster has a name and for that to work you need a computer account in Active directory. usually the wizard creates this.

    My question is what does adding a virtual name create? Do you need rights in active directory for that name to register. What if you don’t have those rights? Does your admin need to create aliases? Does the cluster service account need any rights to them.

    I’ve been searching high and dry for any information on not being an admin and virutal server names with no luck.


  6. Balmukund says:

    Hi Eric,

    When you create any Virtual Network Name in Cluster, it does not create the object in AD. There is a check box  "Enable Kerberos Authentication" at Right Click > Properies > Parameters. If that box is checked, it would registry Virtual Network Name in Active Directory.

    By default an account can create 10 objects in AD.

    Refer –

    Please let me know if your question is unanswered.

    • Balmukund
  7. Paul says:

    Greate article,

    After step 11, I cannot open SQLCluster from Node1 or Node2. If i try to ping the ping fails. I noticed Cluster service is started and running on both nodes. If i try to create a new cluster and provide the name of sqlcluster, I cannot proceed as sqlcluster can be seen. Any help would be appreciated.



  8. Paul says:

    More information included…

    The error message that i receive is "The Cluster Service on node ‘sqlcluster’ cannot be started. The network path was not found. Error ID: -2147024843 (80070035).

    Thanks again,


  9. Balmukund says:


    Sorry to hear that you could not proceed smoothly. Can you please let me know where exactly you faced failure? You mentioned step 11, it would help if you can tell which part of series (Part 3)?

    I would go by looking at event log to check the failure. Is your cluster service running? (your two post contradict each other) If service is not running then check event log to see the reason of failure.

    Please do post back and let us know the problem. I would be happy to help.

  10. Paul says:

    It was network related issue. I am past that stage now. Thanks for the quick reply.



  11. Linda says:


    After step 21, I tried to test failover for MSDTC group. The other three resources are online but MSDTC resource is offline. How can I correct for this?

    If this MSDTC group not online, will SQL 2005 installation fail?


  12. Balmukund says:

    Hi Linda,

    I feel that MSDTC is not configured properly on both the nodes causing it to fail.

    (Configure MSDTC as Resource – Step 1 to be done on both the nodes.)

    Can you please have a look at eventlog on node2 and check the error?

    Run below command on node2

    msdtc -uninstall

    msdtc -install

    and try..

    Hope this helps!


  13. j says:

    Hi Balmukund,

    I am stuck on step 12 in part 4 series of configuring shared disks –

    1. Open Cluster Administrator (Start > Run > CluAdmin)
    2. Create New Group called MSDTC (File > New > Group) and provide details

    I am not able to open a connection to SQLCluster. I says network path not found.

    Please help.

  14. j says:

    Hi Balmukund,

    I am past that problem. I discovered that cluster services were not turned on. After I turned on the cluster service it started working fine.

    I have another problem …

    While configuring MSDTC resource -> adding a distributed transaction coordinator it says that it cannot create a duplicate resource of this type.

    Please help.

  15. kishore says:

    Hi Balmukund,

    I was able to successfully implement everything till step: 20 of part 4.Before going to configure MSDTC i.e step 21.I was testing some of the fail over scenario’s between the groups and nodes will work..It looks like moving the Groups/Resources works between the nodes.But when i manually turn off Node1, Now i am unable to access cluster Administrator and i see Drives Q ,M & X are available on Node 2. Then later i bring back the Node1 and hoping for the ClusterService  to be up and running and expecting the failback from Node2 to Node1..Which is not happening..What i am missing? Any body pl’s help me….Here is the error from Node1 event log:

    Event Type: Warning

    Event Source: MSDTC Client

    Event Category: Cluster

    Event ID: 4148

    Date: 12/21/2009

    Time: 12:16:04 PM

    User: N/A

    Computer: MYNODE1


    The MS DTC service was started before the cluster service on this

    cluster node. This service will now be stopped. If MSDTC has been

    configured to run on a cluster, the MS DTC resource will be brought

    online by the cluster service when it starts. Error Specifics:

    d:ntcomcomplusdtcsharedmtxclumtxclusetuphelper.cpp:932, Pid:

    912, CmdLine: "C:WINDOWSclusterresrcmon.exe" -e 1184 -m 900 -p 224

  16. Balmukund says:

    Hi Kishore,

    If you turn off Node1, you should be able to access cluster administrator which would show Node1 as red cross (means cluster is not able to access that node) Could you please check if cluster service is started on Node2 or not.

    Coming to failover question, if you turn on Node1 back (assuming resources are one Node2) cluster would NOT attempt to bring it back to Node1 unless you have configured failback in group properties.

    Reason: Moving resource back would be another downtime and you may not want to do that in business hours. Failback can be set to "immedietly" or "between x to y" time.

    Hope this answers your question.


  17. kishore says:

    Thanks Balmukund..Your Failback really answers my questions..regarding Cluster service.Here is what i did with Cluster Installation process..I followed the steps and installed new cluster service on Node1( first and added Node2 to the existing cluster.When i turned off Node1 this what it’s happening when i simulated the same..

    1.) As you mentioned now i can see red sign on Node1 & i can browse Node2 info..

    2.) I see all the resources & shared drives are available on Node2 with status "Online", but i see "Cluster IP Address" — Failed

    "Cluster Name" —  Offline status and i see cluster service is started in Node2 -Automatically.In Node i see the following Error Messages in Event Log/Also i have some screen shots i can share with you.If you don’t mind can you send me an email to

    —–Error Messages Node2———

    Event Type: Error

    Event Source: Userenv

    Event Category: None

    Event ID: 1058

    Date: 12/22/2009

    Time: 8:47:12 AM

    User: KKEAdministrator

    Computer: MYNODE2


    Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=KKE,DC=local. The file must be present at the location <\KKE.localsysvolKKE.localPolicies{31B2F340-016D-11D2-945F-00C04FB984F9}gpt.ini>. (The network path was not found. ). Group Policy processing aborted.

    For more information, see Help and Support Center at

    Event Type: Error

    Event Source: Userenv

    Event Category: None

    Event ID: 1030

    Date: 12/22/2009

    Time: 8:47:12 AM

    User: KKEAdministrator

    Computer: MYNODE2


    Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

    For more information, see Help and Support Center at

  18. Balmukund says:

    Looks like machine is not able to access domain controller when it was trying to start cluster service

    Below error says – network path not found.

    \KKE.localsysvolKKE.localPolicies{31B2F340-016D-11D2-945F-00C04FB984F9}gpt.ini>. (The network path was not found. ).

    Hope this helps!


  19. kishore76 says:

    Yes I checked that one..Looks like Node2 is unable to see DC’s GPO.I tried to just type this command in Node2 –> RUN ..i get the same error.But gpt.inifile is located in DC.Any idea how to resolve this issue..In my case i used DC’s administrator account to login to both Node1 & Node2..Pl’s let me know if you have any idea..

  20. Balmukund says:

    Hi Kishore,

    Are you able to ping the DC from Node2? If not, try disabling firewall and check.



Comments are closed.

Skip to main content