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.

You may receive an "RPC server is too busy to complete this operation" error message when you try to log on to a computer that is running Windows Server 2003 with Service Pack 1


View products that this article applies to.

Symptoms

When you try to log on to a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1), you may receive the following error message:
Title: Logon Message
Msg: The System cannot log you on due to the following error:
The RPC server is too busy to complete this operation. Please try again or consult your system administrator.
Additionally, when you enable Net Logon debug logging on the computer, an error message that is similar to the following is logged in the %windir%\debug\netlogon.log file:
<timestamp> [CRITICAL] WW001: NlSessionSetup: Session setup: cannot I_NetServerReqChallenge 0xc0020018
<timestamp> [MISC] Eventlog: 5719 (1) "<domain>" 0xc0020018 c0020018 .... <timestamp> [SESSION] <domain>: NlSetStatusClientSession: Set connection status to c000005e
Note This problem only occurs when the Windows Server 2003 SP1-based computer is under heavy load. The problem of heavy load is usually caused by automated logon attempts by programs that logon to a service or database that resides on the server. If this problem occurs when the program makes an authentication request, the program receives an "STATUS_NO_LOGON_SERVERS" error message.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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.Note This problem can affect both client components and server components in the Netlogon process. If you experience this problem, we recommend that you apply this hotfix to all member servers and to all domain controllers that are running Windows Server 2003 with Service Pack 1.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 SP1 installed on the computer.

Note Windows Server 2003 SP1 is included in x64-based versions of Windows Server 2003.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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.
Windows Server 2003, 32-bit x86-based versions with Service Pack 1
File nameFile versionFile sizeDateTimePlatform
Netlogon.dll5.2.3790.2503419,32806-Aug-200504:30x86

Windows Server 2003, 64-bit Itanium-based versions with Service Pack 1
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Netlogon.dll5.2.3790.2503978,94405-Aug-200513:48IA-64SP1SP1QFE
Wnetlogon.dll5.2.3790.2503419,32805-Aug-200513:48x86SP1WOW

Windows Server 2003, 64-bit x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Netlogon.dll5.2.3790.2503681,47205-Aug-200513:48x64SP1SP1QFE
Wnetlogon.dll5.2.3790.2503419,32805-Aug-200513:48x86SP1WOW

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

For more 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

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003sp2fix, kbHotfixServer, kberrmsg, kbqfe, KB905700

↑ Back to the top

Article Info
Article ID : 905700
Revision : 4
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 679