I am evaluating eM client. Downloaded fresh from your site 3 days ago.
Setting up an account with our company Exchange 2010 works well. However, the folder tree is garbled in some places where sub folders are placed under the wrong parent.
I also seem to have problems with synching mail in some large exchange folders. eM Client crashes. have deleted and recreated the account and will see if it reappears.
Hi, can you make a screenshot of the wrong folder structure, you’re seeing?
If the application is crashing can you see the crash log once you open the application again?
eM Client (6.0.20154.0)
Windows: Microsoft Windows NT 6.2.9200.0, Framework: 4.0.30319.18449
The following error has occurred:
System.OutOfMemoryException: Exception of type ‘System.OutOfMemoryException’ was thrown.
at System.String.Split(String[] separator, Int32 count, StringSplitOptions options)
at MailClient.Utils.Tracing.SafeFileWriterWithTimestamp.Write(String value)
at MailClient.Protocols.Exchange.ExchangeAccount.EwsTraceListener.Trace(String traceType, String traceMessage)
at Microsoft.Exchange.WebServices.Data.ExchangeServiceBase.TraceXml(TraceFlags traceType, MemoryStream stream)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.TraceResponseXml(IEwsHttpWebResponse response, MemoryStream memoryStream)
at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.ReadResponse(IEwsHttpWebResponse response)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest1.Execute() at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalLoadPropertiesForItems(IEnumerable1 items, PropertySet propertySet, ServiceErrorHandling errorHandling)
at Microsoft.Exchange.WebServices.Data.ExchangeService.LoadPropertiesForItems(IEnumerable1 items, PropertySet propertySet) at MailClient.Protocols.Exchange.ExchangeItemSynchronizer2.d__4.MoveNext()
at System.Linq.Enumerable.d__31`3.MoveNext()
at System.Linq.Enumerable.d__23`2.MoveNext()
at MailClient.Protocols.Common.ItemSynchronizeContext2.StoreItems(SynchronizationType synchronizationType, IEnumerable1 newItems)
at MailClient.Protocols.Common.MailItemSynchronizeContext.StoreItems(SynchronizationType synchronizationType, IEnumerable`1 newItems)
Hi, from the screenshot, I’m not completely sure how the folder structure should look like… Can you maybe make a screenshot of the structure in webmail as well?
The folders are sorted alphabetically in the list, but if it should be under a different folder that’s quite of an odd issue… Did you try repairing the mail folder by right clicking the mail account and selecting Properties > Repair, and click on the repair button?
Hi again, I’ve received the logs, can you please try updating your client to this version (http://www.emclient.com/dist/v6.0.20224/setup.msi), Try the repair function once you do so, and let me know if it solved the issue.
seems to be a new crash error:
eM Client (6.0.20224.0)
Windows: Microsoft Windows NT 6.2.9200.0, Framework: 4.0.30319.18449
The following error has occurred:
System.NullReferenceException: Object reference not set to an instance of an object.
at MailClient.Protocols.Exchange.ExchangeItemSynchronizer`2.b__4(ItemChange c)
at System.Linq.Enumerable.ToLookup[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer)
at System.Linq.Enumerable.GroupBy[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer)
at System.Linq.Enumerable.GroupBy[TSource,TKey](IEnumerable1 source, Func2 keySelector, IEqualityComparer`1 comparer)
at MailClient.Protocols.Exchange.ExchangeItemSynchronizer`2.d__6.MoveNext()
at System.Linq.Enumerable.d__31`3.MoveNext()
at System.Linq.Enumerable.d__23`2.MoveNext()
at MailClient.Protocols.Common.ItemSynchronizeContext2.StoreItems(SynchronizationType synchronizationType, IEnumerable1 newItems)
at MailClient.Protocols.Common.MailItemSynchronizeContext.StoreItems(SynchronizationType synchronizationType, IEnumerable`1 newItems)
Hi Peter, I’ve discussed the issue with the developers and they are working on a fix, but unfortunately we can not provide an immediate solution. The issue is caused by a non-standard case that has been used possibly when we were solving the issue previously.
The issue should be fixed with an upcoming release.
I’m sorry for this obstacle, and I hope you’ll give the application a chance once the issue is resolved. I’ll try to keep you posted about the update.
Hi, i don’t have much more information about the issue.
If you want to extend your trial period, can you please contact our sales department at [email protected]