locked
Search Problem with SharePoint 2010: Get Internal server error when doing search RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Am getting Internal server error, corelation id.. when I use the search functionality in SP2010. 

    I've installed Sharepoint 2010 trial version on windows server 2008 r2 and the database server used is a SQL server 2008 R2.

    I got the following messages with ULs viewer for the relative Corelation ID:

     

    Process Product Category Level Message
    w3wp.exe (0x1808) SharePoint Foundation Monitoring High Leaving Monitored Scope (Search Statistics). Execution Time=404.4175
    w3wp.exe (0x1808) SharePoint Server General Medium Constructed a new async cache named Location Configuration Cache
    w3wp.exe (0x1808) SharePoint Server Search Administration High 'SharePoint_SearchApplicationProxy', location cache:  Refreshing location cache
    w3wp.exe (0x1808) SharePoint Server Search Administration High

    SharePoint_SearchApplicationProxy', location cache: Exception while fetching

    location configuration data. StackTrace: Microsoft.SharePoint.SPEndpointAddress

    NotFoundException: There are no addresses available for this application.    

    at Microsoft.SharePoint.SPRoundRobinServiceLoadBalancer.BeginOperation()    

    at Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy.

    GetLocationConfigurations(Int64& lastUpdate, Boolean& useCrawlProxy)     at

    Microsoft.Office.Server.Search.Administration.LocationConfigurationCollection.

    PopulateCollection()     at Microsoft.Office.Server.Search.Administration.

    LocationConfigurationCollection.Init()     at Microsoft.Office.Server.Search.

    Administration.LocationConfigurationCollection..ctor(SearchServiceApplicationProxy

    searchAdmin)     at Microsoft.Office.Server.Search.Administration.LocationCache.

    FetchLocationConfigurationData()
    w3wp.exe (0x1808) SharePoint Server Search Query 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)
    w3wp.exe (0x1808) SharePoint Server Search Query 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)
    w3wp.exe (0x1808) SharePoint Server Unified Logging Service Monitorable

    Watson bucket parameters: SharePoint Server 2010, ULSException14, 06175311

    "sharepoint server search", 0e00129b "14.0.4763.0", 17853a8f "microsoft.

    office.server.search", 0e00129a "14.0.4762.0", 4bad937d "sat mar 27 09:11:25

    2010", 0000320d "0000320d", 0000002d "0000002d", 4a6d3421 "nullreferenceexception"

    , 67316a39 "g1j9"
    w3wp.exe (0x1808) SharePoint Foundation Monitoring High Leaving Monitored Scope (Search Action Links OnInit). Execution Time=395.3955
    w3wp.exe (0x1808) SharePoint Foundation Monitoring High Leaving Monitored Scope (Add WebPart with error#4). Execution Time=527.8118
    w3wp.exe (0x1808) SharePoint Foundation Monitoring High Leaving Monitored Scope (Add WebParts). Execution Time=3601.2636
    w3wp.exe (0x1808) Web Content Management Publishing Medium

    Caught a thread abort exception in TemplateRedirectionPage.ProcessRequest,

    the exception may be expected. stack trace=   at System.Web.UI.Page.

    ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean

    includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at

    System.Web.UI.Page.ProcessRequest(HttpContext context)     at ASP.SEARCHRESULTS_ASP

    X__1518441470.ProcessRequest(HttpContext context)     at Microsoft.SharePoint.

    Publishing.TemplateRedirectionPage.ProcessRequest(HttpContext context)
    w3wp.exe (0x1808) SharePoint Foundation Monitoring Medium

    Leaving Monitored Scope (Request (GET:http://nestestsp:25943/Pages/results.aspx

    ?k=home%20nesintranet)). Execution Time=3811.6724

     

    Can anybody help me find a solution for this issue.

    Thanks

    • Changed type Sweety Devi Tuesday, June 8, 2010 5:59 AM
    Tuesday, June 8, 2010 5:51 AM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi,

    This (Microsoft.SharePoint.SPEndpointAddress NotFoundException: There are no addresses available for this application) probably means that whatever you're trying to do, it can't find the appropriate web service.

    This could be because the necessary services aren't started anywhere in the farm.
    If you go into Central Administration and Click System Settings on the left and select Manage Services on Server, are the following servers started on at least one server in the farm?

    • SharePoint Server Search
    • Search Query and Site Settings Service
    Mirjam
    sharepointchick.com
    • Marked as answer by Sweety Devi Tuesday, June 8, 2010 9:11 AM
    Tuesday, June 8, 2010 7:17 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    We had similar problem here, but all services were running and all features activated. Search was working a few days ago and started to fail at some point.

    The solution was to click through the majority Search Administration pages in Central Admin.

    Monday, August 22, 2011 12:37 PM

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi,

    This (Microsoft.SharePoint.SPEndpointAddress NotFoundException: There are no addresses available for this application) probably means that whatever you're trying to do, it can't find the appropriate web service.

    This could be because the necessary services aren't started anywhere in the farm.
    If you go into Central Administration and Click System Settings on the left and select Manage Services on Server, are the following servers started on at least one server in the farm?

    • SharePoint Server Search
    • Search Query and Site Settings Service
    Mirjam
    sharepointchick.com
    • Marked as answer by Sweety Devi Tuesday, June 8, 2010 9:11 AM
    Tuesday, June 8, 2010 7:17 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    In Fact, the Sharepoint Query and site Setting Services was stopped. The search is working fine now. Thanks

    for the solution and the quick response
    Tuesday, June 8, 2010 9:13 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    We had similar problem here, but all services were running and all features activated. Search was working a few days ago and started to fail at some point.

    The solution was to click through the majority Search Administration pages in Central Admin.

    Monday, August 22, 2011 12:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The answer provided by AKrasheninnikov worked for me as well. My services, too, were all up and running.
    Monday, August 29, 2011 8:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm having the same issue as Sweety Devi has reported. Has there been any solution on this please?

     

    Phu H

    Wednesday, November 2, 2011 12:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    After making sure that all services are up and running,  I had to deactive and activate the "SharePoint Server Site Search" web site collection feature.  Then the search started working for the time being. 

    However, it throws the error again after 8 to 9 hours.  This has been happening for last couple of weeks.  I also came to know from my windows server team that they moved the AD from one place to another.  Since then I am having this issue. 

    The log file has the following error:

    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)

    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)

    Harish Vajja
    Friday, February 3, 2012 9:27 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I think there could be multiple reason for this issue to manifest itself. I recently had this issue and went thru all the solution proposed here and none of them worked for me. After analysing the logs, it indicated managed metadata service had an issue. On futher analysis, I found the Application pool underlying the mangement meta server was not running. I had issue starting the pool. I decided to re-enter the password for it in the Application pool of IIS and Restart services with an IIS reset . Everything started to work.

    Thanks

    Jaise

    • Proposed as answer by Damian79 Thursday, March 31, 2016 2:24 AM
    Thursday, April 19, 2012 8:57 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    We had the same problem since last week. I was about to reboot the server during the night. Thanks to  Jaise's tip on recycling the application pool search started working again. Thanks Jaise for saving my night sleep.

    Alfred Boeren

    Tuesday, April 24, 2012 10:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mirjam/anyone else,

    Both the services are started on the server(s), but I still have the problem.  I have also installed all the hotfixes that sites suggested but I still get the error when searching.

    Please help?

    Kind Regards,

    Marli

    Monday, November 19, 2012 7:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have done all the suggestions, eventually had to rebuild my Farm.

    SharePoint has alot of errors which doesn't help...but we have to 'bypass' it on the front end.  Quite difficult.

    • Proposed as answer by Marli Butler Monday, March 18, 2013 10:01 AM
    Monday, March 18, 2013 10:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Had the same error as Harish Vajja today.

    It turned out the IIS Application Pool of the Search Service was stopped. Just after starting the application pool search worked again.

    Sharepoint Hosting und Beratung www.sharepoint-foundation-hosting.ch

    Tuesday, November 12, 2013 3:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We had the same issue with the Search as well and all required services were running. By just restarting the Search Query and Site Settings Service on the application server worked for us to solve the issue.
    Friday, November 20, 2015 9:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think there could be multiple reason for this issue to manifest itself. I recently had this issue and went thru all the solution proposed here and none of them worked for me. After analysing the logs, it indicated managed metadata service had an issue. On futher analysis, I found the Application pool underlying the mangement meta server was not running. I had issue starting the pool. I decided to re-enter the password for it in the Application pool of IIS and Restart services with an IIS reset . Everything started to work.

    Thanks

    Jaise

    We had the following in our ULS:

    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)    b12c82a2-1ea9-4440-b06a-3001d75acaff

    The following applicaiton pool was stopped:

    ec9ec0c09bc14ef397a2abef0de30b61

    Starting it resolved my issue.


    Vista Ultimate Dell XPS M1330

    Thursday, March 31, 2016 2:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks, it resolves the issue for me.
    Thursday, January 5, 2017 10:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No need to recreate Search application,

    restart all search services

     - SharePoint Server Search

    -  Search Query and Site Settings Service

    - Search Administration Web Service

    -  Web Analytics Web Service

    -  Web Analytics Data Processing Service

    including timer windows services and run the full crawl again will fix the issue.

    Syed Danish Aftab http://www.danishaftab.net

    Sunday, March 24, 2019 6:24 AM