Page 1 of 1

Rx 6.1.0 "Error Writing License"

Posted: Thu Oct 06, 2016 11:54 am
by agr
We recently updated to Ranorex 6.1.0 from 5.4.6.
We have two floating licenses and a license server.

The upgrade went smoothly and the licenses are active. However, when I click on the license info on the startup screen, I get the following error:

"Error Writing License
An error (Access to the path 'C:\ProgramData\Ranorex3_Server.lic' is denied.) occured while writing the License Manager information to file 'C:\ProgramData\Ranorex3_Server.lic'.
Ensure you have sufficient privileges to write to the license file."

Is this a known error? The file itself exists, I can access it with my windows user (local admin rights). I'm running Windows 10 v1511. the behaviour is the same with Win 8.1 and win7 64bit.

Best Regards,
Andreas

Re: Rx 6.1.0 "Error Writing License"

Posted: Tue Oct 11, 2016 11:52 am
by Support Team
Hello Andreas,

This is no known issue in Ranorex. It seems you have no privileges to write into a file, which is located within the "C:\ProgramData" directory. Please try to start Ranorex as administrator and check if the issue still persists.

If this also doesn't help please try to open the Ranorex3_Server.lic file in a text editor and try to modify and save it. You should get a similar error message. If that's the case please contact your system administrator in order to give Ranorex the permissions to edit this file.

Regards,
Bernhard

Re: Rx 6.1.0 "Error Writing License"

Posted: Thu Oct 13, 2016 12:18 pm
by agr
Hello Bernhard,
it works when I start Ranorex 6.1 as Administrator, so it's a permission problem. But shouldn't it work also when i start Ranorex without special rights, just by doubleclicking the icon?

Regards,
Andreas

Re: Rx 6.1.0 "Error Writing License"

Posted: Fri Oct 14, 2016 3:22 pm
by Support Team
Hi Andreas,

This highly depends on the permission restrictions in your company or the permission settings on your computer. I would recommend contacting your IT administrator if you still face that kind of issue.

Regards,
Bernhard