Child pages
  • UNIX Error and Warning Messages
Skip to end of metadata
Go to start of metadata

This appendix contains reference information on all error and warning messages that can occur in PKZIP. An error usually causes the canceling of the task you are performing such as compressing a file. A warning usually indicates that something is wrong, but it is not severe enough to cancel an entire task. It might also be a reminder or query prompt. PKZIP will also return any error codes to the shell. If there were no warnings or errors, 0 is returned.

Error Messages

When an error occurs, PKZIP displays an error message. The following is a description of each error message.

Error

Potential Cause(s)

(E2) Ambiguous option or command specified - XXX.

If you abbreviate an option on your command line, make sure that you are supplying enough characters in the option to delineate it from similarly spelled options. If, for example, you only specify -pr on your command line, PKZIP will generate the (E2) error because it cannot determine whether you are specifying the print or preview option.

(E3) Ambiguous sub-option specified - XXX.

If you abbreviate a sub-option on your command line, make sure that you are supplying enough characters in the sub-option to delineate it from similarly spelled sub-options. If, for example, you only specify -sort=na on your command line, PKZIP will generate the (E3) error because it cannot determine whether you are specifying the name or natural sub-option.

(E4) Unknown or illegal option - XXX.

The option you specified on the command line is invalid. It does not match any known options. Verify that you typed the option correctly. Check the spelling.

(E5) Unknown or illegal sub-option - XXX.

The sub-option you specified on the command line is invalid. It does not match any known sub-options. Verify that you typed the sub-option on your command line correctly. Verify that you are not using an illegal sub-option (-add -sort=crc). Check the spelling.

(E6) No .ZIP file specified.

There was not a .ZIP file specified on the command line. PKZIP does not accept wildcards for .ZIP file name when adding files to a .ZIP archive.

(E7) Can't create: XXX.

PKZIP could not create a .ZIP file when fixing. PKZIP could not create a volume label on a spanned archive. PKZIP could not create a temporary file for a spanned archive. Verify that you have write access to the drive or removable media on which you are creating these files.

(E8) Nothing to do!

You did not do something that is required for a task. For example, PKZIP could not find the file you are trying to open or access. You might have specified to update a pattern such as *.txt and PKZIP did not find any files that matched or that needed updating.

(E9) No file(s) were processed

PKZIP cannot find the file you are trying to access. For example, you might be trying to extract files from a .ZIP archive that do not exist in that archive. Verify that the file(s) you specify on the command line exactly match the file(s) in the .ZIP file. If, for example, the file in the archive is stored with path information, and you attempt to extract it but specify only the file name, you will get the (E9) error.

(E10) No files specified for deletion.

There are no files or file patterns specified for deletion on the command line. In lieu of a specified file or file pattern, PKZIP will not assume that the user wishes to specify all (*) files.

(E11) Disk full, file: XXX.

The hard disk or floppy disk you are writing to is full. This error occurs when PKZIP attempts to write a .ZIP file, or extract a file contained in a .ZIP file to a hard or floppy disk that is full. Free up sufficient disk space and try again.

(E12) Can't find file: XXX.

PKZIP cannot find the .ZIP file you specified. This error will only occur when you use commands/options/sub-options that work with existing .ZIP files. Verify that the file is specified correctly. If you are adding files to an archive, verify that you place the .ZIP file name before specifying files to be added on the command line. If the .ZIP file is not in the same directory where you typed the command, make sure to include path information. For example:

pkzipc -add=freshen /temp/test.zip *.txt

(E13) Can't open .ZIP file: XXX.

The named .ZIP file is read-only or locked by another application and cannot be modified. This may also occur on a Network drive if you do not have sufficient access rights to the file to allow you to modify it.

(E14) Can't create archive: XXX.

PKZIP is not able to create the archive file. Verify that the destination directory is not full, the archive file does not already exist. If you are creating the file on a network drive, confirm that you have the appropriate rights to the network file system.

(E15) Renaming temporary .ZIP file, saved as: XXX.

PKZIP could not rename the temporary file to the specified .ZIP file name. Verify that the destination drive is not full. If you are updating a non-spanned .ZIP file on removable media and the updated archive exceeds the size available on the removable media, you will receive the (E15) error. You will need to recreate the archive for spanning. Keep in mind that you cannot update a spanned archive. If you are creating the file on a network drive, confirm that you have the appropriate rights to the network file system.

(E16) Can't open for write access, file: XXX.

