OutlookGoogleCalendarSync: Unable to reclaim orphan calendar entries in Outlook calendar - System.NullReferenceException
📦 Hotfix is posted on this comment.
OGCS Version: v2.7.8.0 Installed or Portable: Installed
Problem Description
O->G works fine, G->O bombs out
"System.NullReferenceException: Object reference not set to an instance of an object."
Steps to Reproduce the Issue
Happens every sync.
Any other information
Originally working fine - not clear what triggered the problem. Relevant extract from log attached.
2019-03-26 00:01:11,568 DEBUG 9 OutlookGoogleCalendarSync.Console [0] - Checking for orphaned items...
2019-03-26 00:01:12,440 ERROR 9 OutlookGoogleCalendarSync.Console [0] - Unable to reclaim orphan calendar entries in Outlook calendar.
2019-03-26 00:01:13,034 DEBUG 9 OutlookGoogleCalendarSync.Console [0] - The following error was encountered during sync:-
2019-03-26 00:01:13,034 ERROR 9 OutlookGoogleCalendarSync.OGCSexception [0] - System.NullReferenceException: Object reference not set to an instance of an object.
2019-03-26 00:01:13,034 ERROR 9 OutlookGoogleCalendarSync.OGCSexception [0] - Code: 0x80004003;-2147467261
2019-03-26 00:01:13,034 ERROR 9 OutlookGoogleCalendarSync.OGCSexception [0] - at OutlookGoogleCalendarSync.Sync.Engine.googleToOutlook(List`1 googleEntries, List`1 outlookEntries, String& bubbleText)
at OutlookGoogleCalendarSync.Sync.Engine.synchronize()
at OutlookGoogleCalendarSync.Sync.Engine.<>c__DisplayClass19_0.<Start>b__0(Object o, DoWorkEventArgs args)
2019-03-26 00:01:13,034 ERROR 9 OutlookGoogleCalendarSync.Console [0] - Object reference not set to an instance of an object.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 20 (8 by maintainers)
Commits related to this issue
- On Outlook item copy, need to manage /all/ custom properties. Only backup properties that actually exist on the source object. Remove locallyCopied property from source object. #689 — committed to phw198/OutlookGoogleCalendarSync by phw198 5 years ago
- Merge branch 'issue-689' of https://github.com/phw198/OutlookGoogleCalendarSync into release Resolves #689 — committed to phw198/OutlookGoogleCalendarSync by phw198 5 years ago
- Squashed commit of the following: commit 17806cb319a55e524fd3339745dc06a791fbb905 Author: Paul Woolcock <login@paulwoolcock.co.uk> Date: Sat Jun 1 23:08:28 2019 +0100 v2.8.0 commit f79ca9040d... — committed to phw198/OutlookGoogleCalendarSync by phw198 5 years ago
Thanks Paul. That fixed the problem!
Appears to have corrected the problem, I tried a number of combinations, both ways, (move on Outlook, then sync, move on Google, then sync), with drag and drop of event(s). All seemed to work just fine!!
I had no failures of “existing” items that already have the problem as I had already corrected the one that failed last week a few days ago.
📦 Please could you try with v2.7.8.1.zip (see instructions for applying).
This should prevent the cause of the problem from happening again (a bug with click and dragging an Outlook appointment, or copy-and-pasting an appointment).
However, it won’t fix items that already have the problem, but it will now report which item(s) cause the sync to fail - these will need to be manually recreated.