How To Fix ECATT564 - List of application servers system &1 client &2 is not available

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 564

• Message text: List of application servers system &1 client &2 is not available

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 ECATT564 - List of application servers system &1 client &2 is not available ?

  The SAP error message ECATT564 indicates that the system is unable to find a list of application servers for a specified system and client. This can occur in various scenarios, particularly when using the eCATT (extended Computer Aided Test Tool) for automated testing.
  Causes:
  
  Incorrect System or Client Configuration: The specified system or client may not be correctly configured in the SAP landscape.
  Network Issues: There may be network connectivity issues preventing access to the application servers.
  Application Server Down: The application server for the specified system and client may be down or not running.
  Authorization Issues: The user executing the eCATT may not have the necessary authorizations to access the application servers.
  Incorrect eCATT Configuration: The eCATT script may be incorrectly configured, pointing to a non-existent or incorrect system/client.
  
  Solutions:
  
  
  Verify System and Client Configuration:
  
  Check the configuration of the system and client in the SAP system. Ensure that the system ID (SID) and client number are correct.
  Use transaction SM51 to check the list of available application servers and ensure that the specified server is listed.
  
  
  
  Check Network Connectivity:
  
  Ensure that there are no network issues preventing access to the application servers. You can use tools like ping or telnet to test connectivity.
  
  
  
  Check Application Server Status:
  
  Use transaction SM51 to see if the application server is up and running. If it is down, you may need to restart it or contact your system administrator.
  
  
  
  Review User Authorizations:
  
  Ensure that the user executing the eCATT has the necessary authorizations to access the application servers. Check roles and profiles assigned to the user.
  
  
  
  Review eCATT Configuration:
  
  Double-check the eCATT script configuration. Ensure that the system and client parameters are correctly set in the eCATT script.
  
  
  
  Check RFC Connections:
  
  If the eCATT is trying to connect to a remote system, ensure that the RFC connections are correctly configured and operational.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM51: To view the list of application servers.
  SM59: To check and configure RFC connections.
  SU01: To manage user authorizations.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to eCATT or application server connectivity.
  
  
  Logs and Traces: Review system logs (transaction SM21) and developer traces (transaction ST22) for any additional error messages that may provide more context.
  
  
  By following these steps, you should be able to diagnose and resolve the ECATT564 error in your SAP environment.