FIX: Database mirroring sessions may stop intermittently in SQL Server 2005

Article translations Article translations
Article ID: 959006 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

You create a database mirroring session in Microsoft SQL Server 2005. However, the database mirroring may stop intermittently. If you query the sys.dm_db_mirroring_connections dynamic management view (DMV) when the database mirroring stops, the value of the is_send_flow_controlled column is 1.

Note When this column has a value of 1, network flow control has postponed network sends because the network is busy. When the value is 1, the principal server is in the flow controlled state.

When this problem occurs, the following error message is logged in the error log file on the mirror server:
<Date><Time> spid16s Error: 1479, Severity: 16, State: 1.
<Date><Time> spid16s The mirroring connection to "<EndPoint>" has timed out for database "MSS" after 120 seconds without a response. Check the service and network connections.
<Date><Time> spid16s Database mirroring is inactive for database 'MSS'. This is an informational message only. No user action is required.
<Date><Time> spid16s Restart packet created for dbid 5.
<Date><Time> spid22s Restart packet processing for dbid 5.
<Date><Time> spid22s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
<Date><Time> spid22s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
<Date><Time> spid22s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
<Date><Time> spid22s Starting up database '<Database name>'.
<Date><Time> spid22s Bypassing recovery for database '<Database name>' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
When this problem occurs, the following error message is logged in the error log file on the principal server:
<Date><Time> spid27s Error: 1479, Severity: 16, State: 2.
<Date><Time> spid27s The mirroring connection to "<EndPoint>" has timed out for database "<Database name>" after 120 seconds without a response. Check the service and network connections.
<Date><Time> spid26s Error: 1479, Severity: 16, State: 2.
<Date><Time> spid26s The mirroring connection to "<EndPoint> has timed out for database "<Database name>" after 120 seconds without a response. Check the service and network connections.
<Date><Time> spid26s Database mirroring is inactive for database '<Database name>'. This is an informational message only. No user action is required.
<Date><Time> spid26s Error: 1479, Severity: 16, State: 2.
<Date><Time> spid26s The mirroring connection to "<EndPoint>" has timed out for database "<Database name>" after 120 seconds without a response. Check the service and network connections.

CAUSE

If the principal server is in the flow controlled state, the principal server is waiting for acknowledgements (ACKs) from the mirror server to free up some network buffers and to exit the flow controlled state. However, if the connection is idle for 90 seconds, the connection times out. This causes the principal server to free up the network buffers that are allocated for the connection and to create a new connection to resend the messages. Because of a bug in SQL Server 2005, the connection does not time out under certain race conditions.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 3.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 959006 - Last Review: December 16, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbtshoot kbsql2005engine kbexpertiseadvanced kbfix kbbug KB959006

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com