RE: Search Crawl stuck in Stopping State

2011-08-06 Thread Paul Culmsee
I've seen this before. I didn't reply earlier because I hit it with WSS3
search, but that error message is telling. maybe this might help or help you
narrow things down.

 

http://www.cleverworkarounds.com/2009/08/03/troubleshooting-spsearch-and-goo
d-practices-for-moving-large-files/

 

 

 

From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf
Of Nigel Witherdin
Sent: Friday, 5 August 2011 7:50 AM
To: OzMoss
Subject: RE: Search Crawl stuck in Stopping State

 

Hi,

 

The ULS show this error relating to search (though it seems to be query
related, not crawl):

 

Caught exception while retrying Tripoli component: 0x80070002
ddb9e893-6060-46a3-8b12-a7be0e432581

CTripoliConnectionWrapper::SignalError with 0x80070002.
ddb9e893-6060-46a3-8b12-a7be0e432581

Error 0x80070002 from component SVMSP003PR on machine
82c100d7-f0f0-4732-b5a6-aef8a7902756-query-3.
ddb9e893-6060-46a3-8b12-a7be0e432581

_RLokErrorKind In: 0x80070002.  ddb9e893-6060-46a3-8b12-a7be0e432581

_RLokErrorKind Out: 0x80070002, Type: 2.
ddb9e893-6060-46a3-8b12-a7be0e432581

Retry of query component 82c100d7-f0f0-4732-b5a6-aef8a7902756-query-3 has
failed with error: The system cannot find the file specified.   0x80070002.
It will be retried again in 64 seconds.
ddb9e893-6060-46a3-8b12-a7be0e432581

 

Cheers,

 

Nigel

 

  _  

From: akhanna...@gmail.com
Date: Thu, 4 Aug 2011 21:44:31 +1200
Subject: Re: Search Crawl stuck in Stopping State
To: ozmoss@ozmoss.com

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
nigel_wither...@hotmail.com wrote:

Probably as a last resort

 

Cheers, 

  _  

From: jos...@beyondurban.com
To: ozmoss@ozmoss.com
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: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] 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: lied...@hotmail.com
To: ozmoss@ozmoss.com
Subject: RE: Search Crawl stuck in Stopping State
Date: Thu, 4 Aug 2011 10:58:01 +0930

Hi Nigel,

  Have you tried to restart the search service?

Ken

  _  

From: nigel_wither...@hotmail.com
To: ozmoss@ozmoss.com
Subject: Search Crawl stuck in Stopping State
Date: Thu, 4 Aug 2011 01:11:52 +

Hi 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
'SVMSP005PR'.
 
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
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___ ozmoss mailing list
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___ ozmoss mailing list
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss



___ ozmoss mailing list
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Search Crawl stuck in Stopping State

2011-08-04 Thread Nigel Witherdin

Hi,
The ULS show this error relating to search (though it seems to be query 
related, not crawl):
Caught exception
while retrying Tripoli component: 0x80070002  
ddb9e893-6060-46a3-8b12-a7be0e432581

CTripoliConnectionWrapper::SignalError
with 0x80070002.ddb9e893-6060-46a3-8b12-a7be0e432581

Error 0x80070002 from
component SVMSP003PR on machine
82c100d7-f0f0-4732-b5a6-aef8a7902756-query-3.
ddb9e893-6060-46a3-8b12-a7be0e432581

_RLokErrorKind In:
0x80070002.  ddb9e893-6060-46a3-8b12-a7be0e432581

_RLokErrorKind Out:
0x80070002, Type: 2.   ddb9e893-6060-46a3-8b12-a7be0e432581

Retry of query
component 82c100d7-f0f0-4732-b5a6-aef8a7902756-query-3 has failed with error:
The system cannot find the file specified.   0x80070002. It will be
retried again in 64 seconds.   
ddb9e893-6060-46a3-8b12-a7be0e432581
Cheers,
Nigel
From: akhanna...@gmail.com
Date: Thu, 4 Aug 2011 21:44:31 +1200
Subject: Re: Search Crawl stuck in Stopping State
To: ozmoss@ozmoss.com

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 nigel_wither...@hotmail.com 
wrote:







Probably as a last resort
Cheers, 

From: jos...@beyondurban.com
To: ozmoss@ozmoss.com


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: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] 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: lied...@hotmail.com


To: ozmoss@ozmoss.com
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: nigel_wither...@hotmail.com
To: ozmoss@ozmoss.com
Subject: Search Crawl stuck in Stopping State


Date: Thu, 4 Aug 2011 01:11:52 +Hi 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 
'SVMSP005PR'.

 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 
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___ ozmoss mailing list 
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss   
  

___

ozmoss mailing list

ozmoss@ozmoss.com

http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss





___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss   
  ___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Search Crawl stuck in Stopping State

2011-08-03 Thread ken zheng

Hi Nigel,

  Have you tried to restart the search service?

Ken

From: nigel_wither...@hotmail.com
To: ozmoss@ozmoss.com
Subject: Search Crawl stuck in Stopping State
Date: Thu, 4 Aug 2011 01:11:52 +








Hi 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 'SVMSP005PR'.

 

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
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss   
  ___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Search Crawl stuck in Stopping State

2011-08-03 Thread Nigel Witherdin

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: lied...@hotmail.com
To: ozmoss@ozmoss.com
Subject: RE: Search Crawl stuck in Stopping State
Date: Thu, 4 Aug 2011 10:58:01 +0930








Hi Nigel,

  Have you tried to restart the search service?

Ken

From: nigel_wither...@hotmail.com
To: ozmoss@ozmoss.com
Subject: Search Crawl stuck in Stopping State
Date: Thu, 4 Aug 2011 01:11:52 +








Hi 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 'SVMSP005PR'.

 

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
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss   
  

___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss   
  ___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss


RE: Search Crawl stuck in Stopping State

2011-08-03 Thread Nigel Witherdin

Probably as a last resort
Cheers, 

From: jos...@beyondurban.com
To: ozmoss@ozmoss.com
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: 
ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] 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, NigelFrom: lied...@hotmail.com
To: ozmoss@ozmoss.com
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?

KenFrom: nigel_wither...@hotmail.com
To: ozmoss@ozmoss.com
Subject: Search Crawl stuck in Stopping State
Date: Thu, 4 Aug 2011 01:11:52 +Hi 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 'SVMSP005PR'. 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 
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___ ozmoss mailing list 
ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss   
  ___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss