RX 6.2 "Error writing License File"

[Andymann]

Hello everybody, since this morning we are facing the same problem as describerd here: http://www.ranorex.com/forum/rx-6-1-0-e ... 10076.html

In short: We cannot run testcases. When I open the License-info as a non-administrative user I get a message saying "An error (Access to path 'C:\ProgramData\Ranorex3_Server.lic' is denied.) occurred while writing the License Manager Information to file 'C:\ProgramData\Ranorex3_Server.lic'. "

But other than described in the linked thread I do not think that it's a permission-related problem on first hand because the path is basically senseless:

1) The license file is located within the all-users-folder.
2) if anything should be written into programData than it would probably be ProgramData\Ranorex\...

we are facing this issue since this morning (monday). it seems like its occurrence is independent from user and computer (happens everywhere).

[odklizec]

Hi,

As mentioned in the above post, if Ranorex works fine in admin mode and does not work in non-admin mode, then it's most probably a permission issue. I would suggest to ask your system administrator about recent permission or group policy changes. Also, ask them about antivirus-related updates

[Andymann]

I will, but...

why should a program look at especially THAT location?
Up until friday it worked perfectly for non-admin users. If Non-Admin-Accounts need write permission into c:\programData i'd say it's quite big flaw

[Edit] Messed up ProgramData and ProgramFiles [/Edit]

[odklizec]

All I can say is that I don't have a problem with accessing the Ranorex license file both in admin and non-admin mode. So if you suddenly cannot access the file in ProgramData, it's most probably caused by changed company policy/permissions or antivirus? Have you asked your network/computer administrators about recent policy changes/updates?

[Andymann]

I can delete the File from "ProgramData" and recreate it with a non-admin-user by entering the necessary pieces of information for the license server. But then again, no other non-admin-user can access that file since the creator gets "change"-permission, everone else is just able to read. That's pretty normal business, I'd say.

I checked our Virusscanner: No signature-Update etc for the last ~2 weeks

[odklizec]

Unfortunately, I can't help you with this. As mentioned, if everything worked before and suddenly, out of the blue, it stopped working, there most probably changed something in your company group policies/permissions.

BTW, have you tried to add "Everyone" with full access rights to "Ranorex3_Server.lic" file Security permissions? But honestly, if I were you, I would first ask your system admins about recent permission changes

[Andymann]

Anyways...

I reinstalled Ranorex and things turned out to be a little better: I do not get an Error when I open the License-Dialog as a non-Admin-user [Edit] Now I get the ERror when trying to open it as an admin-user ....[/Edit]. It shows the correct info and everything is fine.

But when I want to start a testcase I am prompted with "The License manager coid not be connected". This doesn't happen as an admin

[Edit] So, are there any ideas what I might do in order to get it working after an uninstallation...installation? [/Edit]

[Vega]

Do you have a floating or a node locked license? I have to agree on this one, it sounds like permission and or policy issues. Have you talked to IT as Pavel suggested?

[Andymann]

We have floating licenses. Note: They run out in 04/2017 but are still marked green within Ranorex GUI.

I did some more testing yesterday and nailed it down to the following situation: I have multiple non-admin users. Some can execute testcases, some are prompted with the pink/purple dosbox claining "the license manager could not be contacted. Please check your network connection". Everything happens on the same terminalserver at the same time so it's probably not an issue of the installation or the license server.

Those users who cannot execute testcases just had their profile and home-drive (who knows..) completely whiped and are totally fresh users - just to make sure

Everything is tested with a new ranorex solution which has just been created in the user's context so it's not an issue of a messed up solution either.

to be honest, this starts becoming a little urgent for me. is there anything i can do/trace/provide to stop getting on everybody's nerves?

[Edit] Seems to be solved: As far as I can see there was an issue concerning the list-permissions for the underlying folder of the user's home drive (wtf?). So of course it was an individual permission problem as everybody stated. Nevertheless do I think it would be good to have some more possibilities for enumerating issues like these. After all the error that came up was very misleading [/Edit]