How To Fix ESH_DB044 - InA-protocol still in use

ESH_DB044 - Overview

• Message type: E = Error

• Message class: ESH_DB - ES: Dashboard

• Message number: 044

• Message text: InA-protocol still in use

What causes this issue?

The protocol for the search client has been switched from InA to oData;
but in this system, InA still is used.

System Response

search is still operational, but the InA-protocol is not adapted to new
features, it lags increasingly behind the current oData-protocol, so
that UI-features might not be provided or even be broken.

How to fix this error?

Follow the configuration guidelines and set up the search via oData,
activated on the frontend Server (respectively in in the local
Launchpad, if co-deployed with the application server).

Procedure for System Administrators

The check considers search access over the past two weeks. If the
configuration has been switched to oData meanwhile, you can ignore the
message.

Error message extract from SAP system. Copyright SAP SE.

ESH_DB044 - Details

• The SAP error message ESH_DB044 indicates that the InA (Information Access) protocol is still in use, which typically means that there are active connections or sessions that are preventing the system from performing certain operations, such as shutting down or modifying the InA configuration.
  
  Cause:
  
  Active Sessions: There are active sessions or connections using the InA protocol that have not been properly terminated.
  Long-running Queries: Queries or processes that are still running and utilizing the InA protocol.
  
  Configuration Issues: Misconfiguration in the InA settings or related components that may lead to the protocol being incorrectly flagged as in use.
  
  
  Solution:
  
  
  Identify Active Sessions:
  
  Use transaction codes like SM50 (Process Overview) or SM66 (Global Process Overview) to check for active processes that might be using the InA protocol.
  Look for any long-running queries or sessions that need to be terminated.
  
  
  
  Terminate Sessions:
  
  If you identify any sessions that are no longer needed, you can terminate them using the appropriate options in