How To Fix SOI2424 - System is locked: Ddic or SAP* can still login

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI2 - SOI Messages

• Message number: 424

• Message text: System is locked: Ddic or SAP* can still login

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 SOI2424 - System is locked: Ddic or SAP* can still login ?

  The SAP error message SOI2424 indicates that the system is locked, which typically means that the system is in a restricted state for maintenance or security reasons. However, it also notes that users with certain special authorizations (like DDIC or SAP*) can still log in, which is a common configuration in SAP systems to allow administrators to perform necessary tasks even when the system is locked for regular users.
  Cause:
  
  System Lock: The system may be locked due to maintenance activities, upgrades, or security measures.
  User Authorizations: Users with special authorizations (like DDIC or SAP*) are exempt from the lock, allowing them to log in and perform administrative tasks.
  Configuration Settings: The system may be configured to allow certain users to bypass the lock for emergency access.
  
  Solution:
  
  
  Unlock the System:
  
  If you are an administrator, you can unlock the system by executing the following steps:
  
  Go to transaction code SCC4 (Client Administration).
  Select the client that is locked.
  Change the status from "Locked" to "Active".
  
  
  Alternatively, you can use transaction SM01 to unlock specific transactions if needed.
  
  
  
  Check for Maintenance:
  
  Verify if there are any ongoing maintenance activities that require the system to be locked. If so, coordinate with your team to determine when it can be unlocked.
  
  
  
  Review User Authorizations:
  
  Ensure that only necessary users have access to log in during a system lock. Review the roles and authorizations assigned to users like DDIC and SAP*.
  
  
  
  Consult Documentation:
  
  Check SAP notes or documentation related to system locking and user authorizations for any specific guidelines or best practices.
  
  
  
  Related Information:
  
  User Roles: The DDIC user is a standard SAP user with full authorizations, typically used for development and administrative tasks. The SAP* user is a default administrative user.
  Security Best Practices: It is generally recommended to limit the use of DDIC and SAP* accounts and to create specific administrative users with the necessary authorizations to enhance security.
  System Monitoring: Regularly monitor system status and user logins to ensure that unauthorized access is not occurring during maintenance periods.
  
  If you continue to experience issues or if the system remains locked without a clear reason, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.