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:
Server Execution failed
The following error is logged in the event log:
The server <clsid> did not register with DCOM within the required timeout.
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.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Article ID: 253854 - Last Review: October 23, 2003 - Revision: 3.2
- Microsoft COM+ 2.0 Standard Edition, when used with:
- the operating system: Microsoft Windows 2000
|kbbug kbdcom kbdll kbpending KB253854|