Re: SQL Disconnecting multiple clients

Hi Dana,

Well actually I'm from MS myself and it was client of mine. unfortunately our client didn't have time to wait for us to complete the investigation and decided to reinstall. We therefore never got to the bottom of it, sadly.

Jonathan



dmaxx wrote:
Glad to here we were not alone.

We opened a case last Friday (7/6).

What turned out to be the cause of the issues you were involved in?

Thanks,

Dana

"JPD" wrote:

Hi Dana,

I have seen something similar before and I would suggest that you open a support case with MS. While the error log is not showing anything, you are probably getting sql dumps in the log directory and you should pass them on to MS for analysis.

Regards,
Jonathan



dmaxx wrote:
We have a situation where multiple-random client connections to SQL server get disconnected. The workstations are not consistent, the time is not consistent, and the functions being run are not consistent.

One thing that we can reproduce is that sometime, but not always, if a workstation runs a function that calls a specific stored procedure (SQL native client, ADO, SQL Server 2005 SP2), during the course of the parameter validation (after the .execute) SQL sends an ACK, RST followed by two RST TCP packet back to the client and disconnects the connection.

At the same time, several other connections across multiple computers are also dropped by SQL. However, some computers may have multiple connections to SQL and some, but not all of these will be dropped. Other computers will not have their connections dropped at all.

No SQL server errors are logged. Trace flags 4029 and 3689 have been set.

We have the network packet traces and the SQL profiler output to show this.

This is not reproducable at any other site.

Any ideas on what this could be would be greatly appreciated.
--
Dana Comolli
MS ISV Partner
.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Dont understand what version of SQL to install
    ... I'm talking about developing and testing databases for my client and ... To my XP, I can add SQL Developer 2008 to develop (I guess I should say, ... So I can use SQL Developer 2008 to create a database in standard 2005, ... installed on Client OSs such as Windows Vista. ...
    (microsoft.public.sqlserver.setup)
  • Re: DataSet.GetChanges() in RowChanged(DataRowAction.Add)
    ... have you considered SQL Express and use ... > I realize now that I didn't describe well how the client application is ... > Framework installed on the client machine, but not any SQL Server). ... > 20 tables in different relations with eachother in the database, ...
    (microsoft.public.dotnet.framework.adonet)
  • Managing connections to attached tables
    ... Managing connections to those attached tables? ... Architecture is multi-user VB App connecting to SQL Serve via tables ... We have REPLACED legacy MDB TABLES by "upsizing" to SQL Server. ... There is NO ACCESS CLIENT ... ...
    (microsoft.public.access.modulesdaovba)
  • Managing connections to attached tables
    ... Managing connections to those attached tables? ... Architecture is multi-user VB App connecting to SQL Serve via tables ... We have REPLACED legacy MDB TABLES by "upsizing" to SQL Server. ... There is NO ACCESS CLIENT ... ...
    (microsoft.public.vb.database.dao)