Fix: Office 2016 Grant Access Error on MacOS

A lot of MacOS users are receiving the Grant File Access error when trying to open various file types in Office 2016. The issue typically appears when trying to open Word files, but some users have also reported the issue with Excel and PowerPoint files.

When dealing with this issue, the user will be prompted with a popup asking to provide access privileges when opening a file with an Office 2016 program. If the user selects the file and clicks the Grant Access button, the following error will appear:

Word/Excel/PowerPoint cannot open the document: user does not have access privileges.

As it turns out, the Grant Access error is caused by the updated Apple sandboxing rules. Apple now uses sandboxing to limit various actions by tying them to a specific location. Application sandboxing is very effective in preventing viruses or other malware from affecting OS files. Following the new guidelines, every application that uses custom fonts must ensure that the fonts stay exclusive to that particular application. Apple no longer allows an application to install fonts for system-wide use.

In the event that a system-wide font gets altered along the way, it will be regarded as a security violation and will be replaced at the next update. Starting with Office 2016, Microsoft had to comply with Apple’s rules in order to be able to sell the Office suite in the App Store. Microsoft provides a set of fonts specifically for their software, which will get installed in a different location.

However, most third-party font utilities have not been fully updated to work with the new sandbox rules and will cause conflicts seen as security violations by MacOS. It has been confirmed that third-party font management apps like Suitcase, Linotype Font Explorer, Extense, or FontExplorer X are the main culprits causing the Grant Access error with the Office 2016 suite. As of now, FontBook is the only font management utility that is specifically designed to work with Apple’s new security system.

Note: Some users have reported that reducing the number of fonts in their third-party font management apps has made the issue disappear. If you have a lot of fonts (over 1000), try reducing their number. Then, restart your machine and try again.

Below are a suite of methods that will make the Grant Access error go away. If you have installed an external font management app (other than FontBook), but you don’t need it, follow Method 1 or Method 2. In the event that you’re relying on a third-party font management app, follow Method 3 or Method 4.

Update: We’ve added another method that will address the Grant Access error for users who are encountering the issue with macOS 10.13 High Sierra or above. If this is applicable, move directly to Method 5.

Method 1: Disable fonts from third-party font management apps

Since font management apps like FontExplorer X, Universal Type Server, Suitcase, or Extense are causing the Grant Access error, disabling the fonts in those applications will usually make the issue go away for good.

If you’re using Suitcase Fusion, you can solve this issue easily by clearing the font caches. To do this, open Suitcase Fusion and go to File > Clean Font Caches. Then, restart your system and the office files should open normally.

Note: This fix will only work temporarily. You might be required to repeat the procedure every once in a while.

If you’re using FontExplorer X, Universal Type Server or Extense, you have little choice but to open those applications and disable all fonts. Then, restart your device and try opening the files that were previously showing the error. If that isn’t enough, uninstall the external font management app and follow the instructions below:

  1. Access the Finder app, select Applications and double-click on FontBook.
  2. In FontBook, select All Fonts from the left pane. Then, select any font from the right pane and hold down Command + A to select them all.
  3. With all the fonts selected, access the Edit menu on the top of the window and click on Look for Enabled Duplicates.
  4. Click on Resolve Manually and wait for the list to populate. Shortly after that, you’ll see a window listing the fonts that were checked. Then, click the All header and switch it to Warnings and Errors.
  5. Open each font shown as duplicated. You should be able to view both versions. Choose the oldest font and hit Remove Checked. Do this with all the fonts that are duplicated.
    Note: The “Remove Checked” has been changed to “Resolve Checked” in the newer version and you must check the fonts that you want to keep, not the ones that you want to remove.
  6. Next, go to File and choose to Validate Fonts. Click the All header and change it to Warnings and Errors.
  7. If you encounter any errors (yellow or red), open each one and resolve any duplicate manually like we did in Step 5. Once you have covered each duplicate, click on Validate Fonts again and make sure no errors are shown.
  8. Close FontBook and open any application affected by the Grant Access error. If it’s still displaying the error, reboot and open again.

Method 2: Boot from recovery partition to reset folder permissions

If the method above has been unsuccessful in removing the Grant Access error, let’s try booting from recovery mode and using the Terminal utility to reset the folder permissions and ACLs. This method has proved to be successful for a lot of users that were still struggling with the error after removing the third-party font manager.

  1. Click the Apple icon in the top-left corner and select Restart. While your Mac is restarting, press and hold Command + R to enter Recovery mode.
  2. Once you see the OS X Utilities window, access the Utilities menu at the top of the screen and click on Terminal.
  3. In the Terminal window, type “resetpassword” and press Enter.
  4. Shortly after that, you’ll see the Reset Password window. Go down to Reset Home Folder Permissions and ACLs and click the Reset button.
  5. You might be prompted to insert your password. After you do so, the system will restart.
  6. Try opening the Office app that was previously acting up. It should open without the Grant Access error.
    Note: The issue will reappear if you decide to install and open a third-party font management app that doesn’t comply with Apple’s sandbox rules.

Method 3: Avoid Apple’s sandbox requirements

In previous Mac Office versions (older than Office 2016), users were able to save files in any location and use any font without warnings and permission requests. But this is no longer possible because of the new sandbox requirements. People that use VBA with Excel are severely affected since they are constantly prompted for permissions when running their scripts.

However, Mac has some locations that you can use to avoid those access prompts. These locations allow VBA enthusiasts to run their scripts freely without additional user interaction. Fortunately, we can also use these locations to bypass the grant access error. The trick is, this location is not easily available, so we’ll have to go through additional steps to make it more accessible.

One example of a safe location that avoids Office permission prompts is: /Users/*YourUsername*/Library/Group Containers/UBF8T346G9.Office

You can use this folder to share data between Office programs or with a third-party application since it has both read and write access. Here’s a quick guide on using this location to bypass the Grant Access error:
Note: This guide is only confirmed to work with Excel files, but should theoretically work with other file types from the Office 2016 suite.

  1. Open a Finder window and hold the Alt key while pressing the Go tab in the menu bar. Then, click on Library.
  2. Navigate to Group Containers and then double-click on the UBF8T346G9.Office folder.
  3. Create a new folder inside the UBF8T346G9.Office folder and name it however you want.
  4. Next, move all the Office-related files that are refusing to open in this secure folder. They should all open without issues.

Note: For easy access, you can select the folder and press Command + Ctrl + T to automatically add it to Favorites in Finder.

Method 4: Pull Microsoft fonts from the resource folder (Temporary)

If your work revolves around using an external font management app, then removing it from your system is not an option. Fortunately, some users have been able to make the grant permissions issue go away by removing Microsoft’s fonts from the resource folder. However, this fix will only be temporary. When you allow the next Office update, the fonts will get reinstalled in the package and the error will come back.

Warning: Some users have reported Word crashes after following this method. If you don’t back up the fonts as we’ll do in the steps below, you’ll need to reinstall/repair the Office suite if anything goes wrong.

  1. Access the Finder app and select Applications. Then, right-click on the Office application that is displaying the Grant access error and click on Show Package Contents. In this case, it’s Word, but you can also do it with Excel, PowerPoint, or another Microsoft Office app.
  2. Go to Contents > Resources and locate the Fonts folder. You might see it as Fonts or DFonts. Double-click on it to open.
  3. Next, create a folder on your desktop. We’ll use it to safeguard the MS fonts, so we can restore them if this method fails. Use Command + A to select all fonts from Dfonts and move them to the folder you previously created.
  4. After you have successfully copied the fonts to the new folder, right-click one of the fonts in Dfonts and click Move to Trash.
  5. Once the Dfonts folder is empty, open the Office application that was displaying the Grant access error. It should open normally now.Note: If you’re still seeing the error, or Word crashes during startup, return to Contents > Resources > DFonts(Fonts) and re-add the fonts from the folder we previously created.

Method 5: Clear the Mac OS Font Caches via Terminal 

Some affected users that have been encountering this issue with macOS 10.13 High Sierra or above have reported that the issue has been resolved after they cleaned the font caches by using the Terminal. After doing this and restarting their Mac, most affected users have reported that the Grant access error has stopped occurring.

  1. Close all applications that are currently opened. To do this, press Command + Option + Escape to open the Force Quit Application window. Then, select each opened app and click on the Force Quit button.
    Force Quit all opened apps

    Note: This step is very important. Failing to do so will result in an error if an application that is using the font caches is currently opened.

  2. Once every application is closed, press Command + Shift + U to open the Utility folder and click on Terminal to start it.
    Accessing the Terminal via Utility folder
  3. Type the following command and press Return to run it:
    sudo atsutil databases -remove
  4. You will be asked to provide your account password at the prompt. Do so and press Return once again to grant the necessary permissions.
  5. When the process is complete, type exit to end your command line session, then go to File > Quit to exit the Terminal app.
  6. Restart your Macintosh and the issue should be resolved at the next system startup.
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

32
    MA
    mattj7 Aug 14, 2018

    Hi there, I am desperately trying to fix this problem. I have a client who has excel spreadsheets linking to 1000’s of files, so granting access for each one is a massive blow to usability.

    I tried method 1 and 4 with no success, 3 is not an option, as they’d have to move the data locally.

    On method 2, after booting into recovery and running ‘reset password’ from terminal, I only get a prompt to select the user, then to reset the password, there is no “reset home folder permissions and ACLs” option visible (see below pictures). I also tried the ‘first aid’ option for the disk and volume through disk utility while in recovery. Am I missing something? I’m on macOS High Sierra 10.13.4

    Thanks in advance for any help

    https://imgur.com/a/XN2SEP6

    RL
    Raymond M. Lacroix May 2, 2019

    Step 2 worked beautifully. Merci

    CH
    Chelsea Harris May 8, 2019

    THANKYOU!! You are amazing for helping me. That has driven me nuts all day. Cheers.

    Mélodie May 13, 2019

    Step 5 = AMAZING!
    Thank you so much!

    PL
    panama libre May 30, 2019

    Thank you very much!! Step 5 solved it!! Great!! I had all my work frozen…. you saved me!!

    RS
    Roland Siregar May 31, 2019

    Method 1 worked for me. Thank you so much.

    NL
    Nick Lamb Jun 5, 2019

    Step 5 worked for me, thank you.

    SR
    shirley r Jun 6, 2019

    Method 2 – YAY! And the guidance you provide is very clear. Thanks much!

    GD
    G Davies Jun 6, 2019

    THANK YOU!!! I used method 5 (have Mojave) and it worked like a charm. So easy. Thanks. (I had searched a bit on other sites that didn’t really provide a solution, including from MS.)

    CC
    Claire Parker Cooper Jun 17, 2019

    Tried method 5. Kept saying my password was wrong. This is the password for my computer, correct?

    SW
    Shane Warren Author Jun 18, 2019

    Yes for the computer

    PP
    Phoebe Purtill Jun 19, 2019

    Method 5 Worked Thank yOU!

    DD
    Don Draper Jun 19, 2019

    Great !!!! It was really annoying, you solved my issue! Method #5 worked smoothly

    PW
    Phil Wild Jun 21, 2019

    Used method 5 and it worked!!! Thank you so much. This post saved me hours of misery.

    JC
    Jerud Crandall Jun 24, 2019

    Very helpful article, thank you! But I think a few details may have changed in Mojave. I’m on 10.14.5 and a few steps weren’t quite right for me:
    I used Method 1, but at step 5 the button no longer says “remove duplicate” it says “RESOLVE duplicate”. So you pick the font you want to KEEP and click the button, not pick the one to delete. A very tricky change to have made! Continuing with the process as-written, i validated fonts and got about 60 with warnings, saying they had duplicates. But they did not register when i repeated the “find enabled duplicates” command. I could see the dim, “off” duplicate fonts in fontbook but could find no way to delete or remove them. There was no way to re-invoke the “resolve duplicate” dialog from within the validation results window. So i just stopped the process there.
    I went ahead and also did Method 5.
    Since I had to restart anyway, I also attempted Method 2, but the ‘resetpassword’ terminal command now launches a tool which ONLY does password reset — the other choices (including repairing permissions) are not part of the tool anymore. I suppose these things are moved to a new place, but i stopped trying at this point and just rebooted. My problem was fixed.

    Reply
    SS
    ssgemma Jul 7, 2019

    Method 5 worked for me! I have Mojave 10.14.5

    SK
    Subramanian Kalyanaraman Jul 12, 2019

    Hi. I get access permission error once a week. I work 6 – 8 hours a day predominantly on Word and excel innstalled as office 365 on Mac Pro running Mojave 10.14.5. Typically error disappears after restart. on schedule i restart twice a week. i do not use a 3rd party font management. I tried method 1 above, it said there are no duplicate fonts and there are no issues with them. As i work every day, i do not want to uninstall and reinstall office applications. Any other suggestions? I have tried method 5 next. Will wait a week to check error and revert.

    MJ
    Mike Johnson Aug 6, 2019

    The thing that annoys me is that I have constantly authorize access to the same excel and word documents over and over again. I haven’t received the error mentioned here, I just want to end always getting the popup to grant access, which seems to provide no protection whatsoever.

      SW
      Shane Warren Author Sep 8, 2019

      Based upon my search on this topic, reinstalling Office might help the situation or before trying that you can try giving the Office applications administrative access permanently by right-clicking on the executable and selecting “Properties” from their click on compatibility and check the “Run as Administrator” option.

        TC
        Tom Coradeschi Dec 27, 2020

        We’re talking MacOS here, not Windows, unfortunately…

    SW
    Shane Warren Author Sep 26, 2019

    Try this:
    Quit the application
    Go to the Finder on Mac.
    Press SHIFT+CMD+G simultaneously and paste this folder path into the go todialog: ~/Library/Containers/com.microsoft.Excel/Data/Library/Preferences
    Click on OK to go to the folder.
    Find the file called “com.microsoft.Excel.securebookmarks.plist” and Trash it.
    Restart Excel.

    Reply
    IR
    Ian Ross Oct 1, 2019

    Hi, method 5 worked however it is only a temporary fix as the problem keeps recurring after a while. Have you come up with a permanent fix please so I don’t have to repeatedly close all applications and restart?

    SW
    Shane Warren Author Oct 1, 2019

    Find the specific application that is causing this issue, You can do this by experimenting with different background apps.

      IR
      Ian Ross Oct 1, 2019

      Hi Shane, thanks for responding. It is Word that is causing the problem.

        SW
        Shane Warren Author Oct 2, 2019

        When you go on disabling the background apps, as indicated in the method, disabling which app makes the issue go away?

          IR
          Ian Ross Oct 2, 2019

          Not sure what you mean by ‘disabling apps’, I just followed the exact instructions in method 5?

          SW
          Shane Warren Author Oct 4, 2019

          Hi, I’m sorry I misunderstood your issue. Try to disable any font management application that you might have installed or any additional fonts that you might have installed. Also, try to disable all the fonts that you don’t use often in Office.

    UR
    Uruzone Mar 3, 2020

    Over the years, I’ve tried to address this issue with all of the above, and even MOVING ALL DATA TO A LARGE INTERNAL DRIVE, trying to determine if it was a RAID issue. I also tried deleting Microsoft font folders, per a suggestion by Microsoft. Nothing helped.

    So, here’s what DOES work for us on our set up.

    Our office has twelve internal users, and another eight to ten users via VPN. We are all Mac users with Office 2016 (2011 before that), and have had the aforementioned permissions issue from OS 10.12 forward (perhaps 10.11 — I only know it’s been too long). I have frozen the file server in question at MacOS 10.13.6 and Server version 5.6.3.

    We’ll assume the following:

    1) You have multiple users with differing access to share points. Some have access only to one, some to two, some to three or more. In our office, we have personal folders (accessible only by their respective owners), an Accounting folder (accessible — you guessed it — only by the accounting staff), and a Public folder (accessible by all users).

    2) Users are sharing Word and Excel files, among others.

    3) When one user opens and saves, for example, an Excel file, the permissions change on that file so that this person becomes the owner of it. The file loses its ability to inherit its enclosing folder’s permissions, which state that “Everyone” should have read and write access.

    4) When a second person tries to open that Excel file, they get a “Grant Access” error, or are told they don’t have permission to open it.

    5) You have to manually propagate permissions from the parent folder again for it to open properly for the second user. It’s a fast fix, but should not be necessary, and is impractical on a daily basis. Worse, this fix only lasts until someone saves the file again, and the nightmare starts all over.

    6) You have tried everything I mentioned above and probably more. You are aware that this is a sandboxing issue on the Mac server side, but neither Apple nor Microsoft have addressed it.

    If this sounds like you, read on for the solution that worked for me.

    I will use two people in my example: UserAAA and UserBBB.

    (Note: I’m using the term “folder” here instead of “share point” or “mounted volume”; I just mean any shared directory on a server which has access controlled by a user’s name and password.)

    UserAAA logs in with their name and password every day. This gives them access to the UserAAA folder, the Accounting folder, and the Public folder. That’s all they see.

    UserBBB logs in with their name and password every day. This gives them access to the UserBBB folder and the Public folder. They have no access to the Accounting folder, and do not even see it.

    Both users log in by conncting to SMB://fileshare.myserver.local (or however it’s set up in DNS), with their unique names and passwords. This is how the server knows which volumes to present to them.

    The permissions problem we encounter is because our users have different user names (naturally: it’s how we present only the volumes we want each user to see). But as we know, this means that when UserAAA saves a shared Excel file, UserBBB can no longer open it (and vice-versa) because the last person to save that file ridiculouly becomes its owner, and somehow overrides the server’s explicit permissions, which are no longer inherited.

    I can’t have my users log in with the same user name, because then they would see volumes they shouldn’t see (e.g. UserAAQ would see UserBBB’s folder; UserBBB would see Accounting. Bad!)

    This is where I always ended up. It sucked. Until I remembered an old FTP trick I used to use and applied it here. They CAN share a user name.

    I created a user called PublicUser. ONLY the Public folder is accessible by this user account.

    UserAAA still uses their name and password, and still mounts their personal folder and Accounting folder because of it. UserBBB still uses their name and password, and sees their personal folder only.

    THEN, I have both users log in to the server by IP Address with the PublicUser name. Because we are using the IP address this time, the workstation (the user’s Mac) happily sees this as a different machine, and doesn’t “care” about using a different username and password to access what WE know is actually the same server.

    One way to do this is from the desktop, press Command-K (or go to “Go–Connect to Server”), and type in SMB://PublicUser@IP ADDRESS OF YOUR SERVER (e.g. SMB://PublicUser@192.168.2.100)

    Enter your password for PublicUser, tell it to save the credentials and BOOM! The users are logged in with two different users names. One to see the folders only they should see, and the other (PublicUser) to see the shared Public folder. I have even moved these folders (volumes) into the users’ Login Items in the Users & Groups control panel so that every time the machine starts, it automatically logs into the server with both sets of credentials for the folders needed.

    That’s it! I hope this saves someone else some headaches!

    Patrick

    Reply
    SI
    SIAM Mar 16, 2020

    Method 5 FTW – thanks

    JH
    jhun1023 Jul 6, 2021

    i’m in 2021.
    using docx2pdf for convert MS Word to PDF files.Method 5 didn’t work for me..

    GR
    Gaurav Ramanan Dec 23, 2023

    MY GOD! What an amazing article! I’m developing a Powerpoint Add In and temporarily moving files to the folder you mentioned and then importing it worked like a charm! Method 5 FTW!

    EL
    Elizabeth Jan 17, 2024

    I did method 5 and it worked! Thank you so much Kevin for your help!