dhasler's profile - activity

Our feed for the Southern Oklahoma MLS has been throwing a 404 error since the morning of the 28th.

URL: http://ardmoreoke.rets.paragonrels.co... USER: 1000

Ah, thank you. We must have missed that notification from the MLS.

Southern Oklahoma RETS - 404 Error Our feed for the Southern Oklahoma MLS has been throwing a 404 error since the mornin

Confirmed that we are now getting valid listing counts. Thank you, appreciate the quick fix!

Our feed for Ulster MLS in New York is showing 0 listings. This looks to have started on 12/11 around 11am PST.

Would you be able to check and see why we're not receiving any data?

URL: http://ulster.rets.paragonrels.com/re... USER: pagek

Ulster Feed Showing 0 Listings Our feed for Ulster MLS in New York is showing 0 listings. This looks to have started on

We are seeing some extremely slow photo imports across a number of our Paragon feeds.

For example, we are importing photos for a new feed, Tuolumne County MLS, and the photo import is taking almost 10 minutes to download photos for 5 listings. This is from our log:

2020-06-18 10:21:29 : Added Obect: 20190010 2020-06-18 10:21:29 : Added Obect: 20200368 2020-06-18 10:21:29 : Added Obect: 20200282 2020-06-18 10:21:29 : Added Obect: 20191982 2020-06-18 10:21:29 : Added Obect: 20200748

Those photo sets took until 10:29:10 to import.

URL: http://tcar.rets.paragonrels.com/rets...

User: RelianceNetwork

We are also seeing some significant slowing on our Illinois Alliance feed:

URL: https://RMLSA-rets.paragonrels.com/re...

USER: PARELIANCE NETWORK

Protocol Relative URLs were not being read correctly. Adding HTTP: resolves successfully.

That looks to be the issue. I've updated all of our Paragon feeds to utilize SetLocation=1, added logic for the Protocol

Ah, that may be what's tripping us up. Let me do some testing and verify that's the issue.

Sorry, I was on vacation. Can you confirm that SetLocation=1 should be working for both Tuolumne and Alliance MLS? I wil

Via a GETOBJECT request. The Tuolumne feed is erroring when attempting to SetLocation=1, so we assumed they only provi

We're also seeing a large number of photo errors in our RealSource feed: URL: http://mimls.rets.paragonrels.com/rets/fn

Slow Photo Imports We are seeing some extremely slow photo imports across a number of our Paragon feeds. For example,

We are seeing the same thing here. Any information would be appreciated.

Confirmed. Thank you!

Our RETS feed for the Upper Peninsula MLS in Michigan is currently showing 0 listings present. Sending the query (L_StatusCatID=|1) returns 0 results.

This looks to have begun the morning of 4/20. Would it be possible to see what the issue is?

URL: http://upaor.rets.paragonrels.com/ret... USER: Reliance

Looks like whatever the cause was has been resolved. We are now getting listings returned.

Upper Peninsula MLS - No Listings in Feed Our RETS feed for the Upper Peninsula MLS in Michigan is currently showing 0

I can confirm our feeds are now working as expected. Thank you for you help!

That would certainly explain it. We'll start working on that. Thank you for the update!

We are getting a 404 error when attempting to access the Dawson MLS feed. This began sometime between 2-4pm PST yesterday.

URL: http://dawson.rets.paragonrels.com/re...

USER: REMAXGothenburgNE

We are also seeing this in our North Alabama, Little Rock, Northern Nevada, and Idaho Intermountain feeds.

Dawson MLS - 404 Error We are getting a 404 error when attempting to access the Dawson MLS feed. This began sometime bet

Confirmed. Thanks for the help!

Beginning yesterday sometime between 1pm and 2pm, we began getting an error when querying the RN_6 class in the Illinois Alliance feed.

Using libRETS, any query against that class returns: 'Missing close parenthesis on subquery'

I believe the Egyptian board was merged into Alliance yesterday, and I'm wondering if something got set incorrectly.

URL: https://RMLSA-rets.paragonrels.com/re... USER: PARELIANCE NETWORK

Alliance Feed Error Beginning yesterday sometime between 1pm and 2pm, we began getting an error when querying the RN_6 c

I think we're good. All 100+ feeds have updated successfully. Still scratching my head as to the sudden cause, but oh we