Stefano,

We are not experiencing the same problem, but that same error is reported with a buggy Microsoft Outlook patch released on July 15.

Could be the same issue.

Ron

Thanks Ron, it's such a pity having this problem with MAPI.

The MAPI feature is so much important for us, I hope it will be solved soon :)

Hi Stefano, it's seems to be an Outlook issue, not an SM issue.

It's seems to be related to a broken update that Microsoft has released that could crash Outlook connected to Exchange (yes, Exchange! So it's not a SM fault...).

Check this tweet: https://twitter.com/MSFT365Status/status/1283450504865964032

Hi Gabriele, it can be, but it's something that is coming from JUNE, I hoped that in September the thing was fixed.

BTW, all the computers with that problem, has the latest patch of Office 2019.

We also have this problem just on some computers, others are working fine.

We have narrowed down a scenario that is causing Outlook to crash and we are working with the protocol team at Microsoft and they are looking into it.

Thanks Tim, I hope there will be a fix soon 😊

Is that just related to MAPI / Exchange?

This is just related to the MAPI protocol and has something to do with a particular property on Contacts, Tasks, Notes that have been modified multiple times.  We were finally able to duplicate the behavior and demonstrate it to the Microsoft protocol team.  They have spent the last week trying to figure it out and we are talking to them everyday.

That's sound a bit crazy 😊
I keep my finger crossed and I hope in a quick solution

The MAPI protocol is CRAZY!

How's this coming? With confidence that Outlook will be stable we'd like to ASAP update a test sever. This post re- Outlook concerns us.