mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-26 11:35:47 +03:00
[GH-ISSUE #160] bug in synchronizing #1058
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#1058
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 @cataclop on GitHub (Aug 30, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160
Hello!
I have downloaded the program CalDavSynchronizer -2.5.0
Windows 7 Professional
Outlook 2013
but unfortunately this bug pops-up and I can´t synchronize my calendar
Does anyone can give me the steps to follow?
Many thanks in advance!
Claudia
log_CalDavSynchro.txt
@aluxnimm commented on GitHub (Aug 31, 2016):
401 means you can't authorize. Is the DAV url and username/password correct? Does test settings work? What caldav calendar server are you using or is it a google profile?
Maybe your server needs the option "Force Basic Authentication" in network settings.
@cataclop commented on GitHub (Aug 31, 2016):
Hi thanks for your tips,
yes dav url and password are correct. Just doubled check it again but the
same error occurs.
no, the test doesn´t work "authorisation required"
I use davcal from my server provider
where can I find this option "Force basic authentication" in network
settings? I unfortunately can´t find it!
Many thanks for your big help!
2016-08-31 9:01 GMT+02:00 Alex Nimmervoll notifications@github.com:
@aluxnimm commented on GitHub (Aug 31, 2016):
Open the synchronisation profile settings, in the tree view click on the small triangle left of the profile name, and then you should see network settings. Try the different settings there, see README.md
@cataclop commented on GitHub (Aug 31, 2016):
I found it, thanks, I have click on "Force Basic Authentication" in network
settings but the bug is still there:
CalDavSynchronizer.DataAccess.WebDavClientException: Error al enviar la
solicitud. ---> System.Net.Http.HttpRequestException: Error al enviar la
solicitud. ---> System.Net.WebException: Se ha terminado la conexión: Una
conexión que se esperaba que se mantuviera activa fue cerrada por el
servidor.
en System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
en System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- Fin del seguimiento de la pila de la excepción interna ---
en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task
task)
en
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
en System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
en
CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__9.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se
produjo la excepción ---
en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task
task)
en
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
en
CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__7.MoveNext()
--- Fin del seguimiento de la pila de la excepción interna ---
en
CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.d__7.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se
produjo la excepción ---
en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task
task)
en
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
en System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
en
CalDavSynchronizer.DataAccess.CalDavDataAccess.d__18.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se
produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en
CalDavSynchronizer.DataAccess.CalDavDataAccess.d__18.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se
produjo la excepción ---
en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task
task)
en
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
task)
en
CalDavSynchronizer.Implementation.CalDavRepository
1.<GetAllVersions>d__8.MoveNext() --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción --- en System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) en System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) en GenSync.Synchronization.Synchronizer7.d__17.MoveNext()how can I read READ.MD ? I can´t open it :(
thanks again!
Claudia
2016-08-31 12:42 GMT+02:00 Alex Nimmervoll notifications@github.com:
@aluxnimm commented on GitHub (Aug 31, 2016):
You can read it on the main page here when you scroll down.
You get a different error now, authentication seemed to work.
I guess you will also need "Close connetion after each request" enabled and mabye enable UnsafeHeaderParsing,
In the install dir (The default is
'C:\Program Files (x86)\Gerhard Zehetbauer\CalDavSynchronizer') you will find the app config fileIn this section you can also allow UnsafeHeaderParsing if the server sends invalid http headers.
@cataclop commented on GitHub (Aug 31, 2016):
Well, I did forget to delete before "Calendly" app Ithat was also creating
conflict :( :( so I did remove it and now the CalDavSynchronizer works
very well!
THANKS so much! You made a happy non-expert user :) :)
2016-08-31 12:59 GMT+02:00 Alex Nimmervoll notifications@github.com: