locked
The DTC service could not be installed. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    Sub-component Distributed Transaction Coordinator raised an exception while processing the OC_COMPLETE_INSTALLATION setup message.

    D:\nt\com\complus\dtc\ntdcsetup\src\cdtccore.cpp (line789)

    Error Code = 0xfffffff

     

    The DTC service could not be installed.

     

    I get this error message with Vmware with Windows Server 2003 w SP2, and no other updates, after trying to install WDS. I also get this same error message with Virtual Server 2005 R2, exact error messages, then when I try to set/install for c:\RemoteInstall, I receive a syntax error.

     

    I've noticed before SP2, that if I use the WDSupdate files it doesn't error there, but I will get the same syntax error as I do when select c:\RemoteInstall when setting up the server withing the WDS console. Anyone have this same problem? I've had to resort to installing/test WDS through on computer vs doing it virtually.

     

    I assumed it was because of Virtual Server 2005, but with doubts I tested with Vmware just to be sure.

    Thursday, October 4, 2007 6:41 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    ****************************************************************************************************************************************

    ub-component Distributed Transaction Coordinator raised an exception while processing the OC_COMPLETE_INSTALLATION setup message.

    d:\nt\com\complus\dtc\ntdtcsetup\src\cdtccore.cpp (line 769)

    Error Code = 0xffffffff

     

    The DTC service could not be installed

    ***************************************************************************************************************************************

     

    This is exactly the error i am dealing from a week... it sems that there is no much info about the error.

     

    I want to put my Exchange 2003 Server up, i am running a Windows 2003 Enterprise Edition SP2, on a HP Blade System Model ProLiant BL460c G1.

    When fresh installing windows, i can install the service via control panel or using the command line and after the installation i can start the service.

    I can create the cluster and play with it... the resources spring from NODE1 to NODE2 like a basketball... i mean perfectly.

    If i add the MSDTC Group and it´s Resources the NIGHT(DAY)MARE starts...

    What happens is that the service stops and them keeps me giving error 1067 when i try to start the service. Strange enougth the services becomes damaged on both NODES.

     

    I already followed the steps from the Microsoft Website that sounds like that:

     

    How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 cluster

    View products that this article applies to.
    Article ID : 301600
    Last Review : October 1, 2007
    Revision : 23.1
    This article was previously published under Q301600
    On This Page

    July 5th, 2005 · No Comments

    I worked hard this morning in Google looking for the answer to this. I found one that got me close but I had to change things up enough that I am reposting it here….

    This is on Windows 2003 Enterprise for SQL Cluster. I tried to install MSDTC and it kept giving me an error…

    Event ID: 4389 Source: MSTDC Client

    MS DTC setup failed to populate the shared cluster registry. The DTC resource will not be able to come online.Error Specifics: d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetuphelper.cpp:120, Pid: 1296, CmdLine: “C:\WINDOWS\cluster\resrcmon.exe” -e 1012 -m 1252 -p 1672

    After much pain, here is what I did…

    Delete the DTC resource
    Delete MSDTC shared folder from the quorum disk
    On Node 1:
    * Stop Cluster service
    * Remove Enable network DTC access
    * Run msdtc -uninstall
    * Verify success in event log
    * Delete registry keys:
    HKEY_CLASSES_ROOT\CID
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
    * Evict Node1 from cluster.
    * Reboot
    * Reinstall Enable network DTC access
    * Add Node1 to Cluster
    * Fail everything over to Node1
    * Create MSDTC resource
    Node 2
    * Stop Cluster service
    * Evict node from cluster
    * Remove Enable network DTC access
    * Run msdtc -uninstall
    * Verify success in event log
    * Delete registry keys
    HKEY_CLASSES_ROOT\CID
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
    * Reboot
    * Reinstall Enable network DTC access
    * Verify service started, registry keys created
    * Rejoin cluster
    Then fail the cluster group over to the second node to verify that the DTC
    resource comes online successfully on the second node. After that, reboot
    both servers and verify that the resource would fail over properly to both
    nodes with the rest of the group.

     
    Well... it did not help...
     
    Yesterday become 1.00 O´clock PM and i would like to take some sleep today.. cause the Management just sent an e-mail to BOSS saying that they expect to have the e-mail working in a couple of days.
     
    Any single idea is gold worthy!!!
    Wednesday, July 23, 2008 10:31 AM
  • Question
    Sign in to vote
    2
    Sign in to vote
    I did the following and it worked, mostly quoted from the previous post, bolded where I have added to it:

    Delete the failed DTC resource
    Delete MSDTC shared folder from the quorum disk and or the other shred disk if in a different resource group
    On Node 1:
    * Stop Cluster service, disable it
    * Remove Enable network DTC access
    * Run msdtc -uninstall
    * Verify success in event log
    * Delete registry keys:
    HKEY_CLASSES_ROOT\CID
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
    * Reboot
    * Reinstall Enable network DTC access

    Node 2
    * Stop Cluster service     , disable it
    * Remove Enable network DTC access
    * Run msdtc -uninstall
    * Verify success in event log
    * Delete registry keys
    HKEY_CLASSES_ROOT\CID
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDTC
    * Reboot
    * Reinstall Enable network DTC access

    Node 1:
    *Enable and start the cluster service
    *Start Cluadmin
    *Create the MSDTC resource in the correct group
    *run "msdtc -install"

    Node 2:
         *Enable and start the cluster service
     *run "msdtc -install"

    Then bring MSDTC online and fail the group containing the MSDTC reources over to the second node to verify that the DTC
    resource comes online successfully on the second node. After that, reboot
    both servers and verify that the resource would fail over properly to both
    nodes with the rest of the group.
    Friday, June 26, 2009 11:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The above procedure worked for me.  Thanks!

    When creating the MSDTC resource, I also had to create the MSDTC dependencies (Net Name, IP).

     

    -mike

    Saturday, October 16, 2010 5:22 PM