DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2482977 - Last Review: March 21, 2011 - Revision: 4.0

Hotfix Download Available
View and request hotfix downloads
 

On This Page

SYMPTOMS

Consider the following scenario:
  • An application tries to connect to an instance of Microsoft SQL Server by using the Microsoft SQL Server Native Client 10.0 OLE DB provider.
  • The application uses the extended OLE DB initialization properties in the connection string. For example, the application uses the Server, Database, and FailOverPartner properties in the following connection string:
    Provider=SQLNCLI10.1;Integrated Security=SSPI; Server =<instance_name>; Database =<database_name>; FailOverPartner=<failover_partner_name>;

    Notes
    • <instance_name> is a placeholder that represents the name of the instance.
    • <database_name> is a placeholder that represents the name of the database.
    • <failover_partner_name> is a placeholder that represents the name of the failover partner.
In this scenario, the connection between the application and the instance of SQL Server is not created. Additionally, you receive the 10061 Windows sockets (Winsock) error code and the following error message:
No connection could be made because the target machine actively refused it.

CAUSE

This issue occurs because of an error in the SQL Server Native Client 10.0 OLE DB provider.

If you use extended OLE DB initialization properties for the SQL Server Native Client 10.0 OLE DB provider in the connection string, the connection string is encrypted. However, the extended properties might not be decrypted by the provider. For example, the Data Source and Initial Catalog names might not be decrypted by the provider. Therefore, you receive the error that is mentioned in the "Symptoms" section.

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2498535  (http://support.microsoft.com/kb/2498535/LN/ ) Cumulative update package 3 for SQL Server 2008 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 2008 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:
2402659  (http://support.microsoft.com/kb/2402659/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 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.

SQL Server 2008 R2

The 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 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2489376  (http://support.microsoft.com/kb/2489376/ ) Cumulative Update package 6 for SQL Server 2008 R2
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 2008 R2 fix release. We recommend 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:
981356  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2005 Service Pack 3

The fix for this issue was first released in Cumulative Update 14 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2489375  (http://support.microsoft.com/kb/2489375/LN/ ) Cumulative update package 14 for SQL Server 2005 Service Pack 3
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:
960598  (http://support.microsoft.com/kb/960598/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 1


The fix for this issue was first released in Cumulative Update 12 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467236  (http://support.microsoft.com/kb/2467236/LN/ ) Cumulative update package 12 for SQL Server 2008 Service Pack 1
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 2008 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:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 4

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2489409  (http://support.microsoft.com/kb/2489409/LN/ ) Cumulative update package 2 for SQL Server 2005 Service Pack 4
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:
2485757  (http://support.microsoft.com/kb/2485757/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. 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.

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, submit a request to 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 website:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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 2008 Service Pack 1 (SP1) installed.

Restart information

You may have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry 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.
For all supported x86-based versions of SQL Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
sqlncli10.dll2007.100.2806.02,560,87214-Dec-201016:43x86
Sqlncli_keyfile.dll2007.100.2806.013,67214-Dec-201015:30x86
For all supported x64-based version of SQL Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
sqlncli10.dll2007.100.2806.02,560,87214-Dec-201016:43x86
sqlncli10.dll2007.100.2806.03,161,96014-Dec-201023:45x64
Sqlncli_keyfile.dll2007.100.2806.014,18414-Dec-201022:48x64
For all supported IA-64-based versions of SQL Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
sqlncli10.dll2007.100.2806.02,560,87214-Dec-201016:43x86
Sqlncli_keyfile.dll2007.100.2806.013,67214-Dec-201015:30x86

STATUS

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

MORE INFORMATION

For more information about connection strings and OLE DB provider for SQL Server Native Client, visit the following Microsoft Developer Network (MSDN) website:
General information about connection strings and OLE DB provider for SQL Server Native Client (http://blogs.msdn.com/b/sqlnativeclient/archive/2009/05/07/sql-server-native-client-connection-strings-and-ole-db.aspx)
For more information about connection string syntax, visit the following MSDN website:
General information about the connection string syntax (http://msdn.microsoft.com/en-us/library/ms722656%28VS.85%29.aspx)
For more information about OLE DB initialization properties, visit the following MSDN website:
General information about OLE DB initialization properties (http://msdn.microsoft.com/en-us/library/ms723996%28VS.85%29.aspx)

APPLIES TO
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2005 Service Pack 3
  • Microsoft SQL Server 2005 Service Pack 4
Keywords: 
kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew kbautohotfix KB2482977
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support