Exchange Server 2000 and 2003 Databases Dismount due to Exhaustion of Log Files

Exchange Server supports transaction logging andExchange Server has used all the available transaction
numbers them sequentially. It starts naming themlog files of storage group.
from E nn 00001.log and goes on till E nnffff0.log,Solution
where nn represents the storage group number.To solve the given problem, you need to reset the
When all the log files are exhausted, Exchangelog sequence by removing all the log files to a
Server gives 'JET_errLogSequenceEnd' error anddifferent location. But before you do so, you should
causes different issues, as discussed below. Youensure for databases' consistency. You should follow
need to remove these log files while making surethese steps:
that the databases are healthy. If not, you should1. Select the ' Don't mount this store at start-up'
restore them from backup or repair using eseutiloption to make sure that they don't mount at
utility or a EDB Recovery Software.startup
For instance, you might come across these2. Dismount the database that cannot be dismounted
symptoms in a computer running Exchange Serverby killing the store
2000 or 2003:3. Mount the other storage groups by restarting the
1. The connected users experience failures whenstore
trying to logon to their mailboxes. The databases4. Try to repair the problematic storage group
become inaccessible even when they are mounted. Itdatabases by running eseutil /r
specifically occurs in Exchange Server 2000 that is5. Check for databases' consistency by running eseutil
not using August 2004 Exchange 2000 Server/mh
post-Service Pack 3 update rollup or in original version6. If they are consistent, move checkpoint and log
of Exchange Server 2003. The application log showsfiles to a different location and mount the databases
event ID 1022.7. If the databases remain inconsistent, you should
2. The databases in computer running Exchangedelete the damaged databases provided you have a
Server 2003 SP1 or SP2 or August 2004 Exchangefull backup to restore. If not, you can use a powerful
2000 Server post-Service Pack 3 update rollup getEDB Recovery utility to repair and restore them.
dismounted without displaying any warning. When youEDB Recovery Software are well-designed and
try to mount them, it shows an internal processingexclusive applications that allow you to extract all
error and logs event 1159 and 9518 in application log.user mailboxes from a corrupted Exchange database
and restore them safely.
Cause