All automatic and manual Workflows refuse to start

(0) Share

Report

Posted on by Community Member

Our system, Dynamics 11 On-Premise, has not started a process since this past Saturday around mid morning. If I tell a workflow to run nothing happens, deactivating and reactivating do nothing. There have been no new successful processes in two days.

What is causing this and how do we fix it?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

SavvyLuke 655 on at

Like (0)

Report

Hey Stanton, seems to me that your 'asynchronous service' has stopped running. Try restarting the service to see if the workflows start working again. Here some more help: www.customerdynamics.com/.../What-to-do-When-Your-Workflows-Arent-Firing-in-Microsoft-CRM

Was this reply helpful? Yes No
Suggested answer

PS 23,577 on at

Like (0)

Report

Can you check you async services, try to restart it.

Was this reply helpful? Yes No
Suggested answer

Zohaib Uddin Khan 2,822 on at

Like (0)

Report
Seems like Asynchronous Service has some problem. Asynchronous Service is either installed on your CRM Web server or separate server.

Stop and Re-start the Asynchronous Service.

Go to CRM Web server.

Navigate to Start, select Administrative Tools, then click Services.

Go through the list and find Microsoft Dynamics CRM Asynchronous Processing Service. If you're unable to find on the CRM Web Server, then check your topology diagram and verify on every server in your topology.

Right-click Microsoft Dynamics CRM Asynchronous Processing Service in the Name column of the service listing.

Click Start or Stop. Or, you can click Properties in the shortcut menu and then click Start or Stop in the dialog box.

You must have System Administrator privileges to stop or start the service.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Restarting the a sync fixed it. It was taking up 51% of our server memory. Any recommendations on how to avoid this in the future? I'm not sure why it all of a sudden started eating up so much memory.

Was this reply helpful? Yes No
SavvyLuke 655 on at

Like (0)

Report

It's hard to say what would cause it to stop running. There could be other factors as such as SQL server table locks. That was the most common problem i was having with CRM 4.0 not 2011 and i would have to remove the lock and restarting the async process. Anyhow, if you have some spare time, here is some reading material about the 'async service in CRM' related to your version of course.

Was this reply helpful? Yes No