IIS 7 and Above
IIS Timeouts in logs error 302 and sc-win32-status 64
Last post Mar 18, 2019 02:07 AM by Jalpa Panchal
Mar 16, 2019 10:00 AM|Tengu|LINK
Since 15 days ago, my site started to experience wierd timeouts. I'm using cloudflare and users get 524 errors. I noticed that it happens once you are loged in and you have login cookie, as soon as I delete login cookie, site works again.
Wierd thing is that we havent changed anything in code for long time. I've checked IIS logs and I found this in logs
2019-03-14 00:00:37 (IP OF SERVER* REMOVED) GET / - 80 - IP OF USER Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/72.0.3626.121+Safari/537.36 https://www.google.com/ 302 0 64 1258895
If you see in last 4 values, it shows 302 error and sc-win32-status=64 time-taken 1258895
Anyone had simillar issue? Its dirving me crazy
Mar 18, 2019 02:07 AM|Jalpa Panchal|LINK
This sc-win32-status 64 error indicate that “The specified network name is no longer available.” After IIS sent final response to the client,it will wait for an ACK message from the client. Sometimes clients will reset the connection instead of sending
the final ACK back to server. This is not a graceful connection close, so IIS logs the “64” code to indicate an interruption.Many clients will reset the connection when they are done with it, to free up the socket instead of leaving it in TIME_WAIT/CLOSE_WAIT.Proxies
may have a tendency to do this more often than individual clients.
And Error 542 indicates that cloudflare made a successful TCP connection to the origin web server,but the origin did not reply with an HTTP response before the connection timed out.
Cause of these errors are:
Long running process on the server,such as slow application or query, for which the server wait before it respond to the request.and overloaded web server.
You could prefer below article: