ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » An xml parsing error ''an invalid xml character

Post new topic  Reply to topic
 An xml parsing error ''an invalid xml character « View previous topic :: View next topic » 
Author Message
neWMBGuy
PostPosted: Tue Sep 04, 2012 8:15 am    Post subject: An xml parsing error ''an invalid xml character Reply with quote

Novice

Joined: 01 Aug 2012
Posts: 19

( mb8broker.default ) an xml parsing error ''an invalid xml character (unicode: 0x2229) was found in the prolog of the document.'' occurred on line 1 column 1 when parsing element ''/root/xmlnsc''.
1. A character that is not supported by XML occurs in the instance message data.
XML supports only a subset of control characters; therefore, ensure that no unsupported characters, such as X'00', appear in the document.

2. The Coded Character Set ID that is defined in the message header does not reflect the contents of the instance message.
If the XML document has an XML prologue, the WebSphere MQ CodedCharSetId should be consistent with the XML Encoding field.
3. A reserved XML character appears in the instance message data.
Characters that might be recognized as XML markup - for example, < and & - should be replaced with the corresponding XML entities - &lt; and &amp;.


I imported an XSD thru Message Model Wizard.
the XSD & XML file conforms to each other. not sure why im getting this error.
Same XSD & XML file i've used with success in other non WMB applications

have you guys seen this before?

Message Broker version 8.im Very new to WMB.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Sep 04, 2012 9:10 am    Post subject: Re: An xml parsing error ''an invalid xml character Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

neWMBGuy wrote:
have you guys seen this before?


Yes, the last time a junk character was delivered to the WMB parser. Double check what you're actually getting.

Also check that the CCSID associated with the data is actually the CCSID in which the message is written.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
wbi_telecom
PostPosted: Tue Sep 04, 2012 10:09 am    Post subject: Reply with quote

Disciple

Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA

If the XML has worked with other parsers then check for Byte order mark. Sometimes it appears at the begining of the XML and some parsers have problems with it while others are able to deal with it. i.e. if you open the XML in XML spy or rfhutil, you will not see the Byte order mark unless you view it as HEX.
Cheers,
Back to top
View user's profile Send private message
neWMBGuy
PostPosted: Tue Sep 04, 2012 10:14 am    Post subject: Reply with quote

Novice

Joined: 01 Aug 2012
Posts: 19

Yes after checking with HEX editor i was able to see the beginning chars which were throwing this off.

The same message works with MS Biztalk XML Parser.

Thanks for prompt responses.


This is SOLVED!! i would mark Thanks for both of you (wbi_telecom & Vitor) if there was an Option on the forum.
Back to top
View user's profile Send private message
mgk
PostPosted: Tue Sep 04, 2012 4:57 pm    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
i was able to see the beginning chars which were throwing this off.


What were the characters?

Kind Regards
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Sep 04, 2012 10:16 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

I believe windows issues a byte order information and this does change the actual CCSID.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Tue Sep 04, 2012 10:29 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

neWMBGuy wrote:
MS Biztalk XML Parser.



That explains quite a lot. I've seen Biztalk emit XML that can't be parsed by anything apart from Biztalk itself. This was several years ago so maybe they have made it a bit more standards conformant but somehow I doubt it.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » An xml parsing error ''an invalid xml character
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.