Shared Calendar – Unable to Delete Entries in eM Client (Exchange 2019 On-Prem)

Calendar
1

Hi,

I previously opened a ticket regarding this issue but didn’t get a resolution, so I’m creating a new one with updated details.

We have a shared calendar on our on-premises Exchange Server 2019. Users with full owner rights are unable to delete items in eM Client since about 2 months ago. However, the same users can delete those calendar entries in Outlook without any issue.

Steps already taken:

  • Upgraded to the latest eM Client version.
  • Verified that permissions are correctly set (users have full read/write/owner access).
  • Tested with multiple users (same problem).
  • Confirmed the issue only occurs in eM Client, not in Outlook.
  • Looked for relevant logs under C:\inetpub\logs\LogFiles and C:\Program Files\Microsoft\Exchange Server\V15\Logging\Ews, but couldn’t find anything useful after reproducing the issue.

Request:

  • Can you advise what exact logs you need (EWS or CalDAV) and how to generate them in eM Client to troubleshoot?
  • Is this a known compatibility issue with Exchange 2019 shared calendars in eM Client V10?
  • Any recommended workaround or fix?

Thanks in advance for your help.

2

UPDATE:

dug through the EWS traces. event creation goes through fine, CreateItem works, server returns the ItemId + ChangeKey, no problem there. when i hit delete in em client though… there is no DeleteItem request going out at all.

instead the client keeps hammering GetFolder against the shared mailbox [email protected]. tries msgfolderroot, inbox, drafts, deleteditems, sentitems. every single one comes back with ErrorItemNotFound or ErrorFolderNotFound – literally “Das angegebene Objekt wurde im Informationsspeicher nicht gefunden”

so what’s happening: em client never gets past resolving the folder ids, it can’t find the right target folder, so it never even issues the actual delete call. outlook handles the same mailbox + rights fine, so it’s not perms, owner rights are there.

this looks like a bug in how em client resolves distinguished folders in a delegated/shared mailbox on exchange 2019. the rights are there, exchange replies correctly when outlook asks, only em client is choking.

need confirmation if this is a known regression in 10.3.x or if there’s a fix coming.

3

Anyone?

4

Same here but with an M365 account. Error message like “The special folder could not be created”. Maybe some localization issue?

1 Like
5

We are located in Austria, EU. You also?

6

Germany. Though I just checked switching the UI to english, no change. “Cannot create special folder”
The fun thing is, I can simply move it to local folders and then delete it there.

1 Like