Post reply

A transport-level error

  • May 15, 2007 at 8:37 am

    #120015

    From time to time, while running a query in SSMS, or re-executing a query which was sitting in SSMS for a long time, for example since yesterday, I receive the following error:

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

    For the latter case it's probably understood - SQL Srever apparently runnning an internal job that closes all connections that have not been active for a long time. If this is the case, where can I disable this setting ? However, for the former case, when it throws this error in the middle of query execution, it sounds ominous. How to to fix it, where should I troubleshhot ?

    Thanks

     

  • May 15, 2007 at 9:09 am

    #706534

    Mark

    Is it possible that the SQL Server service has been stopped and started since the connection was made to the database?

    John

  • May 15, 2007 at 9:19 am

    #706539

    I have also experienced this on occasion where I work.  One of two things has occurred; first, the server running SQL Server has been rebooted; or second, we have had network issues that broke the connection.

  • May 15, 2007 at 9:30 am

    #706548

    are you rebooting the server or restarting sql service? i get this whenever i have a query window open in SSMS and the server or service has been restarted

  • May 15, 2007 at 9:55 am

    #706563

    John and SQL Noob: No, SQL Server has not been stopped and started. In order to check whether server has been rebooted or not, I usually run query  select login_time from sysprocesses where spid<10. First 10 SPIDs always belong to SQL Server internal processes, and if it was recently rebooted it would show the time when these processes have started. In my case it's 5/03/2007 which is not recent.

    Lynn: Network issues ? That's interesting one. How can I check them ? And why it was NOT an issue before we converted to 2005 ? Is this SQL Server 2005 specific network issues ?

     

  • May 15, 2007 at 12:40 pm

    #706594

    I had the problem here with QA and SQL Server 2000.  Our network has had issues most of the year for reasons I won't go into that has caused connectivity issues between desktop systems and sql servers or application servers (depending on who the user is).

    I can't really tell you how to go about checking network issues, as I know enough about networking to make it work at home and that's about it.

Viewing 6 posts - 1 through 5 (of 5 total)

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