Workflow instances stop working if the workflow rule contains a Wait condition in Microsoft Dynamics CRM 4.0

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
Assume that you create a workflow rule that contains a Wait condition in Microsoft Dynamics CRM 4.0. When you run a workflow instance that uses the workflow rule, the workflow instance stops working intermittently if the Wait condition is met. Additionally, you notice that you cannot resume the workflow instance during peak times.

Additionally, an error message that resembles the following is logged in the Microsoft Dynamics CRM platform tracing log:
Unhandled Exception: Microsoft.Crm.CrmException: An unexpected error occurred.
at CrmException..ctor(String message, Exception innerException, Int32 errorCode, Boolean isFlowControlException, Boolean enableTrace)
at CrmException..ctor(Int32 errorCode, Object[] arguments)
at ContextService.GetContext(Guid instanceId)
at ContextService.GetOrganizationConfiguration(Guid instanceId)
This problem occurs if you have applied Update Rollup 3 for Microsoft Dynamics CRM 4.0.
For more information about Update Rollup 3 for Microsoft Dynamics CRM 4.0, click the following article number to view the article in the Microsoft Knowledge Base:
961768 Update Rollup 3 for Microsoft Dynamics CRM 4.0 is available
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
Properties

Article ID: 974310 - Last Review: 01/16/2015 17:21:37 - Revision: 2.0

  • Microsoft Dynamics CRM 4.0
  • kbnosurvey kbarchive kbmbsworkflow kberrmsg kbfix kbsurveynew kbmbsmigrate kbqfe kbexpertiseinter KB974310
Feedback