How To Fix ESH_BOS_INDEX_CTRL104 - Data of NW authorization objects could not be indexed

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_BOS_INDEX_CTRL - Trex Inderxing on the ES Hub

• Message number: 104

• Message text: Data of NW authorization objects could not be indexed

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_BOS_INDEX_CTRL104 - Data of NW authorization objects could not be indexed ?

  The SAP error message ESH_BOS_INDEX_CTRL104 indicates that there was an issue with indexing data related to NetWeaver (NW) authorization objects in the Enterprise Search (ESH) system. This error typically arises during the indexing process when the system encounters problems with the data that is supposed to be indexed.
  Causes:
  
  Missing Authorization Objects: The authorization objects that are supposed to be indexed may not exist or may not be properly defined in the system.
  Data Inconsistencies: There may be inconsistencies or corruption in the data related to the authorization objects.
  Configuration Issues: Incorrect configuration settings in the Enterprise Search or the underlying data sources can lead to this error.
  Insufficient Permissions: The user or process attempting to perform the indexing may not have the necessary permissions to access the authorization objects.
  System Performance Issues: If the system is under heavy load or if there are performance issues, it may affect the indexing process.
  
  Solutions:
  
  Check Authorization Objects: Verify that all required authorization objects are present and correctly defined in the system. You can use transaction codes like SU21 to check the definitions.
  Data Consistency Check: Run consistency checks on the data related to authorization objects to identify and resolve any inconsistencies.
  Review Configuration: Ensure that the configuration settings for the Enterprise Search and the data sources are correct. This includes checking the settings in the ESH configuration and the relevant data source settings.
  User Permissions: Ensure that the user or process performing the indexing has the necessary permissions to access and index the authorization objects.
  System Performance: Monitor the system performance and resolve any issues that may be affecting the indexing process. This may involve optimizing database performance or addressing any resource bottlenecks.
  Re-indexing: If the issue persists, consider re-indexing the data. This can often resolve issues related to stale or corrupted index data.
  
  Related Information:
  
  Transaction Codes: You may find it useful to use transaction codes such as SE11 (Data Dictionary), SE80 (Object Navigator), and SU53 (Authorization Check) to investigate further.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review the application logs (transaction SLG1) and traces to gather more information about the error and its context.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.