How To Fix ESH_EX072 - Instances of object type &1 have been set to status 'Failed'

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_EX - Extraction

• Message number: 072

• Message text: Instances of object type &1 have been set to status 'Failed'

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_EX072 - Instances of object type &1 have been set to status 'Failed' ?

  The SAP error message ESH_EX072 indicates that instances of a specific object type have been set to the status 'Failed' in the context of the SAP Enterprise Search (ESH) framework. This typically occurs when there are issues during the indexing or processing of search objects.
  Cause:
  The error can be caused by several factors, including but not limited to:
  
  Data Issues: There may be inconsistencies or errors in the data being indexed, such as missing fields or invalid data formats.
  Configuration Problems: Incorrect configuration settings for the search object or the search connector can lead to failures.
  System Performance: Resource constraints, such as insufficient memory or CPU, can cause the indexing process to fail.
  Network Issues: If the search system relies on external data sources, network connectivity problems can lead to failures.
  Authorization Issues: Lack of proper authorizations for accessing the data can also result in failures.
  
  Solution:
  To resolve the ESH_EX072 error, you can follow these steps:
  
  Check Logs: Review the logs for more detailed error messages. You can find logs in transaction codes like SLG1 (Application Log) or in the ESH administration tools.
  Data Validation: Ensure that the data being indexed is complete and valid. Check for any missing or incorrect data entries.
  Configuration Review: Verify the configuration settings for the search object and connectors. Ensure that they are set up correctly.
  Resource Monitoring: Monitor system resources (CPU, memory, disk space) to ensure that the system is not under heavy load. If necessary, optimize the system performance.
  Re-indexing: If the issue persists, consider re-indexing the affected search object. This can often resolve transient issues.
  Check Authorizations: Ensure that the user executing the indexing has the necessary authorizations to access the data.
  Consult Documentation: Refer to SAP documentation or notes related to the specific object type for any known issues or additional troubleshooting steps.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to the ESH framework or specific object types.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  Support: If the problem persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  By following these steps, you should be able to identify the root cause of the ESH_EX072 error and implement a suitable solution.