WDS3.01 No files indexed

I have installed WDS 3.01 (a few times now) and it looks like it has installed correctly, but the number of files indexed always remains at zero.

There are some errors in the application that appear to be relevant...
There are a few of these:
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3100
Date: 28/02/2007
Time: 11:00:36
User: N/A
Computer: CPU-701642
Description:
Unable to initialize the filter host process. Terminating.
Details: 0 (0x80040150 - Could not read key from registry)

Sometimes the details are:
This operation returned because the timeout period expired. (0x800705b4)

And also there is this error:
Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3024
Date: 28/02/2007
Time: 11:04:37
User: N/A
Computer: CPU-701642
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Windows Application, SystemIndex Catalog

And this warning:
Event Type: Warning
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3036
Date: 28/02/2007
Time: 11:04:37
User: N/A
Computer: CPU-701642
Description:
The content source <c:\documents and settings\> cannot be accessed.
Context: Windows Application, SystemIndex Catalog
Details: This operation returned because the timeout period expired. (0x800705b4)

Any suggestions on how to fix this would be appreciated

thanks
Mark

Answer this question

WDS3.01 No files indexed

Esenthel
I have restarted a number of times now, but still no files indexed and the same errors in the application log.

I am running Windows XP Professional with SP2 & up to date with patches from Windows Update

thanks
Mark
asisurfer

One potential cause of event 3100 (SearchFilterHost failing to start) is if you have the search service set to interactive. You can check if this setting is on by going to control panel -> Adminstrative Tools -> Services, right click on the Windows Search service and click properties. On the Log On tab there is a setting called "Allow service to interact with desktop." If you uncheck that box and restart the search service it should work again.

Please post back here and let us know if this worked or not. We are still trying to understand how this option gets checked in cases where the user doesn't manually set it. Any additional information you could give us would be helpful
Colin T.
thanks for the suggestions David,
unfortunately, it hasn't fixed my problem - no files are being indexed (although I haven't had any new errors appear in the application log since I followed your instructions)

Mark
Nayan Paregi
(Apologies for jumping in here).

Hi,

I have had the exact same symptoms and error messages (3100) with no success at indexing anything.

Tried your suggestion above, still with no success, still with 3100 error. Did get event logs that the catalog was being deleted (1010) and a new SystemIndex created (1004) and confirmed (1005). On starting WDS, however, indexing just does not happen.

Sorry, I am actually using 3.0 but the symptoms are identical and I am finding it hard to find much useful info about what the problem might be.
Shirish Pulikkal
I have the same problems as everyone else above. I tried the suggestion that David posted and didn't have any luck. This is severely crippling my ability to find any messages in Outlook 2007, please help!
HiTech2k
It's not set to interactive. I install/uninstall WDS at least 10 times. By default, the install program doesn't set Allow service to interact with desktop.
asalcedo
Try the automated reset in WDS advanced options. If that doesn't fix it try this:

1) Close all applications (esp Outlook). Stop Indexing service “cmd: net stop wsearch” and check in TaskManager’s process list that SearchIndexer.exe was really stopped.

2) Delete %SystemDrive%\ProgramData\Microsoft\Search\Data\Applications\Windows folder with all its files and subfolders.

3) Delete following registry keys: (You’ll have to change reg key ownership to administrators and change permissions to grant full control for administrators.)

a. “HKLM\Software\Microsoft\Windows Search\Applications\windows”

b. “HKLM\Software\Microsoft\Windows Search\CatalogNames\windows”

c. “HKLM\Software\Microsoft\Windows Search\Databases\windows”

d. “HKLM\Software\Microsoft\Windows Search\Gather\windows”

e. “HKLM\Software\Microsoft\Windows Search\Gathering Manager\Applications\windows”

f. “HKLM\Software\Microsoft\Windows Search\UsnNotifier\windows”

4) In registry, under the key “HKLM\Software\Microsoft\Windows Search” switch “SetupCompletedSuccessfully” subkey to “0” – you’ll have to change reg key ownership and change permissions first.

5) Start indexing service back “cmd: net start wsearch”

6) Wait until “SetupCompletedSuccessfully” subkey switches back to 1.

Let me know.
enric vives
I am experiencing the same issues. I've attempted several uninstalls/installs and re-indexing but to no avail.

My next track of exploration will involve disabling my anti-virus (McAfee VirusScan Enterprise 8.0i) which I don't really like to do but I'm getting warning messages from VSE at about the same time as the "Windows Search Service" errors.

Has there been any progress in the investigations at Microsoft
OmegaMan
I had this exact problem and after a long RegMon session found a solution. I'd be interested to know if it works for others. The post is here.

Regards,
Kevin
craigory
Have you restarted the machine since the install

What is the OS that you have
WDS3.01 No files indexed

Answer this question