Microsoft KB Archive/307765

= How to Troubleshoot the Error Message &quot;RPC Server Is Too Busy to Complete This Operation&quot; =

Article ID: 307765

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0 Enterprise Edition
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q307765



SUMMARY
This article describes how to troubleshoot and diagnose remote procedure call (RPC) error messages.

You may encounter any one of the following symptoms:  When you open Event Viewer or any program that relies on RPC, you receive the following error message:

RPC is too busy to complete the transaction

 The computer is very slow to log on to or off from. You cannot ping the server from the network. RPC-related requests fail.

These symptoms continue to occur even after you apply the RPCrt4.dll hotfix that is described in the following Microsoft Knowledge Base article:

277776 Services Access Violation Because of Heap Damage



Troubleshooting
 Follow the directions in the &quot;Troubleshooting RPC&quot; section in the following article in the Microsoft Knowledge Base:

197814 HOWTO: Troubleshoot RPC Errors

 Disable all third-party services.</li> Attempt to ping the computer from the network.</li> Attempt to open Event Viewer, or the Control Panel Services program.</li></ol>

If you cannot successfully complete each of these steps, an invalid string entry in the SRVCOMMENT value may exist.

This registry value is not present by default; the key and value may be added by any service and the added values are not recognized by the operating system until the next reboot, which is typically when this behavior is first noticed.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this behavior: <ol> Start Registry Editor (Regedt32.exe).</li> Locate the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

</li> On the Security menu, click Permissions. Make sure that the Everyone group has only read-only permissions, check for any other accounts other than System and set those to read only, and then click OK.</li> Open the value and make sure that a valid character exists. Also, check by backspacing across any entry to find out if a valid character or empty field is in the string. This string can be an empty string. By following these steps, you can monitor event logging to capture the failed write attempt by a third-party program.</li> Quit Registry Editor.</li> Restart the computer.</li></ol>

Sample Registry Values
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters &quot;NullSessionPipes&quot;=hex(7):43,4f,4d,4e,41,50,00,43,4f,4d,4e,4f,44,45, 00,53,51,4c,5c,51,55,45,52,59,00,53,50,4f,4f,4c,53,53,00,4c,4c,53,52,50,43, 00,45,50,4d,41,50,50,45,52,00,4c,4f,43,41,54,4f,52,00,00,61,6c,65,72,74, 6d,61,6e,61,67,65,72,00,00 &quot;NullSessionShares&quot;=hex(7):43,4f,4d,43,46,47,00,44,46,53,24,00,00 &quot;Size&quot;=dword:00000003 &quot;Lmannounce&quot;=dword:00000000 &quot;IRPStackSize&quot;=dword:00000007 &quot;CachedOpenLimit&quot;=dword:00000000 &quot;srvcomment&quot;&quot;&quot; <<== THIS VALUE IS NOT INSTALLED BY DEFAULT

Additional Troubleshooting Information
In troubleshooting this symptom, you would typically want to save the specified registry key by exporting the key. In this scenario, if you do not have a tape backup of the entire registry, you will not be able to import the key to reproduce the issue after testing.

A tape backup copies the registry and keeps all malformed characters intact, whereas exporting the registry key from another source allows the value to be corrected to a valid character.

When you troubleshoot this issue, navigate to the specified registry location. In the default view in Registry Editor, you may observe that the string value for SRVCOMMENT seems to be only an open quote followed by a closed quote. No value appears to be specified.

When you double-click the SRVCOMMENT key, you access the string editor, and it is at this point the malformed character in the string may become visible.

<div class="references_section">