| There is no policy called {name} in the DMS {name}
|
You have chosen a Documentum business policy to attach published documents to, but the policy does not exist.
|
| Failed to create the checksum file {name} for backbone file {name}
|
You may not have access to the file or folder. Save the log file information and see your system administrator.
|
| Native file leaf {name} contains multiple documents that cannot be concatenated. Excluding the documents from the publication.
|
You chose Yes for the Use Native File attribute but the parent leaf contains more than one source document. Change Use Native File to No or remove the necessary documents from the leaf.
|
| No Documents detected in Assembly, Executing ECTD XML Backbone only publish.
|
The assembly contains no documents to publish. Only the XML backbone will be published.
|
| Cannot find the file system extension of document {name}: {error description}.
|
Ennov InSight Publisher failed to find the file extension of a document in a DMS repository. The extension is required to save the results in the DMS repository.
|
| Cannot find attribute {name} on element {name} when importing into DMS
|
You have specified attributes that should be copied from leafs to published results, but an attribute of this name cannot be found.
|
| There is no policy called {name}" in the DMS {name}
|
You have specified a Documentum business policy to attach published documents to, but the policy does not exist.
|
| An exception has been detected in resolving attribute {name}, Exception: {description}
|
Internal error; contact Technical Support.
|
| {validation rule class}: {target Xpath}: missing leaf content file {file name}
|
The specified leaf document does not exist or cannot be read. The document may not exist (for example, because of an incremental publish).
|
| There is no attribute named {name} defined on an element of type {name}
|
The attribute may be incorrectly named. Check attribute mappings and see if the attribute exists.
|
| Failed to read content file {PDF file name} : {error description}
|
The PDF document has not been published or does not exist. Please verify the PDF document exists.
|
| Input error: missing or invalid input file {file name}"
|
The document specified does not exist or cannot be accessed. Please verify that the document exists and is readable.
|
| Input error: unable to parse XML file {file name}": {error type}: {error description}
|
The file specified cannot be accessed or its content is invalid. Please verify that the file specified is readable and that its content is valid.
|
| Assembly document {name} does not have an attached DMS document
|
Warning to users that they have forgotten to attach a repository document to an IMA document.
|
| Failed to read content file {name}": {error description}
|
The PDF document has not been published or does not exist.
|
| Input error: missing or invalid input file {name}"
|
This is an installation fault.
|
| No output channel has been specified
|
This element does not have an output channel associated with it. Therefore, it will not be published.
|
| Missing Rendition/Rendition does not exist
|
A rendition does not exist and must be created to successfully publish the assembly as you expect. Documents that are missing renditions will not publish.
|
| This is a placeholder and it is not going to be published.
|
The element is a placeholder. Placeholders cannot be published, and will therefore not be included in the published output.
|
| Unable to set properties for documents in folder {file path}: Unable to find document
|
The distribute sub-job on the
Ennov InSight Rendering server attempts to set properties on placeholders. When there is no document to accept the properties, the sub-job reports an error. This error can safely be ignored for placeholders.
|
| Document are not assigned and a DMS synch is required
|
The document is not assigned. A DMS Sync is required for these documents to publish successfully.
|
| ERROR: ESPSLoadContainer
|
This message is informational and may be safely ignored. This is noted in the Publishing Log.
|
| ERROR: Odd Page Overlay
|
This message is informational and may be safely ignored. This is noted in the Publishing Log.
|
| Excluded from Volume Range
|
You have volumes defined, but this element is not included in a volume. Therefore, it will not be published.
|