A distributed (RPC) application has tried to reach a server that is temporarily too busy. The server may need more resources.
M307765 provides information on how to troubleshoot the error message "RPC Server Is Too Busy to Complete This Operation".
M177446 has information on how to test Microsoft Remote Procedure Call performance.
The following articles have more information on this error:
- M170582 - Backup Exec version 6.11 Rev. 184 installs an RPC service that conflicts with the standard Windows NT RPC service.
- M191370 and M232476 - Increasing the MaxMpxCt parameter on the remote server, may alleviate this problem.
- M257187 - If the time server is not available and the time difference between domain controllers drifts beyond the skew allowed by Kerberos, authentication between the two domain controllers may not succeed and this RPC error messages can result.
- M277776 - This problem can be caused by a heap damage problem in Services.exe that results in an access violation error message. The problem causes the RPC service to be unable to dispatch work to RPC programs that are running on the server.
Symbolic name: RPC_S_SERVER_TOO_BUSY
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.