![logo design studio pro the underlying connection was closed an unexpected error occurred on a send logo design studio pro the underlying connection was closed an unexpected error occurred on a send](https://venturebeat.com/wp-content/uploads/2019/04/chrome-remove-animations.png)
- #LOGO DESIGN STUDIO PRO THE UNDERLYING CONNECTION WAS CLOSED AN UNEXPECTED ERROR OCCURRED ON A SEND PATCH#
- #LOGO DESIGN STUDIO PRO THE UNDERLYING CONNECTION WAS CLOSED AN UNEXPECTED ERROR OCCURRED ON A SEND WINDOWS#
For example: if the server is set to close idle connections after 120 seconds, then I would suggest that the client not use the connection after 100 seconds. The client should be configured to dispose of any connection that is idle for some small amount of time less than N. What does this mean? The server will automatically close the connection after N seconds. The most important/helpful setting for most people that run into this problem is that the client needs to set its "Max Idle timeout" to be something LESS than the connection idle timeout set on the server. NET framework includes an important fix that helps with this type of error but you should still make sure that you have your client and server configured in such a way to limit your exposure to this type of problem.
![logo design studio pro the underlying connection was closed an unexpected error occurred on a send logo design studio pro the underlying connection was closed an unexpected error occurred on a send](https://i.stack.imgur.com/MIdOe.png)
It then tries to use the connection but it blows up. The connection is closed but the client doesn't know that it has been closed. The most common cause of this error is exactly as you describe. Here is a link to a blog written by one of the msft support engineers that works with companies to diagnose these kinds of failures. At the very least I was hoping to have a better understanding as to why this exception is being generated intermittently.
![logo design studio pro the underlying connection was closed an unexpected error occurred on a send logo design studio pro the underlying connection was closed an unexpected error occurred on a send](https://visme.co/blog/wp-content/uploads/2017/08/40-Brilliant-Geometric-Patterns-The-Psychology-of-Shapes.jpg)
#LOGO DESIGN STUDIO PRO THE UNDERLYING CONNECTION WAS CLOSED AN UNEXPECTED ERROR OCCURRED ON A SEND PATCH#
Having searched the internet it seems to be a common problem, that may possibly be fixed by removing keepalives - however, it also seems this is not an option when using NTLM authentication.īefore I start hacking code and implementing dodgy work arounds, I was hoping there was a patch for the 1.1 framework that resolves the issue. I'm fairly certain its not a hardware fault as only this particular application (which is the only application using web services) is having problems. Occasionally though, the exception The underlying connection was closed: An unexpected error occurred on a send. Requests are authenticated using NTLM (Negotiate) and respond fairly quickly (less than a second).
#LOGO DESIGN STUDIO PRO THE UNDERLYING CONNECTION WAS CLOSED AN UNEXPECTED ERROR OCCURRED ON A SEND WINDOWS#
The setup is fairly simple, the client is a windows service and it makes a number of requests to a web service throughout the day. I've been seeing this error intermittently on our Windows 2003 servers while running web services under the 1.1 framework.