How To Fix ESH_BOS_INDEX_CTRL105 - No instance of class CL_ESH_OM_AUTHNW was created

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 105

• Message text: No instance of class CL_ESH_OM_AUTHNW was created

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_CTRL105 - No instance of class CL_ESH_OM_AUTHNW was created ?

  The SAP error message ESH_BOS_INDEX_CTRL105 with the description "No instance of class CL_ESH_OM_AUTHNW was created" typically relates to issues in the Enterprise Search (ESH) configuration, particularly concerning authorization checks or the handling of search queries.
  Cause:
  
  Missing or Incorrect Configuration: The error may arise if the necessary configuration for the Enterprise Search is not set up correctly. This includes missing settings for the authorization object or the search service.
  Authorization Issues: The class CL_ESH_OM_AUTHNW is responsible for handling authorization checks. If there are issues with the authorization settings or if the class is not instantiated properly, this error can occur.
  System or Environment Issues: Sometimes, the error can be due to system inconsistencies, such as missing components or issues with the underlying database.
  
  Solution:
  
  
  Check Configuration: 
  
  Ensure that the Enterprise Search is properly configured. This includes checking the settings in the ESH administration and ensuring that all necessary components are activated.
  Verify that the search service is correctly set up and that the relevant data sources are indexed.
  
  
  
  Review Authorization Settings:
  
  Check the authorization settings for the user or role that is encountering the error. Ensure that the necessary authorizations are granted.
  You may need to adjust the roles or profiles assigned to the user to include the necessary permissions for accessing the search functionality.
  
  
  
  Recreate the Index:
  
  If the issue persists, consider recreating the search index. This can sometimes resolve inconsistencies that lead to errors.
  Use transaction codes like ESH_ADMIN to manage and monitor the indexing process.
  
  
  
  Check for System Updates:
  
  Ensure that your SAP system is up to date with the latest patches and updates. Sometimes, bugs in earlier versions can lead to such errors, and applying the latest support packages can resolve them.
  
  
  
  Debugging:
  
  If you have access to the development environment, you can debug the class CL_ESH_OM_AUTHNW to see why the instance is not being created. This may provide insights into the underlying issue.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be known issues or patches available.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to Enterprise Search, such as EHS_ADMIN for administration and EHS_INDEX for indexing.
  Documentation: Review the official SAP documentation on Enterprise Search for best practices and configuration guidelines.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.