How To Fix TN799 - The archive &1 is not digitally signed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 799

• Message text: The archive &1 is not digitally signed

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 TN799 - The archive &1 is not digitally signed ?

  The SAP error message TN799, which states "The archive &1 is not digitally signed," typically occurs when you are trying to import or process an archive file (such as a transport request or a software component) that is expected to be digitally signed, but the signature is either missing or invalid.
  Cause:
  
  Missing Digital Signature: The archive file you are trying to import does not have a digital signature attached to it.
  Invalid Signature: The digital signature present in the archive file is not valid, possibly due to corruption or tampering.
  Incorrect Configuration: The system may not be configured correctly to recognize or validate the digital signatures.
  Transport Directory Issues: The transport directory may have issues that prevent the system from accessing the necessary signature verification files.
  
  Solution:
  
  Check the Archive File: Ensure that the archive file you are trying to import is indeed supposed to be digitally signed. If it is not, you may need to obtain the correct version of the file.
  Verify Signature: If the file is supposed to be signed, check the signature using appropriate tools or commands to ensure it is valid.
  Recreate the Archive: If you have access to the original transport request or software component, try to recreate the archive with a valid digital signature.
  Check Configuration: Ensure that your SAP system is properly configured to handle digital signatures. This may involve checking the settings in transaction STRUST (SSL Server Standard Trust) or related configuration.
  Transport Directory: Check the transport directory for any issues. Ensure that the transport files are not corrupted and that the necessary files for signature verification are present.
  Consult Documentation: Refer to SAP documentation or notes related to digital signatures and transport management for any specific instructions or troubleshooting steps.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Transport Management System (TMS): Familiarize yourself with the TMS configuration and how it handles digital signatures.
  Security Settings: Review the security settings in your SAP system, especially those related to digital signatures and transport requests.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.