xml -1

[ShawmutSteve]

Hi

I'm suddenly seeing a Rets error '-1' when executing a SearchQuery for
RESI properties from a Rapattoni feed from Southern California. The
SearchQuery is fairly simple: (Property, RESI) (ListingRid=1+),
(LastModifiedDateTime=2012-01-06T05:02:10+)

I find 482 found records, and I'm reading them in batches of 100 using
an offset.

I see this thread:
https://groups.google.com/group/phrets/browse_thread/thread/d487478f50aee54d/c2bc76bd6c82d841?lnk=gst&q=XML+parsing+error#c2bc76bd6c82d841

but I am not clear that I am experiencing the same problem because:
- I cannot find an improperly escaped character in the feed data,
- I do not see the -1 xml error anywhere in rets_debug.txt,
- I DO see this in the rets_debug.txt:
<RETS-STATUS ReplyCode="20208" ReplyText="Maximum Records
Exceeded" />

Is it possible that the 'Maximum Records Exceeded' error is being
remapped to -1, making it look like an xml issue?

Thanks
Steve

[ShawmutSteve]

I figured out that it WAS a parsing error. I'm working not to
identify which field contains the bad data.

Thanks
Steve

On Jan 7, 1:57 pm, ShawmutSteve <shawmutst...@gmail.com> wrote:
> Hi
>
> I'm suddenly seeing a Rets error '-1' when executing a SearchQuery for
> RESI properties from a Rapattoni feed from Southern California.  The
> SearchQuery is fairly simple: (Property, RESI) (ListingRid=1+),
> (LastModifiedDateTime=2012-01-06T05:02:10+)
>
> I find 482 found records, and I'm reading them in batches of 100 using
> an offset.
>

> I see this thread:https://groups.google.com/group/phrets/browse_thread/thread/d487478f5...