Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


Bug #: 50000886 (SQL Hotfix)

↑ Back to the top


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.

↑ Back to the top


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

↑ Back to the top


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 <Database_Name> SET PARTNER OFF
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.

↑ Back to the top


Cause

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

↑ Back to the top


Resolution

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 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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 Server 2005 32-bit version
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.2230.069,48818-Apr-200714:45x86
Databasemailengine.dll9.0.2230.075,12018-Apr-200714:45x86
Logread.exe2005.90.2230.0400,75218-Apr-200714:45x86
Microsoft.analysisservices.adomdclient.dll9.0.2230.0546,16018-Apr-200714:45x86
Microsoft.analysisservices.deploymentengine.dll9.0.2230.0140,65618-Apr-200714:45x86
Microsoft.analysisservices.dll9.0.2230.01,217,90418-Apr-200714:45x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2230.078,19218-Apr-200714:45x86
Microsoft.sqlserver.sqlenum.dll9.0.2230.0910,70418-Apr-200714:45x86
Msasxpress.dll9.0.2230.024,94418-Apr-200714:45x86
Msgprox.dll2005.90.2230.0200,56018-Apr-200714:45x86
Msmdlocal.dll9.0.2230.015,646,06418-Apr-200714:45x86
Msmdredir.dll9.0.2230.03,993,96818-Apr-200714:45x86
Mssqlsystemresource.ldfNot applicable524,28818-Apr-200711:55Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03218-Apr-200711:55Not applicable
Odsole70.dll2005.90.2230.059,76018-Apr-200714:45x86
Qrdrsvc.exe2005.90.2230.0369,52018-Apr-200714:45x86
Rdistcom.dll2005.90.2230.0643,44018-Apr-200714:45x86
Repldp.dll2005.90.2230.0187,24818-Apr-200714:45x86
Replmerg.exe2005.90.2230.0320,88018-Apr-200714:45x86
Replprov.dll2005.90.2230.0550,25618-Apr-200714:45x86
Replrec.dll2005.90.2230.0784,75218-Apr-200714:45x86
Replsub.dll2005.90.2230.0407,40818-Apr-200714:45x86
Spresolv.dll2005.90.2230.0177,00818-Apr-200714:46x86
Sqlaccess.dll2005.90.2230.0350,57618-Apr-200714:46x86
Sqlagent90.exe2005.90.2230.0321,39218-Apr-200714:46x86
Sqlservr.exe2005.90.2230.028,978,60018-Apr-200714:46x86
Sysdbupg.sqlNot applicable218,48605-Apr-200710:52Not applicable
Xmlsub.dll2005.90.2230.0195,44018-Apr-200714:46x86
Xpstar90.dll2005.90.2230.0295,28018-Apr-200714:46x86
Xpstar90.rll2005.90.2230.0155,50418-Apr-200714:46x86
SQL Server 2005 x64-based version
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.2230.088,94420-Apr-200713:34x64
Databasemailengine.dll9.0.2230.075,12020-Apr-200713:34x86
Logread.exe2005.90.2230.0525,16820-Apr-200713:35x64
Microsoft.analysisservices.adomdclient.dll9.0.2230.0546,16018-Apr-200714:45x86
Microsoft.analysisservices.adomdclient.dll9.0.2230.0546,16020-Apr-200713:35x86
Microsoft.analysisservices.deploymentengine.dll9.0.2230.0140,65618-Apr-200714:45x86
Microsoft.analysisservices.dll9.0.2230.01,217,90418-Apr-200714:45x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2230.078,19218-Apr-200714:45x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2230.094,06420-Apr-200713:35x64
Microsoft.sqlserver.sqlenum.dll9.0.2230.0877,93620-Apr-200713:35x86
Msasxpress.dll9.0.2230.024,94418-Apr-200714:45x86
Msasxpress.dll9.0.2230.030,06420-Apr-200713:35x64
Msgprox.dll2005.90.2230.0262,00020-Apr-200713:35x64
Msmdlocal.dll9.0.2230.015,646,06418-Apr-200714:45x86
Msmdredir.dll9.0.2230.03,993,96818-Apr-200714:45x86
Mssqlsystemresource.ldfNot applicable524,28818-Apr-200711:55Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03218-Apr-200711:55Not applicable
Odsole70.dll2005.90.2230.090,99220-Apr-200713:35x64
Qrdrsvc.exe2005.90.2230.0434,03220-Apr-200713:35x64
Rdistcom.dll2005.90.2230.0836,46420-Apr-200713:35x64
Repldp.dll2005.90.2230.0187,24818-Apr-200714:45x86
Repldp.dll2005.90.2230.0237,93620-Apr-200713:35x64
Replmerg.exe2005.90.2230.0417,64820-Apr-200713:35x64
Replprov.dll2005.90.2230.0747,88820-Apr-200713:35x64
Replrec.dll2005.90.2230.01,010,54420-Apr-200713:35x64
Replsub.dll2005.90.2230.0528,24020-Apr-200713:35x64
Spresolv.dll2005.90.2230.0225,64820-Apr-200713:35x64
Sqlaccess.dll2005.90.2230.0357,74420-Apr-200713:35x86
Sqlagent90.exe2005.90.2230.0392,56020-Apr-200713:35x64
Sqlservr.exe2005.90.2230.039,363,95220-Apr-200713:35x64
Sysdbupg.sqlNot applicable218,48605-Apr-200710:52Not applicable
Xmlsub.dll2005.90.2230.0319,85620-Apr-200713:35x64
Xpstar90.dll2005.90.2230.0543,60020-Apr-200713:35x64
Xpstar90.rll2005.90.2230.0156,01620-Apr-200713:35x64
SQL Server 2005 Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.2230.0157,55220-Apr-200715:58IA-64
Databasemailengine.dll9.0.2230.075,12020-Apr-200715:58x86
Logread.exe2005.90.2230.01,098,09620-Apr-200715:58IA-64
Microsoft.analysisservices.adomdclient.dll9.0.2230.0546,16018-Apr-200714:45x86
Microsoft.analysisservices.adomdclient.dll9.0.2230.0546,16020-Apr-200715:58x86
Microsoft.analysisservices.deploymentengine.dll9.0.2230.0140,65618-Apr-200714:45x86
Microsoft.analysisservices.dll9.0.2230.01,217,90418-Apr-200714:45x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2230.078,19218-Apr-200714:45x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2230.0165,74420-Apr-200715:58IA-64
Microsoft.sqlserver.sqlenum.dll9.0.2230.0877,93620-Apr-200715:58x86
Msasxpress.dll9.0.2230.024,94418-Apr-200714:45x86
Msasxpress.dll9.0.2230.057,71220-Apr-200715:58IA-64
Msgprox.dll2005.90.2230.0545,13620-Apr-200715:58IA-64
Msmdlocal.dll9.0.2230.048,718,70420-Apr-200715:58IA-64
Msmdredir.dll9.0.2230.06,249,32820-Apr-200715:58IA-64
Mssqlsystemresource.ldfNot applicable524,28818-Apr-200711:55Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03218-Apr-200711:55Not applicable
Odsole70.dll2005.90.2230.0180,08020-Apr-200715:59IA-64
Qrdrsvc.exe2005.90.2230.0943,98420-Apr-200715:59IA-64
Rdistcom.dll2005.90.2230.01,884,01620-Apr-200715:59IA-64
Repldp.dll2005.90.2230.0187,24818-Apr-200714:45x86
Repldp.dll2005.90.2230.0511,34420-Apr-200715:59IA-64
Replmerg.exe2005.90.2230.0957,29620-Apr-200715:59IA-64
Replprov.dll2005.90.2230.01,619,82420-Apr-200715:59IA-64
Replrec.dll2005.90.2230.02,143,60020-Apr-200715:59IA-64
Replsub.dll2005.90.2230.01,159,53620-Apr-200715:59IA-64
Spresolv.dll2005.90.2230.0498,03220-Apr-200715:59IA-64
Sqlaccess.dll2005.90.2230.0352,11220-Apr-200715:59x86
Sqlagent90.exe2005.90.2230.01,143,66420-Apr-200715:59IA-64
Sqlservr.exe2005.90.2230.072,193,90420-Apr-200715:59IA-64
Sysdbupg.sqlNot applicable218,48605-Apr-200710:52Not applicable
Xmlsub.dll2005.90.2230.0593,26420-Apr-200715:59IA-64
Xpstar90.dll2005.90.2230.0953,71220-Apr-200715:59IA-64
Xpstar90.rll2005.90.2230.0154,99220-Apr-200715:59IA-64
SQL Native Client 32-bit version
File nameFile versionFile sizeDateTimePlatform
Sqlncli.dll2005.90.2230.02,229,16018-Apr-200706:46x86
SQL Native Client x64-based version
File nameFile versionFile sizeDateTimePlatform
Sqlncli.dll2005.90.2230.02,861,99220-Apr-200705:35x64
SQL Native Client Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Sqlncli.dll2005.90.2230.05,374,37620-Apr-200707:59IA-64

↑ Back to the top


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.

↑ Back to the top


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.

↑ Back to the top


Status

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

↑ Back to the top


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

↑ Back to the top


References

For 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 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
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:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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:
913089 How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: 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

↑ Back to the top


Keywords: kb, kbautohotfix, kbsql2005engine, kbhotfixrollup, kbfix, kbpubtypekc, kbqfe, kbexpertiseadvanced, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 936179
Revision : 4
Created on : 5/17/2018
Published on : 5/17/2018
Exists online : False
Views : 79