How To Fix ESH_HANA_ADMIN070 - Could not instantiate ESH connectivity: Local connection not found

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_HANA_ADMIN - ESH HANA Index Administration

• Message number: 070

• Message text: Could not instantiate ESH connectivity: Local connection not found

What causes this issue?

The system tries to access the Enterprise Search (ESH) connectivity to
SAP HANA or to TREX/BWA for the local system. The connectivity for the
local system is not found, or invalid, or not properly configured. The
ESH connectivity cannot be used.
The error can arise in the following cases:
Enterprise Search and the ESH connection have not yet been set up on the
system for the local working client
There are duplicate local connectivities, for example after a system
copy or client copy. In this case, the invalid (copied) connectivity has
to be removed, and any legacy entities (for example search connectors)
belonging to the legacy connectivity have to be either deleted or
migrated.
The local connectivity is correctly set up, but there are legacy
entities (e.g. search connectors) still referring to an invalid
connectivity. Also in this case, the legacy entities have to be deleted
or migrated.

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

System Response

Access to the Enterprise Search services, features and entities is not
possible.

How to fix this error?

The ESH connectivity has to be cleaned up.

Procedure for System Administrators

Depending on the use case you can do the following:
If Enterprise Search has not yet been set up at all on the system:
Run Task List SAP_ESH_INITIAL_SETUP_WRK_CLIENT
If there are duplicate connectivities or if there are legacy search
entities which have to be migrated after a system copy or a client copy:
- Run Task List SAP_ESH_ADJUST_AFTER_COPY (in case of a system copy)
- Run Task List SAP_ESH_ADJUST_AFTER_CLIENT_COPY (in case of a client
copy)
Note that depending on the SAP Basis release of the source system and
depending on the status of the legacy connectors there may be cases
where they cannot be recovered.
If there are legacy entities which have to be removed:
Run e.g. Task List SAP_ESH_CREATE_INDEX_SC with steps "Delete" and
"Create & Index (New) Connectors"
To clean up everything, you can alternatively run Task Lists
SAP_ESH_RESET and then rebuild the connectivity again with
SAP_ESH_INITIAL_SETUP_WRK_CLIENT
To check the consistency of the setup you can run task list
SAP_ESH_CONSISTENCY_CHECK
Alternatively, in on-premise releases it is possible to set up and
configure Enterprise Search manually, e.g. via the customizing tools
available in the IMG. The ESH connectivity for the local system can also
be set up directly with report ESH_ADM_SET_TREX_DESTINATION.
For details refer to the Enterprise Search setup guides and/or SAP
Documentation provided for your release.
For managed cloud releases contact your service partner.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_HANA_ADMIN070 - Could not instantiate ESH connectivity: Local connection not found ?

  The SAP error message ESH_HANA_ADMIN070 indicates that there is an issue with the connectivity to the SAP HANA database, specifically that a local connection could not be found. This error typically arises in the context of the Enterprise Search (ESH) component when it attempts to connect to the HANA database but fails to find the necessary connection configuration.
  Causes:
  
  Missing or Incorrect Connection Configuration: The local connection to the HANA database may not be defined in the system or may be incorrectly configured.
  Network Issues: There could be network-related issues preventing the application from reaching the HANA database.
  Authorization Issues: The user or service account may not have the necessary permissions to access the HANA database.
  HANA Database Not Running: The HANA database instance may not be running or may be in a state that prevents connections.
  Incorrect System Parameters: The system parameters related to the HANA connection might not be set correctly.
  
  Solutions:
  
  
  Check Connection Configuration:
  
  Go to the SAP HANA Studio or the relevant transaction in the SAP GUI (like DBACOCKPIT or SM59 for RFC connections).
  Verify that the local connection to the HANA database is defined and correctly configured.
  Ensure that the connection parameters (host, port, user, password) are correct.
  
  
  
  Test the Connection:
  
  Use the connection test feature in the SAP GUI or HANA Studio to ensure that the connection can be established successfully.
  
  
  
  Check HANA Database Status:
  
  Ensure that the HANA database is up and running. You can check this using the HANA Studio or command line tools.
  If the database is down, restart it and check for any errors in the logs.
  
  
  
  Review User Permissions:
  
  Ensure that the user or service account being used to connect to the HANA database has the necessary permissions.
  Check roles and privileges assigned to the user in the HANA database.
  
  
  
  Check Network Configuration:
  
  Ensure that there are no firewall rules or network issues preventing access to the HANA database.
  Verify that the hostname and port used in the connection configuration are reachable from the application server.
  
  
  
  Review System Parameters:
  
  Check the relevant system parameters in the SAP system that pertain to HANA connectivity. Ensure they are set correctly.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs: Review the application logs and HANA logs for any additional error messages or warnings that could provide more context about the issue.
  Documentation: Refer to the official SAP documentation for Enterprise Search and HANA connectivity for detailed configuration steps and best practices.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.