XADM: STM Database Files Are Inconsistent After You Run the Eseutil /p Command (327346)
The information in this article applies to:
- Microsoft Exchange 2000 Server
- Microsoft Exchange 2000 Enterprise Server
This article was previously published under Q327346 SYMPTOMS After you use the Eseutil.exe utility with the /p switch to try to repair the Exchange 2000 Server Public and
Private information store databases, the Information Store service may not
start. If you look at the consistency of the .edb database files, their state
shows that they have been cleanly shut down. However, if you look at the
consistency of the .stm database files, their state is shown to be
inconsistent. RESOLUTION To resolve this issue:
- Defragment the public and private databases:
- Click Start, and then click Run.
- In the Open box, type cmd, and then press
ENTER.
- Type
drive:\program files\exchsrvr\bin eseutil
/d drive:\program
files\exchsrvr\mdbdata\priv1.edb, and then press ENTER, where
drive is the drive on which Exchange is
installed.
- Repeat the command in step 1c on the public database
file.
- Check the state of both the .edb and .stm database files to
make sure that their appears as a clean shutdown. For information about how to
check consistency by using Eseutil.exe, see the "More Information" section of
this article.
- Make sure that there is no logical damage of the
information stores:
- Click Start, and then click Run.
- In the Open box, type cmd, and then press
ENTER.
- Type
drive:\program files\exchsrvr\bin\isinteg
-s servername -fix -test alltests, and
then press ENTER, where drive is the drive on which
Exchange is installed, and servername is your
Exchange server name.
NOTE: The Isinteg.exe tool finds and removes logical damage at the IS
level. The Eseutil.exe tool checks, diagnoses, and repairs at the database
level.
Modification Type: | Major | Last Reviewed: | 6/9/2005 |
---|
Keywords: | kbprb kbui KB327346 |
---|
|