IProcessInitializer Interface Does Not Register with Microsoft COM+ Rollups

Article translations Article translations
Article ID: 319776 - View products that this article applies to.
This article was previously published under Q319776
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

Symptoms

When you try to start a COM+ application, the following error message may appear in the event log:
A COM+ service (such as Queued Components or Compensating Resource Manager) failed to start.
The service GUID and HRESULT are:{6BEEE4D3-B211-4BC3-8251-FB7BB1D1EB1D}
Server Application ID: {FCDDB75F-ED7D-4528-8C59-FE80C586980A}
Server Application Name: MPSServer
The serious nature of this error has caused the process to terminate.
Error Code = 0x80004002 : No such interface supported

Cause

This problem occurs if you implement the IProcessInitializer interface in a component that resides in a COM+ application. The COM+ Rollup fixes do not register the IProcessInitializer interface in the Comsvcs.dll file.

Resolution

To resolve this problem, manually register Comsvcs.dll.

From a command prompt, navigate to your \%SystemRoot%\System32 directory. To register the interface, type regsvr32 comsvcs.dll.

Status

Microsoft has confirmed that this is a problem in Microsoft Windows 2000.

Microsoft is researching this problem and will post more information in this article when the information becomes available.

Properties

Article ID: 319776 - Last Review: October 26, 2013 - Revision: 2.0
Applies to
  • Microsoft COM+ 1.0
Keywords: 
kbnosurvey kbarchive kbbug kberrmsg KB319776

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