How To Fix ESH_ADM_MSG072 - Search object connectors scheduled for indexing

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool

• Message number: 072

• Message text: Search object connectors scheduled for indexing

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_ADM_MSG072 - Search object connectors scheduled for indexing ?

  The SAP error message ESH_ADM_MSG072 typically indicates that there are search object connectors that are scheduled for indexing but have not yet been processed. This message is part of the SAP Enterprise Search (SAP ESH) framework, which is used to index and search data across various SAP applications.
  Cause:
  The error can occur due to several reasons:
  
  Pending Indexing Jobs: There are indexing jobs that have been scheduled but not executed yet.
  System Performance Issues: The system may be experiencing performance issues that prevent the indexing jobs from running in a timely manner.
  Configuration Issues: There may be misconfigurations in the search object connectors or the indexing settings.
  Resource Limitations: Insufficient system resources (CPU, memory, etc.) may be causing delays in processing the indexing jobs.
  
  Solution:
  To resolve the issue, you can take the following steps:
  
  
  Check Indexing Jobs:
  
  Go to the transaction code /IWFND/ERROR_LOG or /IWFND/MAINT_SERVICE to check the status of the indexing jobs.
  Look for any jobs that are in a "scheduled" or "waiting" state.
  
  
  
  Manually Trigger Indexing:
  
  You can manually trigger the indexing process for the affected search object connectors. Use transaction EHS_ADM to access the Enterprise Search Administration and initiate the indexing.
  
  
  
  Review System Logs:
  
  Check the system logs for any errors or warnings that might indicate why the indexing jobs are not being processed. Use transaction SM21 to view the system log.
  
  
  
  Monitor System Performance:
  
  Use transaction ST03N or ST06 to monitor system performance and resource usage. Ensure that the system has enough resources to handle the indexing jobs.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the search object connectors. Ensure that they are correctly set up and that there are no errors in the configuration.
  
  
  
  Schedule Regular Indexing:
  
  If the issue is related to the frequency of indexing, consider scheduling regular indexing jobs to ensure that the data is kept up to date.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for Enterprise Search for detailed information on configuring and managing search object connectors.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have already taken.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.