How To Fix DAAG_API035 - Undo run &1 could not be stopped

SAP Error Message - Details

• Message type: E = Error

• Message class: DAAG_API - Message Class for Data Aging API

• Message number: 035

• Message text: Undo run &1 could not be stopped

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 DAAG_API035 - Undo run &1 could not be stopped ?

  The SAP error message DAAG_API035 indicates that an undo run (a process that reverses changes made during a previous run) could not be stopped. This error typically occurs in the context of data archiving or data management processes within SAP systems.
  Cause:
  
  Active Processes: The undo run may still be actively processing, and therefore cannot be stopped until it completes.
  System Lock: There may be locks on the database or specific tables that prevent the undo run from being stopped.
  Configuration Issues: There could be misconfigurations in the archiving settings or parameters that are causing the issue.
  Technical Errors: There may be underlying technical issues, such as database connectivity problems or system resource constraints.
  
  Solution:
  
  Check Active Processes: Use transaction codes like SM50 or SM66 to check if the undo run is still active. If it is, you may need to wait for it to complete.
  Review Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context about why the undo run cannot be stopped.
  System Locks: Investigate if there are any locks on the database that might be preventing the operation. You can use transaction SM12 to check for locks.
  Configuration Review: Review the configuration settings related to the archiving process to ensure they are set up correctly.
  Restart the Process: If the undo run is stuck, you may need to restart the process or the entire system, but this should be done with caution and ideally during a maintenance window.
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. They may provide patches or specific guidance based on your system's configuration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM50 (Process Overview), SM66 (Global Process Overview), SLG1 (Application Log), and SM12 (Lock Entries).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to data archiving and undo runs for best practices and configuration guidelines.
  
  Always ensure that you have proper backups and that you are following your organization's change management policies when making changes to the system.