Because the Microsoft Search service is used by other Microsoft products for full-text indexing, a missing or unregistered .DLL meant to be used by Search can cause apparently unrelated problems. This can also happen should the Search components added by Office (in particular, the OFFFILT.DLL filter) come unregistered or get damaged.
Some of the trouble caused by Search going unregistered or missing should be obvious. One possible problem is that a search for common Office documents turns up nothing, e.g., no documents that use standard Office extensions such as .DOC or .XLS appear in the search window.
Another symptom, less common and harder to discern symptom, involves any computer that has SQL Server installed (including SQL Server Developer Edition) with Full-Text Indexing enabled on one or more databases. In such cases, attempting to create a full-text index produces an error similar to this one: Unknown full-text failure (8007007e) occurred in function EnumCatalogs on full-text catalog
The simplest way to repair this is to re-register all the Microsoft Search components from the command line using REGSVR32 /S
In the directory %ProgramFiles%\Common Files\System\MSSearch\Common:
In the directory %ProgramFiles%\Common Files\System\MSSearch\bin:
If you experiencing these problems on a server and this technique doesn't work, you might need to manually restore Microsoft Search from the ground up by removing its installation instance from Windows and re-adding it.
About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators. He is also the author of the book Windows Server Undocumented Solutions.
More information on this topic:
- Tip: Quickly register a .DLL or .OCX
- Topics: Systems Management
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in July 2006