MAC Issue - Drive not accessible after OS Update

MAC Issue - Drive not accessible after OS Update

Specific to Mac users: If you are having issues accessing drive locations through FOS after the OS update, or getting the below error, you will need to grant Citrix Viewer access to files and folders.

Error:
Desktop is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

A device attached to the system is not functioning.

Solution:
1. Navigate to System Preferences
2. Security & Privacy
3. Files and Folders
4. Enable all options under Citrix Viewer

    • Related Articles

    • Granting Citrix Access to Local Drives on a MAC

      The steps below will allow the user to adjust the access to their local drives on a MAC computer, via Citrix. 1. In the Citrix Receiver, select Preferences 2. Then select "File Access" 3. Adjust the access level as desired for the level of access ...

    • Document Drive Mapping

      When using mapped drives to access FOS and it's associated files changes to the server may be required for viewing documents in mobile or submitting documents from Mobile. If the images are mapped to a server name, the account the fosmobilehost ...

    • Granting Citrix Access to Local Drives

      Right-click on the Citrix Workspace icon on the tool bar of your computer and choose Connection Center. *If you do not see the icon, you may need to click on the up carrot to display the additional programs that are running, but are not being ...

    • RESOLVED - Access violation when running personnel report

      As of January 2026, this issue is resolved. If a user tries to run a personnel report, from the personnel module, on either an individual crewmember or multiple selected crews, they may encounter the below access violation error. The solution for ...

    • Error: Access violation at address 50034A17 in module ‘BORLNDMM.DLL’. Write of address 00000000.

      Error: Access violation at address 50034A17 in module ‘BORLNDMM . DLL’. Write of address 00000000. Solution: To resolve this issue, clear the user's temporary files.