How To Fix RM720 - All servers are busy. & attempt after 30 seconds

SAP Error Message - Details

• Message type: E = Error

• Message class: RM - Messages for Repetitive Manufacturing

• Message number: 720

• Message text: All servers are busy. & attempt after 30 seconds

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RM720 - All servers are busy. & attempt after 30 seconds ?

  The SAP error message RM720 "All servers are busy. Please try again after 30 seconds" typically indicates that the SAP system is experiencing high load or resource contention, which prevents it from processing the current request. This can happen for various reasons, including:
  Causes:
  
  High System Load: The SAP application servers may be overloaded with requests, leading to a situation where they cannot handle additional requests.
  Insufficient Resources: The hardware resources (CPU, memory, etc.) allocated to the SAP system may be insufficient to handle the current workload.
  Long-Running Processes: There may be long-running background jobs or transactions that are consuming resources and blocking other requests.
  Configuration Issues: Incorrect configuration of the SAP system or application servers can lead to inefficient resource utilization.
  Network Issues: Network latency or connectivity issues can also contribute to the perception that servers are busy.
  
  Solutions:
  
  Monitor System Performance: Use transaction codes like ST03N (Workload Analysis) and ST06 (Operating System Monitor) to analyze system performance and identify bottlenecks.
  Check Background Jobs: Use transaction SM37 to check for long-running or stuck background jobs that may be consuming resources.
  Increase Resources: If the system is consistently under heavy load, consider scaling up the hardware resources (CPU, memory) or adding additional application servers to distribute the load.
  Optimize Configuration: Review and optimize the configuration of the SAP system, including parameters related to memory allocation and process handling.
  Load Balancing: Ensure that load balancing is properly configured across application servers to distribute requests evenly.
  Review Network Performance: Check for any network issues that may be affecting communication between clients and the SAP servers.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to performance issues and error RM720 for specific recommendations and patches.
  SAP Community: Engage with the SAP Community forums to see if other users have experienced similar issues and what solutions they found effective.
  System Logs: Review system logs (transaction SM21) for any errors or warnings that may provide additional context for the issue.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.