How To Fix ESH_INTEGRATION060 - Back-end system and ES hub share TREX instance; skip step 11

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_INTEGRATION - ESH Integration

• Message number: 060

• Message text: Back-end system and ES hub share TREX instance; skip step 11

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_INTEGRATION060 - Back-end system and ES hub share TREX instance; skip step 11 ?

  The SAP error message ESH_INTEGRATION060 indicates that there is a configuration issue related to the integration between the back-end system and the Enterprise Search (ES) hub, specifically concerning the TREX (Text Retrieval and Extraction) instance. This error typically arises when both the back-end system and the ES hub are configured to use the same TREX instance, which can lead to conflicts or misconfigurations during the integration process.
  
  Cause:
  
  Shared TREX Instance: The back-end system and the ES hub are configured to use the same TREX instance, which is not supported in certain scenarios.
  
  Configuration Issues: There may be inconsistencies in the configuration settings for the TREX instance in either the back-end system or the ES hub.
  Version Mismatch: The versions of the back-end system and the ES hub may not be compatible, leading to integration issues.
  
  
  Solution:
  
  Separate TREX Instances: Ensure that the back-end system and the ES hub are configured to use separate TREX instances.