For a corrupted Index file, please perform the following steps to try to resolve this issue:
1). On the Exchange server, open Registry Editor and back up the entire registry as a precaution.
2). Locate and then click the following registry subkey, where COMPUTERNAME is the name of your server (e.g. MEMEXCHANGE1), and where privcatalog or pubcatalog is the
name of the catalog, for example, privF0857535:
3). Verify first that ALL paths listed under that key are valid. Compare with the folders as viewable in Explorer. If any are missing, create new folders to match the path as found in the registry and restart the Microsoft Search service.
4). If that does not work, export and delete the priv<catalog number> keys.
5). Restart Microsoft Search service.
6). Close and open the ESM agin.
Can you view the new store now? if the issue still occurs, please go to step 2.
Important: Please fully backup your Exchange server and AD first.
1). On Exchange server, stop MS search service.
2). Install the Windows Support tool on your Domain Controller server.
3). On the DC, open ADSIEDIT, navigate to:
Config_Container/Configuration/Services/Microsoft Exchange/<Organization_Name>/Administrative Groups/<Administrative_Group_Name>/Servers/<Server_Name>/Information Store/<Storage_Group_affected_by_issue>.
4) For each mailbox store on this SG (Storage Group), clear the following attributes:
5) On Exchange server, open registry editor and navigate to
HKLM\Software\microsoft\search\1.0\Gather\ExchangeServer_<Computer_Name> Delete all keys with catalog names that match with events ID related to the 80040d1b in the application log.
6) Restart the MS search service.
7). Close and open the ESM again.
What’s the result?
You can also try to download Exchange Best Practices Analyzer (ExBPA) for fixing the basic error.
Bad Behavior has blocked 162 access attempts in the last 7 days.