DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Tue, 14 Aug 2007 19:06:52 -0300,    posted on: microsoft.public.dotnet.framework.adonet        back       

Thread Index
  1    Carlos Mendona


KB928365 and 'Internal .Net Framework Data Provider error 6' issue with .NET 2.0 on databases with failover partner   
Hello,

I work at a Hosting Company in Brazil and we have been experiencing issues
with managed applications using .NET Framework 2.0 that connect to SQL
Server 2005 databases with a failover partner. These issues started
happening after we have applied KB928365
(http://support.microsoft.com/KB/928365).

The issue is an System.InvalidOperationException that is thrown every once
in a while when connecting to the databases. The message is 'Internal .Net
Framework Data Provider error 6.'. Both Operating System (Windows 2003) and
databases (SQL Server 2005) are up to date, including all Security Updates
and Service Packs.

Although not many use failover partners to be able to reproduce the issue,
we have identified people with similar problems while searching for the
exception message in the major search engines. Additionally, the same
problem has been reported at 'microsoft.public.dotnet.framework.adonet', but
it has been suggested that KB928365 should be removed, which is not an
option for us considering the security concerns involved.

I am posting in the newsgroups in hope of reaching someone from the .NET
team to report this issue. I think it may be a bug, but it could also be
some configuration requirement that KB928365 introduced. In either case, it
is an issue that affect big databases and I believe that we should pay
special attention to the case.

I am not familiar with the process of reporting an issue to the .NET and/or
SQL Server teams and I would appreciate if someone could give me a hint.

I thank you in advance.

Carlos Mendona
Date:Tue, 14 Aug 2007 19:06:52 -0300   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us