[GH-ISSUE #91] Unable to connect Exception should be warning #989

New issue

Closed

opened 2026-03-13 23:43:47 +03:00 by kerem · 2 comments

kerem commented

2026-03-13 23:43:47 +03:00

Owner

Originally created by @maybeec on GitHub (Jan 4, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/91

I got the following exception:

<?xml version="1.0" encoding="utf-16"?>
<SynchronizationReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <ProfileName>NONSENSE</ProfileName>
  <ProfileId>d20d7d59-d52b-4972-a770-949eee35a303</ProfileId>
  <StartTime>2016-01-04T08:39:59.1878696Z</StartTime>
  <InitialEntityMatchingPerformed>false</InitialEntityMatchingPerformed>
  <LoadErrors />
  <EntitySynchronizationReports />
  <ExceptionThatLeadToAbortion>System.Net.Http.HttpRequestException: An error occurred while sending the request. ---&gt; System.Net.WebException: Unable to connect to the remote server ---&gt; System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable host NONSENSE
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket&amp; socket, IPAddress&amp; address, ConnectSocketState state, IAsyncResult asyncResult, Exception&amp; exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext&amp; context)
   at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.&lt;ExecuteWebDavRequest&gt;d__a.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.&lt;ExecuteWebDavRequestAndReadResponse&gt;d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CalDavSynchronizer.DataAccess.CalDavDataAccess.&lt;GetEntities&gt;d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at GenSync.Synchronization.Synchronizer`6.&lt;SynchronizeNoThrow&gt;d__4.MoveNext()</ExceptionThatLeadToAbortion>
  <Duration>00:00:06.2303564</Duration>
</SynchronizationReport>

I am quite sure, that this issue arises as I connected to a VPN, while synchronization was starting/running. Nevertheless, maybe it might be more convenient to just log this as a warning if it occurs once to not bother the user with unnecessary exceptions.

I am looking forward to test your free Outlook Add-in as I tried nearly all available DAV-sync software for Outlook available. None of them has been proven stable enough to synchronize productive data.
Until now, I am impressed of yours :) Good job!
Thanks for submitting this to the open source community!

Originally created by @maybeec on GitHub (Jan 4, 2016). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/91 I got the following exception: ``` <?xml version="1.0" encoding="utf-16"?> <SynchronizationReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <ProfileName>NONSENSE</ProfileName> <ProfileId>d20d7d59-d52b-4972-a770-949eee35a303</ProfileId> <StartTime>2016-01-04T08:39:59.1878696Z</StartTime> <InitialEntityMatchingPerformed>false</InitialEntityMatchingPerformed> <LoadErrors /> <EntitySynchronizationReports /> <ExceptionThatLeadToAbortion>System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable host NONSENSE at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context) at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar) --- End of inner exception stack trace --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.<ExecuteWebDavRequest>d__a.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CalDavSynchronizer.DataAccess.HttpClientBasedClient.WebDavClient.<ExecuteWebDavRequestAndReadResponse>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at CalDavSynchronizer.DataAccess.CalDavDataAccess.<GetEntities>d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at GenSync.Synchronization.Synchronizer`6.<SynchronizeNoThrow>d__4.MoveNext()</ExceptionThatLeadToAbortion> <Duration>00:00:06.2303564</Duration> </SynchronizationReport> ``` I am quite sure, that this issue arises as I connected to a VPN, while synchronization was starting/running. Nevertheless, maybe it might be more convenient to just log this as a warning if it occurs once to not bother the user with unnecessary exceptions. I am looking forward to test your free Outlook Add-in as I tried nearly all available DAV-sync software for Outlook available. None of them has been proven stable enough to synchronize productive data. Until now, I am impressed of yours :) Good job! Thanks for submitting this to the open source community!

kerem closed this issue

2026-03-13 23:43:52 +03:00

kerem commented

2026-03-13 23:43:57 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jan 4, 2016):

Thank you very much!
You are right, those network connection issues should not trigger an error report. The reporting and logging feature is still in development and will be improved.

@aluxnimm commented on GitHub (Jan 4, 2016): Thank you very much! You are right, those network connection issues should not trigger an error report. The reporting and logging feature is still in development and will be improved.

kerem commented

2026-03-13 23:44:03 +03:00

Author

Owner

@aluxnimm commented on GitHub (Jan 11, 2016):

Check if online will be performed before sync run to avoid such reports, will be in release 1.14.0.

@aluxnimm commented on GitHub (Jan 11, 2016): Check if online will be performed before sync run to avoid such reports, will be in release 1.14.0.