Ranger Administrator in Read Only Mode

Question

Why does Ranger Administrator open in Read Only mode?

Symptoms

Unable to open Ranger Administrator in edit mode.

The process cannot access the file because it is being used by another process.

Click OK to load in read only mode, or Cancel to close.

Ranger Administrator may fail to open in edit mode for two reasons.

1. The program is already in use on another computer. You can verify this by browsing to the Ranger folder and looking for RAEdit.lck. If this file exists then Ranger Administrator is running on another computer - this can include a terminal services session.

2. The user has read-only permission on the Ranger folder and files. Therefore the user has insufficient access to make modifications to the Ranger configuration files.

Cause

In Ranger Administrator version 4 it was possible for changes made by one administrator to be overwritten by another administrator as multiple copies of Ranger Administrator could be open. To prevent this we developed a locking mechanism so only one copy could be opened in edit mode. Other copies of Ranger Administrator could be opened but in Read only mode.

In addition to ensuring only one copy of Ranger Administrator can be open at any one time users require full permission over the Ranger folder and files to open the program in edit mode. By default this would require the user to be a member of the domain admin group unless specific permission has been granted for the user or group.

Resolution

Ensure that no other copies of Ranger Administrator are open and that you are a member of the domain admin group.

Instructions

First check LAN Ranger applications to see if RangerAdmin.exe is loaded on any clients. If so close the program remotely. Next check the open file list through computer management and close any reference to serverrangerrangeradmin.exe

Next check the users group membership and then compare this to the Ranger folder to see if the user has full control over the folder and files.

If you have confirmed the user has sufficient permission and the error persists then check the Ranger folder for RAEdit.lck. If the file exists this confirms that the program is loaded elsewhere. The options are to continue investigating what could have this program open possibly though a remote session to the server alternatively it maybe easier - when appropriate - to reboot the server to ensure any lock on the program is removed.

Testing

Logon as a high level user, try RangerManager and then using the Ranger Toolbar launch Ranger Administrator.