How to fix broken WSS Crawl/Search

After moving SQL Databases from one server to another in my WSS Farm, Search had a little hissy fit on me.

 

When trying to force a SharePoint crawl…

STSADM -o spsearch -action fullcrawlstart

 

I got this…

‘fullcrawlstart’ action failed. Additional information: Object reference not set to an instance of an object.

 

And the in the Event Log, I had this…

EVENTID 10039
Retry of query machine ‘ITGUS1VMG002’ has failed with error: The system cannot find the file specified.   0x80070002.  It will be retried again in 900 seconds. Component: 1dd5dd14-5a71-438a-9f45-2c74eedc11fa

 

So, to fix it, I had to do this…

1. Performed a Stop of Search (using STSADM)

stsadm.exe -o spsearch -action stop

Which warned me with the following (I chose Yes).

Warning: The Windows SharePoint Services Search service that was enabled on this server will be uninstalled and all index files will be deleted.  Are you sure you want to permanently delete all data in the index? [y/n]

 

2. Performed an IISRESET (when in doubt…)

 

3. Then I reset/built my search settings in Central Admin (choose Start on Windows Search and configure the service with a new database, and appropriate credentials)

 

4. Then I reran my crawl and sure enough, it was happy this time…

 

STSADM -o spsearch -action fullcrawlstart

One response to “How to fix broken WSS Crawl/Search

  1. Thanks Sean! I had the same issue after moving our WSS3 site databases. Those steps worked perfectly.
    Except our event log had:
    Event ID 10032
    Could not create a database session.
    Context: Application ‘8ce145d1-be74-4615-b062-a325b7100c36’
    Details: The database connection string is not available. (0xc0041228)

Comments are closed.