"ERROR: request not found in the TrackedRequests" message logged each time a workflow starts

Article ID: 2537914 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You have a standard Team Site and you create a new workflow using SharePoint Designer 2007 using a site owner account EXCEPT SharePoint System (see http://support.microsoft.com/kb/953289)

The workflow is set to start "On Item Creation"
Only action configured for the workflow is Pause for duration - set duration 0 min.

You open the site in Internet Explorer as Contributor and create a list item to trigger the start of the workflow .

Result:
The workflow starts and logs a "request not found" error. The workflow runs to completion.

The error in ULS resembles :

ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 15, Free call stack = at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request) at Microsoft.SharePoint.SPSite.Close() at Microsoft.SharePoint.SPSite.Dispose() at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.AutoStartWorkflow(SPItemEventProperties properties, Boolean bCreate, Boolean bChange, AssocType atyp) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.AutoStartWorkflow(SPItemEventProperties properties, Boolean bCreate, Boolean bChange) at Microsoft.SharePoint.Workflow.SPWorkflowAutostartEventReceiver.ItemAdded(SPItemEventProperties properties) at Microsoft.SharePoint.SPEventManager.RunItemEventRe…




CAUSE

In this scenario, the behavior is by design. In general this is an indication of a risky coding pattern, which is why there’s a warning, but in this case it is less clearly an indicator of a specific issue. The risk is only partially that of a memory leak, in that passing objects around between threads unexpectedly reduces the ability of our framework code to ensure that resources like SPRequest objects aren’t leaked (particularly in error situations).


RESOLUTION

If the occurrence cannot be associated to a memory condition, the message can be safely ignored. Use the performance monitor to assert whether or not the memory condition exist.

MORE INFORMATION

Tune Web server performance (Office SharePoint Server)

Best Practices: Using Disposable Windows SharePoint Services Objects (http://go.microsoft.com/fwlink/?LinkId=105945&clcid=0x409)

Development Tools and Techniques for Working with Code in Windows SharePoint Services 3.0 (Part 1 of 2) (http://go.microsoft.com/fwlink/?LinkID=101494&clcid=0x409)

Best Practices: Common Coding Issues When Using the SharePoint Object Model (http://go.microsoft.com/fwlink/?LinkId=105946&clcid=0x409)SharePoint Products and Technologies customization policy (http://go.microsoft.com/fwlink/?LinkId=105947&clcid=0x409)
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2537914 - Last Review: May 27, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft Office SharePoint Server 2007
  • Microsoft Office SharePoint Designer 2007
Keywords: 
KB2537914

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com