How To Fix ESH_DB029 - http-service &1 is not active

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_DB - ES: Dashboard

• Message number: 029

• Message text: http-service &1 is not active

What causes this issue?

Service &V1& has not been activated.

System Response

The InA-services are required for the search-UI - for end users, search
is not operational without the two services. From 7.53, InA is
discontinued in favor of the oData-service.
The oData-admin-service is required for the administration UIs, like the
'Fine-Tune Search Ranking' cockpit, the maintenance of term mappings, or
the query log analysis.
The oData-search-service is required for the end-user search-UI as of
7.53. Before that release, the search was done on basis of the
InA-protocol.

How to fix this error?

The InA-services need to be activated in transaction SICF, along the
path default host -> sap -> es -> ina.
The InA-services do not run via Frontend Server; the Web Dispatcher must
be configured so that all InA-requests are directed directly from the
client to the backend system where Enterprise Search has been set up.
The oData-services ESH_ADMIN_SRV and ESH_SEARCH_SRV have to be activated
on the Front End Server via Gateway, transaction /IWFND/MAINT_SERVICE.
The oData-service runs regularly via Gateway on the Frontend Server (if
it is deployed as an instance of its own). No additional configuration
is required.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_DB029 - http-service &1 is not active ?

  The SAP error message ESH_DB029 indicates that a specific HTTP service is not active. This error typically arises in the context of the SAP Enterprise Search (ESH) or when trying to access certain services that rely on HTTP communication.
  Cause:
  The error can occur due to several reasons:
  
  Service Not Activated: The HTTP service that is being called is not activated in the SAP system.
  Configuration Issues: There may be configuration issues in the SAP Gateway or the HTTP service settings.
  Network Issues: There could be network-related issues preventing access to the HTTP service.
  Authorization Issues: The user may not have the necessary authorizations to access the service.
  
  Solution:
  To resolve the ESH_DB029 error, you can follow these steps:
  
  
  Check Service Activation:
  
  Go to transaction SICF (HTTP Service Hierarchy Maintenance).
  Navigate to the service that is causing the issue (you may need to know the specific service name).
  Ensure that the service is activated. If it is not, right-click on the service and select "Activate Service".
  
  
  
  Check Service Configuration:
  
  Verify the configuration settings for the HTTP service in SICF.
  Ensure that the service is correctly configured to point to the right backend and that all necessary parameters are set.
  
  
  
  Check Authorization:
  
  Ensure that the user has the necessary authorizations to access the HTTP service.
  You can check the user roles and authorizations in transaction SU01.
  
  
  
  Check Network Connectivity:
  
  Ensure that there are no network issues preventing access to the service.
  You can use tools like ping or telnet to check connectivity to the server.
  
  
  
  Check Logs:
  
  Review the application logs (transaction SLG1) for any additional error messages or information that might help diagnose the issue.
  
  
  
  Restart Services:
  
  If the service is still not working, consider restarting the relevant services or the SAP system itself.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SICF: For managing HTTP services.
  SLG1: For viewing application logs.
  SU01: For user administration and authorization checks.
  
  
  
  Documentation: Refer to SAP Help Portal or SAP Notes related to the specific HTTP service you are working with for more detailed troubleshooting steps.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.