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

ESH_QL_MSG023 - Overview

• 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