How To Fix ESH_ADM_MSG120 - Crawl &1 has not been resumed

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool

• Message number: 120

• Message text: Crawl &1 has not been resumed

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_MSG120 - Crawl &1 has not been resumed ?

  The SAP error message ESH_ADM_MSG120, which states "Crawl &1 has not been resumed," typically occurs in the context of the SAP Enterprise Search (SAP ESH) when a crawl process is interrupted and not resumed properly. This can happen for various reasons, such as system issues, configuration problems, or manual interruptions.
  Cause:
  
  Crawl Interruption: The crawl process may have been interrupted due to system errors, network issues, or manual intervention.
  Configuration Issues: There may be misconfigurations in the crawl settings or the data sources being crawled.
  Resource Limitations: Insufficient system resources (CPU, memory, etc.) can lead to the crawl process being unable to resume.
  Permissions: Lack of necessary permissions for the user or service account running the crawl can prevent it from resuming.
  
  Solution:
  
  Check Crawl Status: Go to the SAP ESH administration interface and check the status of the crawl. Identify if it is indeed in a paused or interrupted state.
  Resume the Crawl: If the crawl is paused, you can manually resume it from the administration interface. Look for options related to managing crawls and select the appropriate crawl to resume.
  Review Logs: Check the logs for any errors or warnings that occurred during the crawl process. This can provide insights into what caused the interruption.
  Configuration Review: Ensure that the crawl configuration is correct. Verify the data sources, connection settings, and any filters that may be applied.
  Resource Monitoring: Monitor system resources to ensure that there are enough resources available for the crawl to run. If necessary, allocate more resources or schedule the crawl during off-peak hours.
  Permissions Check: Ensure that the user or service account has the necessary permissions to access the data sources and perform the crawl.
  Restart Services: If the issue persists, consider restarting the relevant SAP services or the entire system to clear any temporary issues.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the ESH crawl process.
  Documentation: Refer to the official SAP documentation for Enterprise Search for detailed information on configuring and managing crawls.
  Community Forums: Engage with SAP community forums or support channels for additional insights and troubleshooting tips from other users who may have encountered similar issues.
  
  If the problem continues after trying the above solutions, it may be necessary to contact SAP support for further assistance.