Database error name occurred in function name while accessing the database “error code”.

Details
Product: Exchange
Event ID: 1159
Source: MSExchangeIS
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: Database error name occurred in function name while accessing the database “error code”.
   
Explanation

This event identifies that a critical input/output error or disk error has occurred. One possible cause of this error is that the database disk is full.

This error can also occur if Exchange Server has used all the available transaction log files. Exchange Server 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 mailbox stores and public folder stores of a storage group cannot be restarted.

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 procedures:

  • 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 reset the transaction log file sequence. For detailed steps to resolve 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).

    Note   The procedure to resolve the error associated with Event 1159 is the same procedure you would follow when MSExchangeIS Event 9518 is received. The main difference between Event 1159 and 9518 is that when MSExchangeIS Event 1159 occurs, the mailbox stores and public folder stores of a storage group cannot be restarted. When MSExchangeIS Event 9518 occurs, the mailbox stores and public folder stores can be mounted, but cannot be accessed.

  • If you have not reached the sequential limit of transaction logs for a storage group, check to see if a disk drive that you are using for your transaction logs is full. If the disk is full, delete any unnecessary files.

    If the problem still persists, contact Microsoft Product Support Services.

  • Related:

    Leave a Reply