mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 03:25:48 +03:00
[GH-ISSUE #115] NullReferenceException when syncing with Google Calendar #112
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#112
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wrstlbrnft on GitHub (Feb 19, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/115
I'm using v.1.18.0.0 on Outlook 2016. When syncing (two-way) with my Google calendar, I get a NullReferenceException, as shown in the attached screenshot.
Is there a way to figure out what properties of the offending event cause the NRE so I can fix it by updating the event?
@aluxnimm commented on GitHub (Feb 19, 2016):
Please provide the raw data of the offending server event. For that click on the link below "Server ID" to download the ics file. Attach it here that we can identify the problem.
@wrstlbrnft commented on GitHub (Feb 19, 2016):
Here is the offending event. It was originally created on an Exchange calendar and I then copied it in Outlook to a local calendar which I sync with Google.
offending.ics.txt
@aluxnimm commented on GitHub (Feb 19, 2016):
Can't find anything offending in that ics file and can sync it from Google to Outlook without error. Since the sync is trying to update an existing Outlook item maybe in the Outlook appointment is some error. Delete the item in Outlook and change sync direction Outlook<-Server (Replicate) once to recreate it in Outlook to check if it can be created.
@wrstlbrnft commented on GitHub (Feb 19, 2016):
I deleted the event and re-created it. Now it syncs fine.
I'm sorry if that prevented you from finding out more, which the replicate server->Outlook could have revealed.
Thank you very much for your help!