RE: SetError() #66: XML parse failed at line 2, col 0: no element found

["Dutton, Dave" <dutton@xxxxxxxxxxxx>]

Hi Scott,
    Thanks for the reply.  I have figured it out.  I'm using EXAMPLE 17 and needed to figure out the value of NAME in the SAVEEMBED procedure when the embedded XML was returned from the parser.  Also had to turn the strip CRLF off, and remove writing the XLM header since it is already there.  

Thanks for everything you do for the I community!!  
 

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, February 18, 2016 11:46 PM
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: SetError() #66: XML parse failed at line 2, col 0: no element found

Dave,

The problem here does not appear to be related to HTTP communications, 
rather it's with the way you are trying to parse the XML document.   You 
haven't provided much information about how you're doing this.

Can we see the code that handles the XML parsing?    You have one XML 
document that's wrapped inside another document, which can be a bit tricky.

-SK


On 2/18/2016 9:52 AM, Dutton, Dave wrote:
>     Hello,
>
>        I have been banging my head against the wall trying to figure this
>     out...  This is my first attempt at using HTTPAPI and I get to the web
>     site and download the file OK just cannot parse it.  It appears to have
>     all the tags escaped correctly.
>
>

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