Share via


MsExchangeServiceAppPool High CPU Usage

Question

Wednesday, May 6, 2020 11:44 AM

Hello to the great connoisseurs of exchange.

Recently a disaster happened, 3 of 4 exchange 2016 mbx servers were lost. (Do not ask :))

I had to urgently deploy 3 servers, migrate the database and restore mailboxes.

I ran into an unusual problem. The CPU began to load, judging by the IIS, MsExchangeServiceAppPool. Honestly,
I don’t know which way to look.

There is nothing critical in the logs. Scolding on recover bases that are not mounted. There are a couple of logs on database indices. IIS does not write anything critical to the logs. EWS development tools are not worth it. There is no balancer. Each has its own URL. There are no DAGs either. Judging by what I see in IIS, I get stuck.
I really hope for expert help.

sorry for the russian language on screen

log parser, shows a huge number of 500 errors. can this affect cpu? P.S. 5 thousand mailboxes were turned off and included in new databases

All replies (8)

Wednesday, May 6, 2020 11:55 AM

yes, files grow very fast


Thursday, May 7, 2020 7:32 AM | 1 vote

Following might be useful,

https://techwizard.cloud/2015/06/04/exchange-2010-ecp-app-pool-high-cpu-issue/

further more, configure circular logging and logs file management as below,

https://practical365.com/exchange-server/powershell-script-iis-logs-cleanup/

https://gallery.technet.microsoft.com/clear-exchange-2013-log-71abba44

https://expert-advice.org/exchange-server/move-truncate-logs-exchange-server-2013/


Thursday, May 7, 2020 7:36 AM

Make sure to add AV exclusion for your Exchange as best practice,

/en-us/exchange/antispam-and-antimalware/windows-antivirus-software?view=exchserver-2019

https://gallery.technet.microsoft.com/office/Generate-Antivirus-f1a9a59e


Thursday, May 7, 2020 9:14 AM

Hi Vilgelm Fokht,

Agree with Akshay M. You can download and use Log Parser Studio to analyze the logs and find out which user or devices are hitting the server the most. Attach the Instructions for your reference: Getting Started with Log Parser Studio - Part 1/ Part 2

Also it is recommended to do the following actions, please check whether they can be helpful:

a. Recycle MsExchangeServiceAppPool or restart the entire IIS service;

b. According to this document, please update your Exchange server to the latest version Cumulative Update 16 for Exchange Server 2016.

Regards,

Vincy Cao

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].


Thursday, May 7, 2020 1:08 PM

Hey.
thanks for the answer.

I am currently collecting a dump of the process, maybe this will bear fruit.
I'll be back with the result later.


Thursday, May 7, 2020 1:09 PM

Hi.

I have already collected statistics for the EWS 500 error.
There are really many deviations.
Can they affect processor load?

Or is it worth looking at cyclic connections?


Tuesday, May 12, 2020 9:17 AM

Hi Vilgelm Fokht,

Did the suggestions listed in the previous post help you:

“a. Recycle MsExchangeServiceAppPool or restart the entire IIS service;

b. According to this document, please update your Exchange server to the latest version Cumulative Update 16 for Exchange Server 2016.”

According to your updates, could you provide the detailed EWS 500 error information? It will be helpful for troubleshooting.

And what’s  the result if you follow the advise provided by Udara Kaushalya?

Regards,

Vincy Cao

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].


Friday, May 15, 2020 7:00 AM

Hi Vilgelm Fokht,

Any update now?

If you have any questions or needed further help on this issue, please feel free to post back. If the above suggestion helps, please be free to mark it as answer.

Regards,

Vincy Cao

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].