An information message displaying the Assembler version number.

An information message displayed during bootstrapping.

The DDX object passed to the invoke() method was null. It is required.

DDX Execution error. The error message is provided along with a stack trace if available. Corrective action should be based on any messages or warnings present.

An error occurred while attempting to convert the job log to a com.adobe.idp.Document to return to the client. The exception includes an error message that may indicate the root cause. This error may also occur if the document storage partition is full.

The FontManager could not be contacted. Verify that the FontManager is properly installed. Use the JMX console to verify that it is currently running.

An error occurred while trying to read the content for a result. The content was created, but could not be read from the disk file or input stream. The cause will be provided. This may occur during low disk space or low memory conditions.

An error occurred while trying to passivate the content for a result. The cause will be provided. This can occur if the global temporary storage directory is full or unavailable.

There was no result document for a result node in the DDX or its type is unknown. This is an internal logic error and should be reported to Customer Support.

The document provided as a PDF source was invalid. The document may either be corrupted or the content is not PDF content.

The document provided as an XDP source was invalid. The document may either be corrupted or the content is not XDP containing a PDF document.

The document could not be opened. A chained exception will provide the cause. The most common causes are a corrupt document, an I/O error, or a security-related error.

The shared DOM could not be cloned. A chained exception will provide the cause.

An error occured while saving the specified document. Corrective action will depend on the provided cause. The most common causes are a corrupt document, a security error, or an I/O error. Processing will continue, but the exception may result in excess memory consumption or excess file handle consumption.

An invalid or unknown log level was specified. A default was used instead.

The logging subsystem will generate low-level debugging messages for this job, which will affect performance.

The input map is null. No inputs are available for processing. This is not a problem for a validate-only job, or a DDX document that contains a single <About/> block. However, any other operations will fail due to the missing inputs. Verify that the Map of input documents is not null and contains one or more documents.

The input map is empty. No inputs are available for processing. This is not a problem for a validate-only job, or a DDX that contains a single <About/> block. However, any other operations will fail due to the missing inputs. Verify that the Map of input documents actually contains one or more documents.

The indicated XPath expression could not be found or evaluated within the process context. The corresponding entry will not be included in the input map. This may be a fatal error if the input was required for DDX execution. If the omission was intentional, this warning may be ignored.

The indicated input map object was an unknown class and could not be converted to a com.adobe.idp.Document. The object will not be included in the input map during processing. Verify that the contents of the input map conform to the required inputs.

The specified document failed to close properly. A cause should have been provided, and should be investigated and corrected. Processing will continue but future attempts to use the same document may fail.

A prefix used for all messages.