Microsoft Knowledge Base Email Alertz

(911480) - Describes a problem that occurs when you uninstall Microsoft Dynamics CRM and then install it on a new server. The WFEventLog and WFProcessInstance tables incorrectly list the computer account name of the original server. A workaround is provided.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 911480 - Last Review: August 21, 2007 - Revision: 1.3

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

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 (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.

APPLIES TO
  • Microsoft Dynamics CRM 3.0
Keywords: 
kbmbscrm40no kbtshoot kbmbsmigrate kbbug KB911480
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate