Search Administration crawl continues to pause

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.  

I am attempting to do a full crawl (FAST Search) of a handful of Word, Excel, PowerPoint documents. Has been running for ~3 hours. If I look at the Crawl Queue report in the Administrative Report Library it shows 150 transactions queued. Crawl Processing per Activity - the last entry on the graph is 300 seconds for Initializing Document Filtering for what looks like the entire 2 hrs SQL Server, SharePoint Server and FAST Search servers appear to all have low utilisation (cpu, memory, disk). There are only 2 warnings in the FAST Search crawl log (don't crawl search site and search cache directory). Success = 0, Error = 0, Warning = 2. Before I setup FAST Search, SP Search took approx 6 minutes to crawl a similar list of documents. How do I troubleshoot the issue?

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

Hello,      I have been tasked with building a custom application to develop a report dynamically based upon a search ran in a SharePoint site using user-defined keywords. What I need the application to do is this: 1.) Access the results of a search, and do a full fidelity save of each item. 2.)  If the item returned is a document in a library and it has other versions associated with it, access the meta-data of those other versions and group those results with the item found in the search. 3.) Store the results in XML (probably the easiest), and build a custom display for reporting purposes. If anyone has any advice on how I can accomplish this, I would be very grateful, Thanks!

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

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

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.

I have FAST Search Server for SharePoint 2010 installed in a small testing farm. After the backend and fronent configurated and certificate imported, any of the content crawler I setup there couldn't finish crawling. Neither is any item indexed from the crawl log and I kept monitoring. In some circumstance I can find some warning messages if the authorization didn't pass or something else, but never any content seccessfully indexed. No error or fatal error found either. The execution of following script returned no count:

Get-FASTSearchContentCollection -name "sp"

From the database server I can tell the FAST Server created 7 databases, 3 crawler databases and 3 query databaes plus one Admin db. I monitored that the content in CRAWLSTOREDB is slowly updating, but didn't grow much.

What can I try to see if the CRAWLing activity is going on and if there are any configuration problems? It doesn't seem to be a perfomance problem since the crawler couldn't even complete crawling only a few files from a shared folder.

 Thanks in advance.

Chris

SharePoint 2010 search crawl error:
The SharePoint item being crawled returned an error when requesting data from the web service. ( Error from SharePoint site: Specified argument was out of the range of valid values. )

This error is for both document and folder. The document and folder were created/uploaded via SharePoint User Interface only. Later these doc/folder were deleted. And we found the search result showing the documents that were deleted from the doc library resulting in '404 page not found error' upon clicking. Ofcourse we did an incremental crawl after  deleting the file/folder. The error is same even after full crawl.

Environment details:
1 server - WFE role
1 server - App server role
1 server - index server role

Another information if helpful: We used some third party tool to migrate few sample data in the same server but on different site collection, different content database but on the same web application. The tool migrated the data and set unique permissions too for the migrated files. We tried deleting them via SharePoint interface and that files too gave a similar error!

In Search Administration; Default content access account show 'Error'.
To fix it, I have to always restart 'Office Search Service'.

But need to find permanent solution.

I went through various blogs and found below blog with sucess response.
http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/84f93fbe-f4a6-4683-b25b-b595b9006ad7
I tried same on my server but did not help.

Can someone help?

Hello,

I'm trying to schedule the full crawl of search.

I'm configuring the crawl and in Central Administration/Search Service Application: Edit Content Source in crawl schedules, I choose create schedule for full crawl. A popup appears , I select 1 AM and when I press OK,a popup appears at the SERVER's window (not the internet explorer) saying: An unhandled exception (system.UnauthorizedAccessException) occurred in w3wp.exe [5112]. The just-in-time debugger....

Doing full crawl works, but i'm trying to do scheduled ....

The message is (VS 2010 Debugger):Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

The stack trace (VS 2010 Debugger) is :

