For the complete documentation index, see llms.txt. This page is also available as Markdown.

PDF/A Manager exit codes, formats & reporting

Apryse's PDF/A Manager is a command-line application designed to validate and convert generic PDF documents to PDF/A (ISO 19005-1) compliant format. This section covers basic usage and the command string syntax, used both in the PDF/A Manager Command-Line Application as well as in PDF/A Manager SDK.

Basic Syntax

The basic command-line syntax is:

pdfa [options] file1 file2 folder1 file3 ...

See more options in Command-Line Summary for PDF/A Manager

Exit Codes

To provide additional feedback, PDF/A Manager returns exit codes after completing processing. The exit codes can be used to provide user feedback for logging, etc. This is particularly important for applications running in an unattended environment.

The following table lists possible exit codes and their description:

Exit Code       Description
--------------- ------------------------------------------------------------------
0               All files converted successfully.
1               Document is secured. Need a valid password to open the document.
2               Error opening the input file(s).
3               An unknown exception encountered.

All codes other then '0' indicate that there was an error during the conversion process.

The following illustrates a sample Windows batch script that processes exit codes:

PDF/A Manager Reporting

This section covers PDF/A Manager report formats and all the possible error conversion and validation options.

PDF/A Manager XML Report Format

By default PDF/A Manager stores details of validation and conversion processing in an XML file. The report is saved as 'report.xml' in the output directory. Similarly, the style sheet for the report is saved as 'report.xsl' in the output directory. Double clicking on 'report.xml' will launch a web browser display HTML report as shown in the following figure:

The report includes the following information:

  • The date and time when the report was generated

  • A listing of files that fail validation prior to conversion. The information in this table includes the input PDF filename, error code, error message, and a list of relevant PDF object numbers.

  • A listing of files that pass validation and for which no conversion is necessary.

  • A listing of files that fail validation after to conversion. Usually this list includes files that can't be fully converted to PDF/A without significant information loss.

  • A final list of files that pass validation after conversion.

The general structure of XML report is as follows:

To disable report generation, simply include '--noxml' in the command-line string. Disabling XML report generation will direct processing results to the console window.

PDF/A Manager Validation and Conversion Error Codes

PDF/A Manager analyzes the content of existing PDF files and performs a sequence of modifications in order to produce a PDF/A compliant document. Features that are not suitable for long-term archiving (such as encryption, obsolete compression schemes, missing fonts, or device-dependent color) are replaced with their PDF/A compliant equivalents.

PDF/A Level B Validation Errors

The following table is a non-exhaustive list of checks and conversions performed by PDF/A Manager for Level B Validation:

4.2.2 PDF/A Level A Validation Errors

The following table is a non-exhaustive list of checks and conversions performed by PDF/A Manager for Level A Validation:

Last updated

Was this helpful?