question

HedwigPoon-0862 avatar image
0 Votes"
HedwigPoon-0862 asked EricYin-MSFT commented

Exchange 2016 CU 20 High CPU

Hi,

I did a search but had trouble narrowing down to my specific so, hopefully, this is not a repost.


Running Exchange 2016 Std virtualized in WS2016 Std environment. Installed CU20 fine. Rebooted. Now Exchange services takes 30 minutes to load and, usually, not everything starts. After waiting, I tend to need to manually start Frontend Transport and a few other required services.

Also, two other issues have propped up. After a while (not set time period), a CMD process pops up and uses 80-90%+ CPU and 4-6GB or memory. This grinds Exchange down to a halt. I log in and run Task Manager. When it comes to, I terminate that CMD process and everything is fine again.

The other issue is that I can no longer install any Microsoft Updates after CU20. It downloads and installs then I get the "reverting back" after a few reboots.

None of the old WS2012 Std / Exchange 2013 Std setups are affected. All the WS2016 Std/Exchange 2016 Std setups experience the same issue.

Any suggestions?

Thanks in advance,
Hedwig Poon

office-exchange-server-itpro
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
In my lab(CU20), no issues like you describe have appeared.

1 How often does the CMD show? What does it say if you don't stop it?

2 Do you have other servers with Win2016 with no Exchange server installed or with other CUs of Exchange 2016 installled? Test if they can install Windows updates.
Check the Event log. there might be errors telling you the reason.


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


0 Votes 0 ·
HedwigPoon-0862 avatar image
0 Votes"
HedwigPoon-0862 answered

Hi Eric,

Thanks for responding.

  1. No set time period. It has started to happen on the 2016 sites shortly after CU20. It happens once every 1-2 days. Very random too. If I don't stop it, it will just soak up CPU cycles and bog Exchange down to the point that all local Outlook say they've been disconnected.

  2. Other WS2016 would be the Hyper-V host and the Hyper-V guest for A/D. Those can run Microsoft Updates fine. The problem sites are all Hyper-V guest with Windows Server 2016 Std and Exchange 2016 Std (domain joined).

I checked the event viewer but I couldn't find any specific error listing that coincided with the CMD process. It had lots of error launching Exchange services but eventually they launch.

I've read somewhere some people were having W3WP error. Sometimes, I pop in via OWA to see if it's still working (quick response). If the just spins, I figured it's got that CMD process again. I wonder if OWA is causing it.

Hedwig



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HedwigPoon-0862 avatar image
0 Votes"
HedwigPoon-0862 answered EricYin-MSFT commented

Spoke too soon. One site just spiked CPU.

86016-exchange-highcpu.jpg

Also, these events are shown:

85996-exchange-appsevents.jpg
86056-exchange-systemevents.jpg
86057-exchange-tlsevent.jpg


I've attached a renamed EVTX file as a .log so I can upload it. 86061-21-04-08-eventsevtx.log


Lastly, after terminating the CMD process, I see these in the event viewer (looks OWA related).

85986-exchange-appsevents-afterendtask.jpg



Regards,
Hedwig


· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thx for those.

No proxy servers are used and I ran Qualys SSL test to confirm sites are using TLS 1.2. The second link page discussed enabling the TLS in registry after adding the SCHANNEL keys so I did. We'll see.

I disabled OWA to test but it still had the CMD pop up. In fact, I just checked and the rogue CMD process popped up again using 76%+ CPU so launch Task Manager takes a long time.

Terminating that process restores function.

Further, in checking the error/warning/critical list of the Event Viewer, the Application log shows OWA related issues as well as ASP.NET 4.0.30319.0 listing. I did Recycle the Application Pools items per the link.

Is there a way to revert back to CU19? I did not experience this issue with that update.

Thx again.

Hedwig

0 Votes 0 ·

Hi,
Is your server directly installed with Exchange 2016 cu20, if so, the answer is no. You can only revert back from your full backup.
Does enabling tls 1.2 make a change?

0 Votes 0 ·
Show more comments