CMS Application - Delivery - Manage Delivery - Fatal Error - Content is not allowed in prolog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page will help you to troubleshoot the fatal error message “Content is not allowed in prolog” you may face when launching the Delivery Manager Tool through AIC Portal/CAST-MS.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Step by Step scenario

When opening DMT from CAST-MS

Open CAST MS
Select the Management database.
Click on the Manage Delivery option

Error is seen as below -

Action Plan

Open the CAST-MS log file
Check for the Error stack as below -

Invalid ////C:/Delivery/data/dfce37aa-b9d2-4c90-aa87-8fd1d0f0b73a.entity.xml
com.castsoftware.java.ExternalException:Invalid ////C:/Delivery /data/dfce37aa-b9d2-4c90-aa87-8fd1d0f0b73a.entity.xml
com.castsoftware.java.IOMonitor.throwExternal(IOMonitor.java:222)
com.castsoftware.java.IOMonitor.throwFileInvalid(IOMonitor.java:93)
com.castsoftware.mda.transfer.DocumentSource.parse(DocumentSource.java:104)
com.castsoftware.mda.transfer.DocumentSourceManager.run(DocumentSourceManager.java:301)
com.castsoftware.mda.transfer.FileLoader.run(FileLoader.java:246)
com.castsoftware.dmt.model.DeliveryMemoryDocument.fillDocumentFromPmxFiles(DeliveryMemoryDocument.java:366)
com.castsoftware.dmt.model.DeliveryMemoryDocument.load(DeliveryMemoryDocument.java:281)
com.castsoftware.deliverytool.DMTConfiguredApplication.onInitialize(DMTConfiguredApplication.java:102)
com.castsoftware.deliverytool.GUI.onInitialize(GUI.java:343)
com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:243)
com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:1)
com.castsoftware.util.logger.Logging.execute(Logging.java:527)
com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
com.castsoftware.mda.run.ConfiguredApplication.run(ConfiguredApplication.java:233)
com.castsoftware.deliverytool.GUI$2.call(GUI.java:93)
com.castsoftware.deliverytool.GUI$2.call(GUI.java:1)
com.castsoftware.util.logger.Logging.execute(Logging.java:527)
com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
com.castsoftware.deliverytool.GUI.main(GUI.java:77)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
com.castsoftware.bootstrap.JarBootstrap.executeMain(JarBootstrap.java:529)
com.castsoftware.bootstrap.JarBootstrap.main(JarBootstrap.java:755)
Content is not allowed in prolog.
org.xml.sax.SAXParseException:Content is not allowed in prolog.
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:999)
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
com.castsoftware.mda.transfer.DocumentSourceManager$Parser.run(DocumentSourceManager.java:602)
com.castsoftware.mda.transfer.DocumentSource.parse(DocumentSource.java:88)
com.castsoftware.mda.transfer.DocumentSourceManager.run(DocumentSourceManager.java:301)
com.castsoftware.mda.transfer.FileLoader.run(FileLoader.java:246)
com.castsoftware.dmt.model.DeliveryMemoryDocument.fillDocumentFromPmxFiles(DeliveryMemoryDocument.java:366)
com.castsoftware.dmt.model.DeliveryMemoryDocument.load(DeliveryMemoryDocument.java:281)
com.castsoftware.deliverytool.DMTConfiguredApplication.onInitialize(DMTConfiguredApplication.java:102)
com.castsoftware.deliverytool.GUI.onInitialize(GUI.java:343)
com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:243)
com.castsoftware.mda.run.ConfiguredApplication$2.call(ConfiguredApplication.java:1)
com.castsoftware.util.logger.Logging.execute(Logging.java:527)
com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
com.castsoftware.mda.run.ConfiguredApplication.run(ConfiguredApplication.java:233)
com.castsoftware.deliverytool.GUI$2.call(GUI.java:93)
com.castsoftware.deliverytool.GUI$2.call(GUI.java:1)
com.castsoftware.util.logger.Logging.execute(Logging.java:527)
com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
com.castsoftware.deliverytool.GUI.main(GUI.java:77)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:606)
com.castsoftware.bootstrap.JarBootstrap.executeMain(JarBootstrap.java:529)
com.castsoftware.bootstrap.JarBootstrap.main(JarBootstrap.java:755)

3. The following error “Content is not allowed in prolog.” appears when you have a malformed entity.xml file.

CMS Application - Delivery - Manage Delivery - Fatal Error - Invalid delivery path entity xml

Mon, 01 Jan 0001 00:00:00 +0000

Document Title

Solution to known problem - CMS Application - Error - Invalid delivery path entity.xml

Purpose (problem description)

Following error is raised while managing DMT in CMS

Invalid ////D:/Sources/XXX/Source_Delivery/7.3.0-DeliveryFolder/data/{f1191e12-785b-49b3-aa4b-6c117aa19698}/4acc97ea-eb7d-49ad-8bce-25d1ce57c15a.entity.xml
com.castsoftware.java.ExternalException:Invalid ////D:/Sources/XXX/Source_Delivery/7.3.0-DeliveryFolder/data/{f1191e12-785b-49b3-aa4b-6c117aa19698}/4acc97ea-eb7d-49ad-8bce-25d1ce57c15a.entity.xml com.castsoftware.java.IOMonitor.throwExternal(IOMonitor.java:222)
com.castsoftware.java.IOMonitor.throwFileInvalid(IOMonitor.java:93)
com.castsoftware.mda.transfer.FileLoader.load(FileLoader.java:366)
com.castsoftware.mda.transfer.FileLoader.run(FileLoader.java:288)
com.castsoftware.dmt.model.DeliveryMemoryDocument.fillDocumentFromPmxFiles(DeliveryMemoryDocument.java:368)
com.castsoftware.dmt.model.DeliveryMemoryDocument.load(DeliveryMemoryDocument.java:283)
com.castsoftware.deliverytool.DMTConfiguredApplication.onInitialize(DMTConfiguredApplication.java:88)
com.castsoftware.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS2	✅

Step by Step scenario

Delivery the package in DMT
In CMS accept the delivery
Click on Mange delivery - Error encountered

Action Plan

CMS Application - Delivery - Manage Delivery - Fatal Error - The packaging in the delivery has not been fully completed

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page discusses a technology independent solution to the problem when the error message ‘The packaging in the delivery has not been fully completed’ is shown when trying to package or remove a package in the Delivery Manager Tool (DMT). There are also additional TKB pages dealing with some technology specific issues for this problem. Here is a screenshot of the problem:

Observed in CAST Version, CAST Extension Version, CAST Component Version

CMS Application - Delivery - Manage Delivery on Documentation - V2

CMS Application - Delivery - Manage Delivery - Fatal Error - Content is not allowed in prolog

CMS Application - Delivery - Manage Delivery - Fatal Error - Invalid delivery path entity xml

CMS Application - Delivery - Manage Delivery - Fatal Error - The packaging in the delivery has not been fully completed