First time here? Check out the FAQ!

What does Unencoded Error indicate in a RETS Response?

I'm getting an error about Unencoded Error in a RETS Response? What does this mean, and how do I fix it?

vendorsupport's avatar
asked 2015-06-12 13:21:44 -0500
bwolven's avatar
updated 2015-12-08 16:39:03 -0500
edit flag offensive 0 remove flag close merge delete


add a comment see more comments

1 Answer


This generally means that there is a value in a record that doesn't have a corresponding description in the RETS Lookup metadata so it can't translate the value in the field to it's corresponding Long Value when data is returned in the decoded format.

Some of the possible reasons: * A lookup value was removed but it is still referenced in one of the records. * The static metadata is out of sync with Paragon lookup values and needs to be refreshed. The refresh would synchronize the lookups in paragon with the static metadata used by rets.

bwolven's avatar
answered 2015-06-12 17:02:58 -0500
edit flag offensive 0 remove flag delete link


We use the latest version of rets connector as our download tool. what we have tried is clearing the metadata cache, stopping the service and closing the application. removing the meta data file to force a download of the latest metadata. we get a new metadata file that still has the issue

SmarterAget's avatar SmarterAget (2015-06-18 10:41:24 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer