Deciphering an 0xc103798a Exchange Server setup error code

Microsoft Exchange Server 2003 and Exchange 2000 Server can experience a setup failure with the error code:

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.

What this cryptic error doesn't tell you is that COM+ is involved. In fact, if you dig into the logs generated by the Exchange Server setup utility, you won't see any mention of the COM+ catalog there either.

The closest you may get is this error: The command regsvr32 /s cdowfevt.dll failed, returning error code 5 (Access is denied).

The COM+ catalog is a kind of registry for all the COM+ components currently installed in a given instance of Windows. Unfortunately, even in Windows Server 2003, it can be damaged in such a way that it will prevent certain kinds of products from installing or running at all.

If you experience a COM+ complication during an Exchange Server setup, you should attempt to repair the damaged COM+ catalog. This process requires some careful work with system fi

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft Exchange Server 2003 Changing email address formats in Exchange Server 2003 Should you remove .STM files from Exchange Server 2003? Troubleshoot 'System Attendant' error messages in OWA Configuring the default recipient policy in an Exchange 2003 environment Removing old disclaimers from Exchange Server 2003 ExMerge gotchas to watch for when migrating Exchange 2003 mailboxes Recovering deleted items after an Exchange 2003 migration Linking two Exchange 2003 servers in different forests Microsoft Exchange Server virtualization tutorial Installing Exchange Server 2003 and a domain controller on the same hardware Microsoft Exchange Server 2003 Research Microsoft Exchange 2000 Server Troubleshooting Outlook calendar errors on a BlackBerry device How to move Exchange 2000 to new server hardware Error 1053: Exchange System Attendant service could not start Solve server problems with the Exchange Troubleshooting Assistant tool Move mailboxes to Exchange 2007 after Windows upgrade Third-party tools that modify NDRs for oversized email IP address changes for an Exchange 2000 recovery server Exchange Server 2003 tips and tricks -- 7 tips in 7 minutes How to enable Exchange Server public folder logging Exchange Server error message: 'A non-delivery report with a status code of 5.4.0 was generated for recipient' Microsoft Exchange 2000 Server Research Exchange Server Deployment and Migration Advice Exchange Server 2007: Email archiving tips and hosted services trends Exchange Insider e-zine ExMerge gotchas to watch for when migrating Exchange 2003 mailboxes Mailbox viewing problems after migrating to Exchange 2007 Migrating mailboxes across domains with the Exchange Management Console Recovering deleted items after an Exchange 2003 migration Linking two Exchange 2003 servers in different forests Installing Exchange Server 2003 and a domain controller on the same hardware Outlook Web Access issues after an Exchange 2003 migration When to use Move Mailbox Wizard or ExMerge to move Exchange mailboxes

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary E2K  (SearchExchange.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

les and will require that the server be offline for some time.

If your server was upgraded from a previous edition of Windows Server, it might explain how the damage originated.

If this was a fresh install of Windows, you might be better served by simply reinstalling Windows completely again. But this time around, pay close attention to any possible post-installation configuration (for instance, third-party software) that might have caused the COM+ catalog problem.

After repairing the damaged COM+ catalog, you'll need to remove and reinstall IIS, and then reinstall Exchange Server and apply any relevant service packs.

About the author: Serdar Yegulalp is editor of Windows Insight, a newsletter devoted to hints, tips, tricks, news and goodies for all flavors of Windows users.

Do you have comments on this tip? Let us know.

Please let others know how useful this tip was via the rating scale below. Do you have a useful Exchange Server or Microsoft Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a thank-you gift only an IT geek could love.

Rate this Tip To rate tips, you must be a member of SearchExchange.com. Register now to start rating these tips. Log in if you are already a member. DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.