How To Fix ESH_FL_MSG168 - Task with key &1 of job &2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_FL_MSG - File Processing

• Message number: 168

• Message text: Task with key &1 of job &2 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_FL_MSG168 - Task with key &1 of job &2 not found ?

  The SAP error message ESH_FL_MSG168, which states "Task with key &1 of job &2 not found," typically occurs in the context of the SAP Enterprise Search or the SAP NetWeaver system when a scheduled job or task cannot be found or has been deleted.
  Cause:
  
  Job Deletion: The job or task that the system is trying to reference has been deleted or is no longer available in the system.
  Job Not Scheduled: The job may not have been scheduled correctly, or it may not have been executed yet.
  Database Issues: There could be issues with the database or the job management tables that prevent the system from retrieving the job information.
  Authorization Issues: The user may not have the necessary authorizations to view or access the job/task.
  
  Solution:
  
  Check Job Status: Use transaction code SM37 to check the status of the job. Look for the job with the specified job name and see if it exists or if it has been deleted.
  Re-schedule the Job: If the job is not found, you may need to re-schedule it. Ensure that the job is set up correctly and that all parameters are properly configured.
  Check Logs: Review the job logs for any errors or warnings that might indicate why the job is not found.
  Database Consistency: If you suspect database issues, you may need to run consistency checks or consult with your database administrator.
  Authorization Check: Ensure that the user has the necessary authorizations to access job information. You may need to check roles and permissions.
  System Restart: In some cases, a system restart may help resolve temporary issues related to job management.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM36 (Job Scheduling), and SM21 (System Log) for troubleshooting.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review the SAP documentation related to job scheduling and management for best practices and guidelines.
  
  If the issue persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.