Sql server client resets connection how to#
Sql server client resets connection driver#

Is there any other technique I can use as a DBA or sysadmin to troubleshoot this further, or anything I can suggest to the developer that might provide him with useful information or make the problem less likely to happen?

Further, I'm not sure that the developer would be able to take advantage of this evidence in order to solve the problem. I could set up a trace to confirm this, but I'd have to record quite a lot of unrelated activity, and the problem is only happening once every few days.

It appears to suggest that the client's program is calling sp_reset_connection while a batch is still running.

Sql server client resets connection driver#

If you set Async=true we perform additional locking in the client driver to prevent this from happening.ДЇurther information about this error is scarce. If you are using MARS and using the same connection on multiple concurrent threads what can happen is the call to reset the connection can get slightly delayed and trigger this error. If you set Async=true on the connection string it should prevent this problem.

I'm told the application's connection string has asynchronous processing enabled, per Matt Neerincx's comment in this thread (I don't have access to the application servers to confirm this myself):.

The open connection appears to definitely have MARS enabled, as net_transport in sys.dm_exec_connections shows Session.

The client program shows up in sys.dm_exec_connections as.

They probably won't upgrade major versions without extensive testing, but applying a newer CU is viable.

SQL Server version is (SQL Server 2008 SP3 CU12).

The client is using Entity Framework (yes, I know.), with MARS enabled (yes, I know.).

Sql server client resets connection how to#

The cause of the blocking is straightforward, but how to stop the error from occurring is not. When this error occurs, a typical outcome is a session that is holding locks, but has no SQL running (no row in sys.dm_exec_requests for the session_id), and causes blocking until it is killed. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, or when the client sends a request while the session is resetting a connection. The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. I'm working with a developer who is struggling to stop the following error: