How To Fix UG171 - ADDON: Transport & was already archived and cannot be read (see longtext)

SAP Error Message - Details

• Message type: E = Error

• Message class: UG - Messages for Repository Switch

• Message number: 171

• Message text: ADDON: Transport & was already archived and cannot be read (see longtext)

What causes this issue?

To determine the objects which need to be rescued during the upgrade,
RDDIT006 needs to read different transport requests. In this system
table entries of table E071K were already archived and thus the needed
information is not available in the system anymore.

System Response

SUM stops with error message.

How to fix this error?

Check note 1901786 and restore the entries for the mentioned transport.
After that repeat the phase within SUM.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UG171 - ADDON: Transport & was already archived and cannot be read (see longtext) ?

  The SAP error message UG171 indicates that a transport request (or transport) has been archived and cannot be accessed or read in its current state. This typically occurs when a transport request has been moved to an archive for storage, often as part of a system maintenance or data management strategy.
  Cause:
  
  Archiving Process: The transport request has been archived as part of a regular maintenance process. This is done to free up space in the transport directory and to manage the transport landscape effectively.
  System Configuration: The system may be configured to automatically archive transport requests after a certain period or after they have been imported into the target system.
  Manual Archiving: An administrator may have manually archived the transport request.
  
  Solution:
  
  
  Restore the Transport Request: If you need to access the transport request, you will need to restore it from the archive. This typically involves using the SAP Archive Management tools to retrieve the archived transport request.
  
  Use transaction code SARA to access the Archive Management.
  Identify the relevant archive object for transport requests and restore the specific transport request.
  
  
  
  Check Transport Logs: Review the transport logs to understand the status of the transport request and determine if it can be re-imported or if there are any dependencies that need to be addressed.
  
  
  Consult Documentation: Refer to the SAP documentation or help files for specific instructions on how to manage archived transport requests in your version of SAP.
  
  
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is impacting your development or production environment.
  
  
  Related Information:
  
  Transport Management System (TMS): Understanding how the TMS works can help in managing transports effectively and knowing when they might be archived.
  Archiving Strategy: Review your organization's archiving strategy for transports to ensure it aligns with your operational needs.
  System Performance: Regularly archiving transports can help improve system performance by reducing the amount of data in the transport directory.
  
  Preventive Measures:
  
  Regular Monitoring: Keep an eye on transport requests and their statuses to avoid unexpected issues.
  Documentation: Maintain clear documentation of transport requests and their purposes to facilitate easier management and retrieval if needed.
  Training: Ensure that team members are trained on the transport management and archiving processes to minimize errors and improve efficiency.
  
  By following these steps, you should be able to address the UG171 error and manage your transport requests more effectively.