Unalbe to parse document

Hello Experts,
Recently we upgraded from SAp Business Connector 4.7 to BC 4.8 and on testing a scenario getting the below error -
"Unable to parse document.
0000E8  [B2BUNKW.XML.0003] <exception message="Error parsing document. reasons include:
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document &#39;XCBL35.xsd&#39;, because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not &lt;xsd:schema&gt;.,
org.xml.s
Unable to parse document.
0000E8  [B2BUNKW.XML.0003] <exception message="Error parsing document. reasons include:
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document &#39;XCBL35.xsd&#39;, because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not &lt;xsd:schema&gt;.,
org.x
And there is XML Schema defiend in BC developer as well.
Please help me. Its quite urgent!!!!
Regards,
Narayanareddy B

Hi Inaki,
Thanks for the reply.
Yes i am doing it in BC 4.8 server and we see the issue in that server.
But we trigger the same IDOC in sap bc 4.7 serevr where it has processed fine.
And BC server is maintaine dion jdk1.55 version and is it a roadblock for parsing, kindly let me know any idea on this.
And i see the error coming at "createEnvelopFromString" step.
Please help me if have any further information as it is quite urgent.
Hi bhargava,
I am doing on BC 4.8 server., anyhow thanks for your respose.
Regards,\
Narayanareddy B

