locked
CRM workflows don't run. RRS feed

  • Question

  • On my development system workflows just don't run. My knowledge of CRM deployments (rather than development) is pretty low so I have done what I know - restart IIS, restart async service but they still don't run. They don't even appear as system jobs - it's as though I never ran the workflow in the first place.

    Can anybody give any suggestions?
    Thursday, July 23, 2009 10:11 AM

Answers

All replies

  • I see that you restarted the asynch service, that's the correct first step - did it continue running, or did it start, then stop?


    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, July 23, 2009 10:50 AM
    Moderator
  • (also - since you're just getting started with CRM dev - can you give me some information about the workflow itself? - What does it do?/When is it supposed to run?/have you published it?)
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, July 23, 2009 10:52 AM
    Moderator
  • I'm happy with development - it's the deployment issue. This isn't a custom workflow - it's any workflow.
    Thursday, July 23, 2009 10:55 AM
  • It restarted happily.
    Thursday, July 23, 2009 11:06 AM
  • And the async service - does it continue to run after you restart it?
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, July 23, 2009 11:07 AM
    Moderator
  • Since this is on your dev server - is it an isolated enviornment or is it in your original domain/just a different iis/sql - just wondering if the asynch service is still pointing to / servicing your production (or other CRM server) and 'ignoring' your dev server. -

    (I had this happen to me once and it was confusing at first - but easy to resolve.)
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, July 23, 2009 11:17 AM
    Moderator
  • It was set up by one of our IT guys and was copied from the live system. It may well be that it is trying to service the live system still. How would I check / fix?
    Thursday, July 23, 2009 11:29 AM
  • try to check your settings in DB, search for a value of your host header and update them

    I use host header value crm for my crm webpage:

    UPDATE dbo.DeploymentProperties SET NVarCharColumn = 'crm' WHERE
    ColumnName IN ('ADWebApplicationRootDomain', 'AsyncSdkRootDomain',
    'ADSdkRootDomain')


    Jan
    Thursday, July 23, 2009 11:34 AM
  • I'll have a look, though we don't use a host header as CRM is the only site on both the live and dev machines.
    Thursday, July 23, 2009 11:37 AM
  • Verify in the registry (in HTLM SOFTWARE\MICROSOFT\MSCRM -) that all references are to the current dev server -

    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, July 23, 2009 12:31 PM
    Moderator
  • Both the database and registry look OK. I have talked with the CRM guy who's going to flatten the box and reinstall. The nuclear option ;)
    Thursday, July 23, 2009 1:41 PM
  • Make sure the CRM person uses the supported redeployment method of setting up your dev environment - that should help you avoid issues.

    http://support.microsoft.com/default.aspx/kb/KB952934
    Scott Sewell, CustomerEffective | http:\\blog.CustomerEffective.com | Twitter:@ScottSewell
    Thursday, July 23, 2009 1:46 PM
    Moderator
  • Are the workflows recently created? If so, is the scope of the workflow organisation?

    Leon Tribe
    Want to hear me talk about all things CRM? Check out my blog
    http://leontribe.blogspot.com/
    or hear me tweet @leontribe

    Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe
    • Proposed as answer by Leon TribeMVP Thursday, July 23, 2009 6:31 PM
    Thursday, July 23, 2009 6:30 PM