mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 11:35:47 +03:00
[GH-ISSUE #124] Not syncing: System.Threading.Tasks.TaskCanceledException: A task was canceled. #1022
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#1022
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 @digitalkram on GitHub (Apr 5, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/124
hi there
for me sync is not working at all using Outlook 2013 and owncloud as CalDAV-Server. Connection testing succeeds.
Sync report:
If there is more information required just let me know.
Cheers,
@aluxnimm commented on GitHub (Apr 5, 2016):
Sounds like a timeout issue or network problem, since it is around 90secs. Any errors in the owncloud server log? You can try various network settings or use a tool like fiddler to debug the network traffic. Maybe also updating the latest Windows/Office and ,net patches helps, what versions are you using?
@digitalkram commented on GitHub (Apr 5, 2016):
hi aluxnimm,
thanks for your fast response. Windows/Office are set by company policy. However based on your hint that TaskCanceledException might counterintuitively indicate a timeout issue I checked a bit. When I test my configured profile I can see the resulting request in the ownlcoud log and your plugin reports connection success.
When I start a sync I see the following in the OC logs:
And that is it. Is it possible that the REPORT operation (whatever it is) is taking too long for the timeout setting of the plugin? The calendar is HUGE and the server system is not very performant...
@aluxnimm commented on GitHub (Apr 5, 2016):
only the 401 log entry? means not authorized. what network settings are you using? expand tree view in sync profile and try preemptive or force basic auth and close connection after each request. furthermore you can increase calDavConnectTimeout in config file, see readme.
@digitalkram commented on GitHub (Jun 1, 2016):
sorry that this stalled. had a crazy time lately :)
well, when I limit the time range it is working so I think authorization is working in general. I have a time off for a month or two now - finally. I'll close this for now and might or might not get back to you.
anyways thanks for your replies and helpfulness so far 👍 :)