Created by Thaza Karath, last modified by John McMahon on Aug 21, 2023


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(tick)
Step by Step scenario

When opening DMT from CAST-MS

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

Error is seen as below - 

Action Plan
  1. Open the CAST-MS log file
  2. Check for the Error stack as below -  
Error stack
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.

              a. To identify the same, open the entity.xml in the error using Internet Explorer - "Invalid ////C:/Delivery/data/dfce37aa-b9d2-4c90-aa87-8fd1d0f0b73a.entity.xml"

                           

             b. If the entity.xml file is corrupt you will see the below screen in Internet Explorer 

                         

           c. Open the entity.xml file using Notepad++ and check for any formatting errors like extra characters, spaces etc. and remove them. Open the edited entity.xml file using Internet Explorer again and see that the xml file opens as expected. 

                         

      4. Launch DMT again and see that it opens as expected. 

      5. If you do not find the information you are looking for or solution for your problem, in this page, contact CAST Technical Support and provide below relevant input.  

 

Relevant Input

  1. Provide screenshots describing the error. 
  2. CAST-MS log file
  3. Entity.xml file that has thrown the error. 
Notes/comments