Post reply

Existing connection was forcibly closed by the remote host

  • December 4, 2006 at 9:02 am

    #171118

    Sometimes, when I re-run a script left in my open SSMS session from the last day or some time ago, I get the following error message:

    Msg 10054, Level 20, State 0, Line 0

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

    If I re-run it again, it's fime, SQL Server just assigns another SPID to it and resubmits it. But my question is what is default time value for such kind of inactivity and where I can set this it ?

    Thanks

  • December 4, 2006 at 2:44 pm

    #675633

    Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1

    http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm

     

    MohammedU
    Microsoft SQL Server MVP

  • December 4, 2006 at 3:54 pm

    #675655

    My server is running on Windows NT 5.2, or it is the same as Windows Server 2003 ?

    Here is full output of my @@version:

    Microsoft SQL Server 2005 - 9.00.1399.06 (X64) 

    Oct 14 2005 00:35:21

    Copyright (c) 1988-2005 Microsoft Corporation

    Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)

    In this article they recommend to add a value to the Registry. I am kind of scared to manually update production Registry. I think it is a sort of bug, why Microsoft did not take steps to fix it in the first place ? I understand that this is retorical question, but the way they suggest to solve the problem is not an appropriate way to do.

     

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply