TMR17 is dead for good. For all.

cressjl

Member
I attempted to download TMR17 from my page, since I purchased it. TMR17 installed correctly, but would not start. Instead, it persisted in presenting an error message claiming that I was not authorized to use the software that I had clearly purchased! I generated a trouble ticket, but this is the response I received:
Unfortunately due to the expiry of the security certificate used by Trainz Model Railroad 2017, and some older builds of Trainz: A New Era, these editions are not currently able to authenticate with our servers. Due to the age of this version of Trainz, we unfortunately no longer support this version, and as such no updates are planned for this version.

The expiry of security certificates is a requirement of all secure internet connections, such as those used for login services, and for authentication with our website.
Really? So, now we purchase a standalone program that should, like TS12, run until the day the last computer running a compatible operating system dies, won't work because of Microsoft certificates?

How many other programs, such as TRS22 PE, will soon die and no longer run because we cannot connect to the online server and get our pat on the back to run the software we paid good money for?

IS THERE ANYONE OUT THERE actually running TMR17 successfully? (BTW: I was only trying to validate the Japan Model Railroad that won't work under Trainz Plus.)
 
Doesn't take much of a search to find the fix. Yes, my TMR17 works fine.
 
Doesn't take much of a search to find the fix. Yes, my TMR17 works fine.
Thanks for providing this help, but this is perplexing. I must not have searched too well, because I did not see the tutorial that you referenced. I will check it out more thoroughly.

But why would the response to the trouble ticket be such as it is? Should they not also point users to this tutorial, if this is the case?

Thanks for the help.
 
Last edited:
But why would the response to the trouble ticket be such as it is? Should they not also point users to this tutorial, if this is the case?

Thanks for the help.
N3V stated their policy as it applies to versions that have reached end of life. They did that as well when it first happened. But the last sentence provides the answer and there were enough users that knew what it meant to figure out that using the newer certificates from newer versions would solve the problem. It is safe to assume that the lawyers insist that end of life status be maintained and therefore N3V didn't point to the thread with the fix as that might be seen as supporting a product that had reached end of life. Lawyers:mad:
 
Last edited:
N3V stated their policy as it applies to versions that have reached end of life. They did that as well when it first happened. But the last sentence provides the answer and there were enough users that knew what it meant to figure out that using the newer certificates from newer versions would solve the problem. It is safe to assume that the lawyers insist that end of life status be maintained and therefore N3V didn't point to the thread with the fix as that be seen as supporting a product that had reached end of life. Lawyers:mad:
Perhaps when a product has reached end of life N3V could remove the authentication to enable the continued use of a paid for product.
 
The certificates are not for authentication, they are for verification for site security. TMR2017 just happened to be caught in the time period when security standards were changing, rendering them no longer valid for verification. A lot of sites that use security (https instead of http requires certs) had to make the change to more secure certificates at the time, but N3V chose not to change those for this product, per what WReeder said above. Most of us would not have called that product support, just site security updates, hence the comment about lawyers. At any rate, the fix is pretty easy, just copy the newer certs into the TMR folder in the correct place.
 
The certificates are not for authentication, they are for verification for site security. TMR2017 just happened to be caught in the time period when security standards were changing, rendering them no longer valid for verification. A lot of sites that use security (https instead of http requires certs) had to make the change to more secure certificates at the time, but N3V chose not to change those for this product, per what WReeder said above. Most of us would not have called that product support, just site security updates, hence the comment about lawyers. At any rate, the fix is pretty easy, just copy the newer certs into the TMR folder in the correct place.
100% correct. Removing the authentication would allow bad guys to fake DNS of the authentication server and partially defeat the phone home feature of the software.
 
According to the support reply authentication is the problem and the failure is caused by the certificates. Sure the solution is easy if you have a subsequent N3V product, but if you don't?
This is on the Trainz Life Cycle policy page of the wiki.
Q: Will the named products continue to operate after the listed end-of-support date?

A:
We will do nothing specific to prevent the products from operating. However, if they were to stop working for some reason (for example, they were found to be incompatible with the latest Windows Operating System) we would not take any steps to resolve the issue. Additionally, any product features which rely on server support (for example, in-game Download Station access or iTrainz) may cease functioning correctly.

This is one of the reasons to read and understand the MyTrainz Agreement that covers issues like this.

 
I understand completely. I don't have many pieces of software for that same reason. I was all set to buy Adobe's Photoshop Elements at Christmas until they unveiled the new life cycle policy. The software will work for 3 years from the time you first run it. It then won't start after that.
 
I appreciate all the outstanding discussion that you knowledgable folk have provided. I used to be a whole lot more active on the forums than I am now, but I may be coming back! Thanks for the help.
 
I understand completely. I don't have many pieces of software for that same reason. I was all set to buy Adobe's Photoshop Elements at Christmas until they unveiled the new life cycle policy. The software will work for 3 years from the time you first run it. It then won't start after that.

You'll own nothing and be happy :mad:
 
Back
Top