Do you have any question about this error?
Message type: E = Error
Message class: ESH_TST_SMK_MSG - Smoke Test
Message number: 114
Message text: Crawler was created
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.
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.
ESH_TST_SMK_MSG114
- Crawler was created ?The SAP error message ESH_TST_SMK_MSG114, which states "Crawler was created," typically indicates that a crawler process has been successfully initiated in the SAP Enterprise Search (SAP ESH) environment. This message is not necessarily an error but rather an informational message indicating that the crawler has been created and is ready to run.
Cause:
- Crawler Initialization: The message is generated when a new crawler is created in the SAP ESH system. This can happen during the configuration of the search system or when a new data source is added.
- Configuration Changes: If you have made changes to the search configuration or added new data sources, the system will create a new crawler to index the data.
Solution:
- Check Crawler Status: After receiving this message, you should check the status of the crawler to ensure it is running correctly. You can do this through the SAP ESH administration interface.
- Run the Crawler: If the crawler is not running, you may need to manually start it to begin indexing the data.
- Monitor Logs: Review the logs for any additional messages or errors that may indicate issues with the crawler or the indexing process.
- Configuration Review: Ensure that the configuration settings for the crawler and the data sources are correct. This includes checking connection settings, indexing rules, and any filters that may be applied.
Related Information:
If you are experiencing issues beyond the informational message, it may be helpful to provide additional context or error messages for more targeted troubleshooting.
Get instant SAP help. Start your 7-day free trial now.
ESH_TST_SMK_MSG113
Connector ID could not be composed: &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_TST_SMK_MSG112
Connection type could not be created: &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_TST_SMK_MSG115
Crawler &1 was added to search connector
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_TST_SMK_MSG116
Error during initial indexing of object type &1: &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.