How To Fix TR779 - Requests with archived object keys are not released

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 779

• Message text: Requests with archived object keys are not released

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 TR779 - Requests with archived object keys are not released ?

  The SAP error message TR779 indicates that there are transport requests that contain archived object keys, which cannot be released. This typically occurs when the transport request includes objects that have been archived in the system, and the system does not allow the release of such requests.
  Cause:
  
  Archived Objects: The transport request includes objects that have been archived. Archiving is a process in SAP that moves data from the database to a storage medium to improve performance and manage data volume.
  Transport Request Integrity: SAP enforces integrity checks on transport requests to ensure that all objects within a request are available and not archived. If any object in the request is archived, the request cannot be released.
  
  Solution:
  To resolve the TR779 error, you can follow these steps:
  
  
  Identify Archived Objects:
  
  Use transaction code SE01 or SE09 to display the transport request.
  Check the objects included in the transport request to identify which ones are archived.
  
  
  
  Remove Archived Objects:
  
  If possible, remove the archived objects from the transport request. You can do this by editing the transport request and excluding the archived objects.
  Alternatively, you may need to create a new transport request that only includes non-archived objects.
  
  
  
  Unarchive Objects (if necessary):
  
  If the archived objects are still needed, consider unarchiving them if your business process allows it. This may involve restoring the objects from the archive.
  
  
  
  Consult with Basis Team:
  
  If you are unsure about the implications of unarchiving or removing objects, consult with your SAP Basis team or system administrator for guidance.
  
  
  
  Check Transport Logs:
  
  Review the transport logs for additional details on the error and to ensure that there are no other issues preventing the release of the transport request.
  
  
  
  Related Information:
  
  Archiving Process: Understand the archiving process in SAP and how it affects transport requests. This can help in planning future transports and managing object lifecycles.
  Transport Management System (TMS): Familiarize yourself with TMS and how it handles transport requests, including the rules around archived objects.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates regarding this error message.
  
  By following these steps, you should be able to resolve the TR779 error and successfully release your transport request.