Skip to main content

Detected use of SPRequest for previously closed SPWeb object

I was working on configuring a SharePoint 2010 farm and I received this error while trying to create an Enterprise Search Center on the root site collection.:

Detected use of SPRequest for previously closed SPWeb object. Please close SPWeb objects when you are done with all objects obtained from them, but not before. Stack trace: at Microsoft.SharePoint.WebControls.ScriptLink.SharePointClientJs_Register(Page page) at Microsoft.SharePoint.WebControls.ScriptLink.InitJs_Register(Page page) at Microsoft.SharePoint.WebControls.ScriptLink.RegisterForControl(Control ctrl, Page page, String name, Boolean localizable, Boolean defer, Boolean loadAfterUI, String language) at Microsoft.SharePoint.WebControls.ScriptLink.Register(Page page, String name, Boolean localizable, Boolean defer, Boolean loadAfterUI, String language, String uiVersion) at Microsoft.SharePoint.WebControls.ScriptLink.RegisterOnDemand(Page page, String strKey, String

I tried creating a blank site and a basic search center and there were no errors. It seemed that this error had something to do with some site collection level features. I activate the SharePoint Standard and Enterprise features and tried creating an Enterprise Search Center sub-site on the root site collection, result was same. I checked the ULS logs and the error was still the same.

I tried activating the SharePoint Server Publishing Infrastructure and then recreated the Enterprise Center, this time it worked like a charm!

The sad part is that nothing much can be inferred from the ULS log message.

There was this another error for the same corelation Id:
No document templates uploaded for list "$Resources:core,MasterPageGallery;" -- none found for list template "100".

Not sure what this really means, but I'm happy that the problem is solved.

Comments

Edwin Sanchez said…
You rock, man!

Thanks a lot for this timely information. You saved me
September 20, 2012 at 7:56 AM
Post a Comment

Popular posts from this blog

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...
Post a Comment
Read more

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more