This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


When starting a SharePoint Workflow Integration process with participants assigned in serial, only the first user in the destination set is able to action the worklist item. Thereafter no worklist items are created for the users in serial in the destination set.

Note: After installing this Hotfix it is required to restart the “Windows SharePoint Services Timer” service.

  • Go to Start > Administration Tools > Services
  • Right-click on “Windows SharePoint Services Timer” and select Restart

Error Scenario

Note: The circumstances described in this article are one scenario under which this issue may, or is known to occur. The description is intended to be specific to the scenario described and does not take into account all possible scenarios or circumstances.
  1. Create a K2 Web Designer process
  2. On an activity, add two or more destination users and enable “Assign participants in serial instead of in parallel”
  3. Configure the Outcomes Rule as “All Participants selected the ‘Approved’ outcome”
  4. Start the workflow
  5. User 1 can action the worklist item
  6. User 2 does not receive the worklist item

Error Message

The following error message can be found in the SharePoint Log file:

ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads.
ThreadId = 5, Free call stack =
at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request)
at Microsoft.SharePoint.SPWeb.Invalidate() at Microsoft.SharePoint.SPWeb.Close()
at SourceCode.SharePoint.Common.K2IntegrationList.Dispose()
at SourceCode.SharePoint.Workflow.Proxy.Common.GetK2IntegrationListItem(SPWorkflowActivationProperties properties)
at SourceCode.SharePoint.Workflow.Proxy.MultipleTasksAndUsers.taskReplicator_ChildInitialized(Object sender, ReplicatorChildEventArgs e)
at System.Workflow.ComponentModel.Activity.RaiseGenericEvent[T](DependencyProperty dependencyEvent, Object sender, T e)
at System.Workflow.Activities.ReplicatorActivity.ExecuteTemplate(ActivityExecutionContext executionContext, ChildExecutionStateInfo childStateInfo)
at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
at System.Workflow.Runtime.Scheduler.Run() at System.Workflow.Runtime.WorkflowExecutor.RunScheduler()
at System.Workflow.Runtime.WorkflowExecutor.RunSome(Object ignored)
at System.Workflow.Runtime.Hosting.DefaultWorkflowSchedulerService.WorkItem.Invoke(WorkflowSchedulerService service)
at System.Workflow.Runtime.Hosting.DefaultWorkflowSchedulerService.QueueWorkerProcess(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state) , Allocation call stack (if present) null

Error Resolution

This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error.

The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: http://portal.k2.com/downloads/bp/Default.aspx