Outlook 2003 Search function works for some users, not for others

We are running Exchange 2007 SP2 (Rollup 4) on Windows 2008 servers.  The Exchange version is 08.02.0254.000.  Clients are running Outlook 2003 on Windows XP computers.

We recently started getting complaints from some users that their search function in Outlook stopped working.  They enter a word in the Find window that they know is in the subject of a message, but the search does not find anything.  This is only happening for some users and not others.

When I run the command Test-ExchangeSearch -identity <user id> on the Exchange 2007 mailbox server, it results in "False" for the people who are having this problem, and "True" for those who are not having the problem.  It appears that all the users who have this problem all have mailboxes on the same Exchange mailstore.  For users with mailboxes on the other mailstores,  the search fuction is working correctly.

Thanks very much for any assistance!
Who is Participating?
AmitIT ArchitectCommented:
There are two ways to do this task.

First to use the ResetSearchIndex.ps1
Second to use manual method. In this you need to first stop the MSExchangeSearch service, delete the Catlog directory and start it again. For more information please refer to below article


there is sp3 for exch 2007. have you considered installing that yet?
AmitIT ArchitectCommented:
Looks like index issue for that database. Rebuild the index again for that db.

Check below links, talks about same issue
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

AmitIT ArchitectCommented:
SerendipityTooAuthor Commented:

I'm sorry for the delay in responding.  I haven't had access to a computer this weekend, so I'm using my mobile phone.

I had seen the article that has the Test-ExchangeSearch command.  That's where I picked that up and found that all the users with a problem were on the same database.  I wasn't sure about the solution in that one because it talked about installing Service Pack 1, which is in the past.

It looks like the other link you sent, with the suggestion to delete the index catalog file, will be the solution for me.  I won't be able to try it at work for 2 or 3 days, but if it works, I will definitely come back and award the points.

Thank you so much for helping me!
@SerendipityToo :: being up to date on your service packs is important too as i suggested here, http:#a35118977. you indicate in your question that your Exchange 2007 server is on SP2 rollup 4 and there is SP3 available now.


Good Luck!
AmitIT ArchitectCommented:
Hi SerendipityToo

Thanks for the update. Take your time, and let me know, if you face any issue.

SerendipityTooAuthor Commented:
digitap:  Thank you for the reminder for updating the service packs.  When we get very busy, this kind of update tends to slip down the priority list, but I do need to make it a higher priority.  I see that Service Pack 3 updates the MSSearch process.  Since our current problem is only on one out of four databases, I'm going to try the suggestion for rebuilding the index first.

amit:  When I do the manual update procedure, am I correct that I should delete the entire folder with the name starting with "CatalogData-" that is under the problem database, or am I supposed to delete only the files contained in that folder?  If I delete the entire folder, will the folder be recreated automatically with the correct name when I restart the MSSearch service?

Thank you!
sounds good.
If Test-ExchangeSearch returns Result = false or time -1,  the intdexer is not working properly. Solve your Exchange Index problem before.
To do this, ensure that all your database are index enabled ( use "get-Mailboxdatabase | fl name,indexenabled ).
Then executa the script "ResetSearchIndex -all -force" ( the script is located in %PROGRAMFILES%\Microsoft\Exchange Server\scripts ). This command will ask you to confirm delete the actual catalog , and a reindexing work will begin.
When the reindexing is finished ( run test-exchangesearch again ), the script will show a "true" result and its searchtime.
Then check the Outlook search again.
It your are running your Outlook in cache mode, disable it in order to check if this is the problem.
If yout test-exchangesearch fail again, try to stop services ( Microsoft Exchange Search Indexer and Microsoft Search ( Exchange ) ) , and reregister manually the dlls. ( msfte.dl , msfteproxy.dll ans MapiProtocolhandlerstub.dll ) , then start the services again and re-run the "resetSearchindex" again.
SerendipityTooAuthor Commented:
Last night I used the manual method on the specific database that was having the search problem, and then decided to run the script to rebuild the indexes on all four databases.  The Outlook Search works great now for everyone on all databases.

I awarded the bulk of the points to Amit because he was the first to point me in the direction of rebuilding the search index and provided me with links to information that worked for me.  I also gave points to AGS because of the additional information provided, and I did use the command to verify the databases were all index enabled.

Thank you very much to everyone for helping me solve this problem!  Experts Exchange is a wonderful resource.
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.

All Courses

From novice to tech pro — start learning today.