The search service is not able to connect to the machine that hosts the administration component

The search service is not able to connect to the machine that hosts the administration component

When you are running your SharePoint 2010 beta 2 on a machine that has the domain controller, you might sometimes face this issue of SharePoint search sevice not working, inspite of a Search Service Application being associated. This is what I did to solve this:
I had this problem as well on my SharePoint 2010 machine and I feel this specifically occurs when you have the Domain Controller running on the same machine. I sorted out with the following steps:


  
  1. Deleted the 3 databases that gets created along with a Search Service Application from SQL Server directly
  2. Stopped the SharePoint Search Service using stsadm command
  3. Reset all the crawled index
  4. Started the Search Service again using stsadm
  5. Created a new Search Service Application (I also ensured - the same account - for example spsearch is used for the Crawl Service, Search Service and Query Service Application pools) - previously I had admin account for the Crawl Service and the custom account for the application pools)
  6. iisreset - bingo - started working :)

 

Comments

  1. Colud you please provide a tutorial for "Reset all the crawled index" because I delete the service and I think the crawled index is the problem.

    ReplyDelete
    Replies
    1. $searchApp = Get-SPEnterpriseSearchServiceApplication -Identity “SearchAppName”

      if($searchApp -ne $null) {

      $searchContext = [Microsoft.Office.Server.Search.Administration.SearchContext]::GetContext($searchApp)

      $searchContext.Reset($true)

      }

      Delete

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

HTTPS Site InfoPath Issue : You do not have permissions to access a web service that provides data required for this form to function correctly

Windows 7 Blue Screen because of ConnectiFy