Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I've recently had some trouble with search in my SharePoint 2010 environment and thought I'd finally seen the end of it. Turns out I was wrong because now when anyone tries to search from anywhere within my site collection they get this error:

Search error
Each time someone searches the Correlation ID is different but I pulled this data out of ULS viewer (for the sake of formatting I'm just going to list the Level and Message columns for each item under the same Correlation ID):

  • (Medium) Name=Request (GET:http://xxxx:80/search/results.aspx?k=search&cs=This%20Site&u=http%3A%2F%2Fflspvm)
  • (Medium) Site=/
  • (High) Leaving Monitored Scope (PostResolveRequestCacheHandler). Execution Time=10.0834044550355
  • (Medium) SearchBoxEx AfterDeserialize begin
  • (Medium) SearchBoxEx AfterDeserialize end
  • (Unexpected) CoreResultsWebPart::OnInit: Exception initializing: System.NullReferenceException: Object reference not set to an instance of an object.
    at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()
    at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)
  • (Exception) Internal server error exception: System.NullReferenceException: Object reference not set to an instance of an object.
    at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()
    at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e) System.NullReferenceException: Object reference not set to an instance of an object.
    at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.SetPropertiesOnQueryReader()
    at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnInit(EventArgs e)
  • (Monitorable) Watson bucket parameters: SharePoint Server 2010, ULSException14, 06175311 "sharepoint server search", 0e00178d "14.0.6029.0", 17853a8f "microsoft.office.server.search", 0e0017da "14.0.6106.0", 4def6b97 "wed jun 08 08:31:19 2011", 00003297 "00003297", 0000002d "0000002d", 4a6d3421 "nullreferenceexception", 67316a39 "g1j9"
  • (Medium) Leaving Monitored Scope (Request (GET:http://xxxx:80/search/results.aspx?k=search&cs=This%20Site&u=http%3A%2F%2Fxxxx)). Execution Time=32.3624929984118

I honestly have no idea where to begin. What do I do to resolve this?

share|improve this question
1  
Did you checked that the SharePoint timer and SharePoint Search Service are running? Also have a IISReset (or even go for a full reboot at extremes) and make sure these Services are starting properly. Ocassionally expired/changed passwords could also be the cause of services not starting –  C. Marius - MVP Aug 8 '12 at 18:58
    
..also it might the case the your Search Service Application Proxy is not functioning properly, you could easily re-create it using this sharepoint.stackexchange.com/questions/5238/… –  C. Marius - MVP Aug 8 '12 at 18:59
    
Now I feel dumb. IISReset fixed it. Post that as an answer and I'll give you the checkmark. –  newuser Aug 8 '12 at 19:14
    
Done, thanks for getting back! –  C. Marius - MVP Aug 8 '12 at 19:17

2 Answers 2

up vote 4 down vote accepted

Did you checked that the SharePoint timer and SharePoint Search Service are running? Also have a IISReset (or even go for a full reboot at extremes) and make sure these Services are starting properly. Ocassionally expired/changed passwords could also be the cause of services not starting.

share|improve this answer
    
IISReset did it. Thanks! –  newuser Aug 8 '12 at 19:22

Have you edited your Core Search Results Webpart properties at all? Have you deleted some Managed Metadata properties in search? You can get a null reference exception when the xslt is attempting to reference or access a property it can't find.

A good way of testing this out is creating a new page and adding a core search results web part. That will get settings back to default. If you still get an error the problem is not with the webpart. Hope that helps.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.