Problem fixed for me as well.
The error message tells you which mailbox/which folder.
I saw that the oldest email in EM client in this folder is the first email ‘after the email causing the problem’.
I used the Outlook Web Access (Webmail), browsed the folder, looked for the email causing the problem, and deleted it. It moved the email to the trash. In EM client, error message changed to say the problem is now with the Trash folder. I searched for the email in the trash folder, and deleted it. Problem fixed.
Same error here, the useful only information I can see in the error message and stack trace is that the issue is with my Sent folder, I have removed the past 3 months work of emails that have an attachment and I am still getting the error, any idea how to narrow this down on a Mac?
I am having this problem as well, with the Sent folder only. Based on posts I saw here, I deleted all emails with attachments other than the pdf and word docs we normally use - problem persists. It’s so unfortunate that “Gary” stubbornly keeps repeating himself denying that the problem is with EMClient when it plainly is. He should be escalating this to support and fixing the problem. If your goal is to alienate customers Gary - good job. I’m done wasting my time trying to solve the problem and will just move to another client.
Same Error here since a few days:
[Exchange Web Services] personal******* An internal server error occurred. The operation failed., Property: [Calc:PersonId] PersonId, PropertyErrorCode: CorruptedData, PropertyErrorDescription: .
It keeps popping up and if I delete the oldest Mail (that seems to be the Problem) of one folder the message renews for another folder - very weird.
According to Microsoft it might be an issue with the Protocol.
I am also suddenly having the same problem everyone else is reporting. From reading this thread, apparently the problem is caused by an attachment to an email.
I went to the folder indicated in the error message and deleted every email that had an attachment, but that didn’t help.
Since this doesn’t happen with other email clients, something about the way eM Client is interacting with the server is producing the server error.
While I appreciate that this is a “Server Error” my ISP points to the client as cause. The posts from eM Client point to the server as causing the error.
Yes, there is a server error but we need help on determining the cause.
Regardless who’s “fault” it is, during the interaction between eM Client and the server, there is a message that is causing an error/abort.
Can you get any assistance in a strategy for tracking down and identifying that email for deletion?
Would deleting the eM Client database and/or removing the program and letting it rebuild the database from the server as if it were a new install be a possible solution?
I have the same issue. I tried deleting all my emails with .vcf card attachment and restart emClient but it didn´t work so at the end I will have to come back to outlook as a email client. it´s a pity as I bought a lifetime license.
This response is verging on childish. You know that there is an issue with certain types of attachments. You also know that this issue doesn’t seem to occur with any other mail client. It’s a bit like a fuel station putting the wrong fuel into one of their tanks, then someone putting that wrong fuel into an engine and the fuel station saying it’s not our problem, only the car manufacturer can fix it. That may be true, but the fuel station damn well ought to be looking into why it happened and making sure it doesn’t happen again. Like others, I have just bought a lifetime license and this is making me reconsider.
I’m having exactly the same issue with the same error. Came across this thread while searching for a solution. Adding my voice here hoping EM client tech support can offer up a path to trouble shoot or solve this. I’ve been using EM client for years and I love it, but I need to solve this.
We are having exactly the same problem. em Client was working fine for a long time then it stopped working with the error message shown many times above. It now appears that it is caused by .vcf file attachments. It did not have this problem previously but then em stopped synching folders for all our accounts. The emails with .vcf attachments work fine in our Outlook client, and they used to work in em Client as well. But likely after an update they dont work in em Client anymore. The em client is obviously formatting the attachment in a way the the server rejects since the attachment works fine with other mail clients. That makes it a Client Problem, not a Server Problem. I was blown away reading how the em support staff just blew off all customer concerns. We have been looking for an Outlook replacement, its shure not going to be em client since they refuse to fix or even acknowledge their own errors.
I find the response from the developers pathetic, especially after I just threw money away on lifetime upgrades.
If we use Outlook with exactly the same data we don’t get a problem. People have tried other mail clients and no problem. So there is clearly something that eM Client is doing to the data that messes up Exchange. It may be that Exchange should handle the malformed data better, but that’s like demanding it handles all unexpected errors - completely impractical. So either the eM Client developers get their heads out of their arses or they start losing a lot of customers. Too late for me because I’ve already paid so I’m prepared to wait a bit longer, but if I do leave, I’m not going to go quietly.
The VCF solution worked. Get rid of emails with VCF attachments and it’s fine. Shocking how Gary just blamed Microsoft for the issue. Clearly a EM Client issue as all other platforms worked just fine.
Same here: One email with VCF attachment caused the issue.
But one things seems to be different to the oder reports here. Every now and then synching was possible. So all mails did show up in emClient. But all delayed for some hours or even days.
Posting again on this topic as I’ve not been able to solve this yet. I’ve contacted Microsoft support multiple times and they say everything is working normally on the server side. The fact that all other email clients I try including Mac Mail, and Outlook are working normally without errors points to em client as the culprit. Multiple emails with Gary have resulted in no action except to tell me it’s a server issue and nothing can be done. I paid for lifetime licenses, and VIP support but Gary has stopped returning my emails. I asked if I could talk to a supervisor in the hopes this can get elevated to a higher level at em client. As others have mentioned, clearly this is a client issue of some type or the error would show up using other email clients using the same server (with the same settings). I want to keep using em client, it’s my favorite email and calendar program. This issue may force me to stop using the software. I hope someone at em client reads this and jumps in to help. This is beyond frustrating.
I am experiencing the same issue with the platform and very frustrating error message on the sent folder. It won’t update timely as a result and can’t see new messages in the sent folder for a 12-24 hr delay.
I tried archive all the emails in the sent folder to solve the vcf or attachment proposal. However, that did not resolve the error message
In an attempt to solve this issue I updated my Mac OS to the latest version 15.1 and updated eM Client to the latest version 10.1.4588 hoping that this would solve the issue.
I have 3 macs running eM Client. On one of them this error went away after all these updates, but on the other two it remained.
I then completely uninstalled eM Client from one of the problematic macs, and reinstalled it. 24 hours later the error seems to be gone and is not recurring. Fingers crossed that this holds. I suspect that there is some kind of cached file or corrupt file that is contributing to the error and once I fully uninstalled the program that file is gone therefore eliminating the problem.
I’m not a software engineer, but this is clearly some kind of eM Client related issue. As I’ve said before other mail programs I’ve tested all work without error using exactly the same servers and settings. I’m hoping that this information about a clean removal and reinstall helps others. I wish tech support had suggested that earlier.
I’m curious if others on this thread have tried a full uninstall and reinstall? Did the problem go away? Did it stay working without errors?