locked
Workflow does not work RRS feed

  • Question

  • Dear All,

     

    Unfortunately I can not fix the problem with the workflows. I tried to use old workflows from CRM 3 in CRM 4 but they did not work, then I created new workflows (several times, very ease ones). I know that I hav to unpublish it and there is a difference between automatic and manual... I tried all of them.

     

    I got the info that the CRM "Asynchronous processing service" has to run on the server. At the beginning it was not startet although the start option was automatic. In the meantime the service starts automatically. But.... none of the workflows runs.....

     

    Does anybody has an idea how can I find out what is missing or how to solve the problem.

     

    Thanks

     

    Best regards

     

    Torsten 

    Thursday, November 6, 2008 1:18 PM

Answers

  • If you are using a custom host header please take a look at the following blog:


    "After you get MSCRM 4.0 up and running (install or upgrade) on your system with a custom host header you may find that workflow doesn't work (or flow), imports sit in a submitted state forever, the email router and outlook client cannot connect to the MSCRM server. This could also happen if you change the website details in IIS. What is happening is even though you access your server on a specific URL, internally in the Async service (which handles the workflow, duplicate detection and imports) and the email router and outlook client actually just use the URL you used to connect to the Discovery Service.

    The discovery service is a web service which gives back the real URL to the web services in MSCRM, so if you changed IIS it still gives back the old ones. There is also a bug in the RTM of MSCRM 4.0 which causes it to use the machine name instead of the host header after upgrades. So you go to http://<nice name> and the discovery service gives back to http://<machine name>/mscrmservices/2007/crmservice.asmx which doesn't exist since your host headers should have it as http://<nice name>/mscrmservices/2007/crmservice.asmx

    You can pick this up using fiddler on the email server or desktop machine when trying to configure the email router or outlook client respectively. So I went though this with Microsoft PSS and they came back with a SQL command you can run to fix this." 

    Thursday, November 6, 2008 1:43 PM

All replies

  • Hi,

    Are you using a custom host header?


    Thursday, November 6, 2008 1:40 PM
  • If you are using a custom host header please take a look at the following blog:


    "After you get MSCRM 4.0 up and running (install or upgrade) on your system with a custom host header you may find that workflow doesn't work (or flow), imports sit in a submitted state forever, the email router and outlook client cannot connect to the MSCRM server. This could also happen if you change the website details in IIS. What is happening is even though you access your server on a specific URL, internally in the Async service (which handles the workflow, duplicate detection and imports) and the email router and outlook client actually just use the URL you used to connect to the Discovery Service.

    The discovery service is a web service which gives back the real URL to the web services in MSCRM, so if you changed IIS it still gives back the old ones. There is also a bug in the RTM of MSCRM 4.0 which causes it to use the machine name instead of the host header after upgrades. So you go to http://<nice name> and the discovery service gives back to http://<machine name>/mscrmservices/2007/crmservice.asmx which doesn't exist since your host headers should have it as http://<nice name>/mscrmservices/2007/crmservice.asmx

    You can pick this up using fiddler on the email server or desktop machine when trying to configure the email router or outlook client respectively. So I went though this with Microsoft PSS and they came back with a SQL command you can run to fix this." 

    Thursday, November 6, 2008 1:43 PM
  • Were you able to solve your problem?


    Tuesday, November 18, 2008 6:38 PM