I'm having an issue with out Exchange 2007 environment. Users have severely broken email search abilities, even after rebuilding the index catalog (which actually made things worse). The issue does not transcend all users and there doesn't seem to be any correlation between any of them (some have mailboxes of 8000+ items going back several years, some with 200 items that are only 3 months old, seems to affect users on all mailbox storage groups). What seems to fix the issue is moving the mailbox to another storage group. I currently have 5 storage groups for email, one for public folders. Luckily, one of those storage groups is new and meant for large mailboxes. I can move the mailbox to that SG and then move it back. That fixes the search issue EVERY TIME. The only problem is that this takes forever and I have about 6000 total users. I'd hate to have to do this for even 10% of the users. What is actually happening during the move that could fix this problem? What can I do via PowerShell that will cause the same effect, per mailbox, without actually moving the mailbox?

seems something going at the databae level or the disk. as you said when you moved from one db to another it get fixed. Next thing i will check is it happening to the users in a particular database? Where Technology Meets Talent

It's definitely affecting users in all databases, but not every user is affected (for example, my mailbox was not affected).

Do you find/see any errors in the EVENT VIEWER? Since when is it happening? did you apply any pathces? What SP have you on the Exchange ? I would also check the hard disk health.Where Technology Meets Talent

We're at SP3 Rollup 5 No disk issues at all, the array reports as healthy and no errors at all on any of the disks. I have an occasional error (which occurs while moving a mailbox, but sometime occurs if I'm not moving a mailbox as well): Event Type: Error Event Source: MSExchangeIS Mailbox Store Event Category: Logons Event ID: 1022 Date: 11/23/2011 Time: 1:10:12 PM User: N/A Computer: Mailbox001 Description: Logon Failure on database "Fourth Storage Group\Mailbox Database" - Windows account xxxxxx\Hubtransport001$; mailbox /o=First Organization/ou=First Administrative Group/cn=Recipients/cn=xxxxxx. Error: 1245 Client Machine: Hubtransport001 Client Process: edgetransport.exe Client ProcessId: 0 Client ApplicationId: Client=Hub Transport Aside from this, I don't have any other errors related to exchange.

how about searching via OWA?Where Technology Meets Talent

That's a good question. We don't have many OWA users. I haven't had any reports of there being search issues with OWA, but that doesn't mean there aren't any. I guess I don't have a concrete answer for that.

I would recommend to have the user logong to the OWA and do the search at the same time when they complain about broken search.Where Technology Meets Talent

On Wed, 23 Nov 2011 17:30:47 +0000, icepop77 wrote: >I'm having an issue with out Exchange 2007 environment. Users have severely broken email search abilities, even after rebuilding the index catalog (which actually made things worse). > > > >The issue does not transcend all users and there doesn't seem to be any correlation between any of them (some have mailboxes of 8000+ items going back several years, some with 200 items that are only 3 months old, seems to affect users on all mailbox storage groups). > > > >What seems to fix the issue is moving the mailbox to another storage group. I currently have 5 storage groups for email, one for public folders. Luckily, one of those storage groups is new and meant for large mailboxes. I can move the mailbox to that SG and then move it back. That fixes the search issue EVERY TIME. > > > >The only problem is that this takes forever and I have about 6000 total users. I'd hate to have to do this for even 10% of the users. What is actually happening during the move that could fix this problem? What can I do via PowerShell that will cause the same effect, per mailbox, without actually moving the mailbox? If these are the primary mailboxes for the users, and they're using Outlook 2010 (and maybe 2007 -- I forget!), then the search isn't using the indexes in the database if they're working in cached mode. So, how about information regarding the client-side stuff? Searches, for the most part, are being handled by the desktop search software. If you have people that aren't using Outlook in cached mode you should change that. It'll relieve your Exchange server of server of a lot of unnecessary work and put the search work on the client. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

The environment is mostly terminal sessions (Citrix), so Cached Mode isn't really an option. The issue extends to terminal users (cache mode disabled) as well as regular desktop users in cached mode.

On Fri, 25 Nov 2011 13:45:02 +0000, icepop77 wrote: >The environment is mostly terminal sessions (Citrix), so Cached Mode isn't really an option. It is with Outlook 2010. >The issue extends to terminal users (cache mode disabled) as well as regular desktop users in cached mode. Use Outlook Web Access and enable content indexing on the Exchange databases (not the best thing to do with your release of Exchange but it's better than what you're doing now). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP