#Sql server client resets connection driver#
#Sql server client resets connection code#

You could also check the documentation for whatever pieces of business objects is hitting SQL Server and see if they have anything documented about using MARS.

You can tell if it's enabled or not from the connection string, pretty much why I suggested posting it if you have access to it. That could still just be from the last error and issues with MARS. Time spent during login: total 0 ms, enqueued 0 ms, network writes 0 ms, network reads 0 ms, establishing SSL 0 ms, network reads during SSL 0 ms, network writes during SSL 0 ms, secure calls during SSL 0 ms, enqueued during SSL 0 ms, negotiating SSPI 0 ms, network reads during SSPI 0 ms, network writes during SSPI 0 ms, secure calls during SSPI 0 ms, enqueued during SSPI 0 ms, validating login 0 ms, including user-defined login processing 0 ms.

This may have been caused by client or server login timeout expiration.

#Sql server client resets connection code#

Network error code 0x2746 occurred while establishing a connection the connection has been closed. This is what I've in extended event around that time from server B. It seems to do nothing other than cause problems. And the best fix for that is to get rid of MARS. I've only seen that last error when using MARS. Is this all Business Objects - anything else connecting at that time? And what jobs are failing - SQL Server jobs or other jobs? This error occurs when a client sends a request to reset the connection while there are batches still running in the session, o r when the client sends a request while the session is resetting a connection.

#Sql server client resets connection driver#

The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. T he first four bytes (DWORD) of the Data section contains the error code. Performance data for this service will not be available. The Open Procedure for service 'ReportServer' in DLL 'perf-ReportServer-rsctr.8.dll' failed. The first four bytes (DWORD) of the Data section contains the error code. The Open Procedure for service 'SQLSERVERAGENT' in DLL '' failed. When I look at the event log, I get the following error messages.

Report (business objects) connects to SQL server using a generic sql account. Around 2am in the morning, certain jobs fails and report fails at the same time.