starred/outlookcaldavsynchronizer

Fork 0

mirror of https://github.com/aluxnimm/outlookcaldavsynchronizer.git synced 2026-04-25 11:05:56 +03:00

[GH-ISSUE #349] CalDAV synchronizing error with error messages #801

New issue

Closed

opened 2026-03-01 17:41:39 +03:00 by kerem · 7 comments

kerem commented

2026-03-01 17:41:39 +03:00

Owner

Originally created by @eungmo on GitHub (Apr 4, 2022).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/349

I got this error message.
"System.Xml.XmlException: '', hexadecimal value 0x08, is an invalid character. Line 3668. position 9.

It happened with only few calendars.
I have 10 calendars and the 2 calendars are not synchronized with this exception. (8 calendars are OK)

I checked my caldav server and access log provide non error code and error message.
I think caldav server provided the schedules data but the client (CalDAV Synchronizer) cannot parsing data.
Could anyone help me to solve this issue?

Outlook version: 2019 MSO (16.0.10384.20023) 64bit
CalDAV Synchronizer version: 4.2.0.0

Originally created by @eungmo on GitHub (Apr 4, 2022). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/349 I got this error message. "System.Xml.XmlException: '', hexadecimal value 0x08, is an invalid character. Line 3668. position 9. It happened with only few calendars. I have 10 calendars and the 2 calendars are not synchronized with this exception. (8 calendars are OK) ![image001](https://user-images.githubusercontent.com/1171393/161499924-4577140d-c435-40e2-95b5-e3f6a2cfab4a.png) I checked my caldav server and access log provide non error code and error message. I think caldav server provided the schedules data but the client (CalDAV Synchronizer) cannot parsing data. Could anyone help me to solve this issue? - Outlook version: 2019 MSO (16.0.10384.20023) 64bit - CalDAV Synchronizer version: 4.2.0.0

kerem closed this issue

2026-03-01 17:41:39 +03:00

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@mgrn0 commented on GitHub (Jun 13, 2022):

I am having the same problem, except the hexadecimal value being complained about is 0x15 – and I do have the setting "Accept invalid chars in server response" enabled, but it does not help.

How can I figure out which (calender) event is causing the issue? It seems to be bound to individual events since some days sync works and a few days later it stops (and repeating...)

@mgrn0 commented on GitHub (Jun 13, 2022): I am having the same problem, except the hexadecimal value being complained about is 0x15 – and I do have the setting "Accept invalid chars in server response" enabled, but it does not help. How can I figure out which (calender) event is causing the issue? It seems to be bound to individual events since some days sync works and a few days later it stops (and repeating...)

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@eungmo commented on GitHub (Jun 14, 2022):

I totally agree with you.
If I can notice what event makes this error, then it would be really help me.
(Could anyone provide the event uid on the message when the error (System.Xml.XmlException) occurred?)

@eungmo commented on GitHub (Jun 14, 2022): I totally agree with you. If I can notice what event makes this error, then it would be really help me. (Could anyone provide the event uid on the message when the error (System.Xml.XmlException) occurred?)

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@mgrn0 commented on GitHub (Jun 14, 2022):

In my case I have to fiddle around with the amount of days to sync in the future (try and error between 5 and 15 days) in order to get a sync working at all; this ends up in dozens of duplicated entries for my recurring events :/

@mgrn0 commented on GitHub (Jun 14, 2022): In my case I have to fiddle around with the amount of days to sync in the future (try and error between 5 and 15 days) in order to get a sync working at all; this ends up in dozens of duplicated entries for my recurring events :/

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@mgrn0 commented on GitHub (Jun 27, 2022):

I have set the synchronizer to 'just' mirror all events (to wipe everything on sync and just mirror events in one direction), however I end up with dozens of duplicates while the above error occurs. Is this normal?

@mgrn0 commented on GitHub (Jun 27, 2022): I have set the synchronizer to 'just' mirror all events (to wipe everything on sync and just mirror events in one direction), however I end up with dozens of duplicates while the above error occurs. Is this normal?

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@mgrn0 commented on GitHub (Sep 11, 2022):

really nobody having same / similar issues? it's such an annoying bug…

@mgrn0 commented on GitHub (Sep 11, 2022): really nobody having same / similar issues? it's such an annoying bug…

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@aluxnimm commented on GitHub (Feb 18, 2023):

You need to export the whole calendar as an ics file from the server, open with notepad++ and find that invalid characters.
We will hopefully fix the issue and filter our invalid xml characters in our next release.

@aluxnimm commented on GitHub (Feb 18, 2023): You need to export the whole calendar as an ics file from the server, open with notepad++ and find that invalid characters. We will hopefully fix the issue and filter our invalid xml characters in our next release.

kerem commented

2026-03-01 17:41:40 +03:00

Author

Owner

@mgrn0 commented on GitHub (Sep 21, 2023):

just want to leave that here: synchronization works flawless for me since that last release. never again had the problem / error showing up. thanks for fixing this!

@mgrn0 commented on GitHub (Sep 21, 2023): just want to leave that here: synchronization works flawless for me since that last release. never again had the problem / error showing up. thanks for fixing this!