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

UG171 - Overview

• 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