I am switching from Windows to MAC/Parallels and wanted to import my license file by downloading from my account.
The download works, but I am still in trial mode.
How can I continue to use my current version (10.0.0.1489)?
Hi,
the easiest way: launch C:\Program Files (x86)\RemObjects Software\Everwood\Bin\RemObjects.Everwood.LicenseManager.exe and do export/import
Hello Evgeny,
that’s one of the things I have tried, but it still shows trial mode.
Hi.
what product(s) are you using, and what version? Can you send me the .license file you are trying to import, so we can review it?
Hello Marc, I will send you the files by mail.
1 Like
I just bought a new license. When I now try to use it, I get a notice that my trial version has expired, and I should launch the license manager.
If I now download the license file using the license manager, I get a successful license download, and I can see the new license.
But restarting the service manager again I still get the message “Your Trial License has Expired”.
I uninstalled RemObjects again, deleted all directories that I could find, deleted all RemObjects entries in the registry, and reinstalled the just downloaded version again. I then downloaded the license using the license manager, but still no change.
Please advise how I can get the new version finally working.
Can you elaborate what you mean by “But restarting the service manager again”?
Does %APPDATA%\RemObjects Software\Licenses contain your new license file and only that one file? If you look inside the file, do the dates you see reflect your license dates?
Yes, there is only one file (ImportLicense0.license). The file contains all licenses I have ever bought. I also deleted this file and made a new download using the LicenseManager.
The license manager shows the following:
Here is part of the downloaded license file:
Where are we with this issue?
Somebody working on it?
The license itself looks fine. Can you show us exactly what is failing/ what does
“But restarting the service manager again”?
mean? what service manager? Can you post a screenshot of the error you get/of where it shows trial mode?
Hello Marc, here’s what I am doing:
Launch Service Builder:
Click on “Launch LicenseManager”, it is showing all my licenses:
Close the LicenseManager and return to the Service Builder screen, still shows “expired”:
Click on “Cancel” to close the Service Builder, and start it again - same screen:
Next, close Service Builder, and delete the license file.
Then restart Service Builder - again “expired”. From the “expired” window, click on “Launch LicenseManager”, this time (after deleting the license file), it shows an empty screen:
Click on “Download Licenses” in the menu bar:
Click on “Download License”:
Click “Ok”, the LicenseManager shows my licenses again:
Close LicenseManager, Service Builder still shows “expired”:
Click “Cancel”, relaunch the Service Builder, and I will get the “expired” screen again.
Hi,
what Remoting SDK version are you using? .1489?
can you send your .license file to support@, pls?
Sent!
Version is .1489.
1 Like
Hi George,
This seems to be an issue with the old version not properly handling the new license file. We don’t quite know whats happening yet, as this format ha snot changed.
While we sort this out, could I ask your to simply use the latest version f ServiceBuilder, 1605, instead of 1489?
Most likely tis will be the paper final solution as well since whatever the issue with 1489 is, we cannot go back and fix an old build, any fixes we do would be in a new build, anyways…
If for some reason you need to keep building against the 1489 version of the library (which I don’t recommend), you can make a copy of the Source and/or Dcu folder, before you install 1605, and then opt it back (or reference them from the copied location).
is this feasible?
thanx,
marc
Out of curiosity: do you still have your old OC around, and of so could you send me the Licenses folder that had the licenses that were working for you on that machine?
I’d love to compare, because we cannot find any relevant ant change to how we generate the license files that would explain why the new licenses fails on 1489 (but work in latest). The license generation literally hasn’t changed since 2016 or so…
Seeing the licenses that work for you would help us understand the issue (even though we probably cannot fix it.
Also, you could try copying those license file(s) from the old PC into the new system, and see if that saves the issue for you…
thanx!
Hello Marc,
as you suggested I uninstalled the 1489 version and installed the latest build.
The Service Builder is now starting without any issues.
I will check if the new version will have any impact on my application and will get back to you then.
But this will take a little bit of time…
Cool!
this would still be appreciated, if its no trouble, as im curious what the issue is…