mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 03:25:48 +03:00
[GH-ISSUE #99] System.Runtime.InteropServices.COMException (0x80020009) #996
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#996
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 @maybeec on GitHub (Jan 11, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/99
Hi, I recently observed the following exception:
I read the message
Sie müssen in die Felder "An", "Cc" oder "Bcc" mindestens einen Namen oder eine Kontaktgruppe eingeben., but I cannot interprete it sufficiently. Can I see which calendar entry causes this error?@aluxnimm commented on GitHub (Jan 11, 2016):
Some invalid recipient or organizer data.
You are using owncloud right?
You should be able to download the ics with the server url combined with the path in XXXX in your error report. Please post the ics file.
@maybeec commented on GitHub (Jan 11, 2016):
Yes, you are right, I am using the Owncloud 8.2.2.
Here the ics file. I just replaced alpha numeric characters with X and 9. As a hint. The summary also contains german umlauts.
@aluxnimm commented on GitHub (Jan 11, 2016):
Summary doesn't matter.
ORGANIZER;CN=:mailto:OwnCloud%20Kalender ??? that is no valid email and no cn or you changed that part too?
@maybeec commented on GitHub (Jan 11, 2016):
No, I did not changed it.
I already observed this issue. It is somehow changed by any other sync client on a mobile phone or touchpad for example. If this is the pointer, I have to investigate which tool causes this change.
You are sure, that Outlook CalDAV Synchronizer is not the cause for this? Than I can investigate into a different direction. Maybe even Owncloud causes this issue.
@maybeec commented on GitHub (Jan 11, 2016):
Or is the PRODID the identifier of the last client changing the appointment? That would make finding the errorneous software more easier 🎯
@aluxnimm commented on GitHub (Jan 11, 2016):
Yes roundcube :)
Well but we shouldn't cause a COM Exception either but ignore the wrong organizer, will test it and fix the issue from our side.
@maybeec commented on GitHub (Jan 11, 2016):
Ok, thanks.
Nevertheless, I deactivated the roundcube caldav extension to prevent it from destroying further future appointments as well.
The bad about this change is also, that Outlook will not allow to change your appointments anymore :(
@aluxnimm commented on GitHub (Jan 11, 2016):
fixed in latest commit, if no valid mailto and no cn is present, organizer is skipped,
@maybeec commented on GitHub (Jan 11, 2016):
👍 thanks!
@aluxnimm commented on GitHub (Jan 12, 2016):
fixed in 1.14.0
@maybeec commented on GitHub (Jan 13, 2016):
Thanks, but now I got the following issue :)
Any Idea? I had a look at the server logs, but found nothing of interest.
@maybeec commented on GitHub (Jan 13, 2016):
Maybe also an owncloud issue, I will investigate on that in some spare time.
@aluxnimm commented on GitHub (Jan 13, 2016):
There must be some event in Owncloud with invalid INTERVAL in a recurrence rule.
I found an issue with the Outlook Obejct Model that sets INTERVAL=0 for appointments with all workday recurrence, and we export it as
RRULE:FREQ=WEEKLY;INTERVAL=0;BYDAY=MO,TU,WE,TH,FR which should be INTERVAL=1 of course. Will fix that.
Maybe related to #58 and the referenced events there