Leaf Messages

You can view leaf error messages in either the publishing log or the Publishing Readiness query.

Message Description

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.

Folder Messages

Message Description
Cannot find attribute '{name}' on element '(name)' when importing into DMS You have specified attributes that should be copied from leaf elements to published results, but the attributes specified in this message cannot be found.
Could not find an ICH definition. No DTD/schema has been specified; one is required to publish an eCTD.
Leafs {name 1} and {name 2} produce documents at the same location {location}. Change one of the leaf output paths to resolve this issue.
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 attribute {name} on element {name} when importing into DMS You have specified attributes that should be copied from leaf elements to published results, but an attribute of this name cannot be found.
Invalid input error: {error description} The specified XML file or one of its dependencies (for example, a DTD or stylesheet) does not exist or cannot be read.
Cannot find the Insight configuration file {name} An installation fault has occurred.

The leaf with assembly path

{name} has no output file defined.

 You did not enter a path for the leaf. Each leaf requires a resulting file name. A temporary name is generated and publishing continues.
You have not defined any agency definitions for your assembly. You have not chosen the XML definition files in the publishing options.
ERROR: Error with Component 4 Occurs when Ennov InSight is unable to put multiple files together, often because one is encrypted or contains invalid data. This is noted in the publishing log.

Leaf Messages

Message Description
ERROR: XML structure error: line 155, column 25: The content of element type m1-5specific"" must match ((m1-5-1bibliographic|m1-5-2abridged)?,(leaf|nodeextension)*)" Elements m1-5-1-bibliographic and m1-5-2-abridged are both present in your assembly structure. Remove one to create a valid xml. This is noted in the publishing log.
ERROR: NVPair has no attribute name NONE is not a valid selection for country. Please assign all related sequences to a specific country. This is noted in the publishing log.
WARNING: Page number is missing Indicates that a native file leaf is included in publishing and will not be counted in page numbering. This is noted in the publishing log.

WARNING: FileNameRule: leaf output path ../../../../JCS 24-17 AppC1/0000/m1/eu/16environrisk/162-gmo/1-6-2nodeext-01.pdf contains invalid characters: `J', `C', `S', ` `,

`A'. [XPath: /eu:eubackbone/m1-eu/m1-9-clinicaltrials/leaf/@xlink:href]

 Indicates that an output folder, output file name, or eCTD metadata used for XML paths contains illegal characters. Most illegal characters are normalized for valid output, but these must be confirmed in the output. This is noted in the publishing log.
Missing Content, no children. The leaf has no content documents assigned to it. This warning is only valid on standard leaf elements, and not applicable to reference leaf elements.
The extended attributes, output folder, or leaf output file name contain non-substitutable characters that contribute to the eCTD output path. Override manually by changing the output folder or leaf output file name to use only valid eCTD characters.
File name is blank A file name is not specified. At publishing time, if this is not corrected, the publishing engine will use the leaf name as the file name.
File extension on the leaf file name doesn't match the type of document. The leaf output file name extension does not agree with the file type for the first document under the leaf. This should be corrected prior to performing an eCTD publish.
Only one document will be published This warning appears when a native file leaf has more than one child beneath it. In this instance, only the first child document will be included.

Leaf Messages