How To Fix OT779 - Locked package successfully published in SMP

OT779 - Overview

• Message type: E = Error

• Message class: OT - SAP Online Correction Support (SOCS)

• Message number: 779

• Message text: Locked package successfully published in SMP

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.

OT779 - Details

• The SAP error message OT779 "Locked package successfully published in SMP" typically indicates that a package in the SAP Mobile Platform (SMP) has been locked, preventing further modifications or deployments until it is unlocked. This can occur for various reasons, such as a package being in use, an ongoing deployment, or administrative actions that require the package to be locked.
  
  Cause:
  
  Ongoing Deployment: If a deployment process is currently running, the package may be locked to prevent changes during this time.
  Manual Locking: An administrator may have manually locked the package to prevent changes while performing maintenance or updates.
  System Error: Sometimes, system errors or interruptions can lead to a package being locked unintentionally.
  
  
  Solution:
  
  Check Deployment Status: Ensure that no deployment processes are currently running. If a deployment is in progress, wait for it to complete.
  Unlock the Package: If you have administrative access, you can unlock the package through the SMP management console. Look for