How To Fix ESH_ESAAS_MSG060 - Status of async. service call (ESaaS) is not available

ESH_ESAAS_MSG060 - Overview

• Message type: E = Error

• Message class: ESH_ESAAS_MSG - Search as a Service (ESaaS)

• Message number: 060

• Message text: Status of async. service call (ESaaS) is not available

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_ESAAS_MSG060 - Status of async. service call (ESaaS) is not available ?

  The SAP error message ESH_ESAAS_MSG060 indicates that the status of an asynchronous service call (ESaaS - Enterprise Services as a Service) is not available. This error typically arises in the context of SAP's Enterprise Search or related services when there is an issue with the asynchronous processing of a service call.
  Causes:
  
  Service Unavailability: The asynchronous service may not be available due to system downtime, maintenance, or configuration issues.
  Network Issues: There may be network connectivity problems that prevent the service from being reached.
  Configuration Errors: Incorrect configuration settings in the SAP system or in the ESaaS setup can lead to this error.
  Timeouts: The service call may have timed out due to long processing times or heavy load on the system.
  Data Issues: There may be issues with the data being processed, such as missing or invalid data.
  
  Solutions:
  
  Check Service Status: Verify if the asynchronous service is up and running. You can check the service status