How To Fix ESH_QL_MSG061 - Could not reset keys for LQA ID generation - see longtext

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_QL_MSG - ESH Query Logging

• Message number: 061

• Message text: Could not reset keys for LQA ID generation - see longtext

What causes this issue?

You are maintaining the personalization customizing for Enterprise
Search (transaction ESH_CUST_PERS), or the personalization customizing
is being set up as part of a general setup step for Enterprise Search,
e.g. you are running an ESH setup task-list such as
SAP_ESH_INITIAL_SETUP_WRK_CLIENT. The option "Log queries anonymously"
has been set.
During the setup phase for query logging in anonymized mode or during
the action "Reset Keys" an error has occurred. The key for the
generation of Anonymized Query Logging IDs (LQA IDs) could not be set or
reset.

System Response

The system may not be able to set new LQA IDs (instead, you will find
IDs with text '###_hmac_exception'), or may not be able to generate LQA
IDs based on the updated key (IDs continue to be generated but are based
on an old/outdated key). As a consequence, statistics on search usage
may not return accurate numbers.
The error only affects evaluations based on anonymized data (option "Log
queries anonymously" activated).
For users actively participating in personalized search there are no
consequences.

How to fix this error?

The error is not critical for day-to-day business.
If the error reoccurs it is recommended to reset the anonymization keys
once again in the ESH personalization customizing (transaction
ESH_CUST_PERS).

Procedure for System Administrators

For further details see the accompanying messages from the HMAC / key
maintenance infrastructure.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_QL_MSG061 - Could not reset keys for LQA ID generation - see longtext ?

  The SAP error message ESH_QL_MSG061 indicates that there is an issue with resetting keys for LQA (Logical Query Architecture) ID generation. This error typically arises in the context of SAP's Enterprise Search or when working with the SAP HANA database.
  Cause:
  The error can be caused by several factors, including:
  
  Database Issues: There may be problems with the underlying database, such as corruption or misconfiguration.
  Configuration Errors: Incorrect settings in the LQA configuration can lead to issues with key generation.
  Missing Authorizations: The user executing the operation may not have the necessary authorizations to perform the reset.
  System Lock: The system might be in a locked state due to ongoing processes or transactions that are preventing the reset of keys.
  Technical Issues: Bugs or inconsistencies in the SAP system or the specific version being used.
  
  Solution:
  To resolve the error, you can try the following steps:
  
  Check System Logs: Review the system logs (transaction SM21) for any related error messages that might provide more context.
  Verify Configuration: Ensure that the LQA configuration is correct. You can check the settings in transaction /IWFND/MAINT_SERVICE or /IWFND/ERROR_LOG.
  Check Authorizations: Make sure that the user has the necessary authorizations to perform the operation. You can use transaction SU53 to analyze authorization issues.
  Database Consistency: Run database consistency checks to ensure that there are no underlying issues with the database.
  Restart Services: If the system is locked, consider restarting the relevant services or the entire system if necessary.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates available that resolve the issue.
  Contact SAP Support: If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance.
  
  Related Information:
  
  Long Text: The error message suggests checking the long text for more detailed information. You can usually find this by navigating to the error message in the SAP GUI and selecting the option to view the long text.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM21 (System Log), and ST22 (Dump Analysis) to help diagnose the issue.
  Documentation: Review SAP documentation related to LQA and Enterprise Search for best practices and configuration guidelines.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.