tag:blogger.com,1999:blog-1575476679976002386.post6126812175758206622..comments2010-05-15T10:49:54.129+02:00Einar Otto Stangvikhttp://www.blogger.com/profile/14646027402573050232noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-1575476679976002386.post-86584774900704020942010-04-22T10:27:53.685+02:002010-04-22T10:27:53.685+02:00I totally agree. You would think this was something Microsoft would have fixedRasmushttp://my4hours.comnoreply@blogger.comtag:blogger.com,1999:blog-1575476679976002386.post-24127100950689752602010-04-21T11:30:42.131+02:002010-04-21T11:30:42.131+02:00@Rasmus: You&#39;re very welcome!<br /><br />I&#39;m slightly disappointed by the fact that this is still required in SharePoint 2010, though. One would think that they had come up with a way for the object model to detect changes made by e.g. the timer process, and either reload its state data, or notify the user. <br /><br />I&#39;m all down with eventual consistency, but at least providing sane error messages would help.Einar Otto Stangvikhttp://www.blogger.com/profile/14646027402573050232noreply@blogger.comtag:blogger.com,1999:blog-1575476679976002386.post-90390048991275374212010-04-21T11:11:30.782+02:002010-04-21T11:11:30.782+02:00You are my hero...<br /><br />We have been over this on a SharePoint 2010 solution. Everything was scripted with PowerShell, but when it came to creating our sitecollections based on our own template, we got the error.<br /><br />We have even tried to run IISRESET but this didn&#39;t help anything.<br /><br />When I used your code I got a null exception with the &quot;ThreadContext&quot;, so I had some serious digging in the SharePoint 2010 internal API.<br /><br />The unsafe code you did is the exact same, but the clearing of the SPRequestManager is different.<br /><br /> Type sprequestmanager = typeof(SPFarm).Assembly.GetType(&quot;Microsoft.SharePoint.SPRequestManager&quot;, true, true);<br /> Type spthreadcontext = sprequestmanager.Assembly.GetType(&quot;Microsoft.SharePoint.Utilities.SPThreadContext&quot;);<br /> MethodInfo setcontext = spthreadcontext.GetMethod(&quot;Set&quot;, BindingFlags.Static | BindingFlags.NonPublic);<br /> Type[] genericArguments = new Type[] { sprequestmanager };<br /> MethodInfo setcontextgeneric = setcontext.MakeGenericMethod(genericArguments);<br /><br /> // set hte current sprequest manager to null!<br /> setcontextgeneric.Invoke(null, new object[] { null });<br /><br />Now I have created a PowerShell SnapIn with a cmdlet called Reset-SPContext and running this is out script makes everything work, yeah!<br /><br />Thanks again.Rasmushttp://my4hours.comnoreply@blogger.comtag:blogger.com,1999:blog-1575476679976002386.post-76116523880022610652009-10-15T01:10:56.639+02:002009-10-15T01:10:56.639+02:00That&#39;s a great little line of code, saves IISRESET&#39;ing all the time which takes AGES! ;-)Jeremy Thakehttp://www.blogger.com/profile/14264476485361437612noreply@blogger.com