Open Rails Update failed

[cn bala]

Got the message that the update can't be done because of an error. Anyway here is what I see from the monitor screen below:

OpenRails

The update check failed due to an error.

System.Net.WebException: The remote name could not be resolved. 'openrails.org' at System.Net.WebClient.DownloadDataInternal(Uri addres.WebRequest&request)
at System.Net.WebClient.DownloadStrings (Uri address)
atORTS.Updater.UpdateManager. Check() in
E:\Documents\Coding\Jenkins\jobs\Open Rails Stable\workspace\Source\ORTS.Updater\UpdateManager .cs:line175

Now I don't have E drive and right now the program of Open Rails is in J drive. Am I suppose to change the drive letter from E: to J:?
If yes, then where do I look for this in the program of Open Rails?

Forgot to add the version of Open Rails and mine is 1.3.1.4328.

John

[slipperman]

NO, John, don't change your system!! That line refers to the system the update (at Open Rails) is running on.

It might be a problem with your internet service. Try again, and if it still doesn't work, go to http://openrails.org/download/program/ and download the latest Testing version (X4332).

Cheers,
Ged

[cn bala]

Thank you to Ged for quick reply and just download the latest Testing version (X4332) and see what happen with this after installed.

John

[cn bala]

Still the same problem as no one from Open Rails development team is helping to see what is the problem with this update check? Over at other forums there are more than 25 members read but not offer help with this. Surprised to see this.

John

[MsSheare]

Mine just updated as well and now I have the same issue. did what was suggested here and it now says Update check failed.

[cn bala]

I was hoping one of the member's name, baldwin will give us something to say about update check failed.

John

[geepster775]

Its not uncommon for the updater to bork once in awhile, requiring some basic troubleshooting skills to overcome. Whenever it happens, I simply delete the OpenRails_Testing folder (the application files) and replace it with the fresh current X version download. I do pull out and save the Documentation subfolder prior to deleting the old, and then transplanting that into the fresh copy in order to keep the current version of manuals.

I also make it a habit of cleaning out the cache at least once or twice a year

Go to {Systemdrive}/Users/{Username}/AppData/Roaming/OpenRails/ and delete everything
Go to {Systemdrive}/Users/{Username}/AppData/Roaming/OpenRails/Loadcache and delete everything.

If you have the updater set to Testing, it is going to check once a week. If there is trouble or your internet is down/offline when it checks, it comes back with the UPDATE CHECK FAILED message. It keeps that message until it does the next scheduled check time or you force it to check again by clicking in the options page and then closing it by clicking on okay.

You can also temporarily set the updater to Unstable and have the updater check basically on demand and update via the updater to the current X version, again triggered by cycling through the Options/Okay buttons.

[bwbrgb]

Whenever I get the " Update Check Failed " message I go to OPTIONS and turn off " Updates " . Say OK - get out of options , then go back in and turn on your Update Option of choice - then OK and It has always worked for me .
I use Win 10 and also Win 7 .

[cn bala]

Thank you for the trick but what will happen with this next time again with " Update Check Failed " I was expecting the developmental team of Open Rails should look into this to see why this is happening to this problem?

Thank you,

John

[Komachi]

Eh this has been going on long as I can remember with ORTS. Not something I think that *can* be fixed, best solution truthfully is to just update manually every time.

[mikeebb]

For those who need a reminder (or haven't been told before), a good place to get manual updates is: https://james-ross.co.uk/projects/or/builds

Those are the unstable builds. Look for one issued on a Monday - that's probably the weekly Testing build. Download the zip. Unzip it into your Open Rails program folder replacing whatever's there with the same name. Doesn't update the version number that Windows thinks it is (in the Apps settings) but that doesn't really matter.

When I have problems with the normal Updater, I usually just pull the latest Monday or Tuesday (if no Monday) build from that site and replace the OR program folder contents with it. End of problem. The following week, the updater usually works fine.

Final point: it's not necessary to accept the update every week. It'll continue to be offered, but if what you have is working OK (and especially if you're in the middle of a run or activity) it's often best to stay with the build you're currently using. Saves don't always work in updated builds.

[MsSheare]

Thank you Geepster! that fixed my problem right off and it updated with NO issues.

[bwbrgb]

John !
It doesn't happen on my PC very often - maybe half a dozen times a year . To me it's not a big problem . There are many other ways but this one is the quickest and works for me .