locked
Dynamics CRM 4.0 workflows are not triggering RRS feed

  • Question

  • Hi...

    I have import an organization using deployment manager.
    I can access it without anyu problem and everything seems fine except the following:

    Workflows are not triggering
    Data Import is not working. It remains in the submitted state only.
    I have checked that async service is running and even restarted it. But system jobs are still in waiting state with system job name Workflow Expansion Task.
    I have followed this link and installed the update http://support.microsoft.com/kb/950680/.
    still no luck.

    Can anyone give me a solution for this?



    -Thanks



    Perfectionist
    Monday, June 15, 2009 12:54 PM

Answers


  • "I can access it without anyu problem and everything seems fine except the following"

    My guess is that the Org did not import as expected or the CRM application did not initially install without error otherwise the items you've referenced would most likely be working as expected.

    Please note that before you import an Organization, the Update installed on the new system should match the update installed on the system being imported.  In other words, both CRM systems should have the same Update Rollup.

    It looks to me like you need to start over and ensure you have a successful import which means don't ignore any errors, you have system compatibility with hardware, OS and SQL, and complete all steps referenced in the re-deployment KB.

    Best Regards | Twitter: edwardsdna
    Friday, March 12, 2010 6:23 PM

All replies

  • Also I didn't install rollups 1,2,3,4. 
    I tried to install rollup 4 for server but, it is giving an error. Is it necessary to install previous rollups or can I directly install rollup4 will give all the changes made in 1,2,3 rollups?
    because the above mentioned update http://support.microsoft.com/kb/950680/ is in Rollup1.
    I installed only this update but no luck...





    Perfectionist
    Monday, June 15, 2009 1:59 PM
  • Hi,

    It looks like you DeploymentProperties table entires are corrupted. In order to fix them, you should update three (or sometimes four) columns in th DeploymentProperties table in the MSCRM_Config database. The detailed description of how to accomplish that is on my blog (it's in polish, but I used the Live translator) here: http://www.microsofttranslator.com/BV.aspx?ref=Internal#http://crmblog.pl/2008/10/23/twoj-workflow-czeka-na-zasoby-konfiguracja-klienta-outlook-sie-nie-udaje/. Another way to update the values is described in this KB: http://support.microsoft.com/kb/970630 (the symptom is different, but it's the same issue).
    Or, you can simply use the instructions shown below, replacing SERVER with your current CRM address:


    USE MSCRM_CONFIG
    Update DeploymentProperties SET NVarCharColumn = ‘SERVER‘ WHERE ColumnName = ‘AsyncSdkRootDomain’
    Update DeploymentProperties SET NvarCharColumn = ‘SERVER‘ WHERE ColumnName = ‘ADSdkRootDomain’
    Update DeploymentProperties SET NvarCharColumn = ‘SERVER‘ WHERE ColumnName = ‘ADWebApplicationRootDomain’

    Let us know whether that helps,
    Kuba
    -- Kuba Skałbania, Netwise
    Monday, June 15, 2009 3:56 PM
  • Hi,

    I have already made those changes in DeploymentProperties table.
    Anything else am I missing out???


    -Thanks
    Perfectionist
    Tuesday, June 16, 2009 5:46 AM
  • hi could you correct the problem? I have the same
    Wednesday, March 10, 2010 11:00 PM

  • "I can access it without anyu problem and everything seems fine except the following"

    My guess is that the Org did not import as expected or the CRM application did not initially install without error otherwise the items you've referenced would most likely be working as expected.

    Please note that before you import an Organization, the Update installed on the new system should match the update installed on the system being imported.  In other words, both CRM systems should have the same Update Rollup.

    It looks to me like you need to start over and ensure you have a successful import which means don't ignore any errors, you have system compatibility with hardware, OS and SQL, and complete all steps referenced in the re-deployment KB.

    Best Regards | Twitter: edwardsdna
    Friday, March 12, 2010 6:23 PM
  • Hi Sandra,

    Try to install the latest rollup. This should solve your problem. If it doesn't then let me know....


    -Thanks

    Perfectionist
    Saturday, March 13, 2010 5:48 PM
  •  

    Hi All,

    The workflow is not getting triggered, there is no entry in event viewer.

    It seems to be similar issue. please let me know how to resolve

    Regards

    Prabhu G

     

    Tuesday, May 17, 2011 10:20 AM