Article ID: 830408
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
In Microsoft Exchange Server 2003 or in Microsoft Exchange 2000 Server, you experience the following symptoms.
Symptom 1
You notice that Exchange store databases are dismounted without warning on a computer that is running any of the following items:
- Microsoft Exchange Server 2003 Service Pack 1 (SP1)
- The August 2004 Exchange 2000 Server post-Service Pack 3 update rollup
When you try to mount a dismounted Exchange database in Exchange System Manager, you receive an error message that resembles the following error message:
Additionally, the following events are logged in the Application log:
Event ID: 1159
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Description: Database error 0xfffffdf9 occurred in function JTAB_BASE::EcEscrowUpdate while accessing the database "First Storage Group\Mailbox Store (SERVER)".
Event ID: 9518
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Description: Error 0xfffffddc starting Storage Group Path_of_Storage_Group on the Microsoft Exchange Information Store. Storage Group - Initialization of Jet failed.
Symptom 2
In the original release version of Exchange Server 2003 or in versions of Exchange 2000 Server that are not running the August 2004 Exchange 2000 Server post-Service Pack 3 update rollup, users who have mailboxes in a particular storage group start to experience logon failures or other failures.
This problem occurs when the users connect to their Exchange 2000 Server mailboxes or to their Exchange Server 2003 mailboxes. Although the store databases are still mounted, these databases become inaccessible.
Additionally, an event that resembles the following event is logged in the Application log:
Event Type: Error
Event Source: MSExchangeIS Mailbox
Event Category: Logons
Event ID: 1022
Description: Logon Failure on database Path_of_Database.
Error: -519
CAUSE
This problem may occur if Exchange Server has used all the transaction logs that are available to a storage group.
Exchange uses transaction log files that are numbered sequentially. The first file name in the transaction log file sequence is "E nn 00001.log." The file names increase sequentially to "E nn ffff0.log."
Note In this log file name, nn is the number of the storage group.
The maximum number of transaction log files that can be generated in a single sequence is 1,048,560 (0xFFFF0).
When the last transaction log is filled, the Microsoft Jet database engine returns error "-519 (JET_errLogSequenceEnd)" to the store. This error causes the symptoms in the different versions of Exchange that are mentioned in the "Symptoms" section.
WORKAROUND
To work around this problem, reset the log sequence.
To do this, you must move all existing transaction logs to another location. After you do this, a new sequence of log files that starts with 0x00001 is generated.
Important Before you move the transaction logs, you must verify that all databases in the storage group are in a Clean Shutdown state. To do this and to reset the log file sequence, follow these steps:
- Mark all the databases in the affected storage group to not mount on startup. To do this, follow these steps:
- Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
- Expand Organization, click Servers, click
your server, click Information Store, and then clickyour storage group. - Right-click
your database, and then click Properties. - Click the Database tab.
- Click to select the Don't mount this store at start-up check box.
- Kill the store to dismount the database that could not be dismounted.
To download the latest version of the Debugging Tools for Windows package, visit the following Microsoft Web site: - Restart the store so that other storage groups can be mounted.
- Run eseutil /r on all the databases that are in the affected storage group.
- Verify that the databases were in a Clean Shutdown state. To do this, follow these steps:
- In Exchange System Manager, right-click the first store in the storage group that has run out of transaction log files, and then click Properties.
- Click the Database tab, and then note the paths and the file names of the database files in the Exchange database box and in the Exchange streaming database box.
Each Exchange database is composed of a paired set of files that have the .edb file name extension and the .stm file name extension.
Repeat this step for each store in the storage group. - At a command prompt, move to the Exchange Server bin folder. For example, move to the C:\Program Files\Exchsrvr\bin.
- Type Eseutil /mh
Database_File_Name, and then press ENTER.
Repeat this step for each database in the storage group. This command displays the database file header. The header contains one of the following lines:- State: Clean Shutdown
- State: Dirty Shutdown
- Move logs and checkpoint files to another location in case a recovery is required from an old database. The log files have the .log file name extension. The checkpoint files have the .chk file name extension.
- Mount all the databases in the storage group.
- Click to clear the Don't mount this store at start-up check box for all the databases in the affected storage group.
- The storage group must be backed up when delivery settles down on this computer because you cannot recover log files past the new log file generation point.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Hotfix to help identify the problem
Microsoft has created a hotfix for Exchange 2000 Server to help identify the problem. After you apply this hotfix, the store databases dismount when the Microsoft Jet database engine returns the "-519 (JET_errLogSequenceEnd)" error. This behavior helps Exchange Server administrators quickly identify the problem storage group.
This hotfix is also included in the following items:
- The August 2004 Exchange 2000 Server post-Service Pack 3 update rollup
- Exchange Server 2003 SP1
After you apply the hotfix, the update rollup, or the service pack, you still must manually reset the log files. To do this, see the steps in the "Workaround" section.
Hotfix information
Prerequisites
You must install Exchange 2000 Server Service Pack 3 (SP3) before you apply the hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
Restart information
You do not have to restart the computer after you apply the hotfix. However, the Microsoft Exchange Information Store service and all dependent services will be stopped and then restarted.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Cdoex.dll | 6.0.6527.0 | 3,915,776 | 27-Oct-2003 | 14:47 | x86 |
| Davex.dll | 6.0.6527.0 | 851,968 | 27-Oct-2003 | 14:42 | x86 |
| Davexpc.dll | 6.0.6527.0 | 53,248 | 27-Oct-2003 | 14:42 | x86 |
| Drviis.dll | 6.0.6527.0 | 131,072 | 27-Oct-2003 | 14:38 | x86 |
| Dsaccess.dll | 6.0.6527.0 | 577,536 | 27-Oct-2003 | 14:38 | x86 |
| Dscmsg.dll | 6.0.6527.0 | 184,320 | 27-Oct-2003 | 13:48 | x86 |
| Emsmdb32.dll | 6.0.6527.0 | 962,560 | 27-Oct-2003 | 13:48 | x86 |
| Ese.dll | 6.0.6527.0 | 2,179,072 | 27-Oct-2003 | 14:41 | x86 |
| Eseperf.dll | 6.0.6527.0 | 40,960 | 27-Oct-2003 | 14:41 | x86 |
| Eseperf.hxx | Not applicable | 6,991 | 08-Sep-2003 | 11:48 | Not applicable |
| Eseperf.ini | Not applicable | 391,634 | 27-Oct-2003 | 14:41 | Not applicable |
| Excdo.dll | 6.0.6527.0 | 3,575,808 | 27-Oct-2003 | 14:47 | x86 |
| Eximap4.dll | 6.0.6527.0 | 90,112 | 27-Oct-2003 | 14:37 | x86 |
| Exmime.dll | 6.0.6527.0 | 262,144 | 27-Oct-2003 | 14:39 | x86 |
| Exnntp.dll | 6.0.6527.0 | 176,128 | 27-Oct-2003 | 13:27 | x86 |
| Exodbesh.dll | 6.0.6527.0 | 143,360 | 27-Oct-2003 | 14:42 | x86 |
| Exodbpc.dll | 6.0.6527.0 | 57,344 | 27-Oct-2003 | 14:42 | x86 |
| Exodbprx.dll | 6.0.6527.0 | 200,704 | 27-Oct-2003 | 14:42 | x86 |
| Exoledb.dll | 6.0.6527.0 | 2,179,072 | 27-Oct-2003 | 14:42 | x86 |
| Exosal.dll | 6.0.6527.0 | 81,920 | 27-Oct-2003 | 14:36 | x86 |
| Expop3.dll | 6.0.6527.0 | 32,768 | 27-Oct-2003 | 14:38 | x86 |
| Exproto.dll | 6.0.6527.0 | 32,768 | 27-Oct-2003 | 14:38 | x86 |
| Exprox.dll | 6.0.6527.0 | 307,200 | 27-Oct-2003 | 14:42 | x86 |
| Exschema.exe | 6.0.6527.0 | 143,360 | 27-Oct-2003 | 13:51 | x86 |
| Exsmtp.dll | 6.0.6527.0 | 315,392 | 27-Oct-2003 | 14:42 | x86 |
| Exwform.dll | 6.0.6527.0 | 675,840 | 27-Oct-2003 | 13:53 | x86 |
| Exwin32.dll | 6.0.6527.0 | 180,224 | 27-Oct-2003 | 13:28 | x86 |
| Febecfg.dll | 6.0.6527.0 | 40,960 | 27-Oct-2003 | 13:51 | x86 |
| Iisif.dll | 6.0.6527.0 | 32,768 | 27-Oct-2003 | 14:38 | x86 |
| Iisproto.dll | 6.0.6527.0 | 135,168 | 27-Oct-2003 | 14:39 | x86 |
| Imap4be.dll | 6.0.6527.0 | 61,440 | 27-Oct-2003 | 14:39 | x86 |
| Imap4evt.dll | 6.0.6527.0 | 319,488 | 27-Oct-2003 | 13:54 | x86 |
| Imap4fe.dll | 6.0.6527.0 | 126,976 | 27-Oct-2003 | 13:52 | x86 |
| Imap4svc.dll | 6.0.6527.0 | 126,976 | 27-Oct-2003 | 14:38 | x86 |
| Jcb.dll | 6.0.6527.0 | 40,960 | 27-Oct-2003 | 14:39 | x86 |
| Mdbevent.dll | 6.0.6527.0 | 49,152 | 27-Oct-2003 | 13:28 | x86 |
| Mdbmsg.dll | 6.0.6527.0 | 2,285,568 | 27-Oct-2003 | 13:45 | x86 |
| Mdbrole.dll | 6.0.6527.0 | 32,768 | 27-Oct-2003 | 13:30 | x86 |
| Mdbsz.dll | 6.0.6527.0 | 909,312 | 27-Oct-2003 | 13:48 | x86 |
| Mdbtask.dll | 6.0.6527.0 | 24,576 | 27-Oct-2003 | 14:39 | x86 |
| Nntpex.dll | 6.0.6527.0 | 151,552 | 27-Oct-2003 | 13:27 | x86 |
| Peexch50.dll | 6.0.6527.0 | 94,208 | 27-Oct-2003 | 14:34 | x86 |
| Phatcat.dll | 6.0.6527.0 | 397,312 | 27-Oct-2003 | 14:36 | x86 |
| Pop3be.dll | 6.0.6527.0 | 36,864 | 27-Oct-2003 | 14:38 | x86 |
| Pop3evt.dll | 6.0.6527.0 | 303,104 | 27-Oct-2003 | 13:54 | x86 |
| Pop3fe.dll | 6.0.6527.0 | 24,576 | 27-Oct-2003 | 13:53 | x86 |
| Pop3svc.dll | 6.0.6527.0 | 73,728 | 27-Oct-2003 | 14:36 | x86 |
| Protomsg.dll | 6.0.6527.0 | 163,840 | 27-Oct-2003 | 13:54 | x86 |
| Reapi.dll | 6.0.6527.0 | 532,480 | 27-Oct-2003 | 14:39 | x86 |
| Resvc.dll | 6.0.6527.0 | 311,296 | 27-Oct-2003 | 14:42 | x86 |
| Store.exe | 6.0.6527.0 | 4,661,248 | 27-Oct-2003 | 14:37 | x86 |
| Wmtemplates.dll | 6.0.6527.0 | 3,735,552 | 27-Oct-2003 | 13:53 | x86 |
Hotfix to configure Exchange to log an event before it reaches the end of the log file sequence
To help prevent this problem from occurring, you can apply the hotfix that is described in the following Microsoft Knowledge Base article:
896001 An event is not logged in the Application log before the last available transaction log in the sequence is used in Exchange 2000 Server
This hotfix (hotfix 896001) is included in Exchange Server 2003 SP2.
After you apply hotfix 896001 or Exchange Server 2003 SP2, an event that resembles the following event is logged in the Application log when the last available transaction log in the sequence becomes available:
Issues that occur after you apply hotfix 896001 or install Exchange Server 2003 SP2
You apply hotfix 896001 for Exchange 2000 Server, or you install Exchange Server 2003 SP2. You use the available transaction log files. You then try to mount the stores without performing the steps that are described in the "Workaround" section of this article.
When you do this, events that are similar to the following events may be logged in the Application log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1159
Description: Database error 0xfffffdf9 occurred in function JTAB_BASE::EcEscrowUpdate while accessing the database "First Storage Group\Mailbox Store (SERVER)".
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description: Error 0xfffffddc starting Storage Group Path_of_Storage_Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.
REFERENCES
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870540 Availability of the August 2004 Exchange 2000 Server post-Service Pack 3 update rollup
For more information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: XGEN exhaust exhausted Max Maximum sequence log number
Keywords: kbhotfixserver kbexchange2003sp1fix kbqfe kbfix kbexchange2000presp4fix kbbug KB830408
