Anna
Fri Aug 29 11:10:30 CDT 2008
Hi,
Restart search service, that's the first thing to do.
You can do it from services or using stsadm command.
It will reset your index file content and you will have to crawl all docs
again but it will also ensure that you have updated data in your index file.
What are these error messages exactly (event id's numbers??). Did you check
ULS logs?
Enable also the diagnostic logging (central admin>operations) and choose to
gather search related events.
Install the latest updates, infrastructure update above all. They contain
many fixes for search as well.
Anna
"Rockn" <Rockn@newsgroups.nospam> wrote in message
news:O%23i3s9sBJHA.1628@TK2MSFTNGP03.phx.gbl...
> We are running WSS3, and no changes or updates recently, the search
> service just stopped working.
>
> I reset the service account password again, but have not restarted the
> service yet. I have heard that the search database or the indexes can
> become corrupted which may be the case. The event logs show a couple of
> errors prior to all hell breaking loose and red balls everywhere:
>
> A new query machine, 'GRWEB', has been added to the query rotation based
> on changes to farm topology. Component:
> b5682da5-f95d-421d-b84b-c28772a9a0f3
>
>
>
> Query machine 'GRWEB' has been taken out of rotation due to this error:
> The system cannot find the file specified. 0x80070002. It will be retried
> in 15 seconds. Component: b5682da5-f95d-421d-b84b-c28772a9a0f3
>
>
>
> The accout has all of the proper DCOM permissions..
>
>
> "Anna" <Anja_Amelia@hotmail.com> wrote in message
> news:O4MZ1nsBJHA.1892@TK2MSFTNGP04.phx.gbl...
>> Hi,
>> which version of wss do you have? Recent updates/sp installed?
>> What kind of errors you find in the event logs related to search/timer?
>>
>> Have you tried to change password under the search service is running?
>>
>>
>> Anna
>>
>> "Rockn" <Rockn@newsgroups.nospam> wrote in message
>> news:uWMIJ5rBJHA.3496@TK2MSFTNGP03.phx.gbl...
>>>I am having issues with the search service in WSS3 and keeping it
>>>running. The search service is currently in a "stopping" state and never
>>>actually stops. Rebooting the server takes care of the error for a while,
>>>but the service will stop functioning again the next day. Looking through
>>>the event logs the Timer service is also throwing a lot of errors related
>>>to the search service.
>>>
>>> stsadm command line commands will also not start or stop the service.
>>>
>>
>>
>
>