Author:

Yuval Sinay MVP

COMMUNITY SOLUTIONS CONTENT DISCLAIMER

MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

SYMPTOMS

When you run eseutil /P command or eseutil /mh, you may get error that indicate that the *.STM file doesn't match the *.EDB file that resides on the server.
Usually, in this case, the Information Store service cannot mount the local mail/public store.

CAUSE

There a few reasons for *.STM file corruption:
 
a. Antivirus software periodically scanning the *.EDB or/and *.STM file.
 
b. The *.EDB or/and *.STM size increases significantly.
 
c. Hardware problem.
 

RESOLUTION

By using the instructions in this guide may lose important data, and therefore should be only used as a last resorts. It is recommend that you backup the databases before implement these instructions. Always consider using a valid backup instead of these instructions.
 
The amount of the data that you may lose depends on your mail client software -  If everybody uses Outlook (MAPI protocol), then there will be very little user data in the .STM file. You may lose some in transit messages that haven't been delivered yet. If clients connect via POP3 or IMAP then most of their stuff will be in the .STM file, and its loss will be catastrophic to them. If clients use Outlook Web Access, messages will be in the .EDB file, but attachments sent will be in the .STM file.
 
 
1. Stop any antivirus software on the server.
 
2. Stop "Microsoft Exchange System Attendant" service.
 
     Note: This stage prevent from users to use the server.
 
3.  Go to "Start" -> "Run" and write "Regedit" and press on "Enter" button.
 
4. Navigate to:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan]
 
    In the right side of the screen change the value of "Enable" from 1 to 0.
 
5. Run eseutil /mh command to verity the need to recreate of the *.STM file:
 
       eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"

       eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"

    Note: If the *.EDB files reside in other locations, you may need to change the path to this files in eseutil /mh sentence.
 
6. Run eseutil /p /createstm command to create of the *.STM file:
 
            If the private mailbox store *.STM file may need to recreate, please use the following command:
 
            eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
 
       If the public store *.STM file may need to recreate, please use the following command:
 
      eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"
 
7. Go to "Start" -> "Run" and write "Regedit" and press on "Enter" button.
 
8. Navigate to:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan]
 
    In the right side of the screen change the value of "Enable" from 0 to 1.
 
9. Start "Microsoft Exchange System Attendant" service.
 
10. Open Exchange "System Manager". Navigate to the problematic mailbox store/Public store.
 
11. Run "mailbox cleanup agent" on each mailbox store and choose "reconnect all mailboxes".
 
12. Optional: Open the problematic mailbox store/Public store, right click on the mailbox store/Public store and choose "properties".
         Press on "Database" tab and mark the checkbox "This database can be overwritten by a restore".
 
13. Mount the mailbox store/Public store.
 
   Note: If you Start "Microsoft Exchange System Attendant" service in phase 9, the mailbox store/public store should
                be mount automatically.
 
14. Start the antivirus software that was stop in phase 1.
 
15. Make full backup to the Exchange databases and the local server.

MORE INFORMATION

XADM: Exchange 2000 Server Eseutil Command Line Switches

 
How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003

 
XADM: Exchange and Antivirus Software

 
XADM: Ramifications of Running the ESEUTIL /P or EDBUTIL /D /R Command

 
Preview: Exchange Server 2003 Disaster Recovery Planning Guide

गुण

आलेख ID: 555146 - पिछली समीक्षा: 14/02/2017 - संशोधन: 1

Microsoft Exchange Server 2003 Enterprise Edition, Microsoft Exchange 2000 Enterprise Server, Microsoft Exchange 2000 Server Standard Edition

प्रतिक्रिया