Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: DLLHOST.EXE Causes an Error with RPC_C_AUHN_LEVEL_NONE


Symptoms

Dllhost.exe is the system-provided surrogate that is used by a COM DLL (in- process) server to run in its own separate process. When the default (machine-wide) authentication is set to None on Windows NT 4.0, an error occurs during the launching of Dllhost.exe and it terminates. The client's creation API gets a CO_E_SERVER_EXEC_FAILURE error. This error does not occur under Windows 95.

↑ Back to the top


Cause

This is caused by a bug in the security initialization for Dllhost.exe.

↑ Back to the top


Resolution

Set the machine-wide COM authentication level to a value other than None to resolve this problem. You can use the DCOMCNFG utility to change the machine-wide authentication level. If the machine-wide authentication level must be None, then you can use a custom surrogate instead of Dllhost.exe.

↑ Back to the top


Status

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

This problem was corrected in Windows NT Service Pack 4 and Windows 2000.

↑ Back to the top


More Information

Steps to Reproduce Behavior

  1. Use DCOMCNFG to set the machine-wide authentication level to None. To do this, run Dcomcnfg.exe, select the Default Properties tab and from the Default Authentication Level list box choose None. Click OK.
  2. Run OLEVIEW and select any in-process DLL server object. Select the Implementation tab, and select the Use Surrogate Process check box. Select the Registry tab (this will add the DllSurrogate named value under the AppID key). From the OLEVIEW menu, choose Object...CoCreateInstance flags, select CLSCTX_LOCAL_SERVER and deselect all other items.
  3. Instantiate the object from OLEVIEW. You will get the error message.

↑ Back to the top


Keywords: kb, kboswinnt400sp4fix, kboswin2000fix, kbfix, kbdsupport, kbbug, kbbillprodsweep

↑ Back to the top

Article Info
Article ID : 171359
Revision : 7
Created on : 8/20/2020
Published on : 8/20/2020
Exists online : False
Views : 190