Microsoft KB Archive/936179

= FIX: Error message when you use SQL Native Client to connect to an instance of a principal server in a database mirroring session: &quot;The connection attempted to fail over to a server that does not have a failover partner&quot; =

Article ID: 936179

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems

-



Bug #: 50000886 (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.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by the hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
Consider the following scenario:  You configure database mirroring for a database in SQL Server 2005. In an application, you use SQL Native Client to connect to the instance of the principal server in the database mirroring session. In the application, you set the Failover_Partner option in the connection string to the mirror server. A failover occurs in the database mirroring session.  You run the following statement to restore the database to the principal server: ALTER DATABASE  SET PARTNER OFF </ul>

In this scenario, when you run the application to connect to the instance of the principal server, you receive the following error message:

[Microsoft][SQL Native Client]The connection attempted to fail over to a server that does not have a failover partner.

Note This application can successfully connect to the instance of the principal server before the failover occurs.

<div class="cause_section">

CAUSE
This problem occurs because the synchronization between the principal server and the mirror server is broken.

<div class="resolution_section">

Cumulative update information
The fix for this issue was first released as a hotfix. However, this fix is also included in Cumulative Update 4. 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:

941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

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.

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply this hotfix, you must have SQL Server 2005 Service Pack 1 (SP1) installed. For more information about how to obtain SQL Server 2005 Service Pack 1, 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

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Native Client Itanium architecture version
<div class="resolution_section">

How to apply this hotfix
To apply this hotfix, follow these steps:
 * 1) Apply the SQL Server 2005 hotfix on the principal server.
 * 2) Enable trace flag 1449 on the principal server.
 * 3) Apply the SQL Native Client hotfix on the client computer on which you run the application.

<div class="workaround_section">

WORKAROUND
To work around this problem, follow these steps:
 * 1) Disable the database mirroring endpoint on the principal server.
 * 2) Remove database mirroring on the principal server.
 * 3) Restore the database on the principal server.
 * 4) Enable the database mirroring endpoint on the principal server.
 * 5) Remove database mirroring on the mirror server.
 * 6) Reconfigure the database mirroring on the principal server.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
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:

822499 New naming schema for Microsoft SQL Server software update packages

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

<div class="references_section">