Announcement

Collapse

Mirth Connect 4.1.1 Released!

Mirth Connect 4.1.1 is now available as an appliance update and on our GitHub page. This release contains modifications to the Welcome to Mirth Connect screen and two fixed defects. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Deployment Error: Content is not allowed in prolog

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Deployment Error: Content is not allowed in prolog

    We are getting the following error on deployment. There were several channels enabled, so we disabled them one by one to see which was the problem. At this point there are no channels enabled, but we still get the same message. Note, we've not upgraded to 1.6.1 yet. We are still using 1.5.0.

    Here's the text of the error message.

    com.webreach.mirth.client.core.ClientException: method failed: HTTP/1.1 500 com.webreach.mirth.server.builders.BuilderExceptio n: org.xml.sax.SAXParseException: Content is not allowed in prolog.
    com.webreach.mirth.client.core.ServerConnection.ex ecutePostMethod(ServerConnection.java:93)
    com.webreach.mirth.client.core.Client.deployChanne ls(Client.java:372)
    com.webreach.mirth.client.ui.Frame$70.doInBackgrou nd(Frame.java:2489)
    com.webreach.mirth.client.ui.Frame$70.doInBackgrou nd(Frame.java:2498)
    org.jdesktop.swingworker.SwingWorker$1.call(Unknow n Source)
    java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:269)
    java.util.concurrent.FutureTask.run(FutureTask.jav a:123)
    org.jdesktop.swingworker.SwingWorker.run(Unknown Source)
    java.util.concurrent.ThreadPoolExecutor$Worker.run Task(ThreadPoolExecutor.java:650)
    java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:675)
    java.lang.Thread.run(Thread.java:613)

  • #2
    Reeployment Error: Content is not allowed in pro

    OK, we finally managed to upgrade successfully, and this issue has now vanished. I'm not sure how I managed to post this message twice, but I apologize for spamming the forum.

    Comment

    Working...
    X