mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 11:05:56 +03:00
[GH-ISSUE #437] Sync error - Response Status Code '400' (Bad request) when synching calendar #420
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#420
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 @knicket1 on GitHub (Dec 9, 2024).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/437
Hi,
I get a sync error for certain calendar entries - typically ones that are added by 3rd parties. Here is a paste the Exception message and a screenshot.
CalDavSynchronizer.DataAccess.WebDavClientException: Response status code does not indicate success: '400' ('Bad Request'). Message:
<D:error xmlns:D="DAV:"/>
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.CalDavDataAccess.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.Implementation.CalDavRepository
1.<TryUpdate>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at CalDavSynchronizer.Implementation.CalDavRepository1.d__16.MoveNext()--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at GenSync.EntityRepositories.BatchEntityRepositoryAdapter`4.d__3.MoveNext()
@lvj commented on GitHub (Jan 17, 2025):
Same, started around 2 days ago.
@fips21 commented on GitHub (Jan 24, 2025):
Looks like same problem for me. Startet today with Google calendar.
CalDavSynchronizer.DataAccess.WebDavClientException: Response status code does not indicate success: '400' ('Bad Request'). Message:
<D:error xmlns:D="DAV:"/>
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.DataAccess.CalDavDataAccess.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at CalDavSynchronizer.Implementation.CalDavRepository
1.<TryUpdate>d__16.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at CalDavSynchronizer.Implementation.CalDavRepository1.d__16.MoveNext()--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at GenSync.EntityRepositories.BatchEntityRepositoryAdapter`4.d__3.MoveNext()
@brnbs commented on GitHub (Feb 13, 2025):
Same for me, every day!
@msceex commented on GitHub (Mar 19, 2025):
I have this issue as well. Any update?
@msceex commented on GitHub (Mar 19, 2025):
maybe related? https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/420
@brnbs commented on GitHub (Mar 19, 2025):
To clarify, I only encounter this sync error when events are added automatically by Gmail from emails.
@fips21 commented on GitHub (Mar 19, 2025):
I don't use Gmail at all. Only Outlook and Google calendar.
@rubaboo commented on GitHub (May 14, 2025):
I see there are several issues about this same error (Status code 400). IDK if they all have the same root cause, but here's how I solved mine. (I started having this problem with Google Calendar. It wasn't a transient condition. It was just not syncing anymore.)
I created a new sync profile. Not only did I not change any parameters in it (left everything default), but I compared the new profile to the old one, and everything that I could see in the 2 profiles' settings (incl. Advanced) was identical. Yet, the new profile was syncing, and the old one kept giving me 400. So I deleted the old profile and moved on.
@fips21 commented on GitHub (May 16, 2025):
Seems like it's working with new profile. Thanks.
@petero-dk commented on GitHub (Jun 10, 2025):
This fixed it for me, I have seen this error start showing when I have recurring meetings that are cancelled and moved in Outlook, IDK if that is related but once the error start showing I also see errors with changes to recurring meetings.
@Funkem commented on GitHub (Aug 10, 2025):
Hello together,
we have the same error and a new profile works a few day before it fails again. What can we do to help? Maybe deliver some logs?
Of course, we are using the latest version.
CalDavSynchronizer.DataAccess.WebDavClientException: Response status code does not indicate success: '400' ('Bad Request'). Message:
<D:error xmlns:D="DAV:"/>
bei CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__10.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__9.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__8.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei CalDavSynchronizer.DataAccess.CalDavDataAccess.d__28.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei CalDavSynchronizer.Implementation.CalDavRepository
1.<TryUpdate>d__16.MoveNext() --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei CalDavSynchronizer.Implementation.CalDavRepository1.d__16.MoveNext()--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei GenSync.EntityRepositories.BatchEntityRepositoryAdapter`4.d__3.MoveNext()
@elzik commented on GitHub (Nov 7, 2025):
I have the same issue here.
I have noticed that it seems to happen for recurring calendar events from my Exchange account, but crucially, someone then rearranges the date of a single instance of that recurring event. When Outlook CalDav Synchronizer tries to sync that specific recurring event, I get the error.
@nhl4000 commented on GitHub (Dec 12, 2025):
I had the same issue from Outlook to Google (with synchronization mode: Outlook -> Server (Merge)).
CalDavSynchronizer.DataAccess.WebDavClientException: Response status code does not indicate success: '400' ('Bad Request').I do believe a client changed something with recurring calendar events and it messed things up.
I was able to resolve the issue by:
@lesebas commented on GitHub (Dec 12, 2025):
Same issue for me, solved by duplicating the sync profil and deleting the old one.
@fips21 commented on GitHub (Dec 13, 2025):
Did that some weeks ago but next day same problem again. Now I reduced the time period to zero days in the past and only 30 days in the future. Looks good so far.