Outlook 2013 (Office 365) for Mac Clock Error

Ran into this wonderful error while traveling.  Thankfully, I still had Outlook 2011 still installed, so I had a workaround for a bit.

Clock error
The system clock is inaccurate, please set it to current local time.
This would occur for no obvious reason, although it does seem related to 'travel' related activities when switching time zones.  Outlook would go into offline mode and would require that I activate it first, activation would fail w/ the above error.  If I remember correctly, I had this happen to me two about a month ago as well, but the activation error went away on it's own after I flew back to my timezone.

This time, I screwed around w/ it, and well I probably broke it while trying to fix it before going back to my home time zone.  One of which was deleting the computer from my activated list as a troubleshooting step.  Anyway, Microsoft support on a communities board finally posted a solution, but it was difficult to figure out, so here is a 'translated' step by step.  Specifically step 5 wasn't that clear to me.


  1. Open Keychain Access from your Utilities folder under Applications.
  2. Search for Office and delete any keys that show up.
  3. Open Activity Monitor from your Utilities folder under Applications.
  4. Search for 365 and kill any processes found. (Which may be none)

  5. Navigate to ~/Library/Group Containers/UBF8T346G9.Office and delete the following files
  6. Go to Finder, select "Go" --> "Go to Folder..." and paste the above path.
  7. Open the terminal (also in your utilities folder) and run the following commands - "Defaults delete com.microsoft.Outlook”
Lastly, you may need to download the Outlook dmg install file from Office 365 again to reinstall Outlook.  There appears to be updates included in the latest pkg.  I know I had to in order to get it to activate properly.


Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Azure VMware Solution: NSX-T Active/Active T0 Edges...but