Pace and Cap - Sartin Methodology & The Match Up - View Single Post - RDSS non-responsive workaround

Ted Craven · 07-25-2020, 02:32 PM

This post is a 'landing zone' where I can refer folks (e.g. by email) to the workaround solution to the recently occurring 'non-responsive' issue.

The Workaround:

(Note: you must be using the current version of RDSS: V2.1.049.11. If you are using an earlier version, you should update now to the current version (click the RDSS Icon upper-right corner of the website. This workaround does not work on earlier versions).

IF you are experiencing RDSS to be running very slowly, or if the 'spinning wheel' or Windows 'non-responsive' message appears -- THEN every time you start RDSS please re-register it by going the Registration Tab and click the Update Registration Info button. Then - DO NOT EXIT RDSS, rather just continue straightaway with your handicapping, or downloading/converting Tasks then assembling new race cards.

If you close RDSS or if crashes for some reason, when you restart RDSS, you must again re-register RDSS as described above, before starting your handicapping - otherwise you will continue to experience the 'non-responsive' slow-down problem.

According to the posts above in this Thread, and in my own experience and in numerous email correspondence, this solution almost always works. If not for you - after carefully checking you have followed the above advice - please contact me and I will do my best to help you.

As discussed earlier in this Thread, this problem occurs when RDSS attempts to contact a TwinSpires server periodically to fetch Scratch and other Race Change info, but new recent behaviour from that server is that the request is never fulfilled and RDSS stalls while waiting for the response until a timeout. For some (as yet unknown

) reason, re-registering RDSS first (each session) resolves this problem.

This will require a software update to fully resolve, which I am working on as fast as I can. I will inform everybody when that update is available.

-------
Updated -- October 6, 2020

In the past few weeks, RDSS access to live tote data, scratches and TwinSpires figures ProfitLine and BRIS Prime Power - has stopped because TwinSpires modified its website without notice. Not only RDSS but other software accessing these data have been affected.

There is more discussion about this latest issue further along in this Thread.

I have managed to resolve all these stability issues (and more) in a significant update planned for RDSS before the end of October. I will advise all RDSS users by email and also here on the PaceandCap website about the update.

Thank you all for your understanding!

-------
Updated -- October 27, 2020

All these issues have been fixed and will be available in the update available by October 31, 2020 or earlier. Please check this thread for progress: http://paceandcap.com/forums/showthr...ewpost&t=13314

Ted

07-25-2020, 02:32 PM	#71
Ted Craven Grade 1 Join Date: Jun 2005 Location: Nanaimo, British Columbia, Canada Posts: 9,241	Recap of 'non-responsive' workaround & TwinSpires data outage This post is a 'landing zone' where I can refer folks (e.g. by email) to the workaround solution to the recently occurring 'non-responsive' issue. The Workaround: (Note: you must be using the current version of RDSS: V2.1.049.11. If you are using an earlier version, you should update now to the current version (click the RDSS Icon upper-right corner of the website. This workaround does not work on earlier versions). IF you are experiencing RDSS to be running very slowly, or if the 'spinning wheel' or Windows 'non-responsive' message appears -- THEN every time you start RDSS please re-register it by going the Registration Tab and click the Update Registration Info button. Then - DO NOT EXIT RDSS, rather just continue straightaway with your handicapping, or downloading/converting Tasks then assembling new race cards. If you close RDSS or if crashes for some reason, when you restart RDSS, you must again re-register RDSS as described above, before starting your handicapping - otherwise you will continue to experience the 'non-responsive' slow-down problem. According to the posts above in this Thread, and in my own experience and in numerous email correspondence, this solution almost always works. If not for you - after carefully checking you have followed the above advice - please contact me and I will do my best to help you. As discussed earlier in this Thread, this problem occurs when RDSS attempts to contact a TwinSpires server periodically to fetch Scratch and other Race Change info, but new recent behaviour from that server is that the request is never fulfilled and RDSS stalls while waiting for the response until a timeout. For some (as yet unknown ) reason, re-registering RDSS first (each session) resolves this problem. This will require a software update to fully resolve, which I am working on as fast as I can. I will inform everybody when that update is available. ------- Updated -- October 6, 2020 In the past few weeks, RDSS access to live tote data, scratches and TwinSpires figures ProfitLine and BRIS Prime Power - has stopped because TwinSpires modified its website without notice. Not only RDSS but other software accessing these data have been affected. There is more discussion about this latest issue further along in this Thread. I have managed to resolve all these stability issues (and more) in a significant update planned for RDSS before the end of October. I will advise all RDSS users by email and also here on the PaceandCap website about the update. Thank you all for your understanding! ------- Updated -- October 27, 2020 All these issues have been fixed and will be available in the update available by October 31, 2020 or earlier. Please check this thread for progress: http://paceandcap.com/forums/showthr...ewpost&t=13314 Ted __________________ RDSS - Racing Decision Support System™ Last edited by Ted Craven; 10-27-2020 at 10:04 AM.