License Server 17 install error

[asteroza]

Hi folks, I got roped into a repair situation that looks kinda ugly.


An ancient windows 2003 server apparently had CoCreate License Server 17 installed that was somehow licensing OSD 15.5 on windows 10 PC's. That server died, and the hard disk looks damaged so I don't hold out hope of recovering anything useful. The lucky part was that the license was an MSU serial dongle and I have the settings file for MEls.


So I thought it would be simple enough to slap the yellow Rainbow serial dongle on a different server (windows 2022) and fire up the license server installer from the old CD on a newer server, but the installer dies at the LicenseConfiguration.exe stage. Event viewer says AppCrash without much detail. Tried compatibility modes down to XPSP2 but that didn't help. Installed all the old Visual C++ runtimes just to be sure but no progress. Used Uniextract2 to forcibly extract the installer contents, and there is a LicenseConfiguration.exe there, and tried simply running that in various compatibility modes but it just stops, same AppCrash error logged.


I noticed in a previous thread that there was that security vulnerability notice recently that appears to cover this license server version, which would suggest a newer installer might be available, which might fix installation issues. I got told we weren't on current support, and hadn't been for a long time, so I have no means to download a newer license server installer though.


What even is the correct license server for windows 2022 to be able use an ancient MSU dongle license for OSD 15.5? Do I need some Sentinel HL or HASP driver from Thales as well to properly access the Rainbow dongle?


Am I doomed to have to make a Windows 2003 VM just for this license server, and would that even work?

[Wolfgang]

I guess you do partially refer to https://cocreateusers.org/forum/showthread.php?p=26351 .

try to contact support, may be in addition using the PTC forums at their website.


I think/assume/hope a world wide active company should support their (former) customers in any kind of "Critical Security Vulnerability" they have indirectly caused (or made possible). This should be possible regardless of the current business connection.

Keep in mind: you are still using a legal license to use your Modeling. Yes a rather old one, with rather old version, but still legal IMHO. They should offer the 'fixed Critical Security -issue-version' of MELS to every one!

I keep my fingers crossed.

--------------

you said that it crashes at 'LicenseConfiguration.exe'. I read: service installation is fine, config failed. If I remember right the name of the license server file is the only thing written into the registry.

Does your MELS V17 on the windows 2022 system run at all? do you have access to the http://servername:17171 pages? (even when those do not show any active/valid licence?)