Solved

Exchange 2007 search indexer not working

Posted on 2010-09-21
1
3,308 Views
Last Modified: 2012-08-15
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


Regards,

Rod
0
Comment
Question by:Black-Knight
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
Black-Knight earned 0 total points
ID: 33731761
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

Regards,

Rod
1

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question