[GH-ISSUE #160] bug in synchronizing #159

Closed
opened 2026-02-25 20:31:01 +03:00 by kerem · 6 comments
Owner

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

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](https://github.com/aluxnimm/outlookcaldavsynchronizer/files/446095/log_CalDavSynchro.txt)
kerem closed this issue 2026-02-25 20:31:02 +03:00
Author
Owner

@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.

<!-- gh-comment-id:243676356 --> @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.
Author
Owner

@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:

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.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160#issuecomment-243676356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUXAOZgson4SAZIq1B3PLFyqweg4WyKOks5qlSbkgaJpZM4JxEqV
.

<!-- gh-comment-id:243724836 --> @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: > 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. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160#issuecomment-243676356, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AUXAOZgson4SAZIq1B3PLFyqweg4WyKOks5qlSbkgaJpZM4JxEqV > .
Author
Owner

@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

<!-- gh-comment-id:243726763 --> @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
Author
Owner

@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.CalDavRepository1.<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:

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


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160#issuecomment-243726763,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUXAOdUZCb59g41tKR1lzIdS1LYEn2BVks5qlVqKgaJpZM4JxEqV
.

<!-- gh-comment-id:243728779 --> @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.<ExecuteWebDavRequest>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.<ExecuteWebDavRequestAndReadResponse>d__7.MoveNext() --- Fin del seguimiento de la pila de la excepción interna --- en CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.<ExecuteWebDavRequestAndReadResponse>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.<GetVersions>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.<GetVersions>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.Synchronizer`7.<SynchronizeNoThrow>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: > 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 > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160#issuecomment-243726763, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AUXAOdUZCb59g41tKR1lzIdS1LYEn2BVks5qlVqKgaJpZM4JxEqV > .
Author
Owner

@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 file

CalDavSynchronizer.dll.config

In this section you can also allow UnsafeHeaderParsing if the server sends invalid http headers.

<system.net>
    <settings>
        <servicePointManager expect100Continue="false" />
        <httpWebRequest useUnsafeHeaderParsing="true" />
    </settings>
</system.net>
<!-- gh-comment-id:243730316 --> @aluxnimm commented on GitHub (Aug 31, 2016): You can read it on the main page [here](https://github.com/aluxnimm/outlookcaldavsynchronizer) 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 file ``` CalDavSynchronizer.dll.config ``` In this section you can also allow UnsafeHeaderParsing if the server sends invalid http headers. ``` <system.net> <settings> <servicePointManager expect100Continue="false" /> <httpWebRequest useUnsafeHeaderParsing="true" /> </settings> </system.net> ```
Author
Owner

@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:

You can read it on the main page here
https://github.com/aluxnimm/outlookcaldavsynchronizer 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 file

CalDavSynchronizer.dll.config

In this section you can also allow UnsafeHeaderParsing if the server sends
invalid http headers.

<system.net>




</system.net>


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160#issuecomment-243730316,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUXAOfRb7L0LK5tkZvdf_AeJ1Mfl_bEtks5qlV6TgaJpZM4JxEqV
.

<!-- gh-comment-id:243734742 --> @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: > You can read it on the main page here > https://github.com/aluxnimm/outlookcaldavsynchronizer 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 file > > CalDavSynchronizer.dll.config > > In this section you can also allow UnsafeHeaderParsing if the server sends > invalid http headers. > > <system.net> > <settings> > <servicePointManager expect100Continue="false" /> > <httpWebRequest useUnsafeHeaderParsing="true" /> > </settings> > </system.net> > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/160#issuecomment-243730316, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AUXAOfRb7L0LK5tkZvdf_AeJ1Mfl_bEtks5qlV6TgaJpZM4JxEqV > .
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/outlookcaldavsynchronizer#159
No description provided.