How To Fix OL858 - Error in asynchronous method start: Maximum number of sessions reached

SAP Error Message - Details

• Message type: E = Error

• Message class: OL - Workflow object types: Run-time system

• Message number: 858

• Message text: Error in asynchronous method start: Maximum number of sessions reached

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 OL858 - Error in asynchronous method start: Maximum number of sessions reached ?

  The SAP error message OL858, which states "Error in asynchronous method start: Maximum number of sessions reached," typically occurs when the maximum number of allowed sessions for a user or for the system has been reached. This can happen in various scenarios, particularly in environments with high user activity or when there are background jobs that consume sessions.
  Causes:
  
  Session Limit Reached: Each user has a limit on the number of concurrent sessions they can open. If this limit is reached, new session requests will be denied.
  System-Wide Session Limit: The SAP system itself has a maximum number of sessions that can be active at any given time. If this limit is reached, no new sessions can be created.
  Long-Running Transactions: If there are long-running transactions or background jobs that are not releasing sessions, they can contribute to reaching the session limit.
  Configuration Issues: Incorrect configuration of session parameters in the SAP system can lead to this error.
  
  Solutions:
  
  
  Check User Session Limits:
  
  Go to transaction SU01 and check the user profile settings for the user experiencing the issue. Ensure that the "Maximum Number of Sessions" is set appropriately.
  
  
  
  Monitor Active Sessions:
  
  Use transaction SM04 to monitor active user sessions. Identify users with many open sessions and ask them to log off unnecessary sessions.
  Use transaction SM50 to check for long-running processes that may be holding sessions.
  
  
  
  Increase Session Limits:
  
  If necessary, consider increasing the session limits. This can be done by adjusting the parameters in the instance profile:
  
  rdisp/max_wprun_time: Maximum time a work process can run.
  rdisp/wp_no_dia: Number of dialog work processes.
  rdisp/wp_no_btc: Number of background work processes.
  
  
  After making changes, restart the SAP instance for the changes to take effect.
  
  
  
  Review Background Jobs:
  
  Check for any background jobs that may be consuming sessions and ensure they are completing successfully. Use transaction SM37 to monitor background jobs.
  
  
  
  Session Cleanup:
  
  If there are orphaned sessions or processes, consider using transaction SM12 to delete any locked entries that may be causing issues.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  
  Related Information:
  
  SAP Documentation: Review the official SAP documentation for session management and configuration settings.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  System Monitoring Tools: Utilize SAP Solution Manager or other monitoring tools to keep track of system performance and session usage.
  
  By following these steps, you should be able to diagnose and resolve the OL858 error effectively.