Character conversion error: Unconvertible UTF-8 character beginning..

Hello,
I'm using TrAX for XSLT transformations, and having a following
problem
Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
        at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
        at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
        at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
        at org.apache.crimson.parser.Parser2.maybeTextDecl(Parser2.java:2795)
        at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.java:2880)
        at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1167)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
        at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
        at mlts.converter.XMLImport.outputESGML(XMLImport.java:311)
        at mlts.converter.Converter.processFile(Converter.java:312)
        at mlts.converter.Converter.Convert(Converter.java:229)
        at test.main(test.java:7)Following the source code, I've found that the exception is thrown
when it reads DTD. I tried to read DTD using InputSource
in ascii, in latin-1 and my program reads it without any problem.
I really appreciate any help,
Thanks

http://forum.java.sun.com/thread.jsp?forum=34&thread=254927

Similar Messages

  • Character conversion error: "Unconvertible UTF-8 character beginning with 0

    Hi All,
    I developed an Adapter Module and added to Adapter Framework.
    package sample;
    import java.io.InputStream;
    import java.text.SimpleDateFormat;
    import java.util.Date;
    import javax.ejb.CreateException;
    import javax.ejb.SessionBean;
    import javax.ejb.SessionContext;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.NodeList;
    import com.sap.aii.af.mp.module.Module;
    import com.sap.aii.af.mp.module.ModuleContext;
    import com.sap.aii.af.mp.module.ModuleData;
    import com.sap.aii.af.mp.module.ModuleException;
    import com.sap.aii.af.ra.ms.api.Message;
    import com.sap.aii.af.ra.ms.api.XMLPayload;
    @ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
    @ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
    @ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
    @ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
    @stateless
    public class SetAttachmentName implements SessionBean, Module {
         private SessionContext myContext;
         private String mailFileName = "UStN";
         public void ejbRemove() {
         public void ejbActivate() {
         public void ejbPassivate() {
         public void setSessionContext(SessionContext context) {
              myContext = context;
         public void ejbCreate() throws CreateException {
         public ModuleData process(
              ModuleContext moduleContext,
              ModuleData inputModuleData)
              throws ModuleException {
              // create a second attachment for the receiver mail adapter
              try {
                   //                  get the XI message from the environment
                   Message msg = (Message) inputModuleData.getPrincipalData();
                   //               creating parsable XML document
                   InputStream XIStreamData = null;
                   XMLPayload xmlpayload = msg.getDocument();
                   XIStreamData = xmlpayload.getInputStream();
                   DocumentBuilderFactory docBuilderFactory =
                        DocumentBuilderFactory.newInstance();
                   DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
                   Document doc = docBuilder.parse(XIStreamData);
                   //            finding the tag's name from the Modules tab in the Directory that will hold the attachment's name
                   String absenderIDTag = null;
                   absenderIDTag = moduleContext.getContextData("<RCVPRN>");
                   //            finding the content of the tag that will be used as the attachment's name (assuming it's the only tag with this name)
                   Element element = doc.getDocumentElement();
                   NodeList list = doc.getElementsByTagName(absenderIDTag);
                   mailFileName += "_" + list.item(0).getFirstChild().toString();
                   String anIDTag = null;
                   anIDTag = moduleContext.getContextData("<CREDAT>");
                   element = doc.getDocumentElement();
                   list = doc.getElementsByTagName(anIDTag);
                   mailFileName += "_" + list.item(0).getFirstChild().toString();
                   Date date = new Date(System.currentTimeMillis());
                   //            Add date to the Message
                   SimpleDateFormat dateFormat = new SimpleDateFormat("yyyyMMdd");
                   mailFileName += "_" + dateFormat.format(date);
                   String belegNummerTag = null;
                   belegNummerTag = moduleContext.getContextData("<BULK_REF>");
                   element = doc.getDocumentElement();
                   list = doc.getElementsByTagName(belegNummerTag);
                   mailFileName += "_" + list.item(0).getFirstChild().toString();
                   //               creating the attachment
                   byte by[] = xmlpayload.getText().getBytes();
                   XMLPayload attachmentPDF = msg.createXMLPayload();
                   attachmentPDF.setName(mailFileName);
                   attachmentPDF.setContentType("application/pdf");
                   attachmentPDF.setContent(by);
                   //adding the message to the attachment
                   msg.addAttachment(attachmentPDF);
                   //                  provide the XI message for returning
                   inputModuleData.setPrincipalData(msg);
              } catch (Exception e) {
                   //                  raise exception, when an error occurred
                   ModuleException me = new ModuleException(e);
                   throw me;
              //                  return XI message
              return inputModuleData;
    I get the following error
    Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
    Any tips, pointers ?
    Thanks in Advance
    Mukhtar

    Hi Henrique,
    I am using .getNodeValue()
    import java.io.InputStream;
    import java.text.SimpleDateFormat;
    import java.util.Date;
    import javax.ejb.CreateException;
    import javax.ejb.SessionBean;
    import javax.ejb.SessionContext;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.NodeList;
    import com.sap.aii.af.mp.module.*;
    import com.sap.aii.af.ra.ms.api.*;
    @ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
    @ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
    @ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
    @ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
    @stateless
    public class UStNAttachmentName3 implements SessionBean, Module {
         private SessionContext myContext;
         private String mailFileName = "UStN";
         public void ejbRemove() {
         public void ejbActivate() {
         public void ejbPassivate() {
         public void setSessionContext(SessionContext context) {
              myContext = context;
         public void ejbCreate() throws CreateException {
         public ModuleData process(
              ModuleContext moduleContext,
              ModuleData inputModuleData)
              throws ModuleException {
              // create a second attachment for the receiver mail adapter
              try {
                   // get the XI message from the environment
                   Message msg = (Message) inputModuleData.getPrincipalData();
                   // creating parsable XML document
                   InputStream XIStreamData = null;
                   XMLPayload xmlpayload = msg.getDocument();
                   XIStreamData = xmlpayload.getInputStream();
                   DocumentBuilderFactory docBuilderFactory =
                        DocumentBuilderFactory.newInstance();
                   DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
                   Document doc = docBuilder.parse(XIStreamData);
                   // finding the tag's name from the Modules tab in the Directory that will hold the attachment's name
                   String absenderIDTag = null;
                   absenderIDTag = moduleContext.getContextData("<RCVPRN>");
                   // finding the content of the tag that will be used as the attachment's name (assuming it's the only tag with this name)
                   Element element = doc.getDocumentElement();
                   NodeList list = doc.getElementsByTagName(absenderIDTag);
                   mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
                   String anIDTag = null;
                   anIDTag = moduleContext.getContextData("<CREDAT>");
                   element = doc.getDocumentElement();
                   list = doc.getElementsByTagName(anIDTag);
                   mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
                   Date date = new Date(System.currentTimeMillis());
                   // Add date to the Message
                   SimpleDateFormat dateFormat = new SimpleDateFormat("yyyyMMdd");
                   mailFileName += "_" + dateFormat.format(date);
                   String belegNummerTag = null;
                   belegNummerTag = moduleContext.getContextData("<BULK_REF>");
                   element = doc.getDocumentElement();
                   list = doc.getElementsByTagName(belegNummerTag);
                   mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
                   // creating the attachment
                   byte by[] = xmlpayload.getText().getBytes();
                   XMLPayload attachmentPDF = msg.createXMLPayload();
                   attachmentPDF.setName(mailFileName);
                   attachmentPDF.setContentType("application/pdf");
                   attachmentPDF.setContent(by);
                   //adding the message to the attachment
                   msg.addAttachment(attachmentPDF);
                   // provide the XI message for returning
                   inputModuleData.setPrincipalData(msg);
              } catch (Exception e) {
                   // raise exception, when an error occurred
                   ModuleException me = new ModuleException(e);
                   throw me;
              // return XI message
              return inputModuleData;
    Still I get the same error.
    org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
    Adapter-Framework: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
    Regards,
    Mukhtar

  • HTTP-Receiver: Code page conversion error from UTF-8 to ISO-8859-1

    Hello experts,
    In one of our interfaces we are using the payload manipulation of the HTTP receiver channel to change the payload code page from UTF-8 to ISO-8859-1. And from time to time we are facing the following error:
    u201CCode page conversion error UTF-8 from system code page to code page ISO-8859-1u201D
    Iu2019m quite sure that this error occurs because of non-ISO-8859-1 characters in the processed message. And here comes my question:
    Is it possible to change the error behaviour of the code page converter, so that the error will be ignored?
    Perhaps the converter could replace the disruptive character with e.g. u201C#u201D?
    Thank you in advance.
    Best regards,
    Thomas

    Hello.
    I'm not 100% sure if this will help, but it's a good Reading material on the subject (:
    [How to Work with Character Encodings in Process Integration (NW7.0)|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]
    The part of the XSLT / Java mapping might come in handy in your situation.
    you can check for problematic chars in the code.
    Good luck,
    Imanuel Rahamim.

  • Unconvertible UTF-8 Character error

    Hi All ,
    I have a problem while parsing a XML which has some Special characters
    like, '�', '�', '�' etc.
    The error is as follows :
    org.xml.sax.SAXParseException : Character conversion error : "Unconvertible
    UTF-* character begining with 0x96" (line number may be too low)
    Could you please help me out here ....
    thanx
    Bibhu

    This problem is related to the xml encoding. When using non-ascii characters you should specify which encoding is used in the document.
    For instance,
    <?xml version="1.0" encoding="ISO-8859-9"?>
    The encoding code depends on the locale of your text editor or operating system. You can check it by the system property file.encoding.
    From the following page you can obtain more information about xml encoding: http://www.w3schools.com/xml/xml_encoding.asp
    Best regards...
    Mert Nuhoglu

  • Character conversion error when installing Java Portlet Container Preview

    I'm trying to tets out JSR 168 portlets on our Oracle 10g server. I'm following the instructions at http://portalstandards.oracle.com/
    I download and try to install the "Java Portlet Container Preview Release 2", and I get the following error:
    [oracle@jupiter home]$ java -jar ~/wsrp-install.jar ~/jwsdp-1.3
    File "/home/oracle/jupiter_mid/j2ee/home/config/global-web-application.xml" modified successfully
    oracle.webdb.utils.PortalExceptionImpl: Error transforming file "config/server.xml"
    at oracle.portal.PortalException.<init>(PortalException.java:66)
    at oracle.webdb.wsrp.server.install.InstallException.<init>(InstallException.java:31)
    at oracle.webdb.wsrp.server.install.Main.applyTransformation(Main.java:387)
    at oracle.webdb.wsrp.server.install.Main.install(Main.java:122)
    at oracle.webdb.wsrp.server.install.Main.main(Main.java:98)
    Caused by: javax.xml.transform.TransformerException: Character conversion error: "Unconvertible UTF-8 character beginning with 0x92" (line number may be too low).
    at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:739)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:715)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1129)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1107)
    at oracle.webdb.wsrp.server.install.Main.applyTransformation(Main.java:371)
    ... 2 more
    caused by: ; SystemID: http://xmlns.oracle.com/ias/dtds/application-server-9_04.dtd; Line#: 1; Column#: -1
    javax.xml.transform.TransformerException: Character conversion error: "Unconvertible UTF-8 character beginning with 0x92" (line number may be too low).
    at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:739)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:715)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1129)
    at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1107)
    at oracle.webdb.wsrp.server.install.Main.applyTransformation(Main.java:371)
    at oracle.webdb.wsrp.server.install.Main.install(Main.java:122)
    at oracle.webdb.wsrp.server.install.Main.main(Main.java:98)
    [oracle@jupiter home]$
    This is what the server.xml looks like:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <!DOCTYPE application-server PUBLIC "-//Oracle//DTD OC4J Application-server 9.04//EN" "http://xmlns.oracle.com/ias/dtds/application-server-9_04.dtd">
    <application-server localhostIsAdmin="true"
    application-directory="../applications"
    deployment-directory="../application-deployments"
    connector-directory="../connectors">
    <rmi-config path="./rmi.xml" />
    <sep-config path="./internal-settings.xml" />
    <jms-config path="./jms.xml" />
    <javacache-config path="../../../javacache/admin/javacache.xml" />
    <log>
    <file path="../log/server.log" />
    </log>
    <transaction-config timeout="30000" />
    <java-compiler name="javac" in-process="false" extdirs="/home/oracle/jupiter_mid/jdk/jre/lib/ext" />
    <global-application name="default" path="application.xml" />
    <application name="BC4J" path="../applications/BC4J.ear" auto-start="true" />
    <application name="BC4JManager" path="../applications/BC4JManager.ear" auto-start="true" />
    <application name="IsWebCacheWorking" path="../applications/IsWebCacheWorking.ear" auto-start="true" />
    <application name="jdev_test2" path="../applications/jdev_test2.ear" auto-start="true" />
    <global-web-app-config path="global-web-application.xml" />
    <web-site default="true" path="./default-web-site.xml" />
    <cluster id="1214162165" />
    </application-server>
    server.xml looks ok, and I've tried tweaking it to no avail. Anyone know what could cause this?

    Could you make sure you don't have any extra Apache libraries hanging around in your global classpath, i.e. ensure there is nothing extra in <J2SE Home>/jre/lib/extThere's a xercesImp.jar under mid/j2ee/OC4J_Portal/applications/jpdk/jpdk/WEB-INF/lib/xercesImpl.jar, but there's also one under jwsdp-1.2/jaxp/lib/endorsed/xercesImpl.jar. Is that supposed to be in there?
    Neither of these are getting loaded, though; running java -verbose shows that all of org.apache.xalan.* is being loaded from mid/jdk/jre/lib/rt.jar
    FWIW, ../../lib/xmlparserv2.jar does exist, but doesn't look like it's being loaded. :-\

  • SAX  FATAL:Unconvertible UTF-8 character

    Is there someone that knows how to eliminate this annoying error, that randomly
    appears(it seems to appear every time I reboot the system...)?
    Whe have seen this problem running wlps 3.2 on several machines, linux, solaris
    and winnt, all pointing to some oracle database 8.1.6 with thin jdbc driver
    Reloading the WLCS_RULESET_DEFINITION table from another stable environment eliminate
    the problem...
    Fri Nov 02 11:04:29 CET 2001:<I> <JDBC Pool> Connection for pool "commercePool"
    created.
    SAX FATAL[ejb://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/RegoleLogoBanca:1,-1]:
    Character conversion error: "Unconvertible UTF-8 character beginning with 0xbb"
    (line number may be too low).
    Fri Nov 02 11:04:30 CET 2001:<E> <T3Services> COMMERCE_SERVER_FRAMEWORK,LOG_ERROR,"Error
    in AdvisorBean.advise() : Exception com.beasys.commerce.axiom.reasoning.rules.service.RulesServiceException
    thrown while processing advislet : com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdviceRequestImpl)."
    com.beasys.commerce.axiom.advisor.AdvisorException: Rules Service RulesServiceException
    thrown : RulesService:Unable to apply rules :: RulesService:Unable to get context
    wrapper :: RulesService:Unable to create context wrapper :: RulesService:Unable
    to create ruleset for xml rules :: org.xml.sax.SAXParseException: Character conversion
    error: "Unconvertible UTF-8 character beginning with 0xbb" (line number may be
    too low).
    at com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(ContentSelectorAdvisletImpl.java:157)
    at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:100)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
    at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    ContentSelectorTag:Unable to get advice:
    com.beasys.commerce.axiom.advisor.AdvisorException: Exception thrown during Advislet.advise
    method
    at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:117)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
    at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    ContentSelectorTag:Unable to evaluate tag:
    javax.servlet.jsp.JspTagException: ContentSelectorTag:Unable to get advice.
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:160)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)

    Fulvio - for an answer to this, refer to my post in the other thread that you started.
    PJL
    "fulvio" <[email protected]> wrote:
    >
    Is there someone that knows how to eliminate this annoying error, that
    randomly
    appears(it seems to appear every time I reboot the system...)?
    Whe have seen this problem running wlps 3.2 on several machines, linux,
    solaris
    and winnt, all pointing to some oracle database 8.1.6 with thin jdbc
    driver
    Reloading the WLCS_RULESET_DEFINITION table from another stable environment
    eliminate
    the problem...
    Fri Nov 02 11:04:29 CET 2001:<I> <JDBC Pool> Connection for pool "commercePool"
    created.
    SAX FATAL[ejb://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/RegoleLogoBanca:1,-1]:
    Character conversion error: "Unconvertible UTF-8 character beginning
    with 0xbb"
    (line number may be too low).
    Fri Nov 02 11:04:30 CET 2001:<E> <T3Services> COMMERCE_SERVER_FRAMEWORK,LOG_ERROR,"Error
    in AdvisorBean.advise() : Exception com.beasys.commerce.axiom.reasoning.rules.service.RulesServiceException
    thrown while processing advislet : com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdviceRequestImpl)."
    com.beasys.commerce.axiom.advisor.AdvisorException: Rules Service RulesServiceException
    thrown : RulesService:Unable to apply rules :: RulesService:Unable to
    get context
    wrapper :: RulesService:Unable to create context wrapper :: RulesService:Unable
    to create ruleset for xml rules :: org.xml.sax.SAXParseException: Character
    conversion
    error: "Unconvertible UTF-8 character beginning with 0xbb" (line number
    may be
    too low).
    at com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(ContentSelectorAdvisletImpl.java:157)
    at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:100)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
    at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    ContentSelectorTag:Unable to get advice:
    com.beasys.commerce.axiom.advisor.AdvisorException: Exception thrown
    during Advislet.advise
    method
    at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:117)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
    at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
    at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
    at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
    at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
    at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    ContentSelectorTag:Unable to evaluate tag:
    javax.servlet.jsp.JspTagException: ContentSelectorTag:Unable to get advice.
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:160)
    at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)

  • Error during JLOAD import with Unconvertible UTF-8 character

    Dear gurus,
    I'm performing a system copy on ECC 6.0. SR£ double stack. During the face of jload import I receive the error
    Unconvertible UTF-8 character beginning with 0xf9
    while importing the table TST_RESERVATION.
    Here you are the full text of the error
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_31-b03, mixed mode)
    org.xml.sax.SAXException: Fatal Error: URI=null Line=1: Errore di conversione caratteri: "Unconvertible UTF-8 character beginning with 0xf9" (il numero riga potrebbe essere troppo basso).
         at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)
         at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1106)
         at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
         at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
         at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
         at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
         at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
         at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
         at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)
         at com.sap.dictionary.database.dbs.DbObjectModificationAnalyser.(DbObjectModificationAnalyser.java:38)
         at com.sap.dictionary.database.opentools.DbTableOpenTools.createTable(DbTableOpenTools.java:70)
         at com.sap.inst.jload.db.DBTable.create(DBTable.java:106)
         at com.sap.inst.jload.Jload.dbImport(Jload.java:278)
         at com.sap.inst.jload.Jload.executeJob(Jload.java:397)
         at com.sap.inst.jload.Jload.main(Jload.java:621)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:331)
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    any sugggestion?
    plese advise soon.

    Hi,
    Are the files from the Java-CD fully readable and fully copied, for instance the java-dumpfile ?
    Ensure JVM settings of note # 716604 area applied. Also, is connect possible to database by 'configtool' or does it throw an error ?
    Br,
    Javier

  • JAXB: Encoding error (Malformed UTF-8, trying to set ISO)

    Hi, I get this error when doing a Unmarshaller.unmarshal( anURL );
    DefaultValidationEventHandler: [WARNING]: Declared encoding "ISO-8859-1" does not match actual one "UTF-8"; this might not be an error.
    DefaultValidationEventHandler: [FATAL_ERROR]: Character conversion error: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (line number may be too low).
    org.xml.sax.SAXParseException: Character conversion error: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (line number may be too low).
         at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
    (...) etc..So far, I set the ISO-8859-1 encoding 4 places;
    1. the xml response from the servlet: xml.append("<?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>\n\n")
    2. the original XSD which the JAXB classes was generated from
    3. In the client, after recieving the string containing the XML: bytes b[] = xmlString.getBytes("ISO-8859-1");
    4. In the client; when posting to the server: httpConn.setRequestProperty("Content-Type","text/xml;charset=ISO-8859-1");
    Yet, JAXB still thinks I'm doing UTF-8 here! Did I forget something?
    thanks,
    bjorn

    bump .. no one knows why this happens?

  • "character conversion error" while parsing xml files

    Hello,
    I'm trying to parse MusicXML (Recordare) files, but I'm getting an exception.
    I'm using the SAX parser (javax.xml.parsers.SAXParser).
    Here is the code I use to instantiate it:
    final javax.xml.parsers.SAXParserFactory saxParserFactory = javax.xml.parsers.SAXParserFactory.newInstance();
    final javax.xml.parsers.SAXParser saxParser = saxParserFactory.newSAXParser();
    final org.xml.sax.XMLReader parser = saxParser.getXMLReader();
    I'm using my own handler, but I get the same exception even if I use org.xml.sax.helpers.DefaultHandler.
    The error I get is:
    Character conversion error: "Illegal ASCII character, 0xc2" (line number may be too low).
    The first few lines of my xml files look like this:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <!DOCTYPE score-partwise
    PUBLIC "-//Recordare//DTD MusicXML 0.6 Partwise//EN"
    "http://www.musicxml.org/dtds/partwise.dtd">
    <score-partwise>
    [...etc...]
    If I delete the <!DOCTYPE ...> line, then I don't get the exception anymore. But the MusicXML files I get (from some other program) always contain this line, and it would be quite some work to delete them from every file manually.
    So does anyone know if there is a way to avoid deleting that line in every file, while still being able to parse the xml files without exceptions?
    Or maybe does anyone know what the exact cause of the exception is? (because I don't know what exactly causes it)
    Thank you in advance.
    Greetz,
    Jipo

    So does anyone know if there is a way to avoid
    deleting that line in every file, while still being
    able to parse the xml files without exceptions?ok this is side-stepping the real problem but I've used this code to filterout DTD references for other reasons   public static InputStream filterOutDTDRef(InputStream in) throws IOException {
          BufferedReader iniReader = new BufferedReader(new InputStreamReader(in));
          StringBuffer newXML = new StringBuffer();
          for(String line = iniReader.readLine(); line!=null; line = iniReader.readLine())
             newXML.append(line+"\n");
          in.close();
          int s = newXML.indexOf("<!DOCTYPE ");
          if(s!=-1)
             newXML.replace(s,newXML.indexOf(">",s)+1,"");
          return new ByteArrayInputStream(newXML.toString().getBytes());
       }and it actually speeds up the parsing phase too (since the DTD ref.s were on the web and the XML standard mandates that there is a fetch for each xml file parsed..)
    you can feed the above into the InputSource constructor that takes an InputStream argument.
    Now for the real problem... 0xc2 is "LATIN CAPITAL LETTER A WITH CIRCUMFLEX" according to a unicode chart - which is not an ASCII character (as the error message correctly reports). I'm not sure why the file is being parsed as ASCII though? You could try parsing in a FileReader to the inputsource and hope it picks up the default character encoding of your system, and that that character encoding matches the file. Or you could try passing in a FileReader constructed with a explicit character encoding (eg "UTF8") and see if that does the trick?
    asjf

  • Numeric or value error: character to number conversion error

    I'm having problems inserting a value from a date picker field (DD-MON-YYYY HH MI )
    i'm submitting this value to a packaged procedure that accepts this field as VARCHAR2 .
    on the insert, i do a to_date( P_DATE, 'DD-MON-YYYY HH:MI PM' )
    and i get the numeric conversion error.
    If I change the to_date on the procedure side, I get the :could not read the end of the format mask - which I've found threads about on this site.
    I've tried using HH24 and different formats, but I get one of the two above errors on the insert.
    If I don't fill in the datepicker field at all, it works fine.
    help is appreciated !
    Bill

    Here is the trace anyway:
    *** ACTION NAME:(application 4000, page 1) 2004-09-24 12:58:44.052
    *** MODULE NAME:(HTML DB) 2004-09-24 12:58:44.052
    *** SERVICE NAME:(TOPS) 2004-09-24 12:58:44.052
    *** SESSION ID:(151.1) 2004-09-24 12:58:44.052
    *** 2004-09-24 12:58:44.052
    ksedmp: internal or fatal error
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    Current SQL statement for this session:
    declare
    rc__ number;
    begin
    owa.init_cgi_env(:n__,:nm__,:v__);
    htp.HTBUF_LEN := 255;
    null;
    null;
    null;
    null;
    f(p=>:p);
    if (wpg_docload.is_file_download) then
    rc__ := 1;
    wpg_docload.get_download_file(:doc_info);
    null;
    null;
    null;
    commit;
    else
    rc__ := 0;
    null;
    null;
    null;
    commit;
    owa.get_page(:data__,:ndata__);
    end if;
    :rc__ := rc__;
    end;
    ----- PL/SQL Call Stack -----
    object line object
    handle number name
    6A3C4A00 532 package body FLOWS_010500.WWV_FLOW_UTILITIES
    6A3C4A00 2502 package body FLOWS_010500.WWV_FLOW_UTILITIES
    6A3C4A00 2748 package body FLOWS_010500.WWV_FLOW_UTILITIES
    6A0E63C8 991 package body FLOWS_010500.WWV_FLOW_FORMS
    6A11675C 932 package body FLOWS_010500.WWV_FLOW_DISP_PAGE_PLUGS
    6A11675C 247 package body FLOWS_010500.WWV_FLOW_DISP_PAGE_PLUGS
    6A4B54E0 8341 package body FLOWS_010500.WWV_FLOW
    6A2A99F0 102 procedure FLOWS_010500.F
    6A2B9E54 10 anonymous block
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    ksedmp+524          CALLrel  ksedst+0 1
    ksedmptracecb+15 CALLrel _ksedmp+0            C
    _ksddoa+118          CALLreg  00000000             C
    ksdpcg+143          CALLrel  ksddoa+0
    ksdpec+180          CALLrel  ksdpcg+0 1966 6D7D208 1
    __PGOSF3__ksfpec+11 CALLrel _ksdpec+0            0
    8
    _kgerev+77           CALLreg  00000000             7474210 1966
    kgerec1+18          CALLrel  kgerev+0 7474210 6DCE5EC 1966 1
    6D7D260
    peirve+465          CALLrel  kgerec1+0
    pevmCVTCN+346 CALLrel _peirve+0           
    pfrinstrCVTCN+36 CALLrel pevmCVTCN+0 6E6E604 71CE370 7160F0C
    pfrrunno_tool+51 CALL??? 00000000
    pfrrun+1834         CALLrel  pfrrun_no_tool+0 6E6E604 6A3C010A 6E6E640
    plsqlrun+1051 CALLrel _pfrrun+0            6E6E604
    peicnt+179          CALLrel  plsql_run+0 6E6E604 1 0
    kkxexe+477          CALLrel  peicnt+0
    opiexe+4896         CALLrel  kkxexe+0 6A2B9E54
    kpoal8+1705         CALLrel  opiexe+0 49 3 6D7E06C
    _opiodr+977          CALLreg  00000000             5E 14 6D7E7CC
    _ttcpip+1827         CALLreg  00000000             5E 14 6D7E7CC 0
    _opitsk+1098         CALL???  00000000            
    opiino+938          CALLrel  opitsk+0 0 0 747ABC0 6DEFB14 D8 0
    _opiodr+977          CALLreg  00000000             3C 4 6D7FBBC
    opidrv+479          CALLrel  opiodr+0 3C 4 6D7FBBC 0
    sou2o+45            CALLrel  opidrv+0 3C 4 6D7FBBC
    opimai+237          CALLrel  sou2o+0
    OracleThreadStart@  CALLrel  opimai+0
    4+899
    77E7D338 CALLreg 00000000

  • PL/SQL: numeric or value error: character to number conversion error in TRG

    Hi,
    I've got strange issue with one trigger which during update of table reports (DB is 9.2.0.8):
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    ORA-06512: at "UDR_LOG", line 345
    ORA-04088: error during execution of trigger 'UDR_LOG'but line 345 is:
    END IF;
    so its kind of strange
    the code looks like
    343 IF nvl(to_char(:old.PKD_ID),'''') <> nvl(to_char(:new.PKD_ID),'''') THEN
    344     v_zmn := v_zmn || 'PKD_ID''' || to_char(:old.PKD_ID) || '''' || to_char(:new.PKD_ID) || '''';
    345    END IF;
    so its concatenation not to_number usage .error is triggered by update statement on any column .
    I'm sorry I cant provide You with whole trigger code .
    So if You could only recommend any investigation method that would be great .
    Regards
    Greg

    Hi, Greg,
    When there's an error in a trigger, the line numbers in the error messages are relative to the first DECLARE or BEGIN statement; often, that's a few lines after CREATE OR REPLACE TRIGGER. Post a few lines after what you already posted.
    If you can't find the error, then create another table for testing this, and create a smaller trigger on that table, which does only enough to cause the error. Then you'll be able to post the complete trigger, and the code needed to re-create the problem.

  • Conversion error, from character set 4102 to character set 4103

    Hi,
    We've developed a JCO server(in Java) with an ABAP report the function provided by the JCO server.
    MetaData:
         static {
              repository = new Repository("SMSRepository");
              fmeta = new JCO.MetaData("ZSMSSEND");
              fmeta.addInfo("TO", JCO.TYPE_CHAR, 255,   0,  0, JCO.IMPORT_PARAMETER, null);
              fmeta.addInfo("CONTENT", JCO.TYPE_CHAR, 255,   0,  0, JCO.IMPORT_PARAMETER, null);
              fmeta.addInfo("RETN", JCO.TYPE_CHAR, 255,   0,  0, JCO.EXPORT_PARAMETER, null);
              repository.addFunctionInterfaceToCache(fmeta);     
    Server parameters:
           Properties prop = new Properties();
           prop.put("jco.server.gwhost","shaw2k07");
           prop.put("jco.server.gwserv","sapgw01");
           prop.put("jco.server.progid","JCOSERVER01");
           prop.put("jco.server.unicode","1");
           srv = new SMSServer(prop,repository);
    If we run JCO server in both my client machine(from developer studio) and in the WAS machine(stand alone Java program), everything is ok. In the Abap side, the SM59 unicode test return the destination is an unicode system, and the ABAP report call the function can run smoothly.
    But we package this JCO server to a web application and deploy to WAS, problem occured. The SM59 unicode test still say the destination is an unicode system. But the ABAP report runs with an ABAP DUMP:
    Conversion error between two character set
    RFC_CONVERSION_FIELD
    Conversion error "RETN" from character set 4102 to character set 4103
    A conversion error occurred during the execution of a Remote Function
    Call. This happened either when the data was received or when it was
    sent. The latter case can only occur if the data is sent from a Unicode
    system to a non-Unicode system.
    I read the jrfc.trc log, it shows it receives data in unicode 4103(that's ok), but send data in unicode 4102(that's the problem).4102 is UTF-16 Big Endian and 4103  UTF-16 Little Endian. Our system is windows on intel 32 aritechture, so based on Note 552464, it should be 4103.
    Why it sends data (Java JCO server send output parameter to ABAP) in 4102?????
    What's the problem??? Thank you very much!!
    Best Regards,
    Xiaoming Yang
    Message was edited by:
            Xiaoming Yang

    Hello Experts,
    Any replies on this?
    I am also getting a similar kind of error.
    Do you have any idea on this?
    Thanks and Best Regards,
    Suresh

  • ORA-06502: numeric or value error: character to number conversion error

    I met the following error when I ran Donald's PL/SQL function to_number_or_null. Could somebody here help me find the resolution? Thanks!
    SQL> create or replace FUNCTION to_number_or_null (
    2 aiv_number in varchar2 )
    3 return number is
    4 /*
    5 to_number_or_null.fun
    6 by Donald J. Bales on 12/15/2006
    7 An errorless to_number( ) method
    8 */
    9 begin
    10 return to_number(aiv_number);
    11 exception
    12 when INVALID_NUMBER then
    13 return NULL;
    14 end to_number_or_null;
    15 /
    Function created.
    SQL> select to_number_or_null('A') from dual;
    select to_number_or_null('A') from dual
    ERROR at line 1:
    ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    ORA-06512: at "CAROL.TO_NUMBER_OR_NULL", line 10

    Only INVALID_NUMBER exception is handled and also VALUE_ERROR should be handeled. You can resolve it by handling VALUE_ERROR exception or by adding WHEN OTHERS as I did in following example.
    SQL> create or replace FUNCTION to_number_or_null (
      2      aiv_number in varchar2 )
      3      return number is
      4     /*
      5     to_number_or_null.fun
      6     by Donald J. Bales on 12/15/2006
      7     An errorless to_number( ) method
      8     */
      9  begin
    10     return to_number(aiv_number);
    11     exception
    12     when INVALID_NUMBER then
    13      return NULL;
    14     when OTHERS then
    15      return null;
    16     end to_number_or_null;
    17  /
    Function created.
    SQL> select to_number_or_null('A') from dual;
    TO_NUMBER_OR_NULL('A')
    ----------------------With kind regards
    Krystian Zieja

  • Error " conversion error between two character sets" in PI MONI

    Hi Experts
    I am doing file to Idoc scenario. I am getting the following error in PI MONI "conversion error between two character sets".
    please suggest me how to solve the issue.
    thanx in advance.

    Hi Mickael
    Below is the complete error message found in PI MONI.
    SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">SYSTEM_DUMP</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>PI Server : XBTO80__0000 : Conversion error between two character sets.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • Character conversion error

    Hi all,
    We are getting the following error when trying to parse an xml string resource - Character conversion error: "Illegal ASCII character, 0xc2" (line number may
    be too low)-. We have not been able to get around this. We have tried creating the InputSource two different ways:
    reader = new StringReader(stringSource);
    src = new InputSource( reader );
    and
    src = new InputSource(new InputStreamReader(new ByteArrayInputStream(stringSource.getBytes())));
    The problem does appear to go away if we treat the DTD we are validating against as a file. If we set it has a uri, we get the above problem.
    Is anyone else experiencing this problem?
    Any help would be greatly appreciated.
    Thanks in advance,
    Greg

    Hi,
    2 possible solutions:
    1) try using the xerces parser instead of sun's parser
    2) look at the posting at the following url and see wether the posted solution solves your problem: http://forums.java.sun.com/thread.jsp?forum=34&thread=67558
    Hope this helps,
    Kurt.

Maybe you are looking for