- If the database cannot be restarted, an offline defragmentation can be performed to reduce its size. Run ESEUTIL /D to perform an offline defragmentation.
- A second option is to upgrade to
Exchange 2000 Enterprise Edition.
- If you choose to perform an
offline defragmentation, it may be that the resulting size (15 GB or greater) is
still too large to leave in production. In this case, you can install a
second Exchange 2000 server in the same Administrative Group and use Move
Mailbox to move half of the mailboxes to another server and then perform offline
defragmentation on the original server a second time. Alternatively, you
can remove information from several user mailboxes and perform offline
It can happen that even
after performing offline defragmentation, the information store database will
still not mount due to ESE Event ID 445. In this case, perform the
- In the LIMITS Tab of the Store Properties set “Keep deleted items for
(days)” to 0.
Make sure the box for “Do not permenantly delete mailboxes and items until the store has been backed up” is NOT checked.
- On the Database Tab of the Store Properties Selecte Customize for the Maintenance Interval. Set the time for the next Quarter/Hour time frame to
start the Maintenance Cycle.
- Clear and save the application and system event log files. At the selected Quarter/Hour time an event ID 700will signal the start of the
Online Maintenance Cycle. When the maintenance cycle has been completed as indicated
by event ID 701 for ALL Stores both public and private the on line
defragmentation has completed.
- From a command prompt run ESEUTIL /D on the affected store .
- When the offline defragmentation has been completed the store should be
reduced in size enough to allow it to mount.
- Make an Exchange-aware online backup of this store.
- Upgrade to Exchange 2000 Enterprise Edition, or use Move Mailbox to move
half of the mailboxes to another server and then perform ESEUTIL /D again, or
perform any maintenance to clear out unnecessary files and messages to reduce the size of the database and perform ESEUTIL /D again.