We are having many issues with users being able to search old emails since migrating to Exchange 2013.  We have renamed the search index files and rebuilt multiple times and they all state healthy at this time but users are still having issues finding old emails.  Trying to see if this is a product issue or a server issue and if so what needs to be done.  Using Standard edition with 5 databases at this time.

Hello

searching from only client? or try from OWA?

Unfortunately both

Hello

Test-ExchangeSearch emailaddress |fl  not add error message?

Hi,

Thank you for your question.

Is there any error when we search email in outlook or OWA? I suggest we could post error to ibsexc@microsoft.com for our troubleshooting.

Did user search email within a week? Because we want to know if those emails were deleted by Retention Policy.

Are there relevant event id or application log?

We could make sure the service of Microsoft Exchange Search is running on all Exchange mailbox server. if the service of Microsoft Exchange Search is running on all Exchange mailbox server. we could restart it to check if the issue persist.

If OWA could search email, we could rebuild the outlook profile to check if the issue persist.

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

Best Regard,

Jim

When we run the Test-ExchangeSearch script seems to error out only on one database.  The error is Time Out for the test period.  Different document ID for each test.  No error in app logs.  Search service is running and we tried to restart and same results.  We rebuilt indexes and no changes for those users.

Hi ,

We could create a new database and new account, then send email to new mailbox on new database to check if the search work. Then we could restart the service of Microsoft Exchange Information Store to check if the issue persist.

If the issue persist, we could run the following command and send result to ibsexc@microsoft.com for our troubleshooting:

Get-MailboxDatabaseCopyStatus Identity <databsename> | FL

Please send timeout error to us.

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

Best Regard,

Jim

Jim -

As stated earlier seems to be one database.  Any issues known with mailboxes of certain size or databases certain sizes?  I feel neither is the case here but curious.  When we do a get copy status we show healthy on all DBs.  Even when we created new search indexes and rebuilt, eventually show healthy.  Here is time out error:

Error                : Time out for test thread.
DocumentId           : 73801
EntryId              : {0, 0, 0, 0, 5, 190, 40, 155, 245, 36, 212, 17, 178, 152, 0, 0...}
Identity             :
IsValid              : True
ObjectState          : New

Hi,

We could run the following command on this specific database to check the status of IndexEnable:

Get-MailboxDatabase <database name> | select *Index*

If it is not TURE, we could enable it by the following command:

Set-MailboxDatabase <database name> -IndexEnabled $true

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

Best Regard,

Jim

IndexEnabled is true on all databases.

Hi,

When we use command to test an display Time out for test thread, if there are some application logs in Event view, we could send application logs to ibsex@microsoft.com for our troubleshooting.

We could rename the Index to original name, then you could tell use steps which you reset index.

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

Best Regard,

Jim