How To Fix ESH_TAU_MSG017 - Recurrying harvesting for Job Id &1 is already scheduled

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_TAU_MSG - Test Automation

• Message number: 017

• Message text: Recurrying harvesting for Job Id &1 is already scheduled

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_TAU_MSG017 - Recurrying harvesting for Job Id &1 is already scheduled ?

  The SAP error message ESH_TAU_MSG017 indicates that a recurring harvesting job for a specific Job ID is already scheduled. This typically occurs in the context of SAP Enterprise Search or SAP Data Hub, where harvesting jobs are used to collect and index data from various sources.
  Cause:
  The error is caused by an attempt to schedule a new harvesting job when there is already an existing job scheduled for the same Job ID. This can happen if:
  
  A user tries to manually schedule a job that is already set to run at a specific interval.
  There is a misconfiguration in the job scheduling settings.
  A previous job has not completed or has failed, leading to a lock on the Job ID.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check Scheduled Jobs:
  
  Go to the job scheduling interface in your SAP system (e.g., transaction code SM37 for job monitoring).
  Look for any existing jobs with the same Job ID that are currently scheduled or running.
  
  
  
  Cancel or Delete Existing Job:
  
  If you find that the job is still running or scheduled, you may need to cancel or delete it before you can schedule a new one.
  Ensure that you have the necessary permissions to perform this action.
  
  
  
  Review Job Configuration:
  
  Check the configuration settings for the harvesting job to ensure that it is set up correctly and that there are no conflicts in scheduling.
  
  
  
  Wait for Completion:
  
  If the existing job is still running, you may need to wait for it to complete before scheduling a new one.
  
  
  
  Check for Errors:
  
  If the existing job has failed, investigate the logs to understand why it failed and resolve any underlying issues before attempting to reschedule.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or support notes related to the specific version of your SAP system for any additional troubleshooting steps or known issues.
  
  
  
  Related Information:
  
  Job Monitoring: Use transaction codes like SM37 (Job Monitoring) to view the status of scheduled jobs.
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message ESH_TAU_MSG017.
  System Logs: Review system logs (transaction SLG1) for any related error messages that might provide more context on the issue.
  
  If the problem persists after following these steps, consider reaching out to your SAP support team for further assistance.