How To Fix ESH_QL_MSG023 - ESH is not set up on system - no ESH configuration / no logsys

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_QL_MSG - ESH Query Logging

• Message number: 023

• Message text: ESH is not set up on system - no ESH configuration / no logsys

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_QL_MSG023 - ESH is not set up on system - no ESH configuration / no logsys ?

  The SAP error message ESH_QL_MSG023 indicates that the Enterprise Search (ESH) is not properly configured in your SAP system. This error typically arises when the system is unable to find the necessary configuration or log system (logsys) for ESH.
  Cause:
  
  Missing Configuration: The ESH configuration might not have been set up in the system. This includes missing settings in the ESH configuration transaction.
  Log System Not Defined: The log system (logsys) that ESH relies on may not be defined or may not be accessible.
  Transport Issues: If the ESH configuration was transported from another system, there may have been issues during the transport process.
  Authorization Issues: The user may not have the necessary authorizations to access the ESH configuration.
  
  Solution:
  
  
  Check ESH Configuration:
  
  Go to transaction /IWFND/MAINT_SERVICE and ensure that the ESH services are activated.
  Use transaction /IWBEP/REG_SERVICE to register the necessary services for ESH.
  
  
  
  Define Log System:
  
  Ensure that the log system is defined in the system. You can check this in transaction SLG1 (Application Log) to see if there are any related logs that indicate issues with the log system.
  If the log system is not defined, you may need to create it in transaction SICF or through the relevant configuration settings.
  
  
  
  Check Transport Requests:
  
  If the configuration was transported, check the transport logs for any errors or issues that may have occurred during the transport process.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access ESH. You may need to check the roles assigned to the user and ensure they include the necessary permissions for ESH.
  
  
  
  Reconfigure ESH:
  
  If the above steps do not resolve the issue, you may need to reconfigure ESH. This can involve going through the ESH configuration steps again to ensure everything is set up correctly.
  
  
  
  Consult Documentation:
  
  Refer to the official SAP documentation for ESH configuration for detailed steps and best practices.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  SAP Community: The SAP Community forums can be a valuable resource for finding similar issues faced by other users and potential solutions.
  System Logs: Review system logs for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to identify and resolve the cause of the ESH_QL_MSG023 error in your SAP system.