system job problems after on premise upgrade from 8.2 to 9.1

(0) Share

Report

Posted on by Nettsales

I am hoping someone may have seen the issue we are facing at the moment... We have just finished upgrading on premise from 8.2 to 9.1 and all went well. However now we are finding an issue where system jobs back up, causing workflows to not run, etc.

When I check the server, there is no issue with resources - plenty of RAM free and near zero CPU usage but if I restart the CRM Async service, around 1,000 system jobs process immediately. Then no more until I restart the service again and another 1,000 jobs process.

I can clear the backlog in this manner, but it's not a way to run the system!

has anyone seen similar behaviour or have an idea where we could look to try and fix this issue?

The jobs are a mix of workflows executing, Rollup fields calculating and all the other tasks that happen each day. I can't spot any particular task that is getting stuck or sitting with a timeout clogging things up.

I've also checked the database deployment and all the DB config parameters are set to the same settings as we had in 8.2.

Cheers,

Simon

I have the same question (0)

All responses (2)

Answers (0)

Community Member on at

Like (0)

Report

Hi Nettsales,

Maybe you can refer the following link:

Async Workflows and System Jobs Stop Working and Stuck with Status Reason "Waiting for Resources" (linnzawwin.blogspot.com)

Was this reply helpful? Yes No
Nettsales 20 on at

Like (0)

Report

Hi Leah,

Thanks for this and it was something we checked but the issue was slightly different in that none of the system jobs were actually failing or getting stuck. It's that the Async process is simply not processing them.

I have raised this issue with Microsoft support and they identified a possible issue with the 9.1 version we are on and moved us to 9.1.4.31 which appears to fix this bug. I have also heard from another user that upgrading to this version solved the same problem they were experiencing.

So I am hopefuly that the issue is resolved with the upgrade, but we'll know after a couple more days of running issue free.

Thanks,

Simon

Was this reply helpful? Yes No