NavigateMason News and Updates

Microsoft Exchange Update as of 11/10/16 for Outlook Users

Released on 10/28:

  • User unable to sync due to bad outlook appointment – Addressed an issue where a user’s outlook calendar has an appointment with no start time, end time or both. This was hidden from the user in outlook but the error exists in the background and thus prevents their calendar from syncing. We have added a process to handle these exceptions for the handful of users it impacted.

Releasing Tomorrow:

  • Exception handling of recurring appointments (either free or busy) with no end date – Given the infinite loop these created while they tried to sync they were impacting not only users calendars with the issue but other non-error user calendar syncs got caught behind them in the syncing process. This has led to situations where a user’s calendar received a “cannot connect to service error” intermittently and can result in double booking. We are implementing a change to limit these recurring appointments to 750 instances so that they can successfully complete the sync. This should then also improve performance for the other users too.
  • User unable to sync due to “Bad argument given for a Folder ID” –  We have a few users who experienced this error code so we have implemented a change that should correct and allow these users to sync
  • New Logging – We are adding additional logging that will allow us to monitor calendar performances every 5 minutes across all members. This will give us greater insight into any additional issues users might face (and at times of day)
  • Additional Worker Capacity – We have added additional dedicated server capacity on our end to continue to support exchange integrations



  • Private Appointments – we completed a thorough diagnosis here and determined private appointment syncs are working correctly. The issue here is a result of the permission at the account level for an individual. When users provide access to our exchange syncing service it is done through either delegating permission or impersonation. However, at the Outlook account level for the user there is also a “can see my private items” permission. This applies more broadly than calendars. If not selected, we would not be able to sync private calendar appointments. The two solutions for end users:
    • Provide that permission to the calendar for syncing – the process for doing so differs for every outlook version (please note this does provide broader access to private items than just calendar though)
    • Create a duplicate “busy” non-private block with each private appointment on outlook. These will then automatically sync to us.