• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3646
  • Last Modified:

Exchange 2007 search indexer not working

Good Afternoon Guys.

Here's the issue: my client has contacted me stating that they cannot perform a search on Microsoft Outlook 2007 (running Microsoft Exchange 2007 on a SBS 2008 box). When they use the search feature, it comes up with "no matches found for 'xxxx'."
I initally thought it was an outlook issue (they are using a terminal server), but then I tested on Microsoft Outlook Web Access and it doesn't work either.

Then I thought, that can only be one thing: the Microsoft Exchange Search Indexer Catalog (also called Full Text Indexing Catalog i believe?).

So here's what I did: I stopped the "Microsoft Exchange Search Indexer", went to %exchange database% folder and deleted the "CatalogData-<guid>-<guid>". Started the service again and guess what? IT WORKS!!!

But unfortunately, not for long! As soon as I do the above procedure, I can perform the search on both outlook and OWA and it comes up with results, and then 50 seconds later I try it again and it doesn't find anything anymore.

Checking the logs, it stops working again right after the following event:

"Exchange Search Indexer completed a full crawl (indexing) of Mailbox Database First Storage Group\Mailbox Database (GUID = 38097b7f-94b4-46b5-94c5-6ded0aa95090)."

I have increased the logging level to Expert, and here's something that also comes up after a couple of minutes:

"Starting from 22/09/2010 12:51:10 PM service 'Exchange Content Indexing' has performed this activity on the server:
RPC Operations: 44915.
Database Pages Read: 141695 (of which 132817 pages preread).
Database Pages Updated: 14721874 (of which 14692966 pages reupdated).
Database Log Records Generated: 14439632.
Database Log Records Bytes Generated: 683911132.
Time in User Mode: 158045 ms.
Time in Kernel Mode: 9205 ms. "

I also tried rebuilding the catalog via Exchange Powershell ("ResetSearchIndex.ps1 [-force] -all"), and same result. It works for a few seconds, than it doesn't anymore.

I believe I am on the right path, but is there anything else that can be done to find out what's going on?

I've already tried http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx and http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_24831374.html also


Craig Rutherford
Craig Rutherford
1 Solution
Craig RutherfordAuthor Commented:
Nevermind guys, I have found a solution. I was going to delete the question but I figured I shoull leave it for further reference:

To fix the issue, do the exactly same thing I mentioned above (rebuild the catalog), but before that, register MapiProtocolHandlerStub.dll.

So, in other words:

Method 1:

Step 1: Start > run > regsvr32 MapiProtocolHandlerStub.dll
Step 2: Open Exchange Management Shell > ResetSearchIndex.ps1 [-force] -all

Method 2:

Step 1: Start > run > regsvr32 MapiProtocolHandlerStub.dll
Step 2:  Start > run > services.msc > stop the "Microsoft Exchange Search Indexer"
Step 3: Go to your %exchange database% folder and delete the "CatalogData-<guid>-<guid>" folder
Step 4: Start the service again


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now