How To Fix TT357 - RFC & &

SAP Error Message - Details

• Message type: E = Error

• Message class: TT - Extended Computer Aided Test Tool (eCATT) messages

• Message number: 357

• Message text: RFC & &

What causes this issue?

RFC Error
You want to remotely execute a test or individual functions of a test
using internally a Remote Function Call (RFC) interface. The system
requires an RFC destination that is processed using transaction SM59.
RFC System Error
This error occurs if a system is terminated on the receiver side.
RFC Communication Error
This error is raised if a problem occurs when establishing the
connection or the communication.

System Response

All RFC errors are registered in the log. In addition, entries are
created in the system log and dumps are written in case of terminations.

How to fix this error?

In its variable part, the error message entered in the log contains an
error text that is output by the RFC interface.
In many cases, the error text describes the cause of the problem so
accurately that the problem can be solved or avoided.
If the error text is unclear or too general - for example, CONNECTION
CLOSED -, you must find other ways to search for the cause of the
problem.
You can search for information in the source system and target system
using the following transactions:
SM21 System log display
ST22 Dump analysis
There are only a few RFC errors for which no system log entries or dumps
are created. In these cases, an RFC trace can help to find the cause of
the error. A corresponding RFC trace option is provided by the
transaction
ST01 System trace

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TT357 - RFC & & ?

  The SAP error message TT357 typically relates to issues with Remote Function Calls (RFC) in the SAP system. The error message may indicate that there is a problem with the RFC connection or configuration. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  RFC Destination Issues: The RFC destination may not be correctly configured or may be pointing to an incorrect system.
  Network Problems: There could be network connectivity issues between the SAP systems involved in the RFC call.
  Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations.
  System Configuration: The target system may not be properly configured to accept RFC calls.
  SAP Gateway Issues: The SAP Gateway service may not be running or may be misconfigured.
  
  Solutions:
  
  
  Check RFC Destination:
  
  Go to transaction SM59 and verify the configuration of the RFC destination.
  Test the connection to ensure it is working properly.
  
  
  
  Network Connectivity:
  
  Ensure that there are no firewall or network issues preventing communication between the systems.
  Use tools like ping or telnet to check connectivity.
  
  
  
  User Authorizations:
  
  Verify that the user used for the RFC connection has the necessary authorizations in both the source and target systems.
  Check roles and profiles assigned to the user.
  
  
  
  System Configuration:
  
  Ensure that the target system is configured to accept RFC calls. Check the instance profile and parameters related to RFC.
  Make sure that the SAP Gateway is running on the target system.
  
  
  
  Check SAP Gateway:
  
  Use transaction SMGW to monitor the SAP Gateway and check for any errors or issues.
  Restart the SAP Gateway if necessary.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: RFC Destinations
  SMGW: SAP Gateway Monitor
  ST22: Dump Analysis (to check for any ABAP runtime errors)
  SICF: HTTP Service Hierarchy (to check if HTTP services are active)
  
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address specific issues related to RFC errors.
  
  
  Logs: Review system logs (transaction SM21) for any additional error messages that may provide more context about the issue.
  
  
  If the problem persists after checking these areas, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.