PKZIP is unable to write to the specified file or device. Verify that you have write access to the file or that your printer is configured correctly. Additionally if you are using the PKSFXS.DAT file, verify that you have PKSFXSDATA environment variable configured correctly.

(E17) Error encrypting file data.

PKZIP encountered a problem with the compressed data that it was trying to encrypt. For example, the disk on which the compressed data was located was bad or corrupt.

(E18) Can't open list file: XXX.

The named list file could not be found. It does not exist, was spelled incorrectly, is not located in the specified directory, or cannot be accessed because the user does not have the appropriate rights to the file.

(E19) Aborted file extract.

Extraction process was terminated by the user while changing disks during a disk spanning operation. The error also occurs on attempting to extract a bad TAR archive.

(E20) Aborted file compression.

Compression process was terminated by the user while changing disks during a disk spanning operation.

(E21) Can't modify a spanned or split .ZIP file

Spanned or split .ZIP files cannot be modified. The archive will need to be recreated.

(E22) Cannot format removable media.

The media cannot be formatted. The media may be write-protected.

(E23) Suboption is too long

The option is too long; that is, longer than 270 characters. See if you can abbreviate the name of the option or its sub-option to make it shorter.

(E24) Insufficient disk space for ZIP comment.

There is not enough space on the system or media to write the ZIP comment.

(E25) Insufficient disk space for updated file.

Insufficient disk space for the new archive. If you are adding files to an archive on a removable media, the media may not be large enough to write the modified file (too large).

(E26) Device not ready: XXX.

The removable media device is not ready. The disk may not be in the drive properly.

(E27) 2.04g compatibility cannot be used with the option - XXX

Option 204, which creates an archive compatible with PKZIP for DOS v. 2.04g, was used with another option that is not supported for that version of PKZIP

(E28) Share violation, file is in use by another process: XXX

The archive XXX is not in a format which PKZIP can understand or contains errors. The errors could be caused by many things but usually mean the archive is corrupted.

(E29) Missing sub-option –XXX

Many options require a sub-option to work. In this case, a required sub-option is missing. Add the appropriate sub-option to your command.

(E34) Invalid archive format: <archive name>

The file is not in a format currently supported by PKZIP, or you attempted to use SecureZIP Partner to extract a non-ZIP archive.

(E58) Invalid archive - method not supported.

The archive uses a compression method that currently is not supported.

(E65) Could not encode archive file: XXX.

The file could not be encoded.

(E71) Can't open PKCS#7 file: XXX.

PKZIP cannot open the PKCS#7 because the file does not exist, user cannot read the file, or file is not a valid PKCS#7.

(E72) PKZIP wanted user input, but silent=input or silent=all was specified

If PKZIP needs user input—for example, to say whether files should be overwritten—but -silent=input or -silent=all is specified on the command line to hide PKZIP messages and prompts, PKZIP halts processing and issues this error.

(E73) Warning configured as an error

The warning immediately preceding this error message has been specified (with the error option) to be treated as a fatal error.

(E75) Incorrect passphrase or certificate not found, unable to open archive: <archive name>

The archive contains encrypted file names that PKZIP cannot decrypt. If the archive is passphrase-protected, you must include the passphrase option with the extract command in the command line.

(E76) Cannot open alternate config file: <file name>

The altconfig option was used, but the specified file could not be opened.

(E77) Archive can only support one file inside!

You tried to add more than one file to an archive of a type that cannot contain multiple files. For example, a GZIP archive can contain no more than one file. If you try to create a GZIP archive to contain three files, PKZIP displays this error and does not create the archive.

(E78) Unable to FTP archive file: <file name>

PKZIP could not transfer the specified file.

(E79) Unable to E-mail archive file: XXX

A problem, perhaps with the network or the mail server, prevented PKZIP from emailing the specified file.

(E80) Unable to run anti-virus

PKZIP was unable to run the anti-virus scanning program. The anti-virus program did not respond to the command line used to launch the program.

(E81) Possible virus detected

The anti-virus program returned a non-zero value after doing a scan. Most anti-virus programs use this return to indicate the possible presence of a virus.

(E82) Too many recipients, recipient count limited to 3275 certificates

You specified too many recipients for encryption. The ZIP file format limits the number of recipients to 3275.

(E83) Specified SFX cannot extract archive created with the option - XXXX

You tried to create an SFX that is not able to handle a feature turned on by the option XXXX. For example, you tried to create a strongly encrypted DOS SFX, or an SFX that uses FNE.

