Re: XML parse failed at line 1, col 0: no element found

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hello Jitender,

On 2/23/2011 7:11 AM, jitender singh wrote:
>  When i have changed the URL got an 500   HTTP/1.1 500 Internal Server
>  Error .
>
>  Please find attached the debug file.
>  Please suggest how i can rid off from this error.



500 just means "an error occurred".  To find out what the error was, you 
have to look at the document that the web server is sending you.  Note 
that the 500 error does *not* mean that you didn't get a response from 
the web server -- you did!  You got a SOAP message in response.

I'll copy/paste it from your debug file, and add some line breaks to 
make it easier to read.  Here's the result:

<soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
    xmlns:xsd="http://www.w3.org/2001/XMLSchema";
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Body>
    <soapenv:Fault>
      <faultcode>soapenv:Sender</faultcode>
      <faultstring>
         Could not retrieve the body of the SOAP request. Error: An
         invalid XML character (Unicode: 0x0) was found in the element
         content of the document.
      </faultstring>
      <faultactor></faultactor>
      <detail/>
    </soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

So, clearly it is receiving the document you are sending, but you have a 
bug somewhere in your code that's inserting an invalid character.

I also noticed that SoapUI capitalizes the <Record> element, but you 
have it in lowercase like <record>.  Please change that to a capital R 
(XML is case sensitive.)

Good luck
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------