Hey Guys, As an update to this, I recreated the crawl components in my topology and this resolved my issue - crawl now running currently indexed 65,000 items Cheers, Nigel From: [email protected] Date: Thu, 4 Aug 2011 21:44:31 +1200 Subject: Re: Search Crawl stuck in Stopping State To: [email protected]
Did you find any pointer to possible cause of this in the ULS logs or Windows Log. On Thu, Aug 4, 2011 at 3:16 PM, Nigel Witherdin <[email protected]> wrote: Probably as a last resort Cheers, From: [email protected] To: [email protected] Date: Wed, 3 Aug 2011 19:38:58 -0700 Subject: RE: Search Crawl stuck in Stopping State Seen this a few time unfortunately. The only way I have been able to resolve this is to delete the search service app. Is this an option? Cheers Josh From: [email protected] [mailto:[email protected]] On Behalf Of Nigel Witherdin Sent: Thursday, 4 August 2011 11:32 AM To: OzMoss Subject: RE: Search Crawl stuck in Stopping State Hi Ken, I have tried restarting the service from the services.msc snap-in on all boxes (and confirmed that this did actually remove the "mssearch.exe" process), and have also tried restarting the timer service on all boxes, but this did not help Cheers, Nigel From: [email protected] To: [email protected] Subject: RE: Search Crawl stuck in Stopping State Date: Thu, 4 Aug 2011 10:58:01 +0930Hi Nigel, Have you tried to restart the search service? Ken From: [email protected] To: [email protected] Subject: Search Crawl stuck in Stopping State Date: Thu, 4 Aug 2011 01:11:52 +0000Hi All, At a customer site where the environment is SP 2010 using Enterprise search, the crawl of the “Local SharePoint site” content source is stuck in a state of “Stopping”. Have attempted to force the crawl to stop by using the PowerShell commands: $searchapp = Get-SPEnterpriseSearchServiceApplication "Search Service Application" $contentsource = Get-SPEnterpriseSearchCrawlContentSource "Local SharePoint Sites" -SearchApplication $searchapp $contentsource.StopCrawl() However this does not appear to have any affect. Also tried the STSADM command: Stsadm –o osearch –action stop But this gives the response: 'stop' action failed. Additional information: Invalid search service unprovisioning: application 'Search Service Application' still has a ready component '82c100d7-f0f0-4732-b5a6-aef8a7902756-crawl-1' on server 'SVMSP0000005PR'. Not sure what is the best way to progress – need to stop the crawl so I can reconfigure the content source, reset the index and then recrawl the corpus. Any advice would be greatly appreciated. Cheers, Nigel _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