(E84) Fatal policy error - nnnnn, contact your system administrator

A critical problem has occurred with a policy file or policy certificate. The number is a policy error code to help your administrator resolve the problem.
On this error, PKZIP goes into read-only mode. In read-only mode, PKZIP will still extract files from archives but will not add files to a new or existing archive and disables the related controls.

(E85) Unable to encrypt, no certificates passed -strict check

The strict option was used, and no recipient certificates passed strict checking, so no certificate was available to use to encrypt

(E86) Archive is not signed by a specified verification certificate

The verifysigner option was used to specify one or more certificates, but the archive to be extracted was not signed using any of these certificates

(E87) Certificate not found: XXX

The verifysigner option was used to specify one or more certificates, but not all of the certificates could be found, either locally or in a specified LDAP directory

(E88) Multiple certificates found: XXX

The verifysigner option was used to specify one or more certificates, and multiple certificates were found—probably in an LDAP directory—that matched the criterion XXX

(E89) Policy requires the ZIP archive to be encrypted

A policy requires encryption but no passphrase or recipient was specified

(E90) Policy requires the ZIP archive and/or files to be signed

A policy requires the archive to be signed but no signing certificate was specified or none is available

(E91) Policy prohibits creation of non-ZIP archives

Only ZIP archives can be created when a policy requires encryption or signing

(E92) Timeout error on file: XXX

The timeout period elapsed while PKZIP waited for a response from another process before reading or writing more of the specified archive file on a socket or block device

(E93) Timestamp failed

  • PKZIP unable to connect to Internet.
  • Timestamp server URL is incorrect.
  • Problem with signed file. Each file in the archive must be signed with the same hash algorithm. Be sure to sign each file in the archive.
  • Problem with time stamp server. Try again later.

(E94) Can't modify a timestamped .ZIP: <name>

You cannot change an archive (or files in an archive) that has been timestamped.

(E100) Insufficient memory

Insufficient memory is available to process the archive. Try making more memory available to PKZIP. If this does not rectify the problem, then the archive may be corrupted. The -fix command may correct the problem. If you receive this message when you try to create a new archive, possibly you are attempting to compress too many files. Reduce the number of files and try again. If you are using a LIST file in your PKZIP command, the LIST file may be too large. See "Compressing Files with a List File."

(E150) Error reading .ZIP file.

PKZIP cannot read the .ZIP file or is unable to read the central directory record. The file might be located on a corrupt disk or part of a disk. This includes floppy disks.

(E155) Too many files in XXX.

PKZIP cannot add or extract files in excess of the limit of 16,383 with the 204 option enabled. Reduce the number of files you are trying to process.

(E156) File is now too big for valid zip data.

The .ZIP archive is too large and PKZIP is unable to locate the central end record in the .ZIP file. The file is not a valid .ZIP archive or has been corrupted. The fix command may repair the .ZIP file.

(E157) This archive requires a product compliant with ZIP APPNOTE version XX.X

The archive requires a more recent version of PKZIP, or other archiving program, that supports the version of the ZIP file format described in the specified APPNOTE ("application note"). The APPNOTE is a document that is available on the PKWARE Web site.

(E158) Errors encountered reading archive

PKZIP was unable to read the archive.

(E160) Unable to read sponsor list: XXX

Unable to find or read master file with information about PKWARE PartnerLink sponsors

(E161) Unable to read sponsor distribution package

Unable to find or read the distribution package for a PKWARE PartnerLink sponsor

(E162) Unknown sponsor

A sponsor referenced on the command line Is not in the master list of PKWARE PartnerLink sponsors

(E163) Invalid sponsor: <sponsor>

The sponsor distribution package for this PKWARE PartnerLink sponsor failed internal integrity checks. There may be a problem with the signature on the package.

(E164) Archive not signed by an authorized sponsor

SecureZIP Partner cannot extract the archive because it is not signed by a valid PKWARE PartnerLink sponsor.

(E165) Sponsor required but not specified

The SecureZIP Partner command line directed to create an archive, but no PKWARE PartnerLink sponsor recipient was specified (with the sponsor option).

(E166) Unable to create ZIP archive for multiple sponsors

The sponsor option was specified more than once on the SecureZIP Partner command line. An archive cannot be created for multiple sponsors.

(E167) Unable to update ZIP archive using file name encryption

SecureZIP Partner cannot update an archive created with encrypted file names.

