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

Publishing to Adobe Experience Manager at localhost has encountered a problem

Avatar

Avatar
Ignite 3
Level 4
Codelime
Level 4

Likes

45 likes

Total Posts

65 posts

Correct Reply

0 solutions
Top badges earned
Ignite 3
Boost 25
Applaud 5
Give Back 25
Validate 1
View profile

Avatar
Ignite 3
Level 4
Codelime
Level 4

Likes

45 likes

Total Posts

65 posts

Correct Reply

0 solutions
Top badges earned
Ignite 3
Boost 25
Applaud 5
Give Back 25
Validate 1
View profile
Codelime
Level 4

04-06-2021

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Applaud 25
Level 4
diksha_mishra
Level 4

Likes

58 likes

Total Posts

69 posts

Correct Reply

29 solutions
Top badges earned
Applaud 25
Give Back 5
Boost 50
Affirm 25
Give Back 3
View profile

Avatar
Applaud 25
Level 4
diksha_mishra
Level 4

Likes

58 likes

Total Posts

69 posts

Correct Reply

29 solutions
Top badges earned
Applaud 25
Give Back 5
Boost 50
Affirm 25
Give Back 3
View profile
diksha_mishra
Level 4

05-06-2021

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.

Answers (1)

Answers (1)

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,348 likes

Total Posts

3,226 posts

Correct Reply

916 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,348 likes

Total Posts

3,226 posts

Correct Reply

916 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

05-06-2021

Hi,

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