First time here? Check out the FAQ!

Full search not successful [closed]

  • retag add tags

We use a PHP script that cURLs the query to RETS ( The commercial property query is working fine, but the other queries are failing. The error I'm getting back is:

"stopped querying at loop 6 count of returned data was 1"

Nothing has changed on our end and according to CREN, nothing has changed on their end either. Any insight would be appreciated.

JamesPetree's avatar
asked 2018-03-15 17:50:22 -0500
edit flag offensive 0 remove flag reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by JamesPetree
close date 2018-03-16 16:42:13.884279


Please change your RETS login URL from "" to "". I have no idea what your internal processes are doing. If you give me your account name I can look at our logs?

bwolven's avatar bwolven (2018-03-16 09:39:25 -0500) edit

Thank you for the reply, the account name is mtnestates09rets.

JamesPetree's avatar JamesPetree (2018-03-16 09:54:52 -0500) edit

The only thing I see is that your account is limited to 2500 records per request. With Query: (L_ListingID=0-1000000), RE_1=2540 and LD_2 =3781 the rest are less, so MAXROWS is returned. The rest would need to be pulled by using offset or adjusting your query.

bwolven's avatar bwolven (2018-03-16 11:59:45 -0500) edit

In addition to changing the domain name you should probably use RETS/1.7.2 instead of RETS/1.5 too.

bwolven's avatar bwolven (2018-03-16 12:01:22 -0500) edit

I updated to use RETS/1.7.2 and the new domain name, offsets limiting to 2500 were already in place, ran again with same result.

JamesPetree's avatar JamesPetree (2018-03-16 12:16:33 -0500) edit

What is it showing in the RETS Connector logs?

bwolven's avatar bwolven (2018-03-16 15:04:06 -0500) edit
add a comment see more comments

1 Answer


The issue is resolved, thank you very much for your assistance!

JamesPetree's avatar
answered 2018-03-16 16:41:53 -0500
edit flag offensive 0 remove flag delete link


What was the fix?

bwolven's avatar bwolven (2018-03-16 16:45:54 -0500) edit

The issue lied in the parsing of the returned data. There was a change in the data returned and once that was identified and compensated for, the queries began working.

JamesPetree's avatar JamesPetree (2018-03-16 16:52:34 -0500) edit

Is your process sensitive to field additions/changes?

bwolven's avatar bwolven (2018-03-16 16:54:46 -0500) edit

Actually, it was the successful message that was being parsed from the return that was different.

JamesPetree's avatar JamesPetree (2018-03-16 17:09:57 -0500) edit

Ok. Thanks.

bwolven's avatar bwolven (2018-03-16 17:11:58 -0500) edit
add a comment see more comments