How To Fix ESH_CO_COMMON013 - RFC &1 to destination &2 aborted with communication failure


SAP Error Message - Details

  • Message type: E = Error

  • Message class: ESH_CO_COMMON -

  • Message number: 013

  • Message text: RFC &1 to destination &2 aborted with communication failure

  • Show details Hide details


  • 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 ESH_CO_COMMON013 - RFC &1 to destination &2 aborted with communication failure ?

    The SAP error message ESH_CO_COMMON013 indicates that there was a communication failure when trying to establish an RFC (Remote Function Call) connection to a specified destination. This error can occur for various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.

    Causes:

    1. Network Issues: There may be network connectivity problems between the SAP system and the destination system.
    2. Destination Configuration: The RFC destination may not be configured correctly in the SAP system (e.g., incorrect hostname, port, or service).
    3. Authorization Issues: The user credentials used for the RFC connection may not have the necessary authorizations.
    4. Service Availability: The target system may be down or not reachable due to maintenance or other issues.
    5. Firewall Restrictions: Firewalls may be blocking the communication between the two systems.
    6. SAP Gateway Issues: The SAP Gateway service may not be running or may be misconfigured.

    Solutions:

    1. Check Network Connectivity:

      • Use tools like ping or telnet to check if the destination system is reachable from the SAP system.
      • Ensure that there are no network outages or issues.
    2. Verify RFC Destination Configuration:

      • Go to transaction SM59 in the SAP GUI.
      • Check the configuration of the RFC destination (e.g., TCP/IP settings, target host, and service).
      • Test the connection using the "Test Connection" button in the RFC destination configuration.
    3. Review User Authorizations:

      • Ensure that the user credentials used for the RFC connection have the necessary authorizations to access the target system.
      • Check the user settings in transaction SU01.
    4. Check Target System Availability:

      • Verify that the target system is up and running.
      • Check for any scheduled maintenance or downtime.
    5. Firewall and Security Settings:

      • Ensure that firewalls are configured to allow traffic on the required ports for RFC communication.
      • Consult with your network/security team if necessary.
    6. SAP Gateway Configuration:

      • Check if the SAP Gateway service is running on the SAP system.
      • Use transaction SMGW to monitor the gateway and check for any errors.

    Related Information:

    • Transaction Codes:
      • SM59: RFC Destinations
      • SMGW: SAP Gateway Monitor
      • SU01: User Maintenance
    • Logs and Traces:
      • Check the system logs (transaction SM21) for any related error messages.
      • Use transaction ST22 to check for dumps that may provide more context.
    • SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to RFC communication failures.

    By systematically checking these areas, you should be able to identify the root cause of the communication failure and implement the appropriate solution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant