Workflows Not Firing, Microsoft CRM Asynchronous Processing Service Stopping
Posted Tuesday, December 23rd, 2008
I recently promoted a couple of new workflows, but they were not firing correctly. My first thought was the Asynchronous Service was stopped or may need restarting. My assumption was correct; the Asynchronous service on the CRM application server had stopped.
I restarted the service and tried the workflow again, but it still did not fire. Turns out the Asynchronous service had shut down again so I take a look at the event log and the following error was repeated multiple times.
Open the image below in a new window and maximize to view:
After researching the problem, I stumbled across this KB Article.
Based on the information in this article, I checked the Servers table in the MSCRM_Config database and the SQL Server Name did not match the name returned by the Select @@SERVERNAME statement. So, I corrected the Server Name in the Servers table to match the SQL Server Name (Case Sensitivity). I then restarted the Asynchronous Service and workflows fired correctly and the above error did not appear in logs.



