Login or Sign Up to become a member!
LessThanDot Sit Logo

LessThanDot

Data Management

Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.

LTD Social Sitings

Lessthandot twitter Lessthandot Linkedin Lessthandot friendfeed Lessthandot facebook Lessthandot rss

Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.

Your profile

    Search

    XML Feeds

    Google Ads

    « Having Fun With OPENQUERY And Update,Delete And Insert StatementsListing All The User-Defined Data Types That Were Created On Your SQL Server »
    comments

    This question was asked yesterday in our forums
    A transport-level error has occurred when sending the..... by Impal3r

    When i have a query window open In SSMS and I step away for a while and then I run the query I get the following error

    A transport-level error has occurred when sending the request to the server

    what I do then is disconnect from the server, connect again and then I can open anew query window to run the query again. This seems tedious and not really productive. Is there a better way to get around this?

    I actually discovered quite by accident a while back how to resolve this. If you have SSMS open with a query in your query window, then you go away for two hours and when you come back you hit F5. What happens then is that you will see the following 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.)


    What you can do is connect to the server again and try running your query and that will solve it. There is a faster/easier way.....just hit F5 or the execute icon again and the query will also run. That is much easier isn't it?




    *** If you have a SQL related question try our Microsoft SQL Server Programming forum or our Microsoft SQL Server Admin forum

    About the Author

    User bio imageDenis has been working with SQL Server since version 6.5. Although he worked as an ASP/JSP/ColdFusion developer before the dot com bust, he has been working exclusively as a database developer/architect since 2002. In addition to English, Denis is also fluent in Croatian and Dutch, but he can curse in many other languages and dialects (just ask the SQL optimizer) He lives in Princeton, NJ with his wife and three kids.
    Social SitingsTwitterFacebookLinkedInHomePageFlickrLTD RSS Feed
    4957 views
    Instapaper

    2 comments

    Comment from: Mark White [Visitor] Email
    ***--
    Mark White Explanation:

    SQL Server has trashed it's thread that was tied to your SSMS query window and released all resources tied to it (Usually because SQL Server has restarted or someone has killed your process in SQL Activity Monitor).

    When you try to run the first time, nothing will happen because SSMS thinks you're still connected. The second time you run the query, this will force a re-connect and open everything back up, allowing you to query away.
    06/18/09 @ 13:52
    Comment from: Lucas [Visitor]
    Lucas I found that if i change the logging mode in the database to simple from bulk logged or the higher option this manifests itself more times not sure if it is coincidence or relevent
    06/21/09 @ 18:47

    Leave a comment


    Your email address will not be revealed on this site.

    Your URL will be displayed.
    (Line breaks become <br />)
    (Name, email & website)
    (Allow users to contact you through a message form (your email will not be revealed.)