![outlook 2016 sync issues pc outlook 2016 sync issues pc](https://www.remosoftware.com/info/wp-content/uploads/2017/06/featured-sync-gmail-outlook-1280x720.jpg)
- #Outlook 2016 sync issues pc code#
- #Outlook 2016 sync issues pc free#
- #Outlook 2016 sync issues pc windows#
The service doesn’t see or store your Google or Microsoft logins and works directly on servers in the cloud, so your synced calendars are viewable and available on any of your devices. Everything is supported, so long as it can view an Outlook or Google Calendar.
#Outlook 2016 sync issues pc windows#
You can also choose not to display the information about events synced from another calendar, so it will only show the time as busy.īecause all the syncing happens in the cloud, it doesn’t matter whether you’re using Windows 10, macOS, iOS or Android, nor which calendar app you choose to use.
#Outlook 2016 sync issues pc free#
One is that you can choose to sync only your busy or free times, which you can ensure personal events aren’t synced to your work calendar. The section above shows that doing this creates a conflict when Outlook compares the local item with the remote copy and finds the UserProperties stream not initialized on the remote – not a surprise since only the local copy was changed by your code.CalendarBridge is a new online service which can not only sync up to 10 of your Microsoft and Google calendars, but also offers some very useful options. So, on Cached Exchange we are trying to add a UserProperty to the item supplied by the ItemAdd event of the Sent Items folder. The remote is not okay: getting the 0x85400102 property produces the 0x8004010F = MAPI_E_NOT_FOUND exception.
![outlook 2016 sync issues pc outlook 2016 sync issues pc](http://i.stack.imgur.com/6erLx.png)
#Outlook 2016 sync issues pc code#
The local item is okay: we know that the code added a UserProperty to it, and the stream is initialized.
![outlook 2016 sync issues pc outlook 2016 sync issues pc](https://www.vdsearchtool.com/wp-content/uploads/2017/03/troubleshootingoutlooklogging-1.png)
This makes sense: the log appears to tell us that the conflict occurred when comparing these streams on the local and remote items. Searching a little further supplies the missing context and information: the 0x85400102 named property stores the stream of the UserProperties collection. Googling for dispidPropDefStream points to PidLidPropertyDefinitionStream which is here. Googling for 0x8540 helps: reports that StdAfx.h C/C++ header file – part of MFCMAPI ( github) – contains this line: #define dispidPropDefStream 0x8540. To proceed, you should know that the hexadecimal value of a MAPI property has two parts: the ID and type. One of these logs is created in Outlook 2007 ( in German). It is only mentioned in several modification resolution logs published on the web. The conflict occurs when comparing the property 0x85400102 on the local and remote items. The Keywords named MAPI property above is the string that you access via the Category property in OOM see here. The property 0x3FFA001F that they ignore is PidTagLastModifierName see here.
![outlook 2016 sync issues pc outlook 2016 sync issues pc](https://fasrdj186.weebly.com/uploads/1/2/4/2/124209524/322339552.png)
To detect the issue easily, I suggest that your code also change the MailItem.Category property before saving the item. In the ItemSend event of the Sent Items folder, your code adds a UserProperty to the Outlook item that the event handler supplies (and saves the item). The Outlook version used (Outlook 365 in my case) seems to be irrelevant as Google reports a similar conflict to occur in Outlook 2007. Reportedly, turning the Cached Mode off solves the issue. I see this issue in the Sent Items folder on an Exchange account having Cached Exchange Mode (see e.g.