Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I keep getting the following error (in the thousands) in production:

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.)

I even have a 1 G + log file.

The customer isn't happy with the performance of the application.

I can't produce this error in Development,do so I am guessing that the 2 severs are setup differently.

Additional Information:

There is no attempt to make Development and Production servers the same.


Microsoft Windows Server 2003
for Small Business Server
Service Pack 2

Intel(R) Xeon(R) CPU
E5310 @1.60GHz
1.60 GHz, 3.00 GB of RAM
Physical Address Extension

I believe the SQL Server is the SQL 2005 bundled with SBS.

The application is a WinForm program running on user's desktop systems.

I can't get onto the Development Server, but I'm sure that it exceeds the Production stats. I know that the SQL Server is 2005 Standard.

I have also run the program against a local SQL 2005 Express and not gotten any problems (and attached copies of the files from production).

share|improve this question
@jrcs3 You accepted an answer but didn't provide any details. That's not very nice for somebody like me who is having the same problem and searching for a solution. Where's your community spirit?! – Josh Stodola Feb 23 '10 at 15:40
up vote 2 down vote accepted

The only times I have seen this error have been when the client and server have become forcibly disconnected, either because of the SQL service restarting or the network link being down.

The only reason I can think that would cause this to be a regular problem on in production and not development (if the to environments are otherwise identical) could be that in production the client (or the DB access libraries they use) are holding connections open for longer.

With the users reporting performance issues, it could be that you are having concurrency issues causing the server to become far to busy and connections to therefore timeout. Have you done any analysis on the server's performance metrics (memory/swap usage, disk IO, CPU use, SQL server specific performance counters, ...) during times when performance it poor?

Could you provide more detail of the setup? Are the client application(s) and database server all on the same machine? What versions/editions of SQL Server are you using and what access method are you using?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.