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
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.
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.
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:"/>
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.
still the same error.
Fixed with workaround to delete and recreate events instead of updating them for google