How To Fix 01781 - &1 is displayed in a new session (in &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: 01 -

• Message number: 781

• Message text: &1 is displayed in a new session (in &2)

What causes this issue?

For the selected role, transaction PFCG should be started in system &V2&
and displayed in a new session. For technical reasons, it is not
possible to display error messages if the new session is not started. In
this case, display the role in the same session.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

For additional troubleshooting, see SAP Note 1053026

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 01781 - &1 is displayed in a new session (in &2) ?

  The SAP error message "01781 &1 is displayed in a new session (in &2)" typically indicates that a user is trying to perform an action that requires a new session, but the system is unable to do so due to certain restrictions or settings.
  Cause:
  
  Session Limit: The user may have reached the maximum number of allowed sessions. SAP systems typically have a limit on how many sessions a user can open simultaneously.
  User Profile Settings: The user profile may have restrictions on the number of sessions that can be opened.
  System Configuration: The SAP system may be configured to limit the number of sessions for performance reasons.
  Transaction Behavior: Some transactions or actions inherently require a new session to be opened, and if the system cannot comply, this error may occur.
  
  Solution:
  
  Close Unused Sessions: Check the currently open sessions and close any that are not needed. You can do this by logging out of sessions or using the transaction code /nSM04 to manage user sessions.
  Check User Profile: Review the user profile settings to see if there are any restrictions on the number of sessions. This can be done by an administrator using transaction code SU01.
  Increase Session Limit: If necessary, an SAP administrator can increase the session limit for the user or for the system as a whole. This can be done in the system profile parameters (e.g., rdisp/mshost).
  Use a Different User: If the session limit is reached and cannot be changed, consider logging in with a different user account that has available sessions.
  Review Transaction Requirements: If the transaction you are trying to execute requires a new session, ensure that you are following the correct procedure for that transaction.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error message.
  System Performance: Be aware that increasing the number of sessions can impact system performance, so it should be done judiciously.
  User Training: Ensure that users are trained on how to manage their sessions effectively to avoid hitting session limits.
  
  If the problem persists after trying these solutions, it may be beneficial to consult with your SAP Basis team or refer to SAP support for further assistance.