How To Fix ESH_QL_MSG068 - Transaction calculation already running; second instance terminated

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_QL_MSG - ESH Query Logging

• Message number: 068

• Message text: Transaction calculation already running; second instance terminated

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_QL_MSG068 - Transaction calculation already running; second instance terminated ?

  The SAP error message ESH_QL_MSG068 indicates that a transaction calculation is already in progress, and a second instance of the same transaction has been terminated to prevent conflicts or data inconsistencies. This error typically occurs in the context of SAP Enterprise Search or similar applications where multiple instances of a calculation or process cannot run simultaneously.
  Cause:
  
  Concurrent Execution: The error is primarily caused by an attempt to start a second instance of a transaction that is already being processed. This can happen if a user or a background job tries to execute the same transaction while the first instance is still running.
  Long-Running Processes: If the initial transaction takes a long time to complete, it may lead to users attempting to rerun the transaction, resulting in this error.
  System Configuration: Certain configurations in the SAP system may limit the number of concurrent executions for specific transactions.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait for the first instance of the transaction to complete. You can check the status of the transaction in the relevant transaction logs or monitoring tools.
  Check Background Jobs: If the transaction is running as a background job, you can check the job status using transaction SM37. If the job is stuck or taking too long, you may need to analyze and resolve the underlying issue.
  Review Transaction Logic: If this error occurs frequently, review the logic of the transaction to ensure it is optimized and does not take an excessive amount of time to complete.
  Increase Concurrency: If appropriate, consider adjusting system settings to allow for more concurrent executions of the transaction, but be cautious as this may lead to other issues such as data inconsistencies.
  User Training: Educate users about the implications of running the same transaction multiple times and encourage them to check if a process is already running before initiating a new one.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in the process, such as SE38 (for executing programs) or SM37 (for monitoring jobs).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  System Logs: Review system logs (transaction SLG1) for additional context or error messages that may provide more insight into why the transaction is taking longer than expected.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.