Error starting Storage Group on the Microsoft Exchange Information Store..

Details
Product: Exchange
Event ID: 9518
Source: MSExchangeIS
Version: 6.5.7638.0
Component: Microsoft Exchange Information Store
Message: Error <error code> starting Storage Group <name> on the Microsoft Exchange Information Store.<error message>.
   
Explanation

This event is logged if the Microsoft Exchange Information Store service detects an error when mounting the mailbox stores and public folder stores of a storage group.

This problem can occur if Exchange has used all the available transaction log files. Exchange uses transaction log files that are numbered sequentially. The transaction log files start with E0100001.log, and then increment sequentially to E01ffff0.log. When the last transaction log is filled, the Microsoft Jet database engine returns error -519 (JET_errLogSequenceEnd) to the store. However, the store keeps the databases mounted, although database transactions cannot occur.

The maximum number of transaction log files that can be generated in a single sequence is 1,048,560 (0xFFFF0). Typically, it will take several years of operation before this many log files will be generated.

   
User Action

To resolve this error, try one or more of the following:

  • If you have determined that this error is caused because you have reached the sequential limit of transaction logs for a storage group (E01FFFF0.log), you must install Exchange Server Service Pack 1 (SP1) to dismount the databases in that storage group. Then, you must reset the transaction log file sequence. For detailed steps for resolving this error, see Microsoft Knowledge Base article 830408 “A storage group has shut down and will not remount on Exchange 2000 Server or on Exchange Server 2003” (http://go.microsoft.com/fwlink/?linkId=3052&kbid=830408).
  • If you have not reached the sequential limit of transaction logs for a storage group, check to see if there are any ESE errors or MSExchangeIS errors in the event log that can help you determine what is wrong. Possibilities include the following:

    • There may be an error that indicates that a file-level antivirus software is scanning the database or drive M.
    • There may be an error that indicates that disk-level write caching is incorrectly enabled.

    Depending on the severity of the error code and related MSExchangeIS errors and ESE errors, you may have to contact Microsoft Product Support Services or recover from a backup.

Related:

Leave a Reply