We have started experiencing "System.InvalidOperationException: Internal 
..Net Framework Data Provider error 6" exceptions from our Visual Studio 2005 
applications since implementing Mirroring with SQL Server 2005.  If we 
change our connection string so that it does not include the Failover 
Partner, then we do not get these exceptions.  We have also tried removing 
the Network parameter and found that we still get these exceptions, although 
less frequently.

Has anybody else been able to track down the cause of this type of exception 
or come up with a solution?

Thanks,
Jody


Connection Strings:
--------------------
Data Source=Primary; Failover Partner=Mirror;Network=dbmssocn;Initial 
Catalog=Live;Uid=username;Pwd=password;
Data Source=Primary; Failover Partner=Mirror;Initial 
Catalog=Live;Uid=username;Pwd=password;


Exception Message:
--------------------
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()

I think that we have found the solution to our problem.

After switching network cables on each of our database servers, these 
exceptions disappeared.  Prior to doing this, we would see an "Internal .NET 
Framework Data Provider error 6" message at least once every 2 hours.  The 
network cables have been replaced 4 days ago, and we have not seen this 
exception since.

Hope this helps others who are experiencing the same type of issue.

Thanks,
Jody


"Jody Gelowitz"  wrote in message 
news:OHW$F%23O2HHA.4400@TK2MSFTNGP06.phx.gbl...

> We have started experiencing "System.InvalidOperationException: Internal 
> .Net Framework Data Provider error 6" exceptions from our Visual Studio 
> 2005 applications since implementing Mirroring with SQL Server 2005.  If 
> we change our connection string so that it does not include the Failover 
> Partner, then we do not get these exceptions.  We have also tried removing 
> the Network parameter and found that we still get these exceptions, 
> although less frequently.
>
> Has anybody else been able to track down the cause of this type of 
> exception or come up with a solution?
>
> Thanks,
> Jody
>
>
> Connection Strings:
> --------------------
> Data Source=Primary; Failover Partner=Mirror;Network=dbmssocn;Initial 
> Catalog=Live;Uid=username;Pwd=password;
> Data Source=Primary; Failover Partner=Mirror;Initial 
> Catalog=Live;Uid=username;Pwd=password;
>
>
> Exception Message:
> --------------------
> 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()
>
>