(E168) Sponsor not licensed for SecureZIP Partner: <sponsor>

SecureZIP Partner cannot create archives for this PKWARE PartnerLink sponsor. The sponsor is licensed only for extracting archives with Reader, not for using SecureZIP Partner.

(E200) FIPS 140 mode is enabled, but archive is not encrypted with a FIPS-approved algorithm

With the fipsmode option, SecureZIP cannot work with (test, extract, add to, update, view, or open) an archive with encrypted file names that is encrypted using a non-FIPS-approved algorithm.

(E201) FIPS 140 mode is enabled, but encryption requested is not a FIPS-approved algorithm

With the fipsmode option, SecureZIP cannot use the specified algorithm to encrypt. Use listcryptalgorithms with the fipsmode option on to see FIPS-approved algorithms available.

(E202) FIPS 140 mode is enabled, but signature hash requested is not a FIPS-approved algorithm

With the fipsmode option, SecureZIP cannot use the specified hashing algorithm. Use listhashalgorithms with the fipsmode option on to see FIPS-approved algorithms available.

(E203) FIPS 140 mode failed to initialize

FIPS 140 mode could not be initialized for the fipsmode option. The pkzipc binary may be corrupted.

(E252) Only the super user may enter license keys!

You must run PKZIP as root, or be logged on as root, to use the enterlicensekey command.

(E254) Your evaluation period for PKZIP has expired. Please register to continue using this product.

This copy of PKZIP is an evaluation version. If you have purchased PKZIP and have the serial number, enter it when prompted.

(E255) User pressed ctrl-c or control-break.

This error occurs when you press CTRL+BREAK or CTRL+C in the middle of a PKZIP operation.

Warning Messages

Sometimes a condition occurs that might cause a task to pause temporarily. This could be something that prevents part of a task from happening, or simply a message or reminder. For several of these conditions, PKZIP displays a warning message. When a warning occurs, PKZIP returns a value of 1 to the shell.

The following is a description of each warning message:

PKZIP Warning

Potential Cause(s)

(W1) Can't create: XXX.

PKZIP could not create volume label, file, or directory. Verify that you have appropriate access rights to the file or directory.

(W2) Illegal path or drive specified: XXX.

The file being extracted has an invalid name or path. Verify that you have entered the correct path in your command line and that the file does not contain any inappropriate characters such as a colon or leading slash.

(W3) Warning! This file requires a product compliant with ZIP APPNOTE version XX.X

The file requires a more recent version of PKZIP, or other archiving program, that supports the version of the ZIP file format described in the specified APPNOTE ("application note"). The APPNOTE is a document that is available on the PKWARE Web site.

(W4) File fails CRC check.

It is likely that the file PKZIP is trying to extract is corrupt, and was not extracted correctly. For more information, see the   CRC section in "How PKZIP Works in UNIX."

(W7) file: XXX already exists. Overwrite (<Y>es/<N>o/<A>ll/ne<V>er/<R>ename/ <Esc>)?

The file(s) you are trying to extract already exists in the location to which you are extracting. By default, PKZIP prompts you before overwriting a file.

(W8) Could not open file: XXX.

You may not have the proper permissions to access the file or the file may have been locked by another program while PKZIP was trying to access it. If the file is located on a network file system, consult your System Administrator to verify your access rights.

(W9) Could not delete file: XXX.

You do not have the proper permissions to access and delete the file, or another application has the file open. This warning only occurs when the move option is used on the command line.

(W12) Unexpected end of compressed data.

Corrupt data caused PKZIP to abort the extraction before it could finish.

(W13) Skipping encrypted file: XXX.

PKZIP encountered a file that has been passphrase protected. You need the passphrase to access this file.

(W18) Unknown compression method for file: XXX.

An unfamiliar compression method has been used with the current .ZIP file.

(W19) Could not clear archive attribute on file: XXX.

PKZIP could not clear the archive attribute on a file. The file will be compressed but the archive bit cannot be cleared. This warning usually occurs when the add=incremental option is used on the command line.

(W20) Incorrect passphrase for file: XXX.

Verify that you entered the correct passphrase for the file. When a file is passphrase protected, you can only access its contents with the correct passphrase.

Note: Passphrases are case sensitive.

(W21) Invalid temporary file directory: <dir>

PKZIP creates a temporary file for the file(s) being compressed when updating a .ZIP file. PKZIP was unable to create the temporary .ZIP file in the specified location and so used the default temp directory for your system.

