Exchange Setup does not work because of a COM+ issue and error code 0xc103798a

Article translations Article translations
Article ID: 318731 - View products that this article applies to.
This article was previously published under Q318731
Expand all | Collapse all

SYMPTOMS

If you install Exchange 2000 Server or Exchange Server 2003, or apply an Exchange 2000 service pack, Setup may not work, and you may receive the following error message:
Setup failed while installing sub-component miscellaneous Atom with error code 0xc103798a (please consult the installation logs for a detailed description). You may cancel the installation or try the failed step again.
The Exchange 2000 Setup Progress log may contain either:
  • A series of time-outs:
    [23:49:27] ++++ Starting interpreter on file d:\server\setup\i386\exchange\Misc.ins ++++
    [23:49:27] Interpreting line <CreateProcess:D:\EXCHSRVR\bin;regsvr32 /s cdowf.dll;60000>
    [23:49:27] Process created ... waiting (60000)
    [23:49:28] Process has exited with 00000000
    [23:49:28] Interpreting line <CreateProcess:D:\EXCHSRVR\bin;regsvr32 /s cdowfevt.dll;60000>
    [23:49:28] Process created ... waiting (60000)
    [23:49:30] Process has exited with 00000000
    [23:49:30] Interpreting line <CreateProcessSafe:d:\server\setup\i386\exchange\wmi;d:\server\setup\i386\exchange\wmi\wmicons.exe /s;4294967295>
    [23:49:30] Process created ... waiting (-1)
    [23:49:35] Ignoring exit code 00000000
    [23:49:35] Interpreting line <CreateProcess:D:\EXCHSRVR\bin;regsvr32 /s exwmi.dll;60000>
    [23:49:35] Process created ... waiting (60000)
    [23:49:35] Process has exited with 00000000
    [23:49:35] Interpreting line <CreateProcess:C:\WINNT\System32\WBEM;C:\WINNT\System32\WBEM\mofcomp.exe "C:\WINNT\System32\WBEM\exwmi.mof";600000>
    [23:49:35] Process created ... waiting (600000)
    [23:59:35] CreateProcess timed out before the spawned process completed!
  • A failure to register Cdowfevt.dll:
    [19:21:33] The command

    regsvr32 /s cdowfevt.dll

    failed, returning error code 5 (Access is denied.).
    [19:21:33] mode = 'Update' (61957) CBaseAtom::ScSetup (N:\admin\src\udog\setupbase\basecomp\baseatom.cxx:782)
    Error code 0XC103798A (31114): An internal component has failed.

RESOLUTION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

To resolve this issue:
  1. Make sure that the Microsoft Distributed Transaction Coordinator service (MS DTC) is started. By default, this service is installed with Microsoft Windows 2000. If this service is stopped, the error messages that are mentioned in the "Symptoms" section of this article may occur. The MS DTC service is required by Microsoft Exchange setup. The MSDTC service is also required during the installation of an Exchange hotfix or service pack.

    If the MS DTC service does not start, you may have to reinstall the service.

    For additional information about how to reinstall the service, click the following article number to view the article in the Microsoft Knowledge Base:
    279786 How to reinstall MS DTC for a nonclustered Windows 2000 Server
    COM+ is required to register Cdowfevt.dll, and COM+ requires that the MS DTC service be running on the server. The MS DTC service must be running for either Exchange Setup or an Exchange 2000 service pack installation to complete properly. This applies to both clustered and non-clustered Exchange servers.

    On a cluster, the MS DTC service must be running on both nodes. For additional information about this issue on a clustered Exchange 2000 server, and about how to install the MS DTC service on a cluster, click the following article number to view the article in the Microsoft Knowledge Base:
    312316 Setup does not install Exchange 2000 on a cluster if the MSDTC resource is not running
  2. If the MS DTC service is running, the error messages that are mentioned in the "Symptoms" section of this article may be caused by a damaged COM+ catalog. This may be the cause even if you can use the Component Services management console (COM+ Explorer) without experiencing any issues. You can usually repair a damaged COM+ catalog by reinstalling COM+. To reinstall COM+:
    1. In the %SystemRoot%\System32 folder, rename the Clbcatq.dll file to ~clbcatq.dll. Make sure that you include the tilde (~) at the beginning of the file name. If there is already a ~clbcatq.dll file in the %SystemRoot%\System32 folder, move the ~clbcatq.dll file out of the folder or rename the ~clbcatq.dll file first. If the file is in use, you may have to use the rename command from an MS-DOS prompt to rename the file.
    2. Save and delete the
      HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
      key. To do so:
      1. Start Registry Editor (Regedt32.exe).
      2. Locate and click the following key in the registry:
        HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
      3. On the Registry menu, click Save Key, and then save the key to a file.
      4. Make sure that the
        HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
        key is still selected. Either press the DELETE key or right-click the key, and then click Delete.
      5. Quit Registry Editor.
    3. In Control Panel, open the Add or Remove Programs tool, and then open the Add/Remove Windows Components tool. Do not make any changes, just click Next. This reinstalls COM+.
  3. If reinstalling COM+ does not work, you may have to rebuild the COM+ catalog entirely. Typically, you have to start in Safe mode to keep Windows File Protection from reversing the changes. To rebuild the COM+ catalog:
    1. Start in Safe mode.
    2. In the %SystemRoot%\System32 folder, rename the Clbcatq.dll file to ~clbcatq.dll. Even in Safe mode, this file will be in use. However, you can use the rename command from a command prompt to rename the file.
    3. In the %SystemRoot% folder, make a backup copy of the Registration folder, and then try to delete the contents of the folder. Typically, there is one file in the Registration folder that is in use and cannot be deleted. However, after you restart the server in Normal mode, you can remove the file.
    4. Save and delete the
      HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
      key:
      1. Start Registry Editor.
      2. Locate and click the following key in the registry:
        HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
      3. On the Registry menu, click Save Key, and then save the key to a file.
      4. Make sure that the
        HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
        key is still selected. Either press the DELETE key or right-click the key, and then click Delete.
      5. Quit Registry Editor.
    5. Start in Normal mode.
    6. In the %SystemRoot% folder, remove the Registration folder. At this point any remaining files in the folder should no longer be in use.
    7. In Control Panel, open the Add or Remove Programs tool, and then open the Add/Remove Windows Components tool. Do not make any changes, just click Next. This reinstalls COM+, which builds a new registration catalog.
  4. After you complete the preceding steps, you must reinstall any programs that have to register with COM+. On an Exchange server, you must at minimum:
    1. Remove Internet Information Services (IIS), and then install it again.
    2. In the Exchange Setup program, reinstall Exchange.
    3. Apply any Exchange 2000 necessary service packs.
After you create the clean COM+ catalog, you should be able to successfully reinstall Exchange 2000 and the service pack update.

Note This article applies to both:
  • Exchange on a computer that is running Microsoft Windows 2000 Server. -and-

  • Exchange on a computer that is running Microsoft Small Business Server 2000.

Properties

Article ID: 318731 - Last Review: December 3, 2007 - Revision: 5.6
APPLIES TO
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Windows Small Business Server 2003 Premium Edition
  • Microsoft Windows Small Business Server 2003 Standard Edition
Keywords: 
kbprb KB318731

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com