How To Fix ESH_SEARCH086 - Authorization check &1, template &2: Node &3 does not exist

ESH_SEARCH086 - Overview

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 086

• Message text: Authorization check &1, template &2: Node &3 does not exist

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_SEARCH086 - Authorization check &1, template &2: Node &3 does not exist ?

  The SAP error message ESH_SEARCH086 typically indicates an authorization issue related to the Enterprise Search (ESH) functionality in SAP. This error occurs when a user attempts to access a search template or node that they do not have the necessary authorizations for.
  
  Cause:
  
  Missing Authorizations: The user does not have the required authorizations to access the specified search template or node.
  Incorrect Configuration: The search configuration may not be set up correctly, leading to the system not recognizing the node.
  Node Deletion or Inaccessibility: The node specified in the error message may have been deleted or is currently not accessible due to system changes or updates.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 to analyze the authorization check failure. This will show you which specific authorizations are missing.
  Ensure that the user has the necessary roles assigned that include access to the relevant search templates and nodes.
  
  
  
  Review Search Configuration:
  
  Go to transaction EHS_SEARCH_ADMIN or EHS_SEARCH_CONFIG to check the