Error Request Not Found In The Trackedrequests

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads up vote 1 down vote favorite This is an error I receive from Sharepoint when I deploy a custom workflow to a forms library. The workflow is very straightforward and doesn't do anything fancy. I was reading from the an infopath form, but have since stripped down all non-essential code to see if I can get it working. As far as I can tell, other workflows are fine (I've developed others on the same box and they are intact and functioning). The design view of the workflow is as follows: The error occurs after a task is successfully created. This leads me to believe that there is an issue with the while loop, which is waiting for a boolean variable to become true (which is initially set to false). Normally, when the task is altered in any way, the changed event will fire and change the variable to true, then the workflow will continue. I receive this error on the start of this workflow: ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 9, Free call stack = at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request) at Microsoft.SharePoint.SPSite.Close() at Microsoft.Share

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Investigating the root cause behind SharePoint's “request not found in the TrackedRequests” up vote 6 http://stackoverflow.com/questions/918293/error-request-not-found-in-the-trackedrequests-we-might-be-creating-and-closin down vote favorite 3 We have a long standing issue in our bug tracking system about the dreaded "ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads." message in SharePoint's trace log. As we develop Workflow software for the SharePoint market, we look into this issue from time to time to make sure it is not caused by our products. I have http://stackoverflow.com/questions/2021033/investigating-the-root-cause-behind-sharepoints-request-not-found-in-the-track personally come to the conclusion that this is a problem in SharePoint, but perhaps someone else can prove me wrong. Here is what I know: According to the hundreds of search results returned by Google on this topic, this issue appears to be mainly related to SharePoint Workflows, both SharePoint Designer and Visual Studio based workflows. Assuming ULS logging is set to Monitorable, the easiest way to reproduce this problem is to create a new SharePoint Designer Workflow, attach it to a document library, set it to auto start on add/update, don't add any actions, save the workflow and upload a file to the document library. The error is only visible in the SharePoint trace log, it does not appear to impact the execution of the workflow at hand. I have verified that the problem occurs on 32 bit as well as 64 bit systems, Win2K3 and 2K8, WSS and MOSS with SharePoint versions up to the December 2009 Cumulative Update (6524). The problem does not occur when a workflow is started manually. There are dozens of related posts on MSDN Forums, hundreds on Google, one on StackOverflow and none on SharePoint Overflow. There appears to be no answer. Does anyone have any idea about what is going on,

values of the fields were not saved. It was empty. Even though the fields are required. Automatic workflow is kicked off, but no values in the fields.In the ULS Logs I found this error:ERROR: request http://wssmossstuff.blogspot.com/2010/11/error-request-not-found-in.html not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 26, Free call stack = at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request) ....I searched all over on the internet and could not http://www.gandhipritesh.com/2009/01/sharepoint-designer-created-workflow.html find a solution. This Form and Workflow is standard OOB and was not created using SharePoint Designer.To complicate it further, I have 4 Web Front Ends, and only 1 was giving this issue. So I error request started at the Web.Config file.The web.config files differed on the "working" WFE's and the "broken" WFE. The solution is quite simple. In this part of the web.config:The enableViewState and EnableViewStateMac was set to "false" (on the "broken" WFE). So I changed both values to "true". Because that was the value on the "working" WFE's.Walla! Problem solved. Posted by Daniel van der Gryp at 12:09 PM No comments: Post a Comment error request not Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search Custom Search Visitor Locations About Me Daniel van der Gryp View my complete profile Followers Popular Posts Top Link Bar Not an error exactly, but the Top Link Bar doesn't highlight correctly, i.e. when you click on a subsite, the button is not highlighted.... Event 7888 and 5553 I have been getting these errors in my event log: Event Type: Error Event Source: Office SharePoint Server Event Category: Office Server G... Unable to properly communicate with the workflow service SharePoint 2013 It has been a long time since my last blog post. I have been busy. :-)Well I am back again and thought I would share my l... Blog Archive ► 2016 (1) ► August (1) ► 2014 (3) ► August (1) ► July (2) ► 2012 (6) ► April (2) ► February (3) ► January (1) ► 2011 (5) ► December (1) ► November (3) ► April (1) ▼ 2010 (6) ▼ November (1) ERROR: request not found in the TrackedRequests. W... ► July (1) ► March (2) ► January (2) ► 2009 (16) ► November (1) ► October (2) ► September (1) ► August (1) ► July (7) ► June (4) Simple template. Powered by Blogger.