Exchange 2003 SP2 – Event ID 1159 (and others)

Microsoft Exchange

I came into work this morning to a downed Exchange storage group and mail store. In the event log just after the backup ran i saw these string of events in the event log on the Exchange server.

<em>Event Type: Error

Event Source: ESE

Event Category: General

Event ID: 482

Date: 27/10/2010

Time: 21:00:34

User: N/A

Computer: SERVER

<em>Description:

Information Store (672) SG1: An attempt to write to the file “D:\SG1\E00.log” at offset 1253376 (0x0000000000132000) for 512 (0x00000200) bytes failed after 1 seconds with

system error 1784 (0x000006f8): “The supplied user buffer is not valid for the requested operation. “. The write operation will fail with error -1011 (0xfffffc0d). If this error persists then the file may be damaged and may need to be restored from a previous backup.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 414

Date: 27/10/2010

Time: 21:00:34

User: N/A

Computer: SERVER

<em>Description:

Information Store (672) SG1: Unable to write to section 0 while flushing logfile D:\SG1\E00.log. Error -1011 (0xfffffc0d).

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 492

Date: 27/10/2010

Time: 21:00:34

User: N/A

Computer: SERVER

<em>Description:

Information Store (672) SG1: The logfile sequence in “D:\SG1\” has been halted due to a fatal error. No further updates are possible for the databases that use this logfile

sequence. Please correct the problem and restart or restore from backup.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 9558

Date: 27/10/2010

Time: 21:00:34

User: N/A

Computer: SERVER

<em>Description:

An error occurred while writing to the database log file of storage group “SG1”. Attempting to unmount all databases in this storage group.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 471

Date: 27/10/2010

Time: 21:00:34

User: N/A

Computer: >SERVER

<em>Description:

Information Store (672) SG1: Unable to rollback operation #11716372 on database E:\SG1\PFS1\pub1.edb. Error: -510. All future database updates will be rejected.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Error

Event Source: MSExchangeIS

Event Category: General

Event ID: 1159

Date: 27/10/2010

Time: 21:00:34

User: N/A

Computer: SERVER

<em>Description:

Database error 0xfffffbbe occurred in function JTAB_BASE::EcSetCurrentIndex while accessing the database “SG1\MBS1”.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type: Warning

Event Source: MSExchangeIS Mailbox Store

Event Category: General

Event ID: 1115

Date: 27/10/2010

Time: 21:00:41

User: N/A

Computer: SERVER

Description:

Error 0xfffffbbe returned from closing database table, called from function JTAB_BASE::EcCloseTable on table Folders.

For more information, click http://www.microsoft.com/contentredirect.asp.

It turned out that the backup job had started and then caused the problem. It freezes the DB to perform the backup but then it forgot to remove it this meant the exchange DB was left in this “i’m being backed up state”. The next thing because of this, this limit got hit: http://support.microsoft.com/kb/905801

As the limit was hit the store went offline. To fix it I restarted IS, you could also bounce the server.

Hopefully it won’t happen again, i’ve just put it down to the backup job causing the problem.

It might be possible to monitor it, see this link: http://jesperbernle.blogspot.com/2008/07/event-id-1159.html

At least you’d get a warning, I didn’t though, I was on holiday when the limit got reached!

Leave a Reply

Your email address will not be published.