First time here? Check out the FAQ!
0

Getting Errors on pulling data with RETS connector, City and Township fields are failing

  • retag add tags

Error being generated:

Server: http://saam.rets.fnismls.com/rets/fni... User name: BachandRealtyRETS Full pull Local time: 8/25/2016 8:11:59 AM Server time: Thu, 25 Aug 2016 13:11:58 GMT

Running step "Superior Land"

Data file: C:\WINDOWS\system32\GOODRETS\WIMLSLAND.txt Search query: (L_Area=|1,2,3,4,5,6,26,27,28,29,30,31,33,34,35,36,37,38,39,40,41,42,43,48,55,63,68,70,73,75,78,79,80,81,82,83,84,85,89,90),(L_StatusCatID=|1,3) 728 records downloaded Error detected: server failed to send data at offset 701 RETS Status code = 20203: Undecoded values were sent: Miscellaneous Search Error. Lookup: value Courderay not found in Lookup table City_Lkp_2 for Resource 1. [L_City] Miscellaneous Search Error. Lookup: value Other not found in Lookup table Twnshp_Lkp_2 for Resource 1. [LM_char10_53]


Tried refreshing metadata and nothing changed. If I remove these fields from the data pull it completes successfully however these fields are needed for our application. What can I do to fix these errors. Also it has been working for months without an issue, why would everything change?

bachandrealty's avatar
bachandrealty
asked 2016-08-25 08:09:11 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

2 Answers

0

Ok, I have refreshed the metadata on my end several times to date and I am still getting the exact same error. Is there something I should be doing on my end differently or how long will a process like this take normally?

bachandrealty's avatar
bachandrealty
answered 2016-08-29 08:12:01 -0500
edit flag offensive 0 remove flag delete link

Comments

Based on the timing of this response, I think you were ahead of the refresh, so you were experiencing the same error. Have you been able to pull data recently?

vendorsupport's avatar vendorsupport (2016-09-16 11:33:30 -0500) edit
add a comment see more comments
0

I have notified the SSM of the need for a RETS metadata refresh.

Update: 2016-08-30 17:00 CST - The RETS metadata refresh has been completed so lookup metadata should be correct now. Thank you for your patience.

bwolven's avatar
bwolven
answered 2016-08-25 16:18:20 -0500, updated 2016-08-31 10:08:36 -0500
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments

Your Answer

Login/Signup to Answer