Article ID: 944099 - Last Review: April 28, 2009 - Revision: 4.0 FIX: Error message when you use the System.Data.SqlClient managed data provider to connect to an instance of SQL Server 2005 that is configured to use database mirroring: "Internal .Net Framework Data Provider error 6"On This PageSYMPTOMSConsider the following scenario. In an application, you use the managed SqlClient provider to connect to an instance of Microsoft SQL Server 2005. The
instance of SQL
Server 2005 is configured to use database
mirroring. Additionally, you specify a failover partner server in
the connection string of the application.
In
this scenario, you may receive the following error message when
you connect to the principal server after
failover occurs: Internal .Net Framework Data Provider error
6 Error: 18456, Severity: 14,
State: 16. Login failed for user DomainName/UserName CAUSEThis problem occurs because the code in the System.Data.dll file
does not correctly process state
changes for the current
connections in the connection pool. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Restart informationYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.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. The .NET Framework 2.0, x86-based versionsCollapse this table
The .NET Framework 2.0, x64-based versionsCollapse this table
The .NET Framework 2.0, Itanium-based versionsCollapse this table
948815
(http://support.microsoft.com/kb/948815/
)
Availability of the .NET Framework 2.0 post-Service Pack 1 hotfix rollup package for System.Data.dll and System.Data.OracleClient.dll
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONThis behavior was originally reported to occur when you specify a failover partner server in
the connection string of the application. A hotfix has been provided to address the issue. However, this issue can also occur without a failover partner configured in the connection string. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates | Article Translations
|
Back to the top
