How To Fix ESH_REMSEARCH059 - Connection &1 is updated via default schedule

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_REMSEARCH - ES Remote Search

• Message number: 059

• Message text: Connection &1 is updated via default schedule

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_REMSEARCH059 - Connection &1 is updated via default schedule ?

  The SAP error message ESH_REMSEARCH059 indicates that a connection (in this case, denoted as &1) is being updated via a default schedule. This message typically arises in the context of SAP Enterprise Search or SAP HANA, where scheduled jobs are used to update or refresh data connections.
  Cause:
  
  Scheduled Job: The error suggests that there is a scheduled job that is responsible for updating the connection. This could be due to a configuration where the connection is set to refresh at specific intervals.
  Connection Issues: There may be issues with the connection itself, such as network problems, incorrect credentials, or misconfigured settings.
  Data Source Changes: If the underlying data source has changed (e.g., schema changes, data model changes), it may affect the connection and lead to this message.
  System Performance: If the system is under heavy load, it may affect the ability to update connections in a timely manner.
  
  Solution:
  
  Check Scheduled Jobs: Review the scheduled jobs in the SAP system to see when the connection is set to update. You can do this in transaction codes like SM37 (Job Monitoring) to check the status of the job.
  Connection Configuration: Verify the configuration of the connection. Ensure that the connection parameters (like host, port, user credentials) are correct and that the data source is accessible.
  Monitor System Performance: Check the system performance and resource utilization. If the system is under heavy load, consider optimizing the job scheduling or increasing system resources.
  Review Logs: Look at the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Manual Update: If necessary, you can manually trigger the update of the connection to see if it resolves the issue. This can often be done through the relevant transaction or interface in SAP.
  Consult Documentation: Refer to SAP documentation or notes related to the specific version of SAP you are using for any known issues or additional troubleshooting steps.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  System Administration: Involve your SAP Basis team if the issue persists, as they may have deeper insights into system configurations and performance tuning.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the ESH_REMSEARCH059 error message.