The workflow remains in a waiting state after you create a workflow rule to update the status of an opportunity in Microsoft Dynamics CRM 4.0

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
After you create a workflow rule to update the status of an opportunity in Microsoft Dynamics CRM 4.0, the workflow remains in a waiting state. If a platform trace is enabled, you may notice the following error message:
<ErrorId>8004051a</ErrorId>
<ManagedErrorName>OpportunityAlreadyInOpenState</ManagedErrorName>
<ErrorMessage>The opportunity is already in the open state.</ErrorMessage>
<UnManagedErrorName>IDS_OPPORTUNITY_ALREADY_IN_OPEN_STATE</UnManagedErrorName>
Resolution
This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949256 Microsoft Dynamics CRM 4.0 updates and hotfixes
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards
Properties

Article ID: 956237 - Last Review: 01/15/2015 09:18:24 - Revision: 3.0

Microsoft Dynamics CRM 4.0

  • kbnosurvey kbarchive kbsurveynew kbmbsmigrate kbqfe kbhotfixserver KB956237
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)