I know this is Exchange 2013 forum but I see that Exchange 2010 has been removed so I'm hoping someone can still help me out. We are planning to soon move to Exchange 2013 but in the meantime I've been having some indexing/search issues.

We have a particular mail database for one of our departments and after the database was moved to a new disk, the indexing has never been the same since. To remedy this, I had enabled the Windows search feature on the application server (we have Outlook 2013 hosted as a RemoteApp application with the use of user profile disks) and had them switch to cached mode which seems to be hit or miss. I also have tried following the recommended procedure of stopping the search indexer service on Exchange and then I deleted the catalog data folder and then restarted the service to have it rebuild the indexes for the particular database. I have also confirmed through the management shell that the index is in a healthy state for the database.

I have now requested for the user that is testing to disabled cached mode to see if the indexes on the Exchange server will be better and I am awaiting feedback but I thought I would be preemptive and see what any suggestions you all may have with dealing with Outlook / search indexing.

Thank you in advance for your time!

Your following all the right steps so I think you would need to check with the user first to see the results.  Only other issue would be possible DB corruption but if that were the case it would have yielded errors in the application event log on the Exchange server.  Have you reviewed the event logs?

Hi Scott,

Thank you for your question.

Are there any Event IDs in application log which is related to search? I suggest we post those Event IDs to ibsexc@microsoft.com for our troubleshooting.

Did the issue occur on OWA?

Run the following command to check the database status:

Get-MailboxDatabaseCopyStatus -Server <servername>

We could dismount the specific database then mount the specific database, then rebuild the Indexing to check if the issue persist.

We could refer to the following link:

http://blogs.technet.com/b/mspfe/archive/2012/04/27/how-to-troubleshoot-issues-with-exchange-2010-search.aspx

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

The only event that I can find related to indexing is the following:

Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: HR
Error Code: 0x80070057

Sometimes the Error code is 0x80041606 but it seems to occur for all databases and not just the one in question but it may still be worth looking into. Other than that, the content index state is healthy for all databases. I will get back to you about OWA but that's a good idea. I can also try dismounting and mounting and rebuild the indexes one more time as I did not dismount the database when I rebuilt them the other day. I'll also know more once I receive user feedback. In the meantime, I'll take a look at the article that you provided.

Thank you so much for your response!

I don't see anything about database corruption in the Application log and the only error I see for content indexing is:

Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: HR
Error Code: 0x8007005
(or error code 0x80041606)

If you know of any other Event ID's that I should be looking for (including ones for database corruption), I'll filter for those and see if there's anything else to go on.

Thank you so much for your response!

Hi ,

We could restart the service of Microsoft Exchange Information Storeand Microsoft Exchange Mailbox Assistant to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim