A client of one of the non-Community Server sites I manage emailed me with a screenshot of a .NET error that occurred when they tried to use a site email service. Salient excerpt runtime error bits below.
Google keywords: “An established connection was aborted by the software in your host machine” and “Unable to write data to the transport connection.”
There were permission changes made on the network recently that caused some of my SQL Server jobs to fail, so perhaps this was causing similar problems in Exchange World. One thing for sure, as a developer, don’t you hate it when something happens outside of your realm of control that causes your app to break? Dang-gummit, eh?
It doesn’t happen often, but Google failed me on this. There were suggestions of investigating Virus filtering and changing enumeration casting which worked for someone (what?), but nothing helpful.
Here is a possible fix to add to the Google Pool. Specify the actual host name in the host property of the smtp network element in the web.config. I had “localhost” specified, which worked for a long time…until it didn’t.
<network host=”mail.somewhere.com” userNameemail@example.com
The application really isn’t called “DAVE BURKE’S SWEET APP.” I just like to say that.
Server Error in ‘/DAVEBURKES_SWEET’ Application.
Exception Details: System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine Stack Trace:
[IOException: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.]
[SmtpException: Failure sending mail.]
+2074 DBVTSWEETAPP.docemail.EmailDoc() +1039