How To Fix SZDM_LOCK818 - MS subsytem separation was already activated

SAP Error Message - Details

• Message type: E = Error

• Message class: SZDM_LOCK - To be used for messages due to read only locks

• Message number: 818

• Message text: MS subsytem separation was already activated

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 SZDM_LOCK818 - MS subsytem separation was already activated ?

  The SAP error message SZDM_LOCK818 indicates that the MS (Message Server) subsystem separation has already been activated. This error typically arises in the context of SAP systems that are configured for multiple application servers, particularly when there are attempts to activate or modify the configuration related to the message server.
  Cause:
  The error occurs when there is an attempt to activate the MS subsystem separation feature in a system where it has already been enabled. This can happen due to:
  
  Configuration Changes: An administrator may have attempted to reconfigure the message server settings without realizing that the subsystem separation was already active.
  System Upgrades or Migrations: During system upgrades or migrations, certain settings may be retained, leading to confusion about the current configuration state.
  Multiple Administrators: If multiple administrators are working on the system, one may activate the feature while another is unaware, leading to conflicting actions.
  
  Solution:
  To resolve the SZDM_LOCK818 error, you can follow these steps:
  
  
  Check Current Configuration:
  
  Use transaction code SMD or SCC4 to check the current configuration of the message server and verify if the subsystem separation is indeed activated.
  
  
  
  Review System Logs:
  
  Check the system logs (transaction SM21) for any related messages that might provide additional context or details about the activation process.
  
  
  
  Deactivate Subsystem Separation (if necessary):
  
  If you need to deactivate the subsystem separation, you can do so by modifying the relevant profile parameters. This typically involves changing the ms/enable_subsystem_separation parameter to 0 (disabled).
  After making changes, restart the message server for the changes to take effect.
  
  
  
  Consult Documentation:
  
  Review the official SAP documentation or notes related to message server configuration and subsystem separation for any specific instructions or considerations.
  
  
  
  Contact SAP Support:
  
  If the issue persists or if you are unsure about making changes, consider reaching out to SAP support for assistance. They can provide guidance based on your specific system configuration and requirements.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SMD (for monitoring), SM21 (for logs), and SCC4 (for client settings).
  SAP Notes: Search for SAP Notes related to message server configuration and subsystem separation for any known issues or additional troubleshooting steps.
  System Documentation: Ensure that you have access to the system documentation that outlines the configuration settings and best practices for managing the message server.
  
  By following these steps, you should be able to address the SZDM_LOCK818 error and ensure that your SAP system's message server configuration is correctly set up.