(W22) Authenticity Verification Failed!

The Authenticity Verification (AV) information contained in the .ZIP file is corrupt. Failure of AV indicates a file that has been tampered with or damaged. If the file has failed the AV check, the contents are suspect.

(W23) Authenticity Verification Failed!

The stored Authenticity Verification (AV) checksum value did not match the calculated checksum value. The .ZIP file has been tampered with or is perhaps corrupt.

(W26) directory: XXX already exists. Overwrite (<Y>es/<N>o/<A>ll/ne<V>er/<Esc>)?

Assuming the overwrite option is set to prompt, this warning appears when PKZIP attempts to extract a directory over an existing directory with the same name. Answering Y at this prompt will update any extended attributes (EAs) stored in the .ZIP file.

(W29) Can't rename temporary file. Saved as XXX.

PKZIP cannot rename the temporary archive created when updating an archive. The archive was saved under the specified name.

(W36) Empty passphrase, files will not be passphrase protected.

When trying to passphrase protect your file, you entered a passphrase containing no letters or numbers.

(W37) Can't sign file.

This warning appears when PKZIP fails to sign a file using the specified digital certificate. Common reasons are incorrect passphrase for the certificate (not all certificates have passphrases), no private key (certificate needs to have a private key).

(W38) Can't sign central directory.

PKZIP failed to sign the central directory. Common reasons are that an incorrect passphrase was supplied to access the certificate (not all certificates have passphrases) or the certificate lacks a private key (needed to apply a digital signature).

(W39) Signature is invalid.

Someone or something has changed the archive since it was digitally signed. For example, the archive may be corrupt.

(W40) Certificate not trusted.

The certificate is currently not to be trusted.

(W41) Certificate expired.

The certificate has expired. This does not necessarily mean that the certificate or signatures applied with it are not to be trusted. They may simply be old.

(W42) Certificate was revoked.

The issuer has revoked the certificate.

(W43) Certificate not found: XXX.

PKZIP was unable to find a certificate of that name on the system.

(W45) Bad data in compressed stream.

Something was wrong in the stream of compressed data. The ZIP file is corrupt.

(W46) Encryption algorithm is not available. Using: XXX.

PKZIP cannot use the specified algorithm on this system. Use the ListCryptAlgorithms command to view a list of the encryption algorithms that PKZIP can use

(W47) No recipients specified. Recipients will not be used.

You specified the recipient option, but did not include any actual recipients (or specified bogus recipients). When this occurs, SecureZIP will not strongly encrypt files for recipients. If you did not tell it to use passphrases; that is, you did not use the -passphrase option, it will not encrypt files at all. In addition, if you specify passphrase and did not also specify cryptalgorithm, you will not get strong encryption. You will, however, get traditional encryption.

(W48) Invalid item name

The name of an item (file) in the archive is invalid. Possible reasons are: The file has the same name as another file in the same folder; the path name of the archive item contains a file or folder name that exceeds the maximum number of characters allowed (255 for UNIX); the name contains characters that may not be used in file names on your operating system.

(W52) Certificate verification failed!

Something is wrong with the certificate.

(W53) Unknown exception caught: Exception code: XXX

An internal error occurred. Please contact PKWARE Technical Support with the exact command you used and the error code.

(W54) Option 'XXX' is not licensed for use in your copy of PKZIP

Your license key does not allow you to use that option. You must purchase an appropriate license key from PKWARE to use it.

(W55) Command 'XXX' is not licensed for use in your copy of PKZIP

Your license key does not allow you to use that command. You must purchase an appropriate license key from PKWARE to use it

(W56) Recipient not found for file: XXX

The file was encrypted only for recipients, and PKZIP was unable to find a certificate for any of them. Verify that you have access to the private key for one of the recipients.

(W57) Incorrect passphrase or recipient not found for file: XXX

Verify that you entered the correct passphrase for the file. When an archived file is passphrase protected, you can only access the file if you have the correct passphrase. Passphrases are case sensitive.

If the file is encrypted with a certificate, verify that you have access to the private key for one of the recipients.

(W58) Problem reading .ZIP file: <zipfile name>

The .ZIP archive is corrupted. PKZIP can read it, but probably other zipping programs cannot. Use the -fix command to fix the archive so that other programs can read it.

(W59) Multiple certificates found

Multiple digital certificates were found that match the same recipient. These certificates may belong to different people. The archive is encrypted using each of the certificates; the owner of any of them can decrypt.

