I do not see any 102 or 103 error, but we have tons of 1022 for mailboxes that are either over the receive limit or are disabled.
From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Monday, September 21, 2009 9:37 AM To: MS-Exchange Admin Issues Subject: RE: Exch 2007 Index Search issue Can you confirm if you are seeing events 102 or 107 or 1022 in the event logs? It won't help me fix your problem, but might tell me if you have the same issue as us :) From: bounce-8662998-8066...@lyris.sunbelt-software.com [mailto:bounce-8662998-8066...@lyris.sunbelt-software.com] On Behalf Of Senter, John Sent: 21 September 2009 14:04 To: MS-Exchange Admin Issues Subject: Exch 2007 Index Search issue We are running Exchange 2007 SP1 RU8. My mailbox servers are doing CCR with a local node and SCR to a remote data center. We have 8 SG's on each CCR cluster with one Store on each SG. So here is the problem. Every couple of weeks I have users complain that in Outlook they perform a search and get no items found. So I go on the Exchange servers and do a test-exchangesearch for that user and get a ResultFound=False and SearchTime=-1; which indicates the index for that store is corrupt. I will test a random user for each store to see how many are doing this and the results vary, most stores return a true value but a few show false. So I use the ResetSearchIndex.ps1 script to initiate a index rebuild, it eventually finishes and everyone is good again. Then a week or more later it happens again, not always the same stores. I have not found anything to indicate a bug in the index service. Anyone else having this issue? Anyway to keep this from happening, as it requires a lot of the server resources during the re-index and takes several hours to complete. Users are starting to get a little pissed as the Outlook search no longer works. Thanks
