First time here? Check out the FAQ!
0

RETS Status Code 20203 TOPEKAMLS

Hello -

I am trying to use RETS Connector to access the Topeka MLS data. I'm getting the following error when I try to download decoded data:

Server: http://topekamls.rets.fnismls.com/ret... User name: topekastats Full pull Local time: 7/5/2016 2:13:59 PM Server time: Tue, 05 Jul 2016 19:14:01 GMT

Running step "Full Download"

Data file: C:\Users\s352u532\Documents\Stata\MLS\RETSConnector\Topeka_RETSDownload1.txt Search query: (L_ListingID=0+) 6000 records downloaded Error detected: server failed to send data at offset 4001 RETS Status code = 20203: Undecoded values were sent: Miscellaneous Search Error. Lookup: value 1034A not found in Lookup table Subd_Lkp_1 for Resource 1. [LM_Char10_10]

Based on other posts, it appears that the Metadata need to be refreshed. Is this something you YOU do or do I need to contact the local MLS administrator to have this done?

Thank you for your prompt response.

stan.longhofer's avatar
stan.longhofer
asked 2016-07-05 14:21:45 -0500
bwolven's avatar
bwolven
updated 2016-08-01 15:17:40 -0500
edit flag offensive 0 remove flag close merge delete

Comments

Thanks, but I'm afraid just tried a download and I got the exact same error:
RETS Status code = 20203: Undecoded values were sent: Miscellaneous Search Error. Lookup: value 1034A not found in Lookup table Subd_Lkp_1 for Resource 1. [LM_Char10_10] FYI, I did change the server version to 1.7.2

stan.longhofer's avatar stan.longhofer (2016-07-06 08:56:01 -0500) edit

I have notified the SSM. It looks like that particular lookup value is missing in Paragon too. As a workaround you could remove the LM_Char10_10 from your returned fields list.

bwolven's avatar bwolven (2016-07-06 10:20:38 -0500) edit

Can you try it again? The issues with LM_Char10_10 should be resolved now.

bwolven's avatar bwolven (2016-07-06 14:49:11 -0500) edit

I'm afraid I get errors with more Lookup Tables not. I sent a copy of the log to the e-mail address that was associated with this comment.

stan.longhofer's avatar stan.longhofer (2016-07-06 15:48:22 -0500) edit

Still working on getting the rest of the lookup issues cleaned up. Will let you know when they are fixed.

bwolven's avatar bwolven (2016-07-07 10:23:15 -0500) edit
add a comment see more comments

1 Answer

0

I have notified the TOPEKAMLS SSM who will coordinate the refresh.

Please change the URL you are using to:

"http://topekamls-rets.paragonrels.com/rets/fnisrets.aspx/TOPEKAMLS/login?rets-version=rets/1.5"

Also if your clients supports it, change your RETS version to RETS/1.7.2 (change in URL too to be consistent). We are trying to move clients to the newer RETS versions whenever possible.

The RETS refresh for TOPEKAMLS was completed at: 7/6/2016, 8:09 AM CST.

Update: 7/12/2016 14:50 CST - The undecoded value issues have been fixed.

Let me know if you have further issues.

Thank you for your patience.

bwolven's avatar
bwolven
answered 2016-07-05 14:47:11 -0500, updated 2016-07-12 14:44:46 -0500
edit flag offensive 0 remove flag delete link

Comments

Great. Thank you very much. I've found 1.7.2 more reliable generally.

stan.longhofer's avatar stan.longhofer (2016-07-05 15:01:39 -0500) edit

This lookup issue may also be what was causing your ezRETS ODBC driver to fail. I think ezRETS has some logging options you enable to see more detailed error information.

bwolven's avatar bwolven (2016-07-05 15:09:57 -0500) edit

Thanks. The 7/12/16 refresh appeared to fix the issue. I was able to download the decoded values. This did NOT fix the problem I am having with ODBC access, but I will simply change my process to use RETS Connector instead. Thanks again.

stan.longhofer's avatar stan.longhofer (2016-07-13 06:33:46 -0500) edit

Glad to hear you are back working now.

bwolven's avatar bwolven (2016-07-13 08:29:25 -0500) edit

Good Morning. Hate to say it, but the issue has come back: Error detected: server failed to send data at offset 50001 RETS Status code = 20203: Undecoded values were sent: Miscellaneous Search Error. Lookup: value Prairie Hi not found in Lookup table Subd_Lkp_1 for Resource 1. [LM_Char10_10]

stan.longhofer's avatar stan.longhofer (2016-08-01 08:55:01 -0500) edit

I notified the SSM about the need for a refresh.

bwolven's avatar bwolven (2016-08-01 13:37:17 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer