.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Crawl Component Resilience Requires Sharepoint Server Search Administration Component?

Posted By:      Posted Date: September 06, 2010    Points: 0   Category :SharePoint
I have a single crawl database and two crawl components pointing to that crawl database. One of the crawl components also has the Sharepoint Server Search Administration component running. When I close down the server running the Sharepoint Server Search Administration component crawling stops. I removed the crawl component from the server running Sharepoint Server Search Administration component and reindexed and this worked. So the additional crawl component works fine. Checked that incremental crawl would run in 5 minutes. Downed the Sharepoint Server Search Administration component server and uploaded some new content. Crawling did not run. Can anyone confirm that this is expected behaviour? I am now trying to transfer the Sharepoint Server Search Administration component to the other server as part of Disaster Recovery preparation and this is failing as per another recently opened problem.  

View Complete Post

More Related Resource Links

Move Sharepoint Search Administration Component

I am failing to transfer the Sharepoint Search Administration component from one Application Server to another. Using the -Force parameter generates the same result. The $admin and $searchInstance are valid objects. Seems a bit chicken and egg. I am trying to move the web service and the complaint is that the web service is not on the server! PS C:\Users\sp2010setup> $admin | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $searchInstance Set-SPEnterpriseSearchAdministrationComponent : SharePoint Server Search Admin Web Service is not started on server FOOBARSAS2. Please start it and try ag ain. At line:1 char:55 + $admin | Set-SPEnterpriseSearchAdministrationComponent <<<<  -SearchServiceIn stance $searchInstance     + CategoryInfo          : InvalidData: (Microsoft.Offic...rationComponent:    SetSearchAdministrationComponent) [Set-SPEnterpris...rationComponent], Inv   alidOperationException     + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchA    dministrationComponent

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

I encounter the error above when trying to set up Sharepoint Server Search. I have tried both setting up search manually through Central admin (just selecting default for everything) as well as through Powershell (using this: http://stsadm.blogspot.com/2009/12/creating-sharepoint-2010-enterprise.html). I'm using the farm admin as Search account as well as account for Application pools, so I guess permissions should not be the issue.Creating new Search service application seems to be successful, but when going to Searchadministration after creation, then System status displays the error above. Event log does add any info and just displays same error message ("SearchApi.cs throws exception:The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'db397ab0-d9b0-46c4-9077-dc8be62bf586' in search application 'TNS Enterprise Search Service Application' is in a good state and try again."). I have found this http://blog.fpweb.net/sharepoint-2010-server-search-troubleshooting/ stating that the solution is not to use MSDN version of Windows 2008, but does give any explanation why.Any ideas would be appriciated.Best regardsThomas

SharePoint search server 2010 crawl rules

My client wants to create a number of scopes by crawling specific subsites of a CMS 2.0 site.  The CMS site is crawled as a website and security is ignored (e.g. results are not security trimmed). As an example, they want to create a scope called “Audit”.  This scope will use a content source which crawls all content starting at http://server/services/audit and http://server/wssservices/audit. The first is the CMS 2.0 site, the second is a WSS 3.0 site that contains documents for the CMS site. I setup the content source with start address of http://server/services/audit and http://server/wssservices/audit with the crawl settings set to ‘only crawl within the server of each start address’. Additionally, I have created rule with path http://server/services/audit* and set the configuration to “Include all items in this path”, with “Crawl SharePoint content as http pages” also selected.  I have created rule with path http://server/wssservices/audit* with the same configuration settings, except  “Crawl SharePoint content as http pages” is not selected . I have also performed a full crawl after creating the content source and crawl rules. What I would expect to happen is that only results from http://server/services/audit or documents linked from http://server/wssservices/audit would show i

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

I'm expierencing this error message and am not sure what to do to fix this.  I don't want to break anything else on our farm.   The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '9139bef7-69a3-4125-9d0e-e09484cc24ee' in search application 'Search Service Application' is in a good state and try again. Nothing appears under topology.  It just continues to load.  Any suggestions would be appreciated.

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

I just installed the FAST Content Search Service Application.  However, when going to Application Management -> Manage Service Application -> FAST Content SSA, I see the following error:

Crawl status The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'e5ece22e-b215-4c8e-a661-5f20d526de78' in search application 'FAST Search Content SSA' is in a good state and try again. 
Clicking on Content sources brings me to

System.InvalidOperationException: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'e5ece22e-b215-4c8e-a661-5f20d526de78' in search application 'FAST Search Content SSA' is in a good state and try again. 
   at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(SearchServiceApplication application) 
   at Microsoft.Office.Server.Search.Administration.SearchApi.CreateSearchApi(SearchServiceApplication application) 
   at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.get_SearchApi() 
   at Microsoft.Office.Server.Search.Administration.ContentSourceCollection..ctor(Content parent) 
   at Microsoft.Office.Server.Search.Administration.Content.get_ContentSources() 
   at M

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


I was able to create search service , Now i am getting the below error, I ran deleted all the databases, ran psconfig. SSA will be created, but i have the below error

Alos tried recreating service with powershell same error

 System Status    
Crawl status The search service is not able to connect to the machine that hosts the
administration component.
Verify that the administration component 'f26229c3-41f4-4520-865a-2857a0125503' in search
application 'Search Service Application' is in a good state and try again.

but When I check the service, hrere are the results

Name                  : Search Service Application
Id                    : 98c098d0-e92a-47c7-9661-9c81d73a6cd9
ServiceName           : SearchQueryAndSiteSettingsService
QueryTopologies       : {711933b2-7325-43f9-b081-8e6760ec8f1e}
PropertyStores        : {Search_Service_Application_PropertyStoreDB_3e2df6fc77e

SharePoint 2007 Search error Retrieving the COM class factory for component with CLSID {5AD0CC67-477


Hi All,

SharePoint search started failing all of a sudden, so I did some reading and performed "Reset all crawled content". Now the crawl is running fine, however, when search is performed on the site, following exception is thrown:

System.Runtime.InteropServices.COMException (0x800703FA): Retrieving the COM class factory for component with CLSID {5AD0CC67-4776-4D91-B9A8-0078B0BAF32D} failed due to the following error: 800703fa. at Microsoft.Office.Server.Search.Query.QueryInfo.InitializeCanaryChecker() at Microsoft.Office.Server.Search.Query.QueryInfo.GenerateDigest(Page CurrentPage) at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.ClickLogPostdata() at Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart.OnPreRender(EventArgs e)

I came across only one post when I searched for this particular problem and I don't believe we have the same case here. [http://social.technet.microsoft.com/Forums/en-GB/sharepointadmin/thread/84861057-d862-464d-b5fc-888db5bd6805]

Any help would be great.

SharePoint Portal Server 2001: Search and Access Disparate Data Repositories in Your Enterprise


The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.

Kayode Dada

MSDN Magazine April 2002

Office Sharepoint Server Search not working but Windows Server Search is.

I am having an annoying Issue with the Sharepoint 2007 Enterprise search functionality. I cannot get the Search Centre to work, the out of the box webparts crash the page except the Searchbox when the others are closed. The event viewer shows up numerous Errors (Office Sharepoint Server - EventID 7080) returns with and the same when trying to add a search related web part (e.g. core.results, federated etc). EventID 6398 - Timer is a regular as is 7080. Details below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).

Remote connections are connected, I am not 100% on the Instance name, (how would I go about checking this?)

Also I cannot access the link to SharedServices1 - Open Shared Services Admin site (not clickable), guess it's permissions but I seem to have full site permissions, I think I need SSP-Admin to make more edits to the Search, maybe this is related :s

Both Search Servers are runnig, I have tried everything I can think of to fix this and allow the Search Centre to work.

I am running Sharepoint 2007 on SQL Server 2008.

SharePoint Enterprise Search Migration Tool for SharePoint Server 2010

Use this tool when you upgrade to SharePoint Enterprise Search to migrate search-related data, such as best bets, search scopes, and site collection search settings.

FAST Search for SharePoint Server 2010 SDK

Learn how to develop and deploy search solutions in SharePoint Server 2010.

Search Customization and Development Options in SharePoint Server 2007

Examine the powerful platform of SharePoint Server 2007 search for the end user and developer. Learn about the built-in Web Parts for search and writing search queries for your applications.

Displaying the Server Ribbon and Site Actions Menu on Customized Search Pages Upgraded to SharePoint

Learn how to add the Site Actions menu and SharePoint Server ribbon to SharePoint Server 2007 search pages that you upgrade to SharePoint Server 2010 by using visual upgrade.

MS Word Component Not Getting Created on Windows 2008 64 bit Web Server Edition When I Try Using ASP

Hi All, This might look like a similar question to a lot of you considering there are a lot of web activity happening in terms of blogs/forums/suggestions that I have seen with reference to changes that one needs to do in COM+ Services to enable their ASP.NET Web Application to be able to create Word Objects & I have actually used them personally & they worked for me on Windows 2003 32 bit/64 bit servers. The issue started some 1 month back when I was told that we are upgrading our server to Windows 2008 Web Server edition 64 bit ‘cause of some real benefits it offers if used only as a web server. This was just great as we tested a lot of features /functionality that we were using on our existing server & everything seems to be working just fine on this product by Microsoft. However we also have one web module which is responsible for opening up a MS Word 2007 template file at runtime and fill it with data & is then converted into a PDF document. A lot of ideas on Web suggested that we should move onto Open XML standards to generate documents at runtime, which I have been able to do with no issues. But one activity which still requires me to create a Word document is when I have to convert/SaveAs the Word (docx) document into PDF. I tried all the COM+ & registry related changes that I did on my Windows 2003 64 bit server, but nothing seems

Solution deployment requires executing execadmsvcjobs command on search server to complete deploymen

We have multiple Sharepoint 2007 farms and deploy custom code weekly to the farms. On one o the farms it is required to run stsadm -o execadmsvcjobs on the Search server in the farm in order for solution deployments to complete deploying. These are solution recycles that we are running. This is the only farm this happens on and all farms are identical. In central admin it shows the solution state as deploying. Farm Config Sharepoint 2007 SP2 w Dec Cumulative updates 1 WFE 1 Search server 1 SQL server

Failed to change Farm Account in Sharepoint 2010 server, now Central Administration is not accessibl

Hello, I have a problem, that I no longer can access Central Administration Website, only the Sharepoint itself. I was running installation of Sharepoint 2010 Server with administrative account ImTheAdmin, who is a Domain Admin in the domain on one of the Windows 2008 R2 member servers. Besides that, I made ImTheAdmin the primary administrator of the Sharepoint. ImTheAdmin became the only user of this Sharepoint 2010 server after installation.  I installed everything on one box with default installation settings. I used builtin SQL server, not Standard or Enterprise. What then happened is: Using ImTheAdmin account, I opened Central Administration Website, and it said, that I need to change the Farm Account, for the account for Farm was the default one (I think it was network service). So I created a regular domain user MYDOMAIN\SharepointFarmAccount. The account name was too long to be as a Windows 2000 name, so it showed there without last 't', e.g. MYDOMAIN\SharepointFarmAccoun. I thought, Windows 2000 is long gone, so I didn't pay much attention, I think everywhere the account SID is important. I don't know if that is the real problem with my failure later, but it might be one of the reasons. I put MYDOMAIN\SharepointFarmAccount down in to the form of Central Administration Website, added the check mark, that it would react to password changes, and pre

SharePoint Server 2010 Search - not returning results but crawling without errors

I have created a Search Service Application on a SharePoint Server 2010 (RTM) Farm and used the default Content Source. I started a Full Crawl and it suceeded with no errors etc. I ran it a few times and no issues. But if I go to the Intranet Portal Web Appliaction and do a search for a document that would have been crawled it does not show up in search results...nothing does. I am not getting any errors in Event Log or ULS Logs relevant to Search. How can I troubleshoot this problem further?SharePoint Solution Architect, Perth Australia - Microsoft Virtual Technology Specialist - MCTS WSS Dev, WSS Adm, MOSS Dev, MOSS Adm - http://wss.made4the.net/ - Founder of http://www.sharepointdevwiki.com/
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend