starred/outlookcaldavsynchronizer

Fork 0

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

[GH-ISSUE #50] Exception when syncing events with attachements #937

New issue

Closed

opened 2026-03-13 23:24:28 +03:00 by kerem · 8 comments

kerem commented

2026-03-13 23:24:28 +03:00

Owner

Originally created by @aluxnimm on GitHub (Jun 10, 2015).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/50

Originally assigned to: @aluxnimm on GitHub.

Syncing events with an attachement does not work.
I suppose that attachements are not supported but at least the events should be successfully synced with attachements omitted.

Here is a log:

ERROR 2015-06-10 18:56:22,749 [VSTA_Main] neric.Synchronization.States.StateBase`6 . LogException                   - Exception occured:
System.Net.WebException: The remote server returned an error: (400) Bad Request.
   at System.Net.HttpWebRequest.GetResponse()
   at CalDavSynchronizer.DataAccess.CalDavDataAccess.ExecuteCalDavRequest(Uri url, Action`1 modifier, String requestBody)
   at CalDavSynchronizer.DataAccess.CalDavDataAccess.UpdateEvent(Uri url, String etag, String iCalData)
   at CalDavSynchronizer.DataAccess.CalDavDataAccess.UpdateEvent(Uri url, String iCalData)
   at CalDavSynchronizer.Implementation.CalDavEventRepository.Update(Uri entityId, IICalendar entityToUpdate, Func`2 entityModifier)
   at CalDavSynchronizer.Generic.Synchronization.States.UpdateAToB`6.PerformSyncActionNoThrow()
 INFO  2015-06-10 18:56:22,765 [VSTA_Main] ronizer.Scheduling.SynchronizationWorker . RunNoThrowAndReschedule        - Duration of 'Running synchronization profile 'Phil_GoogleCalendar'': 00:00:00.4906890

Original comment by: lost1

Original Ticket: outlookcaldavsynchronizer/35

Originally created by @aluxnimm on GitHub (Jun 10, 2015). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/50 Originally assigned to: @aluxnimm on GitHub. Syncing events with an attachement does not work. I suppose that attachements are not supported but at least the events should be successfully synced with attachements omitted. Here is a log: ``` ERROR 2015-06-10 18:56:22,749 [VSTA_Main] neric.Synchronization.States.StateBase`6 . LogException - Exception occured: System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at CalDavSynchronizer.DataAccess.CalDavDataAccess.ExecuteCalDavRequest(Uri url, Action`1 modifier, String requestBody) at CalDavSynchronizer.DataAccess.CalDavDataAccess.UpdateEvent(Uri url, String etag, String iCalData) at CalDavSynchronizer.DataAccess.CalDavDataAccess.UpdateEvent(Uri url, String iCalData) at CalDavSynchronizer.Implementation.CalDavEventRepository.Update(Uri entityId, IICalendar entityToUpdate, Func`2 entityModifier) at CalDavSynchronizer.Generic.Synchronization.States.UpdateAToB`6.PerformSyncActionNoThrow() INFO 2015-06-10 18:56:22,765 [VSTA_Main] ronizer.Scheduling.SynchronizationWorker . RunNoThrowAndReschedule - Duration of 'Running synchronization profile 'Phil_GoogleCalendar'': 00:00:00.4906890 ``` Original comment by: lost1 Original Ticket: [outlookcaldavsynchronizer/35](https://sourceforge.net/p/outlookcaldavsynchronizer/35)

kerem

2026-03-13 23:24:28 +03:00

closed this issue
added the
sourceforge

auto-migrated

1.0

Google

Google Calendar

attachement
labels

kerem commented

2026-03-13 23:24:44 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 10, 2015):

The 400 bad request response from google has nothing to do with attachments, it is a more general problem when we sync updated events from outlook to google it seems. With SOGo it works, so I will investigate why Google doesnt't like the update.

Original comment by: aluxnimm

@aluxnimm commented on GitHub (Jun 10, 2015): The 400 bad request response from google has nothing to do with attachments, it is a more general problem when we sync updated events from outlook to google it seems. With SOGo it works, so I will investigate why Google doesnt't like the update. Original comment by: aluxnimm

kerem commented

2026-03-13 23:24:49 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 10, 2015):

status: open --> accepted
assigned_to: Alexander Nimmervoll

Original comment by: aluxnimm

@aluxnimm commented on GitHub (Jun 10, 2015): - **status**: open --> accepted - **assigned_to**: Alexander Nimmervoll Original comment by: aluxnimm

kerem commented

2026-03-13 23:24:54 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 10, 2015):

Unfortunately there was an issue with WebExceptionLogging, which caused, that the response Body ( which usually contains a detailled error description) was not logged.
I fixed this issue a few minutes ago. Maybe this could be helpful, for your investigation.

Original comment by: nertsch

@aluxnimm commented on GitHub (Jun 10, 2015): Unfortunately there was an issue with WebExceptionLogging, which caused, that the response Body ( which usually contains a detailled error description) was not logged. I fixed this issue a few minutes ago. Maybe this could be helpful, for your investigation. Original comment by: nertsch

kerem commented

2026-03-13 23:24:59 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 10, 2015):

Not much more info now:
ERROR 2015-06-10 23:07:29,877 [VSTA_Main] neric.Synchronization.States.StateBase`6 . LogException - StatusCode: BadRequest
StatusDescription: Bad Request
Body:
<D:error xmlns:D="DAV:"/>

Original comment by: aluxnimm

@aluxnimm commented on GitHub (Jun 10, 2015): Not much more info now: ERROR 2015-06-10 23:07:29,877 [VSTA_Main] neric.Synchronization.States.StateBase`6 . LogException - StatusCode: BadRequest StatusDescription: Bad Request Body: <?xml version="1.0" encoding="UTF-8"?> <D:error xmlns:D="DAV:"/> Original comment by: aluxnimm

kerem commented

2026-03-13 23:25:04 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 10, 2015):

Maybe the google-implementation doesn't accept updates without preconditions (with etag).

I added a branch ('feature/Update-With-Etag/' ), where the updates are done with preconditions.
Maybe this works with google.

Original comment by: nertsch

@aluxnimm commented on GitHub (Jun 10, 2015): Maybe the google-implementation doesn't accept updates without preconditions (with etag). I added a branch ('feature/Update-With-Etag/' ), where the updates are done with preconditions. Maybe this works with google. Original comment by: nertsch

kerem commented

2026-03-13 23:25:09 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 11, 2015):

still the same error.

Original comment by: aluxnimm

@aluxnimm commented on GitHub (Jun 11, 2015): still the same error. Original comment by: aluxnimm

kerem commented

2026-03-13 23:25:14 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 12, 2015):

Fixed with workaround to delete and recreate events instead of updating them for google

Original comment by: aluxnimm

@aluxnimm commented on GitHub (Jun 12, 2015): Fixed with workaround to delete and recreate events instead of updating them for google Original comment by: aluxnimm

kerem commented

2026-03-13 23:25:19 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jun 12, 2015):