How To Fix ESH_SEARCH130 - Creation of HTTP client: Destination was not found

ESH_SEARCH130 - Overview

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 130

• Message text: Creation of HTTP client: Destination was not found

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_SEARCH130 - Creation of HTTP client: Destination was not found ?

  The SAP error message ESH_SEARCH130 indicates that there is an issue with the HTTP client configuration, specifically that the destination required for the operation was not found. This error typically occurs in the context of the SAP Enterprise Search (ESH) or when trying to connect to an external system or service.
  
  Cause:
  
  Missing Destination: The HTTP destination that the system is trying to access is not defined in the SAP system.
  Incorrect Destination Name: The name of the destination being referenced in the code or configuration does not match any existing destination.
  Authorization Issues: The user may not have the necessary authorizations to access the destination.
  Network Issues: There may be network connectivity issues preventing access to the destination.
  Configuration Errors: There may be misconfigurations in the HTTP client settings or the destination settings.
  
  
  Solution:
  
  
  Check Destination Configuration:
  
  Go to transaction SM59 (RFC Destinations).
  Look for the HTTP destination that is supposed to be used. Ensure that it is defined