How To Fix TQ370 - Starting test RFC

SAP Error Message - Details

• Message type: E = Error

• Message class: TQ - SAPup Messages

• Message number: 370

• Message text: Starting test RFC

What causes this issue?

An RFC is taking place to test the connection to the system, or to
check whether the system was started correctly.

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?

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 TQ370 - Starting test RFC ?

  The SAP error message TQ370, which states "Starting test RFC," typically occurs during the execution of Remote Function Calls (RFC) in SAP systems. This error can arise due to various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.
  Causes of TQ370 Error
  
  
  Network Issues: Problems with the network connection between the SAP application server and the target system can lead to this error. This includes issues like firewalls blocking the connection or network outages.
  
  
  Configuration Issues: Incorrect configuration of RFC destinations in transaction SM59 can cause this error. This includes incorrect settings for the target system, such as the wrong IP address, port number, or logon credentials.
  
  
  System Availability: The target system may be down or not available for RFC calls. This could be due to maintenance, system crashes, or other operational issues.
  
  
  Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations to execute the requested function module.
  
  
  SAP Kernel or Software Bugs: Sometimes, bugs in the SAP kernel or specific function modules can lead to unexpected behavior, including RFC errors.
  
  
  Solutions to TQ370 Error
  
  
  Check Network Connectivity:
  
  Ensure that the network connection between the systems is stable and operational.
  Use tools like ping or traceroute to verify connectivity.
  
  
  
  Verify RFC Destination Configuration:
  
  Go to transaction SM59 and check the configuration of the RFC destination.
  Ensure that the connection type, target host, and system number are correctly configured.
  Test the connection using the "Connection Test" option in SM59.
  
  
  
  Check System Availability:
  
  Verify that the target system is up and running.
  Check system logs for any errors or downtime notifications.
  
  
  
  Review User Authorizations:
  
  Ensure that the user credentials used for the RFC connection have the necessary authorizations to execute the required function modules.
  You can check user roles and authorizations in transaction SU01.
  
  
  
  Check for Software Updates:
  
  Ensure that your SAP system is up to date with the latest patches and updates. Sometimes, applying the latest support packages can resolve underlying bugs.
  
  
  
  Review Logs:
  
  Check the system logs (transaction SM21) and the developer trace files (transaction ST11) for any additional error messages or clues related to the RFC call.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  SM59: RFC Destinations
  SM21: System Log
  ST22: Dump Analysis
  ST01: System Trace
  SU01: User Maintenance
  
  
  
  Documentation: Refer to SAP Help Portal for detailed documentation on RFC and troubleshooting RFC-related issues.
  
  
  By following these steps, you should be able to identify and resolve the TQ370 error in your SAP system.