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

SQL Membership Provider - Lockeuser question

2011-08-04 Thread Paul Noone 
Hi all,
We have an FBA app that uses a simplfieid version of the FBA Users project on 
Codeplex.

I have a small issue where users are being locked out (correctly) but not 
receiving adequate feedback.

I am trying to check the IsLockedOut status of a locked out user during login 
but am getting the exception message when running the following.

private void InitialiseUser()
{
var username = UserName.Text;

try
{
  user = Membership.GetUser(username);
}
catch (Exception ex)
{
  Lblerror.text = ex.Message;
}
}

Could this be because locked out users immediately return an exception?

The associated event code is:

Event code: 4005
Event message: Forms authentication failed for the request.
Reason: The ticket supplied has expired.
Event sequence: 2
Event occurrence: 1
Event detail code: 50202
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss

RE: SQL Membership Provider - Lockeuser question

2011-08-04 Thread Paul Noone 
S'ok. I was half right. :)
Apparently I should be using the LoginError event which captures locked out 
users as well as general authentication failures.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of 
Paul Noone
Sent: Friday, 5 August 2011 1:20 PM
To: ozMOSS (ozmoss@ozmoss.com)
Subject: SQL Membership Provider - Lockeuser question

Hi all,
We have an FBA app that uses a simplfieid version of the FBA Users project on 
Codeplex.

I have a small issue where users are being locked out (correctly) but not 
receiving adequate feedback.

I am trying to check the IsLockedOut status of a locked out user during login 
but am getting the exception message when running the following.

private void InitialiseUser()
{
var username = UserName.Text;

try
{
  user = Membership.GetUser(username);
}
catch (Exception ex)
{
  Lblerror.text = ex.Message;
}
}

Could this be because locked out users immediately return an exception?

The associated event code is:

Event code: 4005
Event message: Forms authentication failed for the request.
Reason: The ticket supplied has expired.
Event sequence: 2
Event occurrence: 1
Event detail code: 50202
___
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss