mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 11:05:56 +03:00
[GH-ISSUE #20] sync error with Sogo server #30
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#30
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 @aluxnimm on GitHub (Jun 4, 2015).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/20
Originally assigned to: @aluxnimm on GitHub.
Hi guys,
I installed the plug-in on an Outlook 2013.
I configured it to sync with a Sogo 2.0.1 calendar. Unfortunately it throws an error I cannot understand or manage to solve it.
You can have attached the log file.
Please tell me if you need more info.
Best regards,
Andrei
Original comment by: andreimiron
Original Ticket: outlookcaldavsynchronizer/29
@aluxnimm commented on GitHub (Jun 4, 2015):
what does test connection say? at the last sync attempts you get a 501 response from server( not implemented). is the server url correct?
Original comment by: aluxnimm
@aluxnimm commented on GitHub (Jun 4, 2015):
Test connection says OK.
The URL I think is correct because the same URL I'm using in a BlackBerry and it is working.
I get the URL from Sogo->Calendar->Properties:Links to this Calendar->CalDAV URL
Best regards,
Andrei
Original comment by: andreimiron
@aluxnimm commented on GitHub (Jun 4, 2015):
Indeed in the previous log attached at the end were some tries with different calendars and settings.
I reconfigured all over again, test the connection and after I tried a synchronisation I get the clean log attached.
Andrei
Original comment by: andreimiron
@aluxnimm commented on GitHub (Jun 4, 2015):
can you send me an ics export from the calendar to reproduce it. I guess it is some problem with an malformed event.
Original comment by: aluxnimm
@aluxnimm commented on GitHub (Jun 4, 2015):
Export from Outlook or from SOGo?
Original comment by: andreimiron
@aluxnimm commented on GitHub (Jun 4, 2015):
from sogo.
Original comment by: aluxnimm
@aluxnimm commented on GitHub (Jun 4, 2015):
Here you have it.
Hope it helps.
Andrei
Original comment by: andreimiron
@aluxnimm commented on GitHub (Jun 4, 2015):
Ok from sogo to Outlook works but do you have events without a subject in Outlook? Only that way I can reproduce the Exception.
Original comment by: aluxnimm
@aluxnimm commented on GitHub (Jun 4, 2015):
try 0.94
Original comment by: aluxnimm
@aluxnimm commented on GitHub (Jun 4, 2015):
Hi,
regardless of CalDav errors, the first error happens, when a new profile is added, whithout selecting an outlook folder.
I added validation for the options, to avoid this scenario in the future.
br
Gerhard
Original comment by: nertsch
@aluxnimm commented on GitHub (Jun 5, 2015):
Hi guys,
I uninstalled the previous version, install the new one (0.9.4). I delete all the entries from Outlook calendar and try a sync and I have a new error. You have attached the new log file.
Alexander: I don't think this was the case because the error (in previous version) appered no matter the sens of the sync (from Outlook to Sogo, from Sogo to Outlook or merge both of calendars).
Gerhard: it is strange that the first time I tried the sync (just after the first installations) indeed the local Calendar folder wasn't selected. But I noticed that and after that all the tests were done with the local folder Calendar selected.
I hope this new log will help you find the problem.
Thanks,
Andrei
Original comment by: andreimiron
@aluxnimm commented on GitHub (Jun 5, 2015):
Hi guys,
I find the problem. It is from the firewall, when I tried by-passing the firewall it works.
I don't know now what is the problem with the firewall I need to investigate more.
Anyway thank you very much for your efforts.
Best regards,
Andrei
Original comment by: andreimiron
@aluxnimm commented on GitHub (Jun 8, 2015):
Original comment by: aluxnimm