All clietns which uses EWS are broken, f.e. Hi, we have the same problems with EWS on WinServer2016 (Patchlevel Jan2023) and latest CU for Exchange 2016. Are more users complaining about EWS problems in the comments. Installed KB5023038-圆4-en.exe for Exchange Server 2016. 'Something went wrong…' and 'Connection problem'. The data field contains the error number. A user with the alias nak_87 also posted some comments about issues (ASP.NET (1325) and WAS (5011) errors) in the Techcommunity article about the security updates.įatal communication error in the Windows Process Activation Service for a process for the application pool 'MSExchangeServicesAppPool'. This is just an addition, in case you want to write another article about this topic.Īt this point my thanks to the readers. On the other hand, access to calendars whose mailboxes are located on unpatched servers works without any problems. I can confirm this from our environment:įor example, access to shared calendars whose mailbox is on a system that has already been patched is also no longer possible ('Calendar could not be updated'). Februar 2023) … there are now more and more hints that there are EWS problems. In the comments to your article: Exchange Server Sicherheitsupdates (14. Īfter blog reader Martin contacted me today with the following mail, I pulled out the hints in this blog post separately. Message: Deserialization of type System.MarshalByRefObject blocked due to InDeny at location ClientExtensionCollectionFormatter. This is how I understand the StackTrace from the event log with ID 1325 Apparently a fix in the current patch has a deserialze issue and ends up in a 'deny' which is supposed to mitigate something in the code somewhere. Practically everything that is based on EWS only works sporadically or not at all.Īnd German blog reader Enno added in this comment:ĮWS problems I have too and we just rolled back the update. Server side search not working, addins not loading, scheduling wizard or calendar shares taking forever to load…. The reports are increasing about EWS crashes and the associated problems.

nk writes in this German comment (I've translated it):

Comments then came in from the readership about issues with EWS (Exchange Web Services).

I had reported in the blog post Exchange Server Security Updates (February 14, 2023). As of FebruMicrosoft has released the security updates for Exchange 2013 to 2019 to address various security vulnerabilities.

Outlook 2019 exchange 2016