Article ID: 312316
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition, when used with:
- Microsoft Windows 2000 Standard Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
This article was previously published under Q312316
SYMPTOMS
If you install Microsoft Exchange 2000 Server or an Exchange 2000 service pack on one node of a cluster that is running Microsoft Windows 2000 Server or Microsoft Windows Server 2003, the Setup program may not work. The Exchange 2000 Server Setup Progress.log may contain the following information:
[09:02:13] Interpreting line <CreateProcess:C:\exchsrvr\bin;regsvr32 /s cdowfevt.dll;60000>
[09:02:13] Process created ... waiting (60000)
[09:02:14] Process has exited with 0x000005
[09:02:14] The command regsvr32 /s cdowfevt.dll failed, returning error code 5 (Access is denied.).
ScCreateProcess (K:\admin\src\libs\exsetup\hiddenw1.cxx:1763)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] CInsParser::ScProcessLine (K:\admin\src\libs\exsetup\hiddenw1.cxx:1226)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] Processing file '\\server\prop\e2k_rtm\enterprise\setup\i386\exchange\Misc.ins', at or near line 2
(CreateProcess:C:\exchsrvr\bin;regsvr32 /s cdowfevt.dll;60000)
CInsParser::ScProcessLine (K:\admin\src\libs\exsetup\hiddenw1.cxx:486)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] Registry file name: '\\server\prop\e2k_rtm\enterprise\setup\i386\exchange\Misc.ins'
CRegistryManager::ScProcessFile (K:\admin\src\udog\setupbase\tools\regmgr.cxx:95)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] Filename = '%sourcedir%\Misc' CBaseAtom::ScAddRegistryKeys (K:\admin\src\udog\setupbase\basecomp\baseatom.cxx:1157)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] CBaseAtom::ScAdd (K:\admin\src\udog\setupbase\basecomp\baseatom.cxx:860)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] Service = '' CBaseServiceAtom::ScAdd (K:\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:196)
Error code 0XC103798A (31114): An internal component has failed.
[09:02:14] mode = 'Install' (61953) CBaseAtom::ScSetup (K:\admin\src\udog\setupbase\basecomp\baseatom.cxx:775)
Error code 0XC103798A (31114): An internal component has failed.
If you are running Exchange 2000 Setup on a computer that is running Windows Server 2003, you may see information that is similar to the following in the Setup Progress.log file:
Setup failed while installing sub-component miscellaneous atom with error code 0XC103798A.
CAUSE
This issue may occur if Microsoft Distributed Transaction Coordinator (MSDTC) is not running on all the nodes of a cluster. The registration of Cdowfevt.dll requires COM+. This requires that the MSDTC service be running on the server.
Microsoft only supports running MSDTC on cluster nodes as a cluster resource. MSDTC running in stand-alone mode on a cluster is not a recommended or supported configuration. Using MSDTC as a non-clustered resource on a Microsoft Cluster service cluster is a problematic configuration as transactions may be orphaned if a cluster failover causes data corruption.
For additional information, visit the following Microsoft Web site:
To set up COM+ on a Windows 2000 cluster, you must run a special program that is named Comclust.exe.
To set up COM+ on a Windows Server 2003 cluster, you must create an MSDTC resource directly by using Cluster Administrator (Cluadmin.exe).
RESOLUTION
To resolve this issue on a Windows 2000 cluster:
- Click Start menu, and then click Run.
- In the Run box, type cmd, and then click OK.
- At The Command Prompt window, on the command line, run the following command:
Comclust.exe
Note Repeat these steps on each of the remaining nodes of the cluster, one node at a time.
When you run Comclust.exe, Comclust.exe creates an MSDTC resource in the cluster and allows sufficient MSDTC functionality for Cdowfevt.dll to register successfully.
To resolve this issue on a Windows Server 2003 cluster, use Cluster Administrator to create an MSDTC resource in the Windows Server 2003 cluster. Note that it is not necessary to dedicate a cluster resource group for MSDTC if Exchange is the only application on this cluster. The existing Cluster Group can be used for this light-use DTC requirement.
For more information about how to configure MSDTC, 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
Additional query words: XADM 0XC103798A comclust cdowfevt.dll msdtc dtc cluster MSCS
Keywords: kbpending kbprb KB312316
