How To Fix RZ795 - Maximum number (32) of external RFC logon groups reached

RZ795 - Overview

• Message type: E = Error

• Message class: RZ - Messages for Computing Center Management System

• Message number: 795

• Message text: Maximum number (32) of external RFC logon groups 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 RZ795 - Maximum number (32) of external RFC logon groups reached ?

  The SAP error message RZ795: Maximum number (32) of external RFC logon groups reached indicates that the system has reached the maximum limit of external RFC (Remote Function Call) logon groups that can be defined. This typically occurs when there are too many external systems trying to connect to the SAP system using RFC connections.
  
  Cause:
  
  Exceeding Limit: The SAP system has a predefined limit of 32 external RFC logon groups. If you attempt to create more than this number, you will encounter this error.
  
  Configuration Issues: There may be misconfigurations in the RFC destinations or logon groups that lead to the system trying to create additional logon groups unnecessarily.
  Legacy Connections: Old or unused connections that are still defined in the system may be consuming the available logon groups.
  
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Review Existing Logon Groups:
  
  Go to transaction SM59 (RFC Destinations) and check the existing external RFC logon