(W60) Unable to connect to LDAP server: <server name/address>

PKZIP was unable to access certificates on an LDAP server specified using the ldap option: the server address was bad.

(W61) Unable to login to LDAP server: <server name/address>

PKZIP was unable to access certificates on an LDAP server specified using the ldap option: the LDAP login failed.

(W62) Central Directory can only be encrypted with strong encryption. Central Directory will not be encrypted.

The cd option was used, which requires strong encryption, but one or both of the following were neither explicitly specified nor configured for use by default: encryption method (passphrase, recipient options), encryption algorithm (cryptalgorithm option).

(W63) You must specify -passphrase or -recipient to encrypt files!

You specified -cryptalgorithm or -cd=encrypt but did not specify either the recipient or passphrase option. Files are not encrypted unless one of these options is used.

(W68) Must specify MailTo, MailFrom and MailServer to email the archive.

You tried to email an archive without specifying all three options MailTo, MailFrom and MailServer. Values for all three must be specified on the command line or configured for use by default.

(W69) Skipping FTP file transfer because of encryption warning XXX.

PKZIP encountered a problem encrypting an archive that you directed to send by FTP, so PKZIP did not send the archive. This warning occurs if, for example, PKZIP can encrypt for only some but not all recipients, or if no passphrase is supplied to use for passphrase encryption.

(W70) Skipping mail file transfer because of encryption warning XXX.

PKZIP encountered a problem encrypting an archive that you directed to send by email, so PKZIP did not send the archive. This warning occurs if, for example, PKZIP can encrypt for only some but not all recipients, or if no passphrase is supplied to use for passphrase encryption.

(W71) Could not attach unzip instructions to the email message

PKZIP failed to attach instructions on how to unzip, as specified by the MailOptions option

(W72) Could not find the unzip instructions

PKZIP could not find the instructions on how to unzip

(W73) Some of the encryption recipients do not have email addresses

PKZIP was told to encrypt for recipients but could not find email addresses for some of the recipients

(W74) PKZIP is unable to access the default user's private key.

PKZIP is unable to access the private key of the default user. The logon passphrase needed to access the certificate that contains the key may have been reset or changed by an administrator. To fix this warning, the user must change his passphrase from his own computer, rather than let an administrator change it from another system.

(W75) Unable to resolve link: XXXX

While updating an archive, PKZIP could not find the original file or the new file

(W76) <certificate> does not pass the strict certificate checks, and will not be used.

The certificate did not pass the strict checking applied by the strict option, used in a command line that updates an archive. The certificate will not be used for the intended signing or encryption.

(W78) Policy error - nnnnn, contact your system administrator

A noncritical problem has occurred with a policy file or policy certificate. Encryption may be disabled. The number is a policy error code to help your administrator resolve the problem.

(W79) Certificate chain is not time nested

A certificate lists a start date or end date that falls outside the period during which an issuing certificate in its trust chain is nominally valid. This may not be cause for concern, but it might indicate a problem.

(W80) Passphrase encryption not available in SecureZIP Partner

You tried to encrypt using a passphrase. SecureZIP Partner automatically applies certificate-based encryption to every new or updated archive for sponsor recipients but does not do any other encryption.

(W85) Warning! Error shredding file: XXX

You used the shred option, but PKZIP was unable to overwrite the file. For example, PKZIP can delete a file on a network drive but cannot overwrite its data on disk.

(W87) Skipping file that is not encrypted with a FIPS-approved algorithm

The same algorithm that was used to encrypt must be used to decrypt. With the fipsmode option, SecureZIP uses only algorithms that are FIPS-validated for your operating system and skips—does not decrypt—any file that was encrypted using some other algorithm.

(W88) Warning! Signature cannot be verified, because it does not use a FIPS-approved algorithm

The file is signed, but the fipsmode option was used, and the signature hash algorithm is not FIPS-approved. The SHA-1 algorithm is not approved after 2010. On some versions of Windows, the algorithms SHA-256, SHA-384, and SHA-512 are not approved.

(W93) Unable to obtain timestamp: <url>

The URL you specified for your Time Stamping Authority (TSA) is missing, incorrect, unavailable, or you are not connected to the Internet.

(W94) Evidence record verification failed

Timestamp hash does not match.

(W95) Evidence record has expired

Last timestamp certificate is no longer valid.

(W96) Evidence record missing file signature(s)

All timestamped files must be signed with the same hash algorithm as the central directory.

  • No labels