Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Publishing to Adobe Experience Manager at localhost has encountered a problem

Codelime
Level 4
Level 4

I'm getting the following "Problem Occurred" modal:

 

Publishing failed
Could not publish to the server.
unknown type: 0,date,dd.MM.yyyy\ HH:mm:ss.SSS
Failed updating F/business.ui.content/src/main/content/jcr_root/conf/business/settings/wcm/policies
org.xml.sax.SAXParseException; lineNumber: 633; columnNumber: 14; The markup in the document following the root element must be well-formed.

 

Any ideas where to start to get it fixed? 

AEM 6.5 Error
1 Accepted Solution
diksha_mishra
Correct answer by
Community Advisor
Community Advisor

This error indicates that your XML has markup following the root element. In order to be well-formed , XML must have exactly one root element , and there can be no further markup following the single root element.

One root element example (GOOD)

<r>
  <a/>
  <b/>
  <c/>
</r>

The most common sources for this error are:

  1. Including stray or extra close tags (BAD):

    <r>
      <a/>
      <b/>
      <c/>
    </r>
    </r>  <!-- shouldn't be here -->
    
  2. Intentionally having multiple root elements (BAD):

    <a/>
    <b/>  <!-- second root element shouldn't be here -->
    <c/>  <!-- third root element shouldn't be here -->
    
  3. Unintentionally having multiple root elements (BAD):

    <r/>  <!-- shouldn't be self-closing -->
      <a/>
      <b/>
      <c/>
    </r>
    
  4. Parsing different XML than you think (BAD):

    Log the XML immediately before providing to the parse that's failing in order to make sure that the XML that the parser is seeing is the same as the XML you think it's seeing. Common errors here include:

    • The filename of the XML document being passed to the parser differs from what you believe it is.
    • The buffer of the XML being dirty. Make sure it's been cleared prior to adding your XML.
    • An earlier program from a prior stage in your pipeline changing the XML prior to the parsing that's yielding this error message.

View solution in original post

4 Replies
diksha_mishra
Correct answer by
Community Advisor
Community Advisor

This error indicates that your XML has markup following the root element. In order to be well-formed , XML must have exactly one root element , and there can be no further markup following the single root element.

One root element example (GOOD)

<r>
  <a/>
  <b/>
  <c/>
</r>

The most common sources for this error are:

  1. Including stray or extra close tags (BAD):

    <r>
      <a/>
      <b/>
      <c/>
    </r>
    </r>  <!-- shouldn't be here -->
    
  2. Intentionally having multiple root elements (BAD):

    <a/>
    <b/>  <!-- second root element shouldn't be here -->
    <c/>  <!-- third root element shouldn't be here -->
    
  3. Unintentionally having multiple root elements (BAD):

    <r/>  <!-- shouldn't be self-closing -->
      <a/>
      <b/>
      <c/>
    </r>
    
  4. Parsing different XML than you think (BAD):

    Log the XML immediately before providing to the parse that's failing in order to make sure that the XML that the parser is seeing is the same as the XML you think it's seeing. Common errors here include:

    • The filename of the XML document being passed to the parser differs from what you believe it is.
    • The buffer of the XML being dirty. Make sure it's been cleared prior to adding your XML.
    • An earlier program from a prior stage in your pipeline changing the XML prior to the parsing that's yielding this error message.

View solution in original post

Arun_Patidar
Community Advisor
Community Advisor

Hi,

How did you updated F/business.ui.content/src/main/content/jcr_root/conf/business/settings/wcm/policies/.content.xml

Codelime
Level 4
Level 4
I opened the file and realized that there was an extra </jcr:root> at the end of the file, so I deleted it. I don't know how that could have happened.