Similar Messages

  • Error parsing document index: invalid character in attribute value

    Hi,
    I am working on an eBook with iBook Author. Once in a while, after I finish working, and want to reopen my eBook a few hours or days after I get the error:
    'title' could not be opened
    Error parsing document index: invalid character in attribute value
    I have to go back to an old backup I always do before quitting.
    What is the reason of this error message and anyw ay to fix/repair it on a version I just saved?
    Thanks,
    JP.

    Hello,
    I have the same error, but for me the above solution did not work.
    Did I understand correctly? This is what I did:
    1. I changed the extension of the IBA file in ZIP
    2. I unzipped the file
    3. in the folder with the unzipped book I have changed the file index.xml in index.html
    4. I zipped it all back (in a ZIP file)
    5. I renamed the extension ZIP archive in IBA
    6. I tried to open the book and I got  the error that there was no index.xml file
    7. I changed the extension of the IBA and in ZIP
    8. I unzipped the file again
    9. I changed back index.xml to index.html and I zipped it back (compressed it)
    10. I renamed the extension ZIP archive in IBA
    11. I opened the book
    Is this correct?
    The problem is that I am still receiving the same error message: Error parsing document index: invalid character in attribute value
    Did I do something wrong?
    If you can help I would be very greatfull, I worked hard on this book and it is the only backup that I have saved.
    Thank you!

  • Parsing documents in Java called via JNI

    My native application is in C running on WinXP, and I am attempting to call an API in Java using JNI. I am quite a JNI newbie so hopefully someone can shed some light on my issue. Everytime I attempt to parse a document in Java using:
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    factory.setValidating(true); // also tried false
    DocumentBuilder builder = factory.newDocumentBuilder();
    builder.setErrorHandler(this);
    Document document = builder.parse(new File(filename));I get an IncompatibleClassChangeError exception thrown. This happens when I parse XML, text, you name it. The Java code works fine outside of JNI. The C source snippet (minus the exception checking) looks like the following:
    testClass = (*env)->FindClass(env, "TestClass");
    testMethod = (*env)->GetMethodID(env, testClass, "test", "(Ljava/lang/String;)I");
    filename = (*env)->NewStringUTF(env, "test.xml");
    value = (*env)->CallIntMethod(env, testClass, testMethod, filename); Any suggestions would be very much appreciated.

    I believe I have found the problem, and it's (of course) an exercise in double-checking everything. It also makes me want to slay my predecessors for their confusing design choices.
    The class JNIMessage isn't in the class hierarchy of Message, though it appears to be if you're not inspecting the code closely enough. This is almost certainly the problem. I was looking in the wrong place; the JNI code is probably not suspect here.

  • Parsing Documents

    I'm using Oracle XmlParser for java in order manage XML documents.
    The only metod I foud in order to read an XML document from a file is : create a DOMParser and use the parse method.
    If I do that and the document is malformed I get an error.
    If I set the validation mode to true or false (setValidationMode) nothing changes.
    Any suggestion ?
    Is there any Oracle forum on Xdk ?
    TIA
    T. Bettinazzi

    If you have control over the file format I would highly suggest you use XML to format the file and then use a SAX XML parser to go through it...this would ease your life considerably. If you can't do that for some reason can you read the line into a string and then say something like if(line.startsWith(" ")...
    to find out if it's a wrapped description line? Also, if you're using java 1.2 or above you should use an ArrayList instead of a Vector to hold your data. Sorry, that didn't really answer your question but I highly suggest using XML.

  • Cant parse Document/Literal WS Response

    It might be the case that i'm not doing correctly, but I cant seem to parse the document/literal response for the life of me. The response parses as expected when I build the web service as an RPC WSDL, but fails when I build as document/literal. The company standard is document/literal wrapped, so thats the one I need to use. Any help would be greatly appreciated!!
    Here is the WSDL contents and the javascript...
    WSDL:
    <wsdl:definitions targetNamespace="http://dao.test.crowley.com">
    <!--
    WSDL created by Apache Axis version: 1.4
    Built on Apr 22, 2006 (06:55:48 PDT)
    -->
    <wsdl:types>
    <schema elementFormDefault="qualified" targetNamespace="http://dao.test.crowley.com">
    <element name="getUserJSON">
    <complexType>
    <sequence>
    <element name="sql" type="xsd:string"/>
    </sequence>
    </complexType>
    </element>
    <element name="getUserJSONResponse">
    <complexType>
    <sequence>
    <element name="getUserJSONReturn" type="xsd:string"/>
    </sequence>
    </complexType>
    </element>
    </schema>
    </wsdl:types>
    <wsdl:message name="getUserJSONRequest">
    <wsdl:part element="impl:getUserJSON" name="parameters">
          </wsdl:part>
    </wsdl:message>
    <wsdl:message name="getUserJSONResponse">
    <wsdl:part element="impl:getUserJSONResponse" name="parameters">
          </wsdl:part>
    </wsdl:message>
    <wsdl:portType name="UserDAO">
    <wsdl:operation name="getUserJSON">
    <wsdl:input message="impl:getUserJSONRequest" name="getUserJSONRequest">
           </wsdl:input>
    <wsdl:output message="impl:getUserJSONResponse" name="getUserJSONResponse">
           </wsdl:output>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="UserDAOSoapBinding" type="impl:UserDAO">
    <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="getUserJSON">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="getUserJSONRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="getUserJSONResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="UserDAOService">
    <wsdl:port binding="impl:UserDAOSoapBinding" name="UserDAO">
    <wsdlsoap:address location="http://localhost:8080/PDFTest/services/UserDAO"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Javascript:
    function testDocumentLiteral(){
         try{
              var cURL = "http://localhost:8080/PDFTest/services/UserDAO?wsdl";
            console.println("\n\n***** ECHO *****");
            console.println("\nWSDL: " + cURL);
              //Set SQL String
            var sqlString = "SELECT * FROM USER WHERE EMPLOYEE_ID = 123456";
              console.println("SQL: " + sqlString);
              // Call the echoString SOAP method -- it is an RPC Encoded method
              SOAP.wireDump = false;
              var response = SOAP.request(
                   cURL: cURL,
                   oRequest: {
                        "http://localhost:8080/PDFTest/services/UserDAO?wsdl:getUserJSON": {
                             sql: sqlString
                   cAction: ""
              var parsedResult = response["http://localhost:8080/PDFTest/services/UserDAO?wsdl:getUserJSONResponse"]["getUserJSONReturn"];
              console.println("Web Service Response: " + parsedResult);
         catch(e){
              console.println("Exception...\n" + e);

    Here is my wireDump:
    <soapenv:Envelope>
    −
    <soapenv:Body>
    −
    <getUserJSONResponse>
    −
    <ns1:getUserJSONReturn>
    [{"firstName":"John","middleName":"X.","lastName":"Doe","employeeId":123456}]
    </ns1:getUserJSONReturn>
    </getUserJSONResponse>
    </soapenv:Body>
    </soapenv:Envelope>

  • Parse document without validating

    Hi all,
    I'm writing a program which will be run in a stand alone machine (i.e. no network connection). When I parse my document which contain a "DOCTYPE", it will have an exception. Also, I don't want to store the DTD file in my local machine. How can I parse a document without validating it in a SAXParser? Thx for all.
    Here is my parser code:
    SAXParserFactory factory = SAXParserFactory.newInstance();
    XMLReader reader = factory.newSAXParser().getXMLReader();
    reader.setContentHandler(new SaxParser());
    reader.parse(xml_file);
    In the XML document:
    <!DOCTYPE package PUBLIC "+//ISBN....." "http://abc.org/dtd.....">
    The exception is:
    java.net.UnknownHostException: abc.org

    how about this code?
    SAXParserFactory factory = SAXParserFactory.newInstance();
    //disable validation
    factory.setValidating(false);
    XMLReader reader = factory.newSAXParser().getXMLReader();
    reader.setContentHandler(new SaxParser());
    reader.parse(xml_file);

  • Error 225 on parsing document

    I am getting an error 225 when parsing the following document, using the XDK 8 xmlparseBuffer() method :
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <TMKCaseMadridAddr>
    <Representative Source="090024db80f0a9a8">
    <Name>Cabinet Hirsch &amp; Associés</Name>
    <Address>Avenue Louise 240, Bte 5</Address>
    <Address>B-1050 Bruxelles</Address>
    </Representative>
    <Correspondence></Correspondence>
    <Holder Source="090024db80f0a9a7">
    <Name>COTY B.V.</Name>
    <Address>Oudeweg 147</Address>
    <Address>NL-2031 CC Haarlem</Address>
    </Holder>
    </TMKCaseMadridAddr>
    Error 225 seems to be to do with duplicate attributes, but the XML looks OK to me. Could it be to do with the é character ? The XML prolog contains the encoding statement, but the call to xmlparseBuffer() defaults the encoding attribute. Does the parser ignore the prolog value ?
    Any help will be greatly appreciated
    Cliff Cooley

    This is getting ridiculous - I can't post the xml as it is actually being input the parser. The xml causing the error 225 is :
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <TMKCaseMadridAddr>
    <Representative Source="090024db80f0a9a8">
    <Name>Cabinet Hirsch & Associés</Name>
    <Address>Avenue Louise 240, Bte 5</Address>
    <Address>B-1050 Bruxelles</Address>
    </Representative>
    <Correspondence></Correspondence>
    <Holder Source="090024db80f0a9a7">
    <Name>COTY B.V.</Name>
    <Address>Oudeweg 147</Address>
    <Address>NL-2031 CC Haarlem</Address>
    </Holder>
    </TMKCaseMadridAddr>
    where the &_amp; doesn't really have a _ (hope this is clear)

  • Java and parsing document

    I need parse different type of document (RTF, PDF, HTML). I need get text and all tables in document. Does anyone have a clue how to do it?

    "+Any parser should give you the structure of the document.+"
    Ok, you are right. But I can not get structure what I need. for example:
    this is text of ducument
    | one | two|
    | 1 | 2 |
    the end of document.
    I need get next structure:
    <text>this is text of ducument</text>
    <table>
    <tr>
    <td>
    <text>one</text>
    </td>
    <td>
    <text>two</text>
    </td>
    </tr>
    <tr>
    <td>
    <text>1</text>
    </td>
    <td>
    <text>2</text>
    </td>
    </tr>
    </table>
    <text>the end of document.</text>

  • Parse XML document which have xlink/xpointer inside

    dear friends,
    There are lots of topic talking about parse xml, validating xml with schema and so on, but no one or any book talking about parsing xml document which can parse document with link inside.
    According to Mr Meggison at http://www.megginson.com/Background/
    we can do it, but he is not expert with this thing.
    For example I have 3 XML document. My main XML document, let named it A.XML have XPointer inside and this element pointing to B.XML and C.XML using xpointer. how to parse A.XML and in the same time my SAX recognized this XPointer and parse also element inside B.XML and C.XML.
    I am really grateull for any helpful information from you.
    best regards

    I think you need to look for a SAX or DOM parser that undestands XPointers and knows how to follow them to additional content.
    I have used XSLT and specified external documents to it. It knows how to read a document and in effect make a nodeset which can be searched with the XPath capabilities of XSLT.
    It sounds like you wnat an <include file="xxx"/> capability and have the parser stop reading the current file, and start reading the second file.
    That works in Schemas, but I'm unaware of any way to do it with SAX or DOM in one pass.
    It would not be too hard to process the first file, say with DOM.
    After the Document is built, go find the <include> elements, read get the attribute needed, build a new Document and merge it into the original Document in place of the <include> element.
    Is this more what you want to do?
    Dave Patterson

  • XML Document parse base dir

    Hy is there anyway to specify a base dir when parsing a document? Have a doctype defined that references a XML file but the file is relative to the parsing document.
    Example :
    <!DOCTYPE something [
    <!ENTITY fileRef SYSTEM "file:./util/otherFile.xml">
    ]>
    <something>
    &fileRef ;
    </something>
    When parsing this document i get the following exception "java.io.FileNotFoundException: ./util/otherFile.xml (The system cannot find the path specified)". Though the file is in the specified directory.
    Another question i have is if it's possible to make any reference to any system environment variables from within an XML document.
    Thanx,
    Daniel Campelo

    Yes, call the setSystemId() method on the InputSource you are giving to the parser. Remember you have to give it a URI, not a path name. (The File class has a method to return the URI of a file path.)
    And sure, you can refer to system environment variables in an XML document. Just don't expect those things to be treated any differently than any other text. If you want them to be replaced by the value of the environment variables, for example, you have to do that yourself.

  • Processing this item failed because of a PDF parser error. Input string was not in a correct format.

    Good Morning,
    We're having issues parsing several hundred PDF files located in two separate Record Center sites. All other PDF documents in the environment are being crawled and parsed without issue. I've verified the permissions for the Search service account, but that
    doesn't seem to be the issue. Searching for this particular error hasn't returned much, but I have ensured that the Search service account has been added to the necessary Local Security Policy objects and cleared the configuration cache. Any help would be
    greatly appreciated.
    Processing this item failed because of a PDF parser error. ( Error parsing document 'https://asdf.com/sites/HRRecords/asdf.pdf'. Input string was not in a correct format.; ; SearchID = 6642FEEF-6921-434E-B084-02809173D8A7 )

    This issue came back up for me as my results aren't displaying since this data is not part of the search index.
    Curious if anyone knows of a way to increase the parser server memory in SharePoint 2013 search?
    http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip
    Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip'. Document failed to be processed. It probably crashed the
    server.; ; SearchID = 097AE4B0-9EB0-4AEC-AECE-AEFA631D4AA6 )
    http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip
    Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The
    function encountered an unknown error.; ; SearchID = 4A0C99B1-CF44-4C8B-A6FF-E42309F97B72 )

  • SharePoint 2013 Search - Zip - Parser server ran out of memory - Processing this item failed because of a IFilter parser error

    Moving content databases from 2010 to 2013 August CU. Have 7 databases attached and ready to go, all the content is crawled successfully except zip files. Getting errors such as 
    Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/file1.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The function encountered an unknown error.; ; SearchID = 7A541F21-1CD3-4300-A95C-7E2A67B2563C
    Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/file2.zip'. Document failed to be processed. It probably crashed the server.; ; SearchID = 91B5D685-1C1A-4C43-9505-DA5414E40169 )
    SharePoint 2013 in a single instance out-of-the-box. Didn't install custom iFilters as 2013 supports zip. No other extensions have this issue. Range in file size from 60-90MB per zip. They contain mp3 files. I can download and unzip the file as needed. 
    Should I care that the index isn't being populated with these items since they contain no metadata? I am thinking I should just omit these from the crawl. 

    This issue came back up for me as my results aren't displaying since this data is not part of the search index.
    Curious if anyone knows of a way to increase the parser server memory in SharePoint 2013 search?
    http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip
    Processing this item failed because the parser server ran out of memory. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Votrevieprofessionnelleetvotrecarrireenregistrement.zip'. Document failed to be processed. It probably crashed the
    server.; ; SearchID = 097AE4B0-9EB0-4AEC-AECE-AEFA631D4AA6 )
    http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip
    Processing this item failed because of a IFilter parser error. ( Error parsing document 'http://sharepoint/materials-ca/HPSActiveCDs/Travaillerauseindunequipemultignrationnelle.zip'. Error loading IFilter for extension '.zip' (Error code is 0x80CB4204). The
    function encountered an unknown error.; ; SearchID = 4A0C99B1-CF44-4C8B-A6FF-E42309F97B72 )

  • Options for XML parsing in WAS 6.20 ABAP and higher

    Hello Experts,
       What options are available to me for working with XML documents in SAP R/3 4.7? I am working on SAP WAS 6.20 ABAP and was wondering which tools/techniques I can use for parsing XML files?
       I am developing an ABAP program and primarily need to be able to parse XML documents. I need to be able to traverse up and down their data structures (trees/nodes/elements/etc.).
       In SAP R/3 4.6 I used to use the iXML library but it seems that there are many advanced and powerful features included in SAP WAS 6.20 ABAP and up.
       Could someone please give me a summary of and their opinions on some these "newer" options?
    Thanks,
    - Vik.

    Hi Vik,
       There are two ways you can parse/interpret XML documents in ABAP -
       1. iXML - Which you have already used in 46 release. It wasn't easy to use set of functions but still it was possible to parse documents using iXML library. In WAS 6.20 you can now use class CL_XML_DOCUMENT which is much more easier to use than iXML library. It is bilt on top of iXML using the same DOM model.
      2. XSLT - Useing XSLT_TOOLS or XSLT transaction you can create XSLT programs to transform XML to ABAP data objects and then work with ABAP data objects. In this case you have the option of using some other tool like XMLSPY to write the XSLT and then copy that to SAP.
    From your post it looks like you will probably have to traverse the tree in unpridictable way, probably DOM based parsing using CL_XML_DOCUMENT is more suitable for you.
    Cheers,
    Sanjeev

  • Problem in Coverting XML String into Document

    Hi,
    I am getting some problem while parsing a String XML in to Document object.
    CODE :
    public static Document converDocument(String xml){
    DocumentBuilderFactory factory=DocumentBuilderFactory.newInstance();
    DocumentBuilder builder = null;
    try {
    builder = factory.newDocumentBuilder();
    } catch (ParserConfigurationException e) {
    e.printStackTrace();
    Document document = null;
    try {
    document = builder.parse(new InputSource(new StringReader(xml)));
    System.out.println("Document is after parsing ====>>>"+document);
    } catch (SAXException e1) {
    // TODO Auto-generated catch block
    e1.printStackTrace();
    } catch (IOException e1) {
    e1.printStackTrace();
    return document;
    The xml which I am passing is :
    <?xml version="1.0" encoding="UTF-8"?>
    <note>
    <to>Tove</to>
    <from>Jani</from>
    <heading>Reminder</heading>
    <body>abc</body>
    </note>
    It is giving the document as null;
    Can anybody please help?
    Regards,
    sheeetal.

    >
    Vikas Sridharan wrote:
    > 
    >       CALL TRANSFORMATION ('ID')
    >       SOURCE XML = lv_output_str "<============ ERRONEOUS = HERE
    >       RESULT ref = <fst_dyn_table> .
    >
    Remove the "=" sign, this code will work :
          CALL TRANSFORMATION ('ID')
          SOURCE XML lv_output_str
          RESULT ref = <fst_dyn_table> .

  • ANN: XML Parser for Java v2.0.2.6

    The v2.0.2.6 of the XML Parser for Java is now available for download. The following features and bug fixes are included:
    Changes:
    Conformance to the XSLT/XPATH October REC.
    New API in XSLStylesheet class:
    removeParam(String param)
    resetParams()
    Bug fixes:
    Bug #1111423: OutOfMemory exception, if multiple calls made to document()
    Bug #1101028: Unexpected character error in DTD parsing document using Docbook DTD
    Bug #1101021: #default not supported in exclude-result-prefixes
    Bug #1099830: Extra characters inserted into output using the XML Parser
    Bug #1099663: HTML output does not allow only doctype-public to be specified
    Bug #1099536: HTML output does not disable escaping for script, style unless lowercase
    Bug #1098738: ArrayOutOfBoundsException xsl:if test="not(@a)'"
    Bug #1095047: XSLProcessor NPE'S on named templates with non-empty namespaces
    Bug #1094971: XSLStylesheet needs methods for removing parameters
    Bug #1092351: Using valueof() shuffles order of elements in my source document
    Bug #1086663: xsl:sort data-type attribute can now be a namespace-prefixed name
    Bug #1086661: xsl:version attribute now required on literal result element
    Bug #1064692: Default xml-serialization should use empty-element syntax
    Bug #1064689: Current() function doesn't work correctly
    This is the sixth production patch release for v2.
    Oracle XML Team http://technet.oracle.com
    Oracle Technology Network
    null

    The link has been fixed. You will go to the v2 download page
    now. Sorry for the inconvience.
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    Renilton Oliveira (guest) wrote:
    : I didn't find the file for version 2.0.0.0 as well.
    : Renilton
    : Andrei Filimonov (guest) wrote:
    : : I tried to download XML Parser for Java v2 it seems that
    only
    : v
    : : 1.0.1.4 is available. Could you please give an exact URL for
    : v2
    : : download?
    : : Andrei Filimonov
    : : Oracle XML Team wrote:
    : : : The Oracle XML v2 parser is now available for download
    here
    : as
    : : : an early beta release and is written in Java. It features
    : an
    : : : improved architecture over the Oracle XML v1 parser and
    has
    : : : shown better performance on small to large XML documents.
    : It
    : : : will also be able to format the XML document according to
    a
    : : : stylesheet, having integrated an XSLT processor.
    : : : Version 2 of the XML Parser for Java, besides
    incorporating
    : an
    : : : XSLT processor, has been re-architected from version 1.
    This
    : : has
    : : : resulted in a number of changes to the class names
    : especially
    : : : those that support Namespaces. See v2changes.txt and
    : the .diff
    : : : difference files in the sample directory.
    : : : Oracle XML Team
    : : : http://technet.oracle.com
    : : : Oracle Technology Network
    null

Maybe you are looking for