How To Fix ESH_EX035 - System is currently locked for updates, e.g. because backup is running

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_EX - Extraction

• Message number: 035

• Message text: System is currently locked for updates, e.g. because backup is running

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_EX035 - System is currently locked for updates, e.g. because backup is running ?

  The SAP error message ESH_EX035 indicates that the system is currently locked for updates. This typically occurs when a backup process is running or when the system is in a state that prevents updates to ensure data integrity. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Backup Process: The most common reason for this error is that a database backup is currently in progress. During this time, the system may be locked to prevent any changes to the data.
  System Maintenance: Other maintenance activities, such as system upgrades or data migrations, can also lead to this error.
  Long-running Transactions: If there are long-running transactions or processes that are holding locks, it may prevent updates.
  Configuration Settings: Certain configurations in the system may lead to locking behavior during specific operations.
  
  Solution:
  
  Wait for Backup Completion: If a backup is running, the simplest solution is to wait until the backup process is completed. You can check the status of the backup in the system logs or monitoring tools.
  Check for Long-running Processes: Use transaction codes like SM66 (Global Work Process Overview) or SM50 (Work Process Overview) to identify any long-running processes that may be holding locks. If necessary, you can terminate these processes, but do so with caution.
  Review System Logs: Check the system logs (transaction SM21) for any messages related to the locking situation. This can provide insights into what is causing the lock.
  Consult with Basis Team: If you are not able to resolve the issue, it may be necessary to consult with your SAP Basis team. They can provide more detailed insights and may need to intervene if there are issues with the backup or other maintenance tasks.
  Check Configuration: Review the system configuration to ensure that there are no settings that are causing unnecessary locks during normal operations.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM21 (System Log), SM37 (Job Monitoring), SM66 (Global Work Process Overview), and SM50 (Work Process Overview) to monitor system activities.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Review SAP documentation related to system maintenance and backup processes to understand how they interact with system locks.
  
  In summary, the ESH_EX035 error is typically a temporary issue related to system maintenance activities. Monitoring the system and waiting for the completion of ongoing processes is usually the best course of action. If the issue persists, further investigation with the help of your technical team may be required.