Today we are announcing the latest set of Cumulative Updates for Exchange Server 2016 and Exchange Server 2013. These releases include fixes to customer reported issues and updated functionality. Exc...
Updated Jul 01, 2019
Version 2.0
Blog Post
@Benoit - We are already aware of this issue. We are working on a fix.
- hi Brent, any word on the fix for the ExSMIME.dll issue? Thanks
- Thank Brent.
Is the DevTeam currently aware of a CPU congestion issue when using Windows Server 2016 ? I have three servers with the same symptoms: setup goes fine but at some point IIS worker processes start going grazy and consume all CPU. It's a lab/non-production environment where there is no user load. Restarting IIS (or the server) has no effect (problem starts again when the AppPools start). Strangely, all IIS worker processes seem to be impacted, so I would suspect an issue related to the .NET 4.6.2 framework or IIS itself. Using Win2016 RTM (Eval) and all available patches installed.
Technet (https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx) doesn't ask for any mandatory hotfix for .NET 4.6.2, neither request that some framework "hack" should be implemented.
Any hint? Thanks.
- @Benoit - We have not seen this behavior. You would need to reach out to support services and have them assist you in determining what is happening.
- Right, it's just a development lab. However I am able to reproduce the problem every time I install new servers. Symptoms are always the same. Server runs fine, then with no apparent reason, IIS AppPools start crashing with a System.NullReference exception. Managed Availabilty probes create a loop: AppPools are restarted, then crash again when probes activity occur. Stopping and disabling the MSExchangeHM and MSExchangeHMRecovery stopped the crashes. Strangely, RemotePS was affected too. While ti was working fine initially, I suddenly could no longer use the RPS web service, however proxying (using the TargetServer Uri param) through another (unaffected) server worked fine. This leads to think that only the CAFE is affected. With MSExchangeHM disabled, and after a couple restarts, RemotePS was back. No idea why this is happening, Servers are running in Hyper-V 2012 R2 and are largely under-sized (again it's a dev lab). However I have others servers of the same size (and same host/disks/etc) on Win 2012 R2 and they run normally.
Strange...
PS: I'm not asking for any kind of support here, only passing out some info... :)