Our search results in Outlook are stopping at a certain date. We get all results prior to the failure date, but no results after it. This issue persists across the network on all of our terminal servers and OWA, however it does not appear to be an issue for domain workstation users - they are able get all search results up to the present date on their workstations, but searches in OWA still yeild no results after early June 09.We have confirmed that all Exchange services are started, including the Microsoft Exchange Search Indexer Service.We have confirmed that all terminal servers are running the same version of Outlook 2003 SP3We have confirmed that recreating a user's Outlook profile has no impact on this issue.Any suggestions are appreciated.Thanks,Matt

Seems like the indexing on Exchange has stopped doing its thing.You can reset the index and have Exchange reindex everything from scratch.in the scripts subfolder of the Exchange installation you have powershell script that clears the index and rebuild it from scratch. "ResetSearchIndex.ps1"you have to run it with some parameters specifying database name or all databases.Be carefull when running this since your server will run as fast as it can with high CPU and a lot of disk activity.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

What about changing to an external search tool? There are some really good tool available for example Lookeen . These tools have a lot more features and they are faster in searching. Another important argument is the size and the ressources such a tool needs. Lookeen is small and needs not much of it. greets

You can use another search engine, but lookeen will only search on the desktop client. it cannot be used by OWA users.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Hi, Yes, I agree with Lasse. The ResetSearchIndex.ps1 script is located in the <drive> :\Program Files\Microsoft\Exchange Server\Scripts folder. The script deletes the CatalogData- <guid of database> folder and its contents. When you restart the MSExchangeSearch service, the CatalogData- <guid of database> is recreated. Also, a full database crawl is started. Regards, Xiu

We have followed your recommendations and run the resetsearchindex.ps1 script. After running the script, we are unable to return any search results on the terminal server or in OWA. Users with a workstation on the domain continue to have no problems.Thanks,Matt

Did you let the index engine finish it's work after you reset the index? it might take a while with high CPU and disk activity.Is the searches slow or dont they work at all?Exchange content index will only index information located inside Exchange.turn on diagnostic loggingfor the index service in Exchange by running:Get-EventLogLevel 'MSExchange Search Indexer*' | Set-EventLogLevel -Level highLook in the application log for more clues.do you have any AV software running on Exchange? you have to exclude several processes or folders. http://technet.microsoft.com/en-us/library/bb332342.aspxreset the logging level withGet-EventLogLevel 'MSExchange Search Indexer*' | Set-EventLogLevel -Level lowestlasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

The index engine ran after the reset, we could see the processor spike, though it did not last very long.The searches do not work at all for a basic search. If we go into advanced search, we can return results based on date received under the advanced tab, but if we add any additional criteria, like sender name or address, or recipient info, we get no results.We turned on the high diagnostic logging as recommended and re-ran the resetsearchindex.ps1 script. The event logs show that the services stopped and restarted, created a new index and then initiated a crawl for each database and enabled indexing for the database. There are also events for each database saying that the Indexer has completed a full crawl, the longest database to complete took about 6 minutes to finish the crawl. There are no errors during the process.

Wher did you search from, Outlook in online or cached mode?Try to search from OWA since this earch always will use Exchange index.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Searched Outlook in Online mode. Search from OWA returns no results.Thanks,Matt

Do you have any AntiVirus software on Exchange server?then you have to exclude directoriesor processes http://technet.microsoft.com/en-us/library/bb332342.aspxlasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

We do have Trendmicro WFBS on the server, and have added the exclusions. Still seeing no change. The reset still runs quickly, shows no errors in the logs, shows the initiated and completed crawl, but when we go to search from a TS user's Outlook, or the OWA, we get no results.One new bit of information, if we use Outlook to do the search, and use the advancedfind feature and change the "Look For" dropdown from "Messages" to "Any type of Outlook item" it appears to find all relevant messages with no problem, but if we only have messages selected in the drop down it still finds nothing.Thanks,Matt

I'am stunned.I guess someone has to take a close look at your server and outlook configuration. I recomend calling MS PSS about this.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

After purchasing support from microsoft, we have determined that the following is the solution to this issue. 1. Logon the Exchange server and open Stop the Microsoft Exchange Search Indexer and the Microsoft Search (Exchange) services 2. Click Start -> Run, type Installer, and then click OK. 3. Right-click the Name column header, and then click More. 4. Select Subject and Click OK 5. Search through the Subject field until you find "Microsoft Full Text Indexing Engine for Exchange Setup v8.1.240.x". The x's denote what version is installed on the server. 6. Right-click the cached Windows Installer file that has the "Microsoft Full Text Indexing Engine for Exchange Setup v8.1.240.x" subject, and then click Uninstall. 7. After the uninstall process has completed, quit the Installer. 8. Open the command windows and locate to Exchange Installation folder, 9. Locate to \Setup\ServerRoles\Mailbox\ 10. Run the command, msiexec /i msfte.msi TARGETDIR="c:\Program Files\Microsoft\Exchange Server" regsvr32 msftepxy.dll 11. Start Microsoft Exchange Search Indexer and the Microsoft Search (Exchange) services.