How To Fix ESH_CHECK_CONN035 - ICM comm. failure while accessing TREX with &1 from app. server &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_CHECK_CONN - Check connector consistency

• Message number: 035

• Message text: ICM comm. failure while accessing TREX with &1 from app. server &2

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_CHECK_CONN035 - ICM comm. failure while accessing TREX with &1 from app. server &2 ?

  The SAP error message ESH_CHECK_CONN035 indicates an issue with the connection between the application server and the TREX (Text Retrieval and Extraction) server. This error typically arises when the application server is unable to communicate with the TREX server due to various reasons.
  Causes:
  
  Network Issues: There may be network connectivity problems between the application server and the TREX server.
  TREX Server Down: The TREX server might be down or not running.
  Configuration Issues: Incorrect configuration settings in the SAP system or TREX settings can lead to connection failures.
  Firewall Restrictions: Firewalls or security settings may be blocking the communication between the servers.
  Resource Limitations: The TREX server may be overloaded or running out of resources (e.g., memory, CPU).
  Incorrect Hostname or Port: The hostname or port number configured for the TREX connection may be incorrect.
  
  Solutions:
  
  Check TREX Server Status: Ensure that the TREX server is up and running. You can check this using the TREX administration tools.
  Network Connectivity: Verify that there is network connectivity between the application server and the TREX server. You can use tools like ping or telnet to test connectivity.
  Review Configuration: Check the configuration settings in the SAP system for the TREX connection. Ensure that the hostname and port are correctly specified.
  
  You can check the settings in transaction SICF (for ICM settings) and TREX Administration.
  
  
  Firewall Settings: Ensure that any firewalls between the application server and TREX server allow traffic on the required ports.
  Monitor Resource Usage: Check the resource usage on the TREX server to ensure it is not overloaded. You may need to optimize or scale the server if it is under heavy load.
  Logs and Traces: Review the logs on both the application server and the TREX server for any additional error messages or warnings that could provide more context about the failure.
  
  Related Information:
  
  TREX Administration: Familiarize yourself with the TREX administration tools to monitor and manage the TREX server.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error.
  Documentation: Refer to the official SAP documentation for detailed information on configuring and troubleshooting TREX connections.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.