FIX: Drag-and-Drop Procedure Does Not Work If CoInitializeSecurity() Authentication Level Is Set to NONE

Article translations Article translations
Article ID: 275913 - View products that this article applies to.
This article was previously published under Q275913
Expand all | Collapse all

SYMPTOMS

If you set the authentication level to NONE, drag-and-drop procedures may not work properly. You can set the authentication level to NONE by using the CoInitializeSecurity function and setting the fifth parameter (authentication level) to RPC_C_AUTHN_LEVEL_NONE. You can also set the authentication level by using a CoSetProxyBlankey call, or by using the Distributed Version of Component Object Model (COM) Configuration utility (Dcomcnfg.exe) or Registry Editor to set the authentication level at the computer or application level. If you use the RPC_CAUTHN_LEVEL_NONE setting for either the client or server, drag-and-drop procedures do not work.

The same code works correctly in Microsoft Windows NT 4.0.

CAUSE

The drag-and-drop procedure uses special functions to initialize the distributed version of COM. This problem occurs because Windows 2000 does not promote authentication levels of NONE to PKT_PRIVACY for local calls. Therefore, Windows 2000 uses the RPC_C_AUTHN_LEVEL_NONE authentication level.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
  Date         Time     Version         Size        File name
  --------------------------------------------------------------
  10/16/2000   04:51p   2000.2.3465.0     165,648   Catsrv.dll
  10/16/2000   04:51p   2000.2.3465.0     571,152   Catsrvut.dll
  10/16/2000   04:51p   2000.2.3465.0      95,504   Clbcatex.dll
  10/16/2000   04:51p   2000.2.3465.0     508,176   Clbcatq.dll
  10/16/2000   04:51p   2000.2.3465.0      37,648   Colbact.dll
  10/16/2000   04:51p   2000.2.3465.0   1,397,520   Comsvcs.dll
  10/16/2000   04:49p   2000.2.3465.0     804,096   Dtcsetup.exe
  10/16/2000   04:51p   2000.2.3465.0     234,256   Es.dll
  10/16/2000   04:51p   2000.2.3465.0     641,296   Msdtcprx.dll
  10/16/2000   04:51p   2000.2.3465.0   1,120,528   Msdtctm.dll
  10/16/2000   04:51p   2000.2.3465.0     150,288   Mtstocom.exe
  10/16/2000   04:51p   2000.2.3465.0      52,496   Mtxclu.dll
  10/16/2000   04:51p   2000.2.3465.0      23,824   Mtxdm.dll
  10/16/2000   04:51p   2000.2.3465.0     104,208   Mtxoci.dll
  10/16/2000   05:52p   5.0.2195.2500     938,768   Ole32.dll
  10/16/2000   05:52p   5.0.2195.2500     184,592   Rpcss.dll
  10/16/2000   04:51p   2000.2.3465.0     382,736   Txfaux.dll
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

Properties

Article ID: 275913 - Last Review: February 23, 2007 - Revision: 3.3
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
Keywords: 
kbhotfixserver kbqfe kbbug kbfix kbwin2000presp2fix KB275913

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