First time here? Check out the FAQ!

Need help with feed transition - Error 20203

Hello, I am in quite a situation here and having a difficult time with this system.

TLDR; I'm getting error 20203, is this a problem with the feed or a problem with the code reading the feed?

We have a client who's MLS feed was built years ago. Up until now, it has continued to function without problem. However, at the end of June the client (unbeknownst to us) had their feed changed from one source to another (or one merged with another, it's not clear).

I was given a new URL and an updated user, but updating the auth credentials did not work. After some time it was clear the issue was with the account as it was not working properly. Eventually they made some change to the account that allowed me to login, though I had to update the PHRETS connection to basic auth for it to work.

I am now faced with this other issue. When trying to sync the data and perform a search, this is the error I am getting. Searching the support forums it is not clear if this is an error that I need to fix somewhere or an error outside of my control.

compucast's avatar
asked 2021-07-09 11:38:53 -0500, updated 2021-07-12 16:35:25 -0500
edit flag offensive 0 remove flag close merge delete


What is your Login URL and the account name you are using (No Passwords),

bwolven's avatar bwolven (2021-07-09 11:46:48 -0500) edit

Hello Bwolven, here are the details


Thank you

compucast's avatar compucast (2021-07-09 12:27:08 -0500) edit
add a comment see more comments

1 Answer


It looks as though the class names may have changed from your original implementation.
These are the classes for Property: HS_1,CD_2,MF_3,FA_4,LD_5,CI_6
Here's the error I see in our logs:
SEARCH ERROR: FNISDex.Exceptions.RetsSearchException: Miscellaneous Search Error. Class [RE_1] does not exist in Resource [Property].
You can try changing RE_1 in your PHP code to HS_1 to see if that fixes your issues.

bwolven's avatar
answered 2021-07-09 17:09:05 -0500
edit flag offensive 0 remove flag delete link


Thank you Bwolven for your help, but unfortunately there is anew error:

Error: 20202

Happens on search function, same as previous error. Searching support for this error it seems that it is related to an invalid field, I would paste them all but there is not enough allowed characters to do so.

I also want to point out that there are two types of properties we are collecting, HS_1 (formerly RE_1) and LD_2 and each have their own large list of fields. Is there some kind of docs or spec I can refer to?

compucast's avatar compucast (2021-07-09 19:36:35 -0500) edit

Just reaching back out about the 20202 error now. Thanks

compucast's avatar compucast (2021-07-12 16:09:54 -0500) edit

There is metadata you can download from RETS and in that there are Long Name values for the fields along with lists of the fields. There is also "" if it is still active where you can enter your connection information and brows the available metadata.

bwolven's avatar bwolven (2021-07-12 16:40:13 -0500) edit

Thank you again, however there is now a new problem, error 20201 no records found.

I am wondering if maybe the search query has changed, but reading support the main response was typically to contact MLS. I'm copying the search parameters below. FYI I tried to locate that info in the link above, but there were no specifics documented on the search transaction.

QUERY: (L_ListingID=1+),(L_City=LakeCarro)
OPTIONS:( [Select] => L_ListingID, ...) **just ID for testing
compucast's avatar compucast (2021-07-13 11:01:27 -0500) edit

L_City is a lookup field so when searching you need to use the lookup's Value from the metadata.
So this query works: (L_ListingID=1+),(L_City=LKC) to return properties in "LAKE CARROLL"

bwolven's avatar bwolven (2021-07-13 16:44:46 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer