web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

100% CPU usage Prod.client.webCoreApp

(0) ShareShare
ReportReport
Posted on by 7

We’re experiencing over 100% CPU usage by one of our new instances, specifically the Prod.Client.WebCoreApp process. Yesterday it actually hit 117%!

Obviously whilst this happens, all 25 users cannot use Business central as it essentially times out under the load. Some will get a network disconnected error in their BC app screen.

Our go live day was Monday this week; the issue first started in the afternoon of day 2, with a full reboot being the only way to resolve. 

By the 3rd day, after disabling the Azure AAD functionality this dropped to only happening at 5:15, and was only then resolved by restarting the IIS twice.

We found an article relating to SPN and added SPN on Self permission to the account on the sever which runs the instance. 

Today being day 4, the issue didn’t happen agin until 4:45, whereby the same overloading of the CPU occurred. restarting the IIS again resolved it.

It’s the latest 2019 release, but 1 cumulative update is available i believe. The only reason we haven’t done this is because the test system didn’t have this issue.

This sever has two gold standard processors with plenty of RAM so physics performance should not be the issue.

Under test environment for the last 2 or 3 months, this was not an issue. The load throughout the day is absolutely fine with all users connected and it’s not until the end of the day this then occurs. Searching online for issues related to the service don’t yield any resolutions, hence my comment here for help.

on the processor monitoring it seems to ramp up from an average of about 6% usage to over the 100 for a few minutes; then takes a short dip before returning to 100 again, all causing such slowness for users that they simply cannot use BC.

interestingly the other two instances we are running do not have their process hitting such cpu heights. The other two are used for a web interface and the scheduler service.

any suggestions welcome.

A3ED015A_2D00_6B46_2D00_4988_2D00_90AB_2D00_973FF37329C9.jpeg

09CA29BE_2D00_2C72_2D00_427E_2D00_BC74_2D00_7A5AB5B68512.jpeg
F9A414EF_2D00_114E_2D00_4C01_2D00_AC64_2D00_E699F10936CB.jpeg


regards

Paul

*This post is locked for comments

I have the same question (0)
  • Corrado Lembo Profile Picture
    15 on at

    Do you have solved?

  • Olli_Samuelson Profile Picture
    5 on at

    Is there any solution for this.

    We have the same problem.

    Best Regards

  • ManishS Profile Picture
    86 on at

    Did you found the reason what and why it is getting triggered.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans