Troubleshoot archive libraries
- Last Updated: February 11, 2026
- 3 minute read
- OpenEdge
- Version 13.0
- Documentation
Cases that raise a STOP condition
The AVM always validates the integrity of signed archive files when it loads them by
verifying the signature information, which guarantees that the manifest and
signature related information have not been tampered with. The AVM raises a STOP
condition with a specific error message (that is, a
Progress.Lang.StopError) if the validation fails, as the
contents of the signed archive file cannot be trusted. Some cases which raise
Progress.Lang.StopError include:- If the signed archive fails validation
- If the signed archive contains more than one signature file
- If the signature file contains an entry for a file that does not exist in the archive file
- If a file has been added or removed from the archive after it has been signed
- If the archive file is compressed and you try to execute an r-code file or load an image file from it
Enable logging
For diagnostic purposes, you can turn on logging to see various log messages related to archive libraries. These logs can be helpful when troubleshooting problems. Log messages are provided related to the validation of signed archive files and the file entries in them.
To enable logging you set the logging level, log entry type
(
Sec.Rcode), and log file name. The Sec.Rcode
log entry type provides information at the following logging levels:- Level 2 (Basic) — Logs messages about values that are missing or incorrect
in the manifest file during archive file validation. Attributes validated at
this level include:
Implementation-Title,Implementation-Vendor,Signature-Policy,Validation-Policy,Package-Type, andBuild-Date. - Level 3 (Verbose) — Logs messages about values that are missing or invalid
from attributes in the manifest file during archive file validation.
Attributes validated at this level include:
Component-Name,Implementation-Version,OpenEdge-version, andBuild-OS. - Level 4 (Extended) — Logs messages for a successful file entry validation.
To enable logging, specify these startup parameters:
-logginglevel n(where n is the desired logging level (for example, 2, 3, or 4))
-logentrytypes Sec.Rcode-clientlog logfilename
Examples of
Sec.Rcode log messages (with headers suppressed) are
shown:
|