Exchange 2010 Discovery Search Folder Time Out

We have an organization with 6 Exchange Servers Mailstore Servers running in a DAG format.  We have recently run into a situation where we are trying to run a Discovery search in the organization and keep getting "Search Folder Time out" with the searches.  

We have tried with "one" phrase and one mailbox to be searched.   We could get that to work intermittently.  But whenever we try to do a search with 3 terms and 8 users in the TO and FROM fields we get the "Search Folder Time Out" error.  In the event viewer we get the error 3003 Discovery.  

We have recently upgraded to SP3 and Roll Up 1 on the servers.  We have 15 servers total in the environment.  We were able to do this before, but now we are unable to do the searches.  This is critical as we have to do these searches all the time.  Any help will be appreciated.

Thanks,
usfidiazAsked:
Who is Participating?
 
usfidiazConnect With a Mentor Author Commented:
I was able to run them after rebuilding the indexes and changing my search query.  I can search with Keywords or TO and From Fields but not both.
0
 
AmitIT ArchitectCommented:
You need to create small query as query limit is by default 64k.
0
 
usfidiazAuthor Commented:
The query we are creating is: "HOSPITAL NAME" OR "LRMC" OR "Person's NAME" is that too large?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
AmitIT ArchitectCommented:
If you are getting 3003 error, that means it is large for Exchange. You have too many Or condition and Exchange need to search and match from several Or condition.

use short queries and merge the result into one later.
0
 
usfidiazAuthor Commented:
I only have 1 keyword and 1 email address in the TO and FROM and one mailbox that we are searching.  It can't get any shorter.
0
 
AmitConnect With a Mentor IT ArchitectCommented:
Cannot help much, as it is design limitation. Check with MS.
0
 
usfidiazAuthor Commented:
Could it be a problem with the indexing catalog being corrupt.  We have noticed that just noticed that OWA isn't able to search now since installing SP3 Rollup 1.  We are going to re-index after hours tomorrow night.  I will let everyone know if this resolves the issue.

Thanks,
0
 
AmitIT ArchitectCommented:
Index corruption could also contribute to this issue.
0
 
AmitIT ArchitectCommented:
Thanks for the update.
0
 
usfidiazAuthor Commented:
It was my solution that fixed the issue, along with changing my search pattern.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.