Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 98
  • Last Modified:

Outlook 2010 Search

We have Exchange 2010 SP3 RU4 and Outlook 2010. We have alot of users who when searching for mail items in the outlook client or OWA, it fails to find all the results, so if a user searches for an email from sender Tommy, it will find a lot of Tommy's emails but some will not be found. I noticed that the ones that are not being found are emails with pdf attachments specifically. It finds Tommy if there are no attachments or the attachment is anything other than a pdf. I have moved the user's mailbox to a different mailbox DB, I have re-profiled outlook (but this happens in OWA also), I have also stopped and restarted the Microsoft Exchange Search Indexer on the Mailbox Servers, and I have also made sure indexing was setup on the outlook clients. Any ideas on what may be causing this. Like I mentioned it happens in outlook client and OWA.
0
timgreen7077
Asked:
timgreen7077
  • 2
  • 2
1 Solution
 
John HurstBusiness Consultant (Owner)Commented:
One possible cause for this is that some of Tommy's emails have been archived and you are not searching Archives. Go to Outlook 2010 search options and make sure you have selected all mailboxes.
0
 
timgreen7077Author Commented:
They are not archived. They are in the primary inbox and in some cases right next to the mail that was found. Also its not a email thread but a single email. If i email the user an email with a pdf attachment the user receives the mail in the inbox, but if they search for mail i sent they find all mail except the one with the pdf attachment. They are searching by the senders name, subject or anything and everything shows except the mail with the pdf attachment.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
If you are having searching issues even from OWA then the indexes are probably corrupt. I would recommend using the resetsearchindexes.ps1 script. This will re-create the indexes and perform a search crawl on the Exchange Server. This does happen from time to time usually when your databases are very large.

Below is the link for exact details on how to use resetsearchindexes.ps1 script.

I would also do this off business hours because it will put a tax on your Exchange server while it is running.

Reset Search Indexes
https://technet.microsoft.com/en-us/library/aa995966%28v=exchg.80%29.aspx

Will.
0
 
timgreen7077Author Commented:
Hi Will
I ran the below cmdlets and Get-MailboxDatabaseCopyStatus –Server "mbxservername" | fl Name,*Index* to see how the status looked and the ContentIndexErrorMessage shows healthy for all the DBs. Do you think running resetsearchindexes.ps1 script is still needed? I haven't done anything at this point, I just wanted to see what you thought first based on the Heathy status I see, but the user's still can't search correctly in OWA.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
The context indexing state health can still be inconsistent with the searching for mailbox items for specific users. A good test would be take a user that is experiencing this issue and move their mailbox to a new mailbox database. If the user can search all mail items then context indexing is a issue for that original mailbox database.

Will.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now