Dave Ireland's CRM & Stuff

CRM Workflows stop firing after Rollup 5

Posted on July 22nd, 2009.

We normally install CRM Rollup Patches on our internal CRM as soon as they come out.  It provides us with a chance to test the installer and sanity-check the application stability afterwards.

So when RU5 came out we installed it to our fully-functional CRM platform (which was running RU4 at the time).  Our internal deployment is a standard 2-box configuration.

After RU5 we noticed no workflows were firing – neither pre-existing ones, nor newly created ones.  It was like the Async service had just gone on vacation – no errors, no action whatsoever.  Even after uninstalling RU5, the problem persisted.

Unable to figure it out, we opened up a ticket with MSFT support to get it resolved.  It turns out that during the installation of RU5, it changed the Server Role of our CRM Server to be that of an Application Server which does not include the Platform Server (and therefore no Async service). 

The fix seems to be as simple as updating the Server Role value in the configuration database, although MSFT warned that further testing may be required on this.  We issued the following sql update:

use mscrm_config
go
update server set roles = 2392107 where roles = 294913
go

After running this update, do an IISRESET and recycle your CRM Async Service, and you should be back in business. 

Thanks to my colleague Peter Gernburd for chasing down the solution.

Make a Comment

Make A Comment: ( 2 so far )

2 Responses to “CRM Workflows stop firing after Rollup 5”

Comments RSS Feed

Where's The Comment Form?