Select the product you need help with
FIX: Error message when you start a database mirroring session in SQL Server 2005: "Communications to the remote server instance 'TCP://<ComputerName>:<PortNumber>' failed before database mirroring was fully started"Article ID: 947462 - View products that this article applies to. Bug: #50002243 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. SYMPTOMSIn Microsoft SQL Server 2005, you configure database mirroring on a database that has a large transaction log file. When you start the database mirroring session, you receive the following error message: Error: 1413, Severity: 16, State: 1.
Communications to the remote server instance 'TCP://ComputerName:PortNumber' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the command when the remote database is started. Date Time SPID Error: 1479, Severity: 16, State: 1.
Date Time SPID The mirroring connection to "TCP://ComputerName:PortNumber" has timed out for database "DatabaseName" after 10 seconds without a response. Check the service and network connections. Date Time SPID Error: 1413, Severity: 16, State: 1. Date Time SPID Communications to the remote server instance 'TCP://ComputerName:PortNumber' failed before database mirroring was fully started. The ALTER DATABASE command failed. Retry the command when the remote database is started. CAUSEThis issue occurs because a time-out error occurs when you start the database mirroring session. When the principal server connects to the mirroring server for the first time, the mirroring server scans the transaction log before the mirroring server responds to the request of the principal server. If the transaction log is very large, and the mirroring server takes more than 10 seconds to scan the transaction log, a time-out error occurs. RESOLUTIONThe fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 946608 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/946608/LN/
)
Cumulative update package 6 for SQL Server 2005 Service Pack 2937137 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
WORKAROUNDTo work around this issue, follow these steps:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 946608
(http://support.microsoft.com/kb/946608/LN/
)
Cumulative update package 6 for SQL Server 2005 Service Pack 2REFERENCESFor more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
935897 For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/935897/LN/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems913089 For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/913089/LN/
)
How to obtain the latest service pack for SQL Server 2005 http://go.microsoft.com/fwlink/?LinkId=71711 For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://go.microsoft.com/fwlink/?LinkId=71711)
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/LN/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 947462 - Last Review: February 1, 2008 - Revision: 1.1 APPLIES TO
|
Back to the top
