Troubleshooting

Common Issues

“Connection timed out” or generally unable to connect

This is typically caused by a network issue or limitation preventing you from being able to connect to the RETS server.

Fix: If you’re behind a firewall or running Internet security software, ensure that you have the ability to establish an outbound connection on port 6103. If port 6103 is not blocked and you still receive this message, wait a few minutes and try again. If you continue to experience problems, contact rets-support@fbsdata.com with details of the issue (including your RETS username) for assistance.

 

Common RETS Errors

“Authentication Failure: Invalid login or password supplied”

This indicates that the login information you’re using to log into the RETS server is incorrect.

Fix: Examine your login credentials and ensure they match with the information provided to you. If problems persist, contact the MLS and/or person who set up your RETS account.

 

“IP address(123.123.123.123) is not listed in your list of valid IP addresses.”

This indicates that you’re trying to access the RETS server from an IP address that’s not been authorized by the MLS.

Fix: Connect to the RETS server from an authorized computer. If problems persist, contact the MLS and/or person who set up your RETS account.

 

“Specified Class (A) is not valid.”

This indicates that you’re trying to access information about Class “A” but that Class doesn’t exist.

Fix: Examine the Class you’ve selected to ensure it does exist. Also, be sure that you’ve selected the correct use of StandardNames. For example, if you’ve set StandardNames to true, “A” is no longer a valid Class. Instead, you’d need to use its StandardName, “ResidentialProperty”. If problems persist, contact rets-support@fbsdata.com with details of the issue (including your RETS username) for assistance.

 

“Your template does not have permission to search on Resource(Agent) – Class(Agent).”

This indicates that you’re trying to search the “Agent” Resource, “Agent” Class, but the MLS has disabled your access to this data type.

Fix: Remove the attempted download from your sequence or contact the MLS to inquire about your access to this data type.

 

“Invalid field (LIST_105) in select parameter.”

This indicates that you’ve instructed the RETS server to return back the values of the LIST_105 field but this field doesn’t exist.

Fix: Examine the fields you’ve instructed the RETS server to return to ensure they’re correct and exist. Also, be sure that you’ve selected the correct use of StandardNames. For example, if you’ve set StandardNames to true, “LIST_105” is no longer a valid field. Instead, you’d need to use its StandardName, “ListingID”. If problems persist, contact rets-support@fbsdata.com with details of the issue (including your RETS username) for assistance.

 

“Column(s) [field1,field2,field4] are not allowed by your template configuration.”

This indicates that you’ve instructed the RETS server to return back field1, field2 and field4, but the MLS has disabled your access to these fields.

Fix: Remove the fields indicated from the list of fields you’d like returned or contact the MLS to inquire about your access to these fields.

 

“Translator Exception: Missing close parenthesis on subquery.”

This indicates that the query you’re attempting either contains invalid characters, unmatched parentheses or is too complex.

Fix: Examine your query to determine proper DMQL usage. If problems still exist, contact rets-support@fbsdata.com with details of the issue (including your RETS username) for assistance.

 

“Offset exceeds available rows.”

This indicates that you Search request has a higher Offset value than the total number of available rows.

Fix: Adjust your Offset value so it doesn’t exceed the total number of records.

Comments on this entry are closed.