How To Fix TN734 - Cannot unpack to "DIR_EPS_ROOT/in" (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: TN - Support Package Manager (SPAM) Messages

• Message number: 734

• Message text: Cannot unpack to "DIR_EPS_ROOT/in" (see long text)

What causes this issue?

The files in the CAR/SAR archives have to be disassembled to the "in"
subdirectory of the directory that is defined by the profile parameter
DIR_EPS_ROOT.
In this SAP system, the parameter DIR_EPS_ROOT references the directory
"&V2&". Since the files in the CAR/SAR archive are packed with the
relative path "EPS/in", and the directory that was defined by
DIR_EPS_ROOT does not correspond to the schema "<(><path>/EPS<)>", the
system cannot disassemble to "$DIR_EPS_ROOT/in".

System Response

The files are disassembled to the "EPS/in" subdirectory of the transport
directory ("&V1&").

How to fix this error?

Continue to disassemble. Copy the disassembled files to the
"$DIR_EPS_ROOT/in" directory. In the Support Package Manager or the
Add-On Installation Tool, choose <LS>'Load Packages' -> 'From
Application Server'</>.
If you want to make automatic disassembly possible, change the path of
your EPS directory so that it corresponds to the schema "<(><path>/EPS
<)>", and adjust the profile parameter DIR_EPS_ROOT accordingly.

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 TN734 - Cannot unpack to "DIR_EPS_ROOT/in" (see long text) ?

  The SAP error message TN734, which states "Cannot unpack to 'DIR_EPS_ROOT/in'", typically occurs during the transport process when the system is unable to unpack transport requests into the specified directory. This can happen for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Directory Permissions: The user or the system may not have the necessary permissions to write to the specified directory (DIR_EPS_ROOT/in).
  Disk Space: The target directory may be out of disk space, preventing the unpacking of transport requests.
  File System Issues: There may be issues with the file system, such as corruption or misconfiguration.
  Transport Directory Configuration: The transport directory may not be correctly configured in the system settings.
  Transport Request Corruption: The transport request itself may be corrupted or incomplete.
  
  Solutions:
  
  
  Check Permissions:
  
  Ensure that the user under which the SAP system is running has the necessary permissions to write to the DIR_EPS_ROOT/in directory.
  You can check and modify permissions using operating system commands (e.g., chmod on Unix/Linux).
  
  
  
  Check Disk Space:
  
  Verify that there is sufficient disk space available on the file system where the DIR_EPS_ROOT/in directory resides.
  Free up space if necessary.
  
  
  
  Check File System:
  
  Run file system checks to ensure there are no issues with the file system that could be causing the problem.
  On Unix/Linux, you can use commands like fsck to check the file system.
  
  
  
  Verify Transport Directory Configuration:
  
  Check the transport directory settings in the SAP system. You can do this by navigating to transaction STMS and checking the configuration.
  Ensure that the transport directory paths are correctly set.
  
  
  
  Check Transport Request:
  
  If the transport request is suspected to be corrupted, you may need to recreate it or check the logs for any errors during its creation.
  
  
  
  Review SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like STMS (Transport Management System) to manage transport requests and check configurations.
  Logs: Review the transport logs for more detailed error messages that can provide additional context for the issue.
  SAP Community: Consider searching or posting in the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.