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.)
Well, that’s a mouthful, isn’t it?
I saw this in our production web site’s log and wondered how serious an issue it is. Our site is ASP.NET MVC 3, using Entity Framework 4.1 for database connectivity.
I dug around and found the best explanations here:
- Michael Aspengren blog post with the same loooong title
- Adapter client throws an exception on performing an operation after the connectivity is restored between the adapter client and the SQL Server database
- Troubleshooting: Connection Forcibly Closed
It’s only appears once in the current log and not at all in the last archived log, so I’m not going to worry about it, yet. But I thought other people might be interested in what it is, what causes it and what to do about it and I wanted to record the explanation sources in case it happens again and I need to do something about it.
Advertisement
