sglee
asked on
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
ASKER
OK. Let me run the script and will post the result
ASKER
I got an error message when I ran:
[PS] C:\Windows\system32>ResetS earchIndex .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:Stri ng) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[PS] C:\Windows\system32>ResetS
------------------------ 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:Stri
+ FullyQualifiedErrorId : CommandNotFoundException
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
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?
i would say there is no harm but if its working i would rather not retry something
- Rancy
- Rancy
ASKER
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.
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.
ASKER
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>.\Reset SearchInde x.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-cae8d de9-edab-4 f88-9
eca6a02a013-8a7b94ad-c5c5- 407e-bc84- 019a254a79 c8
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.
--------------------------
[PS] C:\Program Files\microsoft\exchange server\v14\scripts>.\Reset
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
eca6a02a013-8a7b94ad-c5c5-
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.
ASKER
@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 ...
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 ...
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
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
ASKER
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.
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.
You can always exceute a Exchange Shell command to check the status for all service
Test-ServiceHealth
- Rancy
Test-ServiceHealth
- Rancy
ASKER
That is good to know. Thank you.
ASKER
ResetSearchIndex.ps1 [-force] -all
Is this all I need to do? No deleting files, no restarting services?