How To Fix ECATT558 - In system &1 client &2 tests can only be started using 'Trusted RFC'

SAP Error Message - Details

• Message type: E = Error

• Message class: ECATT - eCATT Messages (Middleware and GUI)

• Message number: 558

• Message text: In system &1 client &2 tests can only be started using 'Trusted RFC'

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 ECATT558 - In system &1 client &2 tests can only be started using 'Trusted RFC' ?

  The SAP error message ECATT558 indicates that you are trying to execute eCATT (extended Computer Aided Test Tool) tests in a system and client that require a "Trusted RFC" connection. This error typically arises when the system configuration does not allow the execution of eCATT tests due to security settings.
  Cause:
  The error occurs because:
  
  The eCATT tests are being executed in a system/client that has been configured to only allow trusted connections for certain operations.
  The RFC (Remote Function Call) connection being used is not set up as a trusted connection.
  
  Solution:
  To resolve this issue, you need to ensure that the RFC connection used for executing the eCATT tests is configured as a trusted RFC. Here are the steps to do this:
  
  
  Check RFC Connection:
  
  Go to transaction SM59 in the SAP GUI.
  Locate the RFC connection that you are using for the eCATT tests.
  
  
  
  Configure Trusted RFC:
  
  If the RFC connection is not trusted, you need to configure it as a trusted RFC.
  In the RFC connection settings, ensure that the "Trusted" option is enabled. This may involve setting up the appropriate authorizations and trust relationships between the systems.
  
  
  
  Maintain Trust Relationship:
  
  If you are working with multiple SAP systems, you may need to establish a trust relationship between them. This can be done by maintaining the necessary entries in the TMS (Transport Management System) or using transaction SM59 to configure trusted connections.
  
  
  
  User Authorizations:
  
  Ensure that the user executing the eCATT tests has the necessary authorizations to perform the actions required by the tests.
  
  
  
  Test Execution:
  
  After configuring the trusted RFC, try executing the eCATT tests again.
  
  
  
  Related Information:
  
  eCATT Documentation: Refer to the official SAP documentation for eCATT for more details on configuration and usage.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates regarding this error message.
  Security Considerations: Be aware of the security implications of enabling trusted RFC connections, as this can affect the overall security posture of your SAP landscape.
  
  By following these steps, you should be able to resolve the ECATT558 error and successfully execute your eCATT tests.