BUG: COM Component Is Not Initialized When You Specify Explicit Path to DllHost.exe as Surrogate (253854)
The information in this article applies to:
- Microsoft COM, when used with:
- the operating system: Microsoft Windows 2000
This article was previously published under Q253854 SYMPTOMS
When you explicitly set the path to DllHost.exe as the surrogate for a Component Object Model (COM) component, you may receive the following error message when you try to instantiate the component:
CoGetClassObject failed
Server Execution failed
CO_E_SERVER_EXEC_FAILURE (0x80080005)
The following error is logged in the event log:
The server <clsid> did not register with DCOM within the required timeout.
RESOLUTION
Instead of explicitly specifying the path to DllHost.exe, leave the path NULL. You can do this with the OleView tool by performing the following steps:
- Start OleView. To do this, click Start, point to Programs, point to Microsoft Visual Studio 6.0, point to Microsoft Visual Studio 6.0 Tools, and then click OleView.
- In the left window pane of OleView, expand the Object Classes root item of the tree control. Under the All Objects item, select your COM component.
- Click the Implementation tab for the COM component found in the right window pane. Click to select the Use Surrogate Process check box, and leave the Path to the Customer Surrogate text box blank.
- Select the Registry tab in the right window pane. By selecting the Registry tab, the changes that you made in step 3 are committed to the registry, and you should see the DllSurrogate named value under the AppID entry in the Registry tab window. The DllSurrogate entry shown in the window will have a NULL value.
By configuring the DllSurrogate named value to have a NULL value, the COM component will run under the System Surrogate DllHost.exe.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 10/23/2003 |
---|
Keywords: | kbbug kbDCOM kbDLL kbpending KB253854 |
---|
|