I am getting the following error message when opening up eM Client can you please help:
eM Client (6.0.19714.0)
Windows: Microsoft Windows NT 5.1.2600 Service Pack 3, Framework: 2.0.50727.3649
The following error has occurred:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MailClient.Protocols.Common.FolderSynchronizer.GetFolderPath(Folder[] folders, Folder folder)
at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass5.b__1(CompletionEventArgs completionEventArgs)
at MailClient.Protocols.Common.RequestIssuer.<>c__DisplayClass5.b__0(Object sender, CompletionEventArgs e)
at MailClient.Commands.Command.Complete()
at MailClient.Commands.Command.Process(WorkerStatus status)
at MailClient.Commands.SynchronizationQueue.ThreadWorker(Object threadData)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
Traced the fault to a mixture of a badly migrated mailbox to office365, It would seem that Em Client does not like imap folders within exchange. Also Em client doesn’t seem to run very well unless the user logged on has local administrator privileges.
Running Windows 8.1
Installed .NET 3.5 Framework
Uninstalled and reinstalled em Client
I too am getting this error, trace follows;
eM Client (6.0.20899.0)Windows: Microsoft Windows NT 6.2.9200.0, Framework: 4.0.30319.34014
The following error has occurred:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at Microsoft.Xna.Framework.LzxDecoder.ReadLengths(Byte[] lens, UInt32 first, UInt32 last, BitBuffer bitbuf)
at Microsoft.Xna.Framework.LzxDecoder.Decompress(Stream inData, Int32 inLen, Stream outData, Int32 outLen)
at MailClient.Protocols.OfflineAddressBook.OabFolderSynchronizer.UncompressLzx(Stream fullFile, Stream outputFile)
at MailClient.Protocols.OfflineAddressBook.OabFolderSynchronizer.GetFolderList(Folder homeFolder, CancellationToken cancellationToken)
at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass5.b__0(WorkerStatus status, CancellationToken cancellationToken) at MailClient.Protocols.OfflineAddressBook.OabGenericCommand.Execute(WorkerStatus status) at MailClient.Commands.Command.Process(WorkerStatus status) at MailClient.Commands.SynchronizationQueue.ThreadWorker(Object threadData) at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart(Object obj)
Hi Danish, do you have .NET framework 4 installed on your computer, in it’s latest available version (4.5.2)?
Also, can you please try to install this update http://www.emclient.com/dist/v6.0.20968/setup.msi and check if the issue persists?
However when I launched it this morning it said update was available, installed update and the problem came back, so i uninstalled and reinstalled from your link and it is working correctly again.
Hi Danish, what version of eM client are you currently using then, do you remember what version did you previously update to?
This is the latest release that should contain all recent bug fixes regarding this situation, I believe it would be best to use this version:
I hope everything is working properly with the latest release, if you come across any other issues or questions, please let me know, I’ll be happy to help.
Hi again Danish, if you’re currently using the above posted version, please download this update that still contains some bug fixes regarding the issues you were having, http://www.emclient.com/dist/v6.0.21034/setup.msi (you might have already received this update).
Glad everything is working properly, please let us know if you come across any other issues or questions, we’ll be happy to help.