Symptoms

Assume that you set up an environment that combines log shipping and database mirroring in Microsoft SQL Server 2008 R2. The database mirroring is running in high-safety mode and automatic failover is configured. In this situation, after an automatic failover, the log shipping may stop working, and the following error is logged in the SQL Server error log:

<Date><Time> spid#  Error: 3456, Severity: 16, State: 1.
<Date><Time> spid#  Could not redo log record (#), for transaction ID (#), on page (#), database '<DatabaseName>' (database ID #). Page: LSN = (#), type = #. Log: OpCode = #, context #, PrevPageLSN: (#). Restore from a backup of the database, or repair the database.
<Date><Time> spid#  Using 'dbghelp.dll' version '4.0.5'
<Date><Time> spid#  **Dump thread - spid = 0, EC = 0x0000000A928F20F0
<Date><Time> spid#  ***Stack Dump being sent to <FilePath>\SQLDump0045.txt
<Date><Time> spid#  * *******************************************************************************
<Date><Time> spid#  *
<Date><Time> spid#  * BEGIN STACK DUMP:
<Date><Time> spid#  *   <Date><Time> spid# 
<Date><Time> spid#  *
<Date><Time> spid#  * HandleAndNoteToErrorlog: Exception raised, major=34, minor=56, severity=16

Additionally, some dump files are generated on the log shipping server.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×