How To Fix ESH_TREX_ADMIN091 - Error occured while trying to fill new/addded authorization indexes

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_TREX_ADMIN - TREX Indexing and Index Administration

• Message number: 091

• Message text: Error occured while trying to fill new/addded authorization indexes

What causes this issue?

This message indicates that the authorization data update for one or
multiple ESH search connectors has failed during a search connector
creation or update process.

System Response

The authorization data update for search connectors is done at the end,
in the 'finalization' phase of the connector creation/update process.

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

In most cases the connectors are already technically ok (successfully
prepared) when this error message occurs, and only the last step
"authorization data update" for the connector has not succeeded. This
means that for repair of the issue only the authorization update has to
be re-executed.
The connectors affected by the issue will be set to status
"Authorization Update Failed" in the Enterprise Search Cockpit.
To be able to see the affected connectors it may be necessary to refresh
the cockpit after end of the job, and/or to reset the "Status" filter in
the ESH Cockpit.

How to fix this error?

If there are connectors in status "Authorization Update Failed" in the
Enterprise Search Cockpit:
You do not have to repeat the connector creation or connector update
Ensure that the original connector update job has come to an end.
(Parallel indexing jobs do not matter).
Mark the connectors in status "Auth Update Failed" and press the option
"Actions" -> "Update Authorization Data" in the ESH Cockpit
This will re-execute the authorization update process for the affected
connectors.
Note: The option "Update Authorization Data" can only be chosen if you
have selected connectors in status "Auth Update Failed". In some cases
the authorization checks are shared by multiple connectors, in these
cases the correction for one connector may correct the issue for others,
too, even if you have not selected them when starting the process.
As an alternative to "Actions" -> "Update Authorization Data" you can
also run report ESH_ADM_RECALC_AUTHS. Start the report with option
"Where status = Failed".
If re-execution of the authorization update does not succeed, e.g. if it
runs in the same errors as the original process, or if it is otherwise
not able to update the connector status to "Active" or to "Prepared" at
the end, the connector update as a whole may have to be repeated.
The same applies for connectors which are in status "Error While
Preparing" (not "Authorization Update Failed") right from the start.
If you are not able to resolve the issue, or if the error occurs
repetitively, contact the SAP support.
Note: Execution of "Actions" -> "Update Authorization Data" (and
execution ESH_ADM_RECALC_AUTHS) does not write a new job log. The error
can continue to be displayed in the original "connector creation" /
"connector update" joblog even if the issue has already been resolved.
Once you do not find any more connectors in status "Authorization Update
Failed" (all set to "Active") you can ignore the fact that the joblog
continues to display the error.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_TREX_ADMIN091 - Error occured while trying to fill new/addded authorization indexes ?

  The SAP error message ESH_TREX_ADMIN091 typically indicates an issue related to the authorization indexes in the SAP Enterprise Search (TREX) system. This error can occur when there are problems with the configuration or the data that is being indexed.
  Causes:
  
  Authorization Issues: The user executing the operation may not have the necessary authorizations to create or modify the authorization indexes.
  Configuration Errors: There may be misconfigurations in the TREX settings or the Enterprise Search configuration.
  Data Issues: The data being indexed may have inconsistencies or errors that prevent the indexing process from completing successfully.
  System Performance: Insufficient system resources (CPU, memory, disk space) can lead to failures during the indexing process.
  Version Compatibility: There may be compatibility issues between different versions of SAP components.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the indexing operation. This may involve checking roles and permissions in the SAP system.
  Review Configuration: Verify the configuration settings for TREX and Enterprise Search. Ensure that all necessary parameters are correctly set.
  Data Validation: Check the data that is being indexed for any inconsistencies or errors. This may involve running data validation checks or reviewing logs for specific issues.
  Monitor System Resources: Check the system resources to ensure that there is enough CPU, memory, and disk space available for the indexing process. If resources are low, consider optimizing the system or increasing resources.
  Check Logs: Review the TREX logs for more detailed error messages that can provide insights into what went wrong during the indexing process.
  Rebuild Indexes: If the issue persists, consider rebuilding the authorization indexes. This can often resolve issues related to corrupted or incomplete indexes.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches and updates.
  
  Related Information:
  
  TREX Administration: Familiarize yourself with the TREX administration tools and how to manage indexes.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Refer to the official SAP documentation for Enterprise Search and TREX for detailed guidance on configuration and troubleshooting.
  
  If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.