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

TN799 - Overview

• 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