System Error 85 has occurred.

Question

Ranger Logon Failure - unable to map default open/save drive (error 85).

Symptoms

N/A

N/A

Cause

N/A

Resolution

N/A

Instructions

In order for Ranger to successfully logon a restricted user to the network a logical drive must be mapped to the users default open / save path. This logical drive (typically h:) allows Ranger to redirect the open / save dialogs to this location ensuring that restricted users are shown a secure drive instead of the local drive and to help with file management by consistently redirected the user to their personal my documents when they open or save work files.

If during the logon process this logical drive cannot be mapped (either by Ranger or by a logon script) then the following error message will appear.

The most common reason for this error is if the drive letter is already in use by another device i.e. a physical drive is using the drive letter or a temporary device (USB Memory Stick) has been added and this has been assigned the drive letter.

To check if this is the case a number of tests can be done;

1. Logon locally as administrator and see if another physical device is using the drive for example a CD-ROM, DVD etc.
2. Use Ranger Administrator to relax the drive security on the group you are testing with (Security Settings), login as a user within the group and then look at the drives that are listed in my computer and see if and where the default drive letter is connected to. You may find that the drive is already mapped to a different share if a persistent drive was created mapped previously.
3. Check that you are not trying to map the drive path twice in your logon scripts. Add a 'pause' statement into the bottom of your users logon script and next time you login look for the following error 'System Error 85 has occurred, the local device name is already in use' if this is present then then you are probably trying to remap the drive for a second time. Try removing this drive mapping in the script by disabling the line (rem) and then try again.

Testing

Logon and test again