Adobe Experience Manager Sites & More

Codelime · 4:17:48 PM

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?

diksha_mishra · 12:48:40 AM

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:

Including stray or extra close tags (BAD):

<r>
  <a/>
  <b/>
  <c/>
</r>
</r>  <!-- shouldn't be here -->

Intentionally having multiple root elements (BAD):

<a/>
<b/>  <!-- second root element shouldn't be here -->
<c/>  <!-- third root element shouldn't be here -->

Unintentionally having multiple root elements (BAD):

<r/>  <!-- shouldn't be self-closing -->
  <a/>
  <b/>
  <c/>
</r>

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.

元の投稿で解決策を見る

diksha_mishra · 12:48:40 AM

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:

Including stray or extra close tags (BAD):

<r>
  <a/>
  <b/>
  <c/>
</r>
</r>  <!-- shouldn't be here -->

Intentionally having multiple root elements (BAD):

<a/>
<b/>  <!-- second root element shouldn't be here -->
<c/>  <!-- third root element shouldn't be here -->

Unintentionally having multiple root elements (BAD):

<r/>  <!-- shouldn't be self-closing -->
  <a/>
  <b/>
  <c/>
</r>

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.

arunpatidar · 6:04:13 AM

Hi,

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

Arun Patidar

Codelime · 6:23:39 AM

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.