Home All Groups Group Topic Archive Search About

Re: KB928365 and 'Internal .Net Framework Data Provider error 6' issue with .NET 2.0 on databases wi

Author
9 Nov 2007 2:08 PM
Carlos Mendonça
I'm posting the stack trace we've captured. Please reply below if you have
captured something different.

System.InvalidOperationException: Internal .Net Framework Data Provider
error 6.
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
   at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
   at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
   at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at (..) <-- our propetary code begins here

The error code comes from the System.Data.Common.ADP.InternalErrorCode
enumerator (value NewObjectCannotBePooled = 6).

Unfortunately, this problem still has no solution and Microsoft is yet to
disclose some information regarding this issue. Up until now, as far as I
know, they haven't acknowledged nor identified the error.

Carlos

Show quote
"Carlos Mendonça" <carlos.mendo***@locaweb.com.br> wrote in message
news:%23vZY99r3HHA.4880@TK2MSFTNGP03.phx.gbl...
> 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 Mendonça
>
>

Author
9 Nov 2007 2:21 PM
Kent Tegels
Hello Carlos,

Can you post the connection string being used? Please sanitize it for userID
and password, of course. :)

Thanks,
Kent Tegels
http://staff.develop.com/ktegels/

AddThis Social Bookmark Button