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
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.CreateOb ject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCrea teRequest(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConne ction(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(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
"Carlos Mendona" <carlos.mendonca@.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 Mendona
>
|||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/
|||Looks like MS issued a hot fix for this on the 9th.
http://support.microsoft.com/kb/944099
"Carlos Mendon?a" wrote:
> 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
>
>
|||Great news! I will ask for some testing and post the results later.
Thanks a lot,
Carlos
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:93BE8F7C-A008-4096-A570-4264AAAF7B83@.microsoft.com...[vbcol=seagreen]
> Looks like MS issued a hot fix for this on the 9th.
> http://support.microsoft.com/kb/944099
>
> "Carlos Mendona" wrote:
issues[vbcol=seagreen]
once[vbcol=seagreen]
..Net[vbcol=seagreen]
and[vbcol=seagreen]
Updates[vbcol=seagreen]
issue,[vbcol=seagreen]
but[vbcol=seagreen]
it[vbcol=seagreen]
and/or[vbcol=seagreen]
|||The fix is not publically available. You have to get it from MS directly.
-Hank
In article <#VFla#qMIHA.4228@.TK2MSFTNGP02.phx.gbl>, "Carlos Mendona"
<carlos.mendonca@.locaweb.com.br> wrote:
>Great news! I will ask for some testing and post the results later.
>Thanks a lot,
>Carlos
>"Mark" <Mark@.discussions.microsoft.com> wrote in message
>news:93BE8F7C-A008-4096-A570-4264AAAF7B83@.microsoft.com...
>issues
>once
>..Net
>and
>Updates
>issue,
>but
>it
>and/or
>
|||Did anyone already receive and test this hotfix ?
I also noticed the kb944099 is talking about version 2.0.50727.948 of
system.data.dll
Today I received Microsoft .NET Framework 2.0 SP1 on Windows update, this
Service pack contains version 2.0.50727.1433 of system.dat.dll and is
superseding KB928365. So this sould also fix this problem.
Anyone already tried 1 of this solutions ?
Kind regrards
Tom
"Mark" wrote:
[vbcol=seagreen]
> Looks like MS issued a hot fix for this on the 9th.
> http://support.microsoft.com/kb/944099
>
> "Carlos Mendon?a" wrote:
|||We did and we confirm it does work. MS indeed solved the problem.
Regards,
Carlos Mendona
"treg" <treg@.discussions.microsoft.com> wrote in message
news:61E93D99-B384-43CB-BCD2-1BF49895AD1D@.microsoft.com...[vbcol=seagreen]
> Did anyone already receive and test this hotfix ?
> I also noticed the kb944099 is talking about version 2.0.50727.948 of
> system.data.dll
> Today I received Microsoft .NET Framework 2.0 SP1 on Windows update, this
> Service pack contains version 2.0.50727.1433 of system.dat.dll and is
> superseding KB928365. So this sould also fix this problem.
> Anyone already tried 1 of this solutions ?
> Kind regrards
> Tom
>
> "Mark" wrote:
issues[vbcol=seagreen]
once[vbcol=seagreen]
..Net[vbcol=seagreen]
2003) and[vbcol=seagreen]
Updates[vbcol=seagreen]
issue,[vbcol=seagreen]
the[vbcol=seagreen]
'microsoft.public.dotnet.framework.adonet', but[vbcol=seagreen]
..NET[vbcol=seagreen]
be[vbcol=seagreen]
case, it[vbcol=seagreen]
and/or[vbcol=seagreen]
hint.[vbcol=seagreen]
|||We are still seeing this intermittently. The web server reporting the error,
along with the live and mirror database servers, all have .NET 2.0 SP1,
System.Data.dll version 2.0.507272.1433. KB944099 talks of a hotfix version
2.0.507272.948 and I would assume that SP1 includes this fix, but it appears
not to have fixed the problem in our case.
Any suggestions?
|||We raised this with MS PSS. They confirmed it was not fixed in SP1 and they
gave us the hotfix, which appears to have fixed it.
No comments:
Post a Comment