We have 3 floating studio licenses and 8 floating runtime licenses. We have tests that run on multiple VMs, including some that are just standalone executables that have been copied to the VM. We had to move our license server to a different server and now the standalone executables fail with a message that they can't find the old license server.
How do we make the standalone scripts use the new license server? We tried recompiling in studio on a machine using the new license server and moving the new executable to the remote VM, but it still says it's looking for the old license server. We don't see any way to change the license server the scripts are looking for.
Moved Ranorex liecense server - standalone executables no longer run
-
- Posts: 27
- Joined: Tue Jun 07, 2016 9:59 pm
Re: Moved Ranorex liecense server - standalone executables no longer run
Hi,
At first, are you sure the new license server is on the same network as the VMs with installed Ranorex? This is a must! Have you tried to ping individual VMs from the license server machine?
Also, make sure that the license server does have open port 7266 TCP/UDP.
And finally, make sure the license server version match your purchased/installed Ranorex version.
At first, are you sure the new license server is on the same network as the VMs with installed Ranorex? This is a must! Have you tried to ping individual VMs from the license server machine?
Also, make sure that the license server does have open port 7266 TCP/UDP.
And finally, make sure the license server version match your purchased/installed Ranorex version.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
-
- Posts: 27
- Joined: Tue Jun 07, 2016 9:59 pm
Re: Moved Ranorex liecense server - standalone executables no longer run
Thanks for your reply. Yes, all of those conditions were met.
We ended up installing the Ranorex License Manager on the VM, which gave us the ability to choose the new license server.
And just in case someone else moves their license server and comes here for answers:
We also ran into a problem where one of our solutions kept looking for the old license server, even after recompiling with Studio that was pointing at the right server. Turned out there was file in the release directory called RanorexLicenseManager.LIC that was pointing to the old server. We were able to just delete that file and then the solution started using the new server (editing the .LIC file also worked). Must be some legacy file from an older version of Ranorex.
All our issues from moving our license server have been resolved.
We ended up installing the Ranorex License Manager on the VM, which gave us the ability to choose the new license server.
And just in case someone else moves their license server and comes here for answers:
We also ran into a problem where one of our solutions kept looking for the old license server, even after recompiling with Studio that was pointing at the right server. Turned out there was file in the release directory called RanorexLicenseManager.LIC that was pointing to the old server. We were able to just delete that file and then the solution started using the new server (editing the .LIC file also worked). Must be some legacy file from an older version of Ranorex.
All our issues from moving our license server have been resolved.