How to: Work Around COM+ System Configuration Check Failure in SQL Server Setup
Microsoft SQL Server 2005 Setup checks that COM+ is properly configured. If configuration errors are found, Setup will continue, but the following warning appears in the System Configuration Check (SCC) report:
"If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup."
COM+ errors can result when Microsoft Distributed Transaction Coordinator (MS DTC) is not running or, in the case of Microsoft Cluster Server, if MS DTC is not a clustered resource. COM+ depends upon MS DTC, and the Message Queue Task in Integration Services depends upon COM +. If COM+ errors occur, the Message Queue Task in Integration Services will not be available until the COM+ system is properly configured.
To use Message Queuing (also known as MSMQ), ensure that MS DTC is running and properly configured. If SQL Server is installed on a cluster, MS DTC must be a cluster resource.
Use the following procedures to reinstall COM+.
To install the Component Services snap-in
From the Windows desktop, click Start and then click Run.
In Open, type MMC, and then click OK.
In the Console window, click File on the menu bar, and then click Add/Remove Snap-in.
In the Add/Remove Snap-in window, click Add.
In the Add Standalone Snap-in window, select Component Services from the list of snap-ins, and then click Add.
Click Close to close the Add Stand-alone Snap-in window, and then click OK to close the Add/Remove Snap-in window.
In the Console Root\Component Services window, expand the Component Services tree. This is where any error message would occur if there was a problem with COM+.
Run SQL Server 2005 Setup again. If you get an error message, reinstall COM+.
To reinstall COM+
From Add or Remove Programs in Control Panel, click Add/Remove Windows Components.
In the Windows Components Wizard, click Next without making any selection changes.
Click through to complete the wizard, and then run SQL Server 2005 Setup again.