A workflow rule does not advance to the next step for a record in Microsoft Dynamics CRM (911480)


The information in this article applies to:

  • Microsoft CRM 3.0

SYMPTOMS

Consider the following scenario in Microsoft Dynamics CRM:
  • You create a workflow rule that has a Wait for condition. For example, closing a case may be used as a Wait for condition.
  • You start the workflow rule. Then, you apply it to records in Microsoft Dynamics CRM.
  • You uninstall Microsoft Dynamics CRM.
  • You install Microsoft Dynamics CRM on a new server. The computer account name of this new server differs from the computer account name of the old server.
  • You open one of the records to which you applied the workflow rule. In this situation, you meet the Wait for condition.
In this scenario, the workflow rule does not advance to the next step for this record.

CAUSE

This problem occurs because the WFEventLog and WFProcessInstance tables for the workflow rule incorrectly list the computer account name of the old server. These tables are Microsoft SQL Server tables.

RESOLUTION

To resolve this problem, contact Microsoft Product Support Services. For a list of Microsoft Product Support Services telephone numbers and support options, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

WORKAROUND

To work around this problem, you must manually update the WFEventLog and WFProcessInstance tables. To do this, follow these steps:
  1. Start Microsoft SQL Query Analyzer.
  2. In the Database list, click <organization_name>_MSCRM.

    Note <organization_name> is a placeholder for the actual name of the company.
  3. Copy and then paste the following script.
    begin tran
Update WFEventLog set MachineName = <new_server> where MachineName = <old_server>

Update WFProcessInstance set OwningMachine = <new_server> where OwningMachine = <old_server>
commit tran
    Note <new_server> is a placeholder for the computer account name of the new server. <old_server> is a placeholder for the computer account name of the old server.
  4. Run the script.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type:MajorLast Reviewed:9/28/2006
Keywords:kbMSCCSearch kbMBSMigrate kbBug KB911480 kbAudEndUser
©2004 Microsoft Corporation. All rights reserved.