Search option in outlook stops working after Exchange Database Repair

Hi,
  Recently i had to repair Exchange mail database due to corruption.
  After the database was repaired,  "Search" option stopped working.
  We use OUTLOOK 2010 and EXCH 2010 in SBS2011.
  What can I try?

Thanks.
sgleeAsked:
Who is Participating?
 
apathy42Connect With a Mentor Commented:
Try rebuilding the full-text index catalog:

http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx
0
 
sgleeAuthor Commented:
Can I just remove all indexes by running the following in EXCH MGMT Shell?

ResetSearchIndex.ps1 [-force] -all

Is this all I need to do? No deleting files, no restarting services?
0
 
apathy42Commented:
The script will do all of that for you.  The manual process is for the case that either that's not working properly or you like doing it step by step.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
sgleeAuthor Commented:
OK. Let me run the script and will post the result
0
 
sgleeAuthor Commented:
I got an error message when I ran:
[PS] C:\Windows\system32>ResetSearchIndex.ps1 [-force] -all
------------------------ Error Message -------------------------
The term 'ResetSearchIndex.ps1' is not recognized as the name of a cmdlet, function, script file, or operable prog
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:21
+ ResetSearchIndex.ps1 <<<<  [-force] -all
    + CategoryInfo          : ObjectNotFound: (ResetSearchIndex.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
0
 
apathy42Connect With a Mentor Commented:
Check to see if "ResetSearchIndex.ps1" is in the Scripts directory (usually %Program Files%\Microsoft\Exchange Server\Scripts).  If so, cd to that directory and run it like so:

.\ResetSearchIndex.ps1 -force -all

By the way, don't put the brackets around the -force...that was just to note that it was optional.
0
 
Manpreet SIngh KhatraConnect With a Mentor Solutions Architect, Project LeadCommented:
[PS] C:\Windows\system32>ResetSearchIndex.ps1 [-force] -all

few points
1. The command should be run from ExchangeShell
2. You need to redirect the Shell to Scripts folder and then run the .ps1 (SHould show something like
[PS] C:\Program Files\Microsoft\Exchange Server\Scripts> .\ResetSearchIndex.ps1 -Force -All

- Rancy
0
 
sgleeAuthor Commented:
Late yesterday afternoon, I rebooted Exchange Server /SBS2011 a couple of times after replacing old RAID controller with faulty memory chip that caused Exch Mail database to get corrupted about two weeks ago. As  Exch Mail database was repaired, I learned that users could not use "Search" fuction in OUTLOOK and that was the reason I opened this question yesterday afternoon.

For some reason, after rebooting the server a couple of times (after RAID card replacement), Search function was working all of sudden. But I know it is not because I ran this script. Because I saw an error due to syntax was not correct and I did not run the script so far (I just saw two additional comments this morning).

That said, I guess I do not need to run it again because it is working, but I still like to try it. Is there a harm running this script now as there is no more problem and users are already in  OUTLOOK?
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
i would say there is no harm but if its working i would rather not retry something

- Rancy
0
 
sgleeAuthor Commented:
you know what, let me try it on my exchange/sbs2011. In that way I will have tried it out and no harm to anyone. I will keep you posted.
0
 
apathy42Commented:
It will not harm anything long-term...it will just take a few hours of search not working as it rebuilds the index...it's possible that full-text indexing was restarted and discovered that it needed to rebuild on its own.
0
 
sgleeAuthor Commented:
It ran successfully. I had to change the directory "C:\Program Files\microsoft\exchange server\v14\scripts". Here is the result:
-------------------------------------------------------------

[PS] C:\Program Files\microsoft\exchange server\v14\scripts>.\ResetSearchIndex.ps1 -Force -All
WARNING: Waiting for service 'Microsoft Exchange Search Indexer (MSExchangeSearch)' to finish stopping...
WARNING: Waiting for service 'Microsoft Exchange Search Indexer (MSExchangeSearch)' to finish stopping...
MSExchangeSearch service stopped
Deleting catalog forMailbox Database

removing: C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\CatalogData-cae8dde9-edab-4f88-9
eca6a02a013-8a7b94ad-c5c5-407e-bc84-019a254a79c8

MSExchangeSearch service Started
-------------------------------------------------------------
It only took several seconds. Of course my exchange database is only  2GB where my customers is close to 90GB.

if that was all, then it was very simple. Thank you for your help.
0
 
sgleeAuthor Commented:
@apathy42
it's possible that full-text indexing was restarted ---> are you referring to "Microsoft Exchange Search Indexer" service in SERVICES.MSC?

I did not  check  SERVICES.MSC when "Search" function was not working because it simply did NOT know what to look for? Maybe that service was stopped and I have not restarted the server since exch database was repaird. During the repair, MS Exchange Engineer restarted Exchange Information Store several during the troubleshooting ...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hope there is no DAG in your customer environment ?
are you referring to "Microsoft Exchange Search Indexer" service in SERVICES.MSC? - This is the same service that stoppe din your command above

If its stopped please start and maybe you wont need to reset the SearchIndexes

- Rancy
0
 
sgleeAuthor Commented:
no DAG exists.
Next time when Search function stops working, I will check the status of "Microsoft Exchange Search Indexer" service in SERVICES.MSC.

Thank you all for your help.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
You can always exceute a Exchange Shell command to check the status for all service

Test-ServiceHealth

- Rancy
0
 
sgleeAuthor Commented:
That is good to know. Thank you.
0
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.