FIX: RPC on Windows 2000 Server returns random "access denied" or "invalid security" error messages to the client
This article has been archived. It is offered "as is" and will no longer be updated.
When a client makes local Component Object Model (COM) calls or remote procedure calls (RPCs) on a computer that is running Microsoft Windows 2000 Server, the server may return random "Access Denied" or "Invalid Security Context" error messages to the client.
When the server is experiencing a high load, or a high call volume, you may receive the error messages that are described in the "Symptoms" section of this article because a distributed COM (DCOM) client incorrectly deletes a security context that is still being used. When the server tries to impersonate the client, it cannot because the security context is no longer valid. The server then returns an error message back to the client..
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------- 03-Oct-2003 22:10 5.0.2195.6824 945,936 Ole32.dll 03-Oct-2003 22:10 5.0.2195.6862 432,912 Rpcrt4.dll 03-Oct-2003 22:10 5.0.2195.6824 192,272 Rpcss.dll 19-Sep-2003 23:51 184.108.40.206 6,656 Spmsg.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New naming schema for Microsoft Windows hotfix packagesFor additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 829589 - Last Review: 10/26/2013 19:54:35 - Revision: 1.6
Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Advanced Server
- kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB829589