Webmail (OWA) not able to search for any mails newer than 5/15/12
I have a user who when she searches in webmail is only getting mails prior to 5/15/12. For example, if i send her an email and she searches my name in webmail it does not popup because the email is newer than 5/15/12. Anything prior to 5/15/12 pops up. She
has tried multiple browsers and different computers but same result. We are using Exchange 2010. Any ideas?
July 6th, 2012 8:42pm
How from Outlook? Same results?
Have you recreated the content index for the mailbox store yet? I would try that if not.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2012 9:32pm
I accessed her inbox from my outlook and the search is working as it should. I then access her email both using webmail & outlook and I noticed that on webmail her inbox only displayed 73,000 emails. But when I accessed her account via outlook
her inbox has over 100,000 emails. Does OWA have a limit on display inbox emails or is there a setting i'm missing??????
July 6th, 2012 10:34pm
I'm trying to run:
ResetSearchIndex.ps1 -force -all
To rebuild the index on Exchange. I know you have to go to <drive>:\Program Files\Microsoft\Exchange Server\Scripts\ to run the command but I can only get to the drive and not Program Files directory. I've tried cd program files
and set-location program files. Does dos commands not work?
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 12:03am
Why don't you use tabcompletion?
An easy way to get to the scripts folder is to type:
cd $exscripts
..but of course you can also type cd "Program Files"Martina Miskovic
July 7th, 2012 12:30am
another option is to stop the Exchange index service, delete the index catalog on disk, and restart the index service and it will automatically restart crawling.
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 7:23am
another option is to stop the Exchange index service, delete the index catalog on disk, and restart the index service and it will automatically restart crawling.
July 7th, 2012 7:23am
I was able to get to the directory with cd $exscripts. But when I type in
ResetSearchIndex.ps1 -force -all I am getting the error below:
The term 'ResetSearchIndex.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program.
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
Suggestion [3,General]: The command ResetSearchIndex.ps1 was not found, but does exist in the current location. Windows
PowerShell doesn't load commands from the current location by default. If you trust this command, instead type ".\ResetS
earchIndex.ps1". See "get-help about_Command_Precedence" for more details.
As for stopping the exchange index service and then deleting the index catalog on disk, where is the index catalog located on the disk by default?
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 9:27am
I was able to get to the directory with cd $exscripts. But when I type in
ResetSearchIndex.ps1 -force -all I am getting the error below:
The term 'ResetSearchIndex.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program.
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
Suggestion [3,General]: The command ResetSearchIndex.ps1 was not found, but does exist in the current location. Windows
PowerShell doesn't load commands from the current location by default. If you trust this command, instead type ".\ResetS
earchIndex.ps1". See "get-help about_Command_Precedence" for more details.
As for stopping the exchange index service and then deleting the index catalog on disk, where is the index catalog located on the disk by default?
In the same directory as the mailbox store it indexes.
July 7th, 2012 9:57am
Ok it looks like the command was .\ResetSearchIndex.ps1 -force -all
After the command, i tested the search in the user's webmail and now instead i'm getting the error "the action could not be completed. Please try again." Before, I was just not getting anything after 5/15/12.....
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 10:29am
The event log app on the exchange server shows multiple event id 102
July 7th, 2012 10:35am
You have to be patient and wait for the indexing to be complete.
http://technet.microsoft.com/en-us/library/bb123701.aspx
Diagnose Exchange Search Issues
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 10:45am
Ok, gotcha...
July 7th, 2012 10:55am
On Sat, 7 Jul 2012 13:27:18 +0000, madbeast wrote:
>
>
>I was able to get to the directory with cd $exscripts. But when I type in ResetSearchIndex.ps1 -force -all I am getting the error below:
>
>The term 'ResetSearchIndex.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. 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
>
>Suggestion [3,General]: The command ResetSearchIndex.ps1 was not found, but does exist in the current location. Windows PowerShell doesn't load commands from the current location by default. If you trust this command, instead type ".\ResetS earchIndex.ps1".
See "get-help about_Command_Precedence" for more details.
That's perfectly normal. Add the ".\" in front of the script name.
..\ResetS earchIndex.ps1
If that doesn't fix the problem then run this cmdlet:
get-executionpolicy
If the result is "Restricted" then run this cmdlet:
set-executionpolicy -ExecutionPolicy RemoteSigned
Then try running the script (with the leading ".\").
---
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 12:42pm
I tested from user's webmail again and still getting error "the action could not be completed. Please try again." After running the .\ResetSearchIndex.ps1 -force -all. Any ideas?
July 7th, 2012 9:15pm
What SP and RU is Exchange at?
Also see:
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/35db030c-277f-49d6-83d6-772f839a47f8/
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 9:45pm
Exchange 2010 Standard 14.1
July 8th, 2012 12:48am