How To Fix /SMB/RUNTIME_CORE104 - System failure when locking Activity &1 (Type &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/RUNTIME_CORE -

• Message number: 104

• Message text: System failure when locking Activity &1 (Type &2)

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 /SMB/RUNTIME_CORE104 - System failure when locking Activity &1 (Type &2) ?

  The SAP error message /SMB/RUNTIME_CORE104 System failure when locking Activity &1 (Type &2) typically indicates that there is a problem related to the locking mechanism in the SAP system. This error can occur in various scenarios, often related to the Business Suite or specific applications that utilize the SAP Business Workflow or similar functionalities.
  Causes:
  
  
  Locking Issues: The error usually arises when the system is unable to acquire a lock on a specific activity or resource. This can happen if:
  
  The resource is already locked by another process.
  There is a deadlock situation where two or more processes are waiting for each other to release locks.
  The lock table is full or has reached its limit.
  
  
  
  Database Issues: Problems with the underlying database, such as connectivity issues or transaction log problems, can also lead to this error.
  
  
  System Configuration: Incorrect configuration settings in the SAP system or the application can lead to locking issues.
  
  
  Code Issues: Custom code or enhancements that improperly handle locking mechanisms can also trigger this error.
  
  
  Solutions:
  
  
  Check Lock Entries: Use transaction code SM12 to check for existing lock entries. If you find locks that are no longer needed, you can delete them (ensure that you have the necessary authorizations and that it is safe to do so).
  
  
  Review System Logs: Check the system logs using transaction SM21 for any related errors or warnings that might provide more context about the issue.
  
  
  Analyze Work Processes: Use transaction SM50 to monitor the work processes and see if there are any processes that are stuck or waiting indefinitely.
  
  
  Increase Lock Table Size: If the lock table is full, consider increasing its size. This can be done by adjusting the profile parameters in the instance profile (e.g., enque/table_size).
  
  
  Check for Deadlocks: If you suspect a deadlock, you may need to analyze the situation further. Use transaction SM21 to look for deadlock messages or use the database's tools to analyze locks.
  
  
  Review Custom Code: If the error is related to custom developments, review the code to ensure that locks are being handled correctly.
  
  
  System Restart: In some cases, a system restart may help clear temporary issues, but this should be done with caution and proper planning.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches or updates.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM21: System log.
  SM50: Monitor work processes.
  SM37: Monitor job logs.
  
  
  
  SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance, providing them with detailed logs and error messages.
  
  
  Documentation: Review SAP documentation related to locking mechanisms and performance tuning for more insights.
  
  
  By following these steps, you should be able to diagnose and resolve the /SMB/RUNTIME_CORE104 error effectively.