F
Fredrik Melin
After upgrading to .NET 2.0 I have the problem of getting error
A transport-level error has occurred when sending the request to the server.
(provider: TCP Provider, error: 0 - An existing connection was forcibly
closed by the remote host.)
When executing various database commands.
(even if the connection command is in the same function as the rest of the
commands)
It seems that with Framework 2.0 it monitors the connection and if it goes
down and comes back up again, just for a fraction, you get this error.
It happens both against old SQL 2000 servers as well as new SQL 2005
servers.
It happens on several diffrent installations, in diffrent countries.
It actually happens even in the SQL Mangement Studio...
Anyone seen this error and found a solution?
(ive posted on various SQL Server forums with no result.)
A transport-level error has occurred when sending the request to the server.
(provider: TCP Provider, error: 0 - An existing connection was forcibly
closed by the remote host.)
When executing various database commands.
(even if the connection command is in the same function as the rest of the
commands)
It seems that with Framework 2.0 it monitors the connection and if it goes
down and comes back up again, just for a fraction, you get this error.
It happens both against old SQL 2000 servers as well as new SQL 2005
servers.
It happens on several diffrent installations, in diffrent countries.
It actually happens even in the SQL Mangement Studio...
Anyone seen this error and found a solution?
(ive posted on various SQL Server forums with no result.)