Microsoft.Office.Server.Search.Administration.CTaskScheduler.Microsoft.Office.Server.Search.Administration.ITaskScheduler.NewWorkItem(String TaskName, Guid& rclsid, Guid& riid, Object& obj)

   at Microsoft.Office.Server.Search.Administration.TaskScheduler.GetITask(String fileName)

   at Microsoft.Office.Server.Search.Administration.TaskScheduler.GetTriggerDescription(TaskTrigger taskTriggerArg)

   at Microsoft.Office.Server.Search.Administration.TaskScheduler.<GetTriggerDescriptionInSecurityContext>b__0()

   at Microsoft.Office.Server.Security.SecurityContext.RunAsPr

Hi,

We installed MOSS on our clients machine and Search has been problematic from the getgo.

When we have performed a forced restart on the osearch service (http://bruteforcesharepoint.blogspot.com/2009_04_01_archive.html), within the next couple of hours the crawler status wil be Error. But, search at this point is still working. Indexing basically stops and event errors are thrown in the event logs, but searching is still possible.

Here are the symptoms:

• the Crawl status is 'Error'
• /ssp/admin/_layouts/searchsspsettings.aspx (Search Settings page) is throwing a HTTP 403 error : The website declined to show this webpage.
• I can still get to the Search Administration, and when I go to view the Content Sources or view the crawl logs specifically, I get the same 403 error.

When I try to 'Reset all crawled content', that is when Search dies. I get the message an exception error message.

When I try to stop the Office SharePoint Search service in Central Admin, it hangs in the Stopping state. It'll only come out of this if I go through the task manger and manually force the process to stop and then start it again using the stsadm -o osearch -action start -role index command then search starts again. And I have to reset the crawled content and perform a f

Can anyone help me figure out why I am not able to crawl the Content Sources for the FAST Search Connector?

The error from the ULS viewer is:

Failed to connect to 1sv-sp2010.wirestone.internal:13391 Failed to initialize session with document engine: Unable to resolve Contentdistributor

I followed the install steps found at http://technet.microsoft.com/en-us/library/ff381267.aspx, including the post install validation.  FAST seems to be working in every way except the crawl.

The port number 13391 was found in Install_Info document. "Content Distributors (for GUI SSA creation):          1sv-sp2010.wirestone.internal:13391"

Thanks,

Craig

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

 Error 
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

Hi,

I created an external content type by creating a new Visual Studio sharepoint project, and creating a content type (The default Entity1 content type). I created a profile page for it and everything, and when I drilled into the content type in central admin - BCS, I saw it wasn't marked as crawlable.

I saw this similar post: http://social.msdn.microsoft.com/forums/en-us/sharepoint2010general/thread/281BCEFD-59EC-41CC-B948-458A4BDA9E49

So I then created an external content type through SPD, leveraging the same code, and creating an external list and profile page. This time, when I drilled into the external content type in the BCS administration, it showed "Crawlable: Yes".

I figured at that point I was good to go, but when I went to my search service application -> Content Sources -> New Content Source and selected Line of Business Data, and selected BDC, it still says "No external data sources to choose from."

I verified also that the account for crawling has permissions for the external content type.

Are there any other things I should be looking for? From everything I read this should "just work" now :)

Thanks,

Bryan

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
              &nb

I am having an issue with indexing user profiles with the SPS3 protocol handler.   Each time it runs I get an "Access Denied" error in my crawl logs.   I have verified that the default content search account has full read permissions on the web application.   I have verified that I don't have a  loop back check issue.

In my environment I have 3 seperate web applications.  One hosts intranet publishing content, one hosts collaboration content and the third is for the mysites.   The web applications all use host headers and share a single IP address.   Everything is over HTTP.

My dev farm is configured with a single web front end, a single services server and a SQL server.    The services server is running the search admin and crawl components.  The web front end hosts the query component.

In the search content source the URL being crawled is SPS3://mysites.domain.com and http://mysites.domain.com.   In the crawl logs it shows the following error for SPS3://mysites.domain.com:

Access is denied. Verify that either the Default Content Access Account has access to t