Ok, first I’ll ask you for one more log file, go to Tools > Settings > Advanced and turn on Network Communication logging, again save the settings, restart the application, when the issue occurs (immediately I guess), go back to the advanced settings window and send me the logs ([email protected]).
The testing account on your server would be great, so maybe send me the necessary information for setup with that log email.
Thank you, I’m sorry you’re experiencing this,
Paul.
Hi,
Previous configuration that worked perfectly with CalDAV & CardDAV:
- Synology with DSM 4.3
- Owncloud 6.0.1
Current configuration does not work with CalDAV & CardDAV
- Synology with DSM 5.0
- Owncloud 6.0.1 and 6.0.2
I receive the same error message:
01:45:44 home [CalDAV / CardDAV] MailExceptions.ConnectionException: La connexion sous-jacente a été fermée : Une erreur inattendue s’est produite lors de l’envoi. —> System.Net.WebException: La connexion sous-jacente a été fermée : Une erreur inattendue s’est produite lors de l’envoi. —> System.IO.IOException: Réception d’un EOF inattendu ou de 0 octet du flux de transport.
01:45:44 à System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
01:45:44 à System.Net.PooledStream.EndWrite(IAsyncResult asyncResult)
01:45:44 à System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
01:45:44 — Fin de la trace de la pile d’exception interne —
01:45:44 à System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
01:45:44 à System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)
01:45:44 à MailClient.CalDav.ProtocolCommands.RequestCommand.Execute(HttpWebRequest httpRequest, CancellationToken cancellationToken, Action`1 logBody)
01:45:44 à MailClient.CalDav.ProtocolCommands.Connector.RunCommand(CalDavAccount account, ICommand command, CancellationToken cancellationToken)
01:45:44 — Fin de la trace de la pile d’exception interne —
01:45:44 à MailClient.CalDav.ProtocolCommands.Connector.RunCommand(CalDavAccount account, ICommand command, CancellationToken cancellationToken)
01:45:44 à MailClient.CalDav.Synchronizer.BootstrapCommand.UpdateOptions(Uri[] baseUris)
01:45:44 à MailClient.CalDav.Synchronizer.BootstrapCommand.Execute(WorkerStatus status)
01:45:44 à MailClient.Commands.Command.Process(WorkerStatus status)
EM Client CardDAV log:
01:45:24.058|011| C: OptionsCommand https://myservername/owncloud/remote.php/carddav/addressbooks/home/
EM Client extract of Network log:
01:45:18.093|001| eM Client: 6.0.20154.0, .NET: 2.0.50727.5477, OS: Microsoft Windows NT 6.1.7601 Service Pack 1
…
01:45:44.805|004| System.Net Error: 0 : [2544] Exception in the HttpWebRequest#58408916:: - La connexion sous-jacente a été fermée : Une erreur inattendue s’est produite lors de l’envoi.
01:45:44.805|011| System.Net Verbose: 0 : [1292] HttpWebRequest#58408916::EndGetRequestStream()
01:45:44.805|011| System.Net Error: 0 : [1292] Exception in the HttpWebRequest#58408916::EndGetRequestStream - La connexion sous-jacente a été fermée : Une erreur inattendue s’est produite lors de l’envoi.
…
More information : the both configuration (previous and current) is working fine for CardDav sync with my iPhone, the android smartphone and tablet.
Thank you for your help.
Pascal
Synology has released a patch for that problem. I have installed the patch, but unfortunately eM Client still can not access the CalDAV server. Could you therefore please have a look with the given data on our server, what happens with the patch? I hope this could speed up the bug fixing a lot.
Kind regards
Christian
Hi, considering your installed patch, are you still receiving the same error as Pascal posted above your reply? Or is the behavior of the application in any way different?
Can you please turn on the CalDav logging in Tools > Settings > Advanced, and send me the logs to [email protected] with a reference link to this forum topic, once you see the issue again.
Thank you,
Paul.
The behaviour is exactly the same. The logs are still empty.
Could you use the account I gave you on our server to log the poblems?
Any response???
I have the same problem, and my log files are also empty. (like Christian Beck)
20:40:10.657|013| C: OptionsCommand https://mydomain.ch/owncloud/remote.php/caldav/calendars/simon/
I using Synology DSM 5.0 (with the newest updates) and Owncloud v 6.0.3
When i setting up teh carddav option in the eM Client i will be show no error or anything. its only not work.
And again two week later and no response? Could you PLEASE have a look what error is reported within eMClient??? You have the access data to our server… If we can not find a solution here, we will most likely go with another client…
No news good news. Is it the case or not. please could you give us some feedback about a possible solution or workaround?
Hi Christian, Hi all of you…
I’m really sorry for leaving you waiting here for such a long time.
I’ve consulted this issue several times with out developers, we finally replicated your issue, thanks to the credentials Christian provided us to his server. The issue should be occurring only on Windows 7, which is why we weren’t able to replicate it sooner.
Although we still don’t have a solution for this issue, but please be patient we’re working on resolving this issue right now.
Thank you very much and sorry for the inconvenience,
Paul.
I have Windows 8 and it also doesn’t work. With another CalDav/Card Client - baikal-server - the sync works great and without any troubles.
Hi,
Today I have installed on all my windows 7 computers the last windows update components + the last version of eM Client 6.0.20310.0 on 2 of my 3 computers. I don’t know which updates have solved this issue but it seems that all is working fine now.
I have just 1 computer which cannot find the new version of eM Client 6.0.20310.0
I had to reinstall eM Client on my last computer and it also works now.
I have downloaded the latest em client and installed it by hand (no updates were found within em client). Then I had some strange effects (no calendars were found). I removed the account and recreated it. Then a carddav/caldav server was found and the different calendars were shown. Going again into the account settings, the carddav section disappeared… (the internal DSM server does not include carddav)
So I have lost ALL account settings, but it looks like em client works again with the caldav server of DSM 5.0 (including the not official DSM patch).
The bad part: The facebook connection was lost some days ago and the new version does not connect to the facebook chat. So a new problem pops up…
Any official statement from em client???
Hi, I’m really glad it started working for you, by any chance does any one of you which update did you install on your Windows 7 machine?
You can download the latest update here (http://www.emclient.com/dist/v6.0.20310/setup.msi) if your application didn’t receive the update automatically.
Christian, not sure which accounts now work and which don’t except the synology one which I understand works in your application as well now.
As to the facebook issue, can you try deleting the account and adding it again, that should help, the facebook api key has a limited time for which you can use it, it’s an issue we’re trying to work on at the moment.
Thank you,
Paul.
Hi Paul,
For information, I just update the eM Client without the latest updates of windows on the Windows 7 pc of my daughter who also had the sync problem with CardDAV. And everything works perfectly also.
So we can deduce that it is simply the update of eM Client which has fixed this bug.
Thank you for your help and have a nice week.
Pascal
I am afraid this is not true. I had two pcs, that did not work with the latest em client version. I have then updated Windows 7 and after that em Client worked without further changes. So it needed one of the latest updates.
Is em client using .net? Both pcs run the security update for .net 4.5.1 …
Yesterday on my 3 PCs windows 7, I made all windows updates including windows. NET Framework 3.5.1 and .NET Framework 4.5 and 4.5.1 + the update of eM Client. And the sync of CardDAV worked again.
Today on the pc windows 7 of my daughter, I just did the update eM Client without any windows update. It worked too.
Afterwards, I did all the windows updates including .NET framework. And it still worked.
These are my findings in my environment.
Hi all, although we’re not completely sure how this was resolved it’s both connected to latest updates of eM Client and Windows as well, in the updates you’ve probably installed there was a change from .NET framework 2 to .NET framework 4, which eM client was updated to use quite recently.
So with both of the updates the issue should be gone. If you updated only windows and you were not running eM Client using .NET 4, the issue would probably be still in place…
I hope this helps, thank you for understanding,
Paul.