RailPro User Group

RailPro => RailPro Specific Help & Discussion => Topic started by: G8B4Life on September 15, 2017, 10:58:41 PM

Title: RailPro Assistant. Server issue or blocked?
Post by: G8B4Life on September 15, 2017, 10:58:41 PM
Got a new issue today. When I started RPA to check something I received the "Bad Email Address" error message. I've used the same email address and password in RPA ever since I signed up years ago and RPA shows the correct info in it's setup and still communicates to the server properly (I can see all the files available etc but of course downloading is not possible). Is anyone else having this issue or did I somehow "annoy" Ring sufficiently enough that I've been blocked?

- Tim
Title: Re: RailPro Assistant. Server issue or blocked?
Post by: nodcc4me on September 16, 2017, 08:06:13 AM
Tim, I just got the same message after installing your latest patched version on my XP netbook. I clicked "Exit" and the program opened normally. I know they have been working on the server intermittently.
Title: Re: RailPro Assistant. Server issue or blocked?
Post by: William Brillinger on September 16, 2017, 09:27:08 AM
I checked with Ting on this issue, he says "It is working now."
Title: Re: RailPro Assistant. Server issue or blocked?
Post by: G8B4Life on September 16, 2017, 09:58:00 AM
Thanks Bill (and Al).

Indeed it is working correctly now. For quite a few hours there I was wondering if I had done something to get myself blocked, given that the server was working but not accepting me as a user.

You must have a good business relationship to be able to contact RE on a weekend. Mind you, I somehow keep thinking it's Sunday there too when it's still only Saturday (insert face palm emoticon here!)

- Tim
Title: Re: RailPro Assistant. Server issue or blocked?
Post by: William Brillinger on September 16, 2017, 10:02:29 AM
Tim Ring has been burning the Midnight Oil (or at least, the Saturday Oil) to get the new releases out for a few weeks now.

I think release of the new features is imminent.

I think your issue was due to updates to the server in preparation for the new releases.