How To Fix ESH_TST_SMK_MSG118 - Crawl &1 was not started: &2

ESH_TST_SMK_MSG118 - Overview

• Message type: E = Error

• Message class: ESH_TST_SMK_MSG - Smoke Test

• Message number: 118

• Message text: Crawl &1 was not started: &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_TST_SMK_MSG118 - Crawl &1 was not started: &2 ?

  The SAP error message ESH_TST_SMK_MSG118 indicates that a crawl process for the Enterprise Search (ES) was not started. The message typically includes two placeholders: &1 for the name of the crawl and &2 for the reason why the crawl was not initiated.
  Causes
  The error can be caused by several factors, including:
  
  
  Configuration Issues: The crawl might not be properly configured in the system.
  Missing Permissions: The user or service account attempting to start the crawl may not have the necessary permissions.
  System Errors: There could be underlying system issues, such as database connectivity problems or service outages.
  Resource Limitations: The system may not have enough resources (CPU, memory, etc.) to start the crawl.
  Crawl Already Running: If a crawl is already in progress, a new crawl cannot be started until the current one finishes.
  
  Solutions
  To resolve the issue, you can take the following steps:
  
  
  Check Configuration: Verify that the crawl configuration is correct. Ensure that all necessary parameters