?
Solved

event ID 1159 is logged in Exchange Server 2007

Posted on 2013-06-09
2
Medium Priority
?
691 Views
Last Modified: 2013-06-16
The Databases were dismounted as the Logs has reached the Maximum Limit 0xfffffd9a(5120).

Exchange server 2007 sp3 MBX seerver
The Exchange store is dismounted, and event ID 1159 is logged in Exchange Server 2007

What is the warning event id?
0
Comment
Question by:Buntyquest
2 Comments
 
LVL 19

Expert Comment

by:Raheman M. Abdul
ID: 39233407
Suggestion: Databases and Logs should be on different drives. This is one of the reason for the issue.

Refer: http://support.microsoft.com/kb/925817
0
 
LVL 8

Accepted Solution

by:
I Qasmi earned 1000 total points
ID: 39233749
http://support.microsoft.com/kb/925817
This KB Article has the workaround in it

The very first thing is you perform a full online backup
This will purge all the logs to the database

You can do this with the vss

http://www.msexchange.org/articles-tutorials/exchange-server-2007/high-availability-recovery/uncovering-new-exchange-2007-sp2-volume-snapshot-vss-plug-in-part1.html

http://www.msexchange.org/articles-tutorials/exchange-server-2007/high-availability-recovery/uncovering-new-exchange-2007-sp2-volume-snapshot-vss-plug-in-part2.html

====================================================================
Many uncommitted ESE transaction log files may be created in the following scenarios:

A process is locked in the backup software that you are using.

The backup software that you are using stopped responding.

You try to move many mailboxes at the same time that a backup process occurs.

The server is experiencing performance issues. For example, disk subsystem issues are preventing the server from responding quickly to simultaneous disk-intensive operations.

To determine how many uncommitted ESE transaction log files are in the storage group, review the checkpoint depth.

The checkpoint depth is the difference between the location of the checkpoint file and the location of the E0x.log file. The checkpoint file lists transactions that were committed to the database. The checkpoint depth indicates how many ESE transaction log files contain content that is not yet committed to the Exchange store
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Upgrading from older Exchange server to the latest Exchange server can be tiresome, error-prone and risky, without being a seasoned exchange server administrators. It can become even problematic if you're an organization that runs on tight timeline…
Here is a method which can be used to help resolve a "Content Index Failed" error on a Microsoft Exchange Server.
This video discusses moving either the default database or any database to a new volume.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month4 days, 1 hour left to enroll

599 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question