IIS 7 & IIS 8
SMTP server error: 0x800ccc14 with Classic ASP/IIS7
Last post Mar 05, 2013 10:23 AM by Ken Schaefer
Feb 26, 2013 02:29 PM|LINK
In our live environment, we run 4 Windows Server 2008 servers with IIS7 using Classic ASP. Randomly once a week, all of our forms that utilize an email response, break upon submission and show the following error:
"The message could not be sent to the SMTP server. The transport error code was 0x800ccc14. The server response was not available"
Things to note:
-nothing shows up in the event logs
-we used wireshark, the SMTP packets don't get created/leave the server
-to fix the issue, we have to reboot the server (very annoying to reboot 1 server every week, its never the same server)
So my assumption is, its an IIS issue. Anyone have an ideas on how to fix or troubleshoot this issue?
Feb 26, 2013 02:54 PM|LINK
Check the SMTP logs.
Feb 26, 2013 03:19 PM|LINK
The problem is, there is nothing in the IIS Logs regarding this error and nothing in the SMTP logs either since its not reaching our SMTP server, its not even leaving our production server.
Feb 26, 2013 08:27 PM|LINK
So, I came across this blog post: http://www.moushigo.com/index.php/2012/02/22/trivial-smtp-asp-net-winsock-connectivity-issues/
The fix was: Restart the Print Spooler service (wtf? why?). Since we are running Classic ASP, we are using the CDO.Message object to send emails. Is there another object that can be used to send email?
Mar 05, 2013 09:05 AM|LINK
The fix was: Restart the Print Spooler service (wtf? why?)
I'm confused too, Print Spooler service just s just a print server. Normally, it will not affect the setting in SMTP.. Maybe some configs in print spooler service crash down cause this error? It sounds make sense.
Your second question, I think, use CDO.Message is better to use others.
Mar 05, 2013 10:23 AM|LINK
0x800ccc14 = SOCKET_INIT_ERROR
So, I'm guessing that there's two possible causes:
a) the web server is unable to open a TCP connection to the remote SMTP server -or-
b) the webserver has an issue creating a TCP socket even before it tries to connect to the remote SMTP server
Since the issue is fixed by restarting the web server, my guess is that the issue is (b). Since TCP sockets aren't handled by IIS, it's an issue further down in the network stack (somewhere in Windows).
What you may be able to do is enable Winsock Event Tracing:
http://msdn.microsoft.com/en-us/library/windows/desktop/bb892103(v=vs.85).aspx You may need to engage Microsoft PSS to help troubleshoot the logs.