tracker issue : CF-3368804

select a category, or use search below
(searches all categories and all time range)

Error 101 (net::ERR_CONNECTION_RESET): The connection was reset

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Aaron Shurmer / Aaron Shurmer (Aaron Shurmer)

Created: 11/20/2012

Components: Web Container (Tomcat)

Versions: 10.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win 2008 Server x64

Vote Count: 4

Duplicate ID:	CF-3488063

Problem Description:
Having recently upgraded to cf10 standard, I've also hit a bit of a wall with what seems to be an iis 7 connector issue. 

I'm running the updater 5, with correctly configured connector for that update, and IIS redirected 404 pages intermittently fail - about a 90% failure rate. failures only occur for remote browsers - probably due to IIS setting for custom error pages or detailed error pages for local browsers.

An example page is

The setup here is IIS sees a 404, and the error page is set in IIS to 'Execure a URL on this site" being a .cfm file in the root dir of the site.

The IIS - > CF redirect works perfectly, I can log CF handling the request, the issue is that 90% of the time the request never makes its way back to the browser - generally receiving 'Error 101 (net::ERR_CONNECTION_RESET): The connection was reset' 

I'm going to guess that this is another as yet unfixed bug in the connector, has anyone else seen such a problem / have any idea how to fix it?

Additional info:
The debug mode on the connector showed nothing exciting - the only error in there seems unrelated time wise but is:
[error] HttpExtensionProc::jk_isapi_plugin.c (2314): failed to init service for request.

I've also tried turning off the buffering in the connector - had no effect.

Steps to Reproduce:
In IIS set error 404 to 'Execure a URL on this site" being a .cfm file in the root dir of the site.
make that file return some data
hit the 404 from a remote browser / machine

Actual Result:
about 90% of the time you will get an:
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset

Expected Result:

Any Workarounds:
front end url redirection so that IIS is purely doing the redirect not the execute fixes the problem - points to the problem being the connectors handling of the execution redirect that IIS is giving it.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3368804

External Customer Info:
External Company:  
External Customer Name: AaronShurmer
External Customer Email:  
External Test Config: My Hardware and Environment details:



404 pages not working is a bit issue
Vote by External U.
17169 | November 20, 2012 04:34:57 PM GMT
This is HUGE issue! A client of mine just upgraded to CF 10 on IIS 7.5 and their intranet has stopped functioning properly due to the 404 issue. Content is getting truncated during AJAX calls and they are unable to load data. Please fix this!
Vote by External U.
17170 | February 12, 2013 01:35:38 PM GMT
This is a problem for us as well.
Vote by External U.
17171 | February 14, 2013 03:32:54 PM GMT
Same config: Win2008 x64, IIS 7.5, CF v10 update 5
Comment by External U.
17163 | February 14, 2013 03:34:23 PM GMT
We are using the 404 mechanism to serve pdf files, this worked until upgrading to cf10. Output is chopped off randomly.
Vote by External U.
17172 | March 06, 2013 07:39:45 AM GMT
Glad I stumbled across this, as I am in the same situation (we use the IIS 404 to CFM file redirect as a very old way of supporting SES-friendly URLS) Once we moved the application to this environment, we started seeing the same issues. At times, the whole page would render, while in others, the connection would abort or (more often) reset. We are running CF 10 Standard Update 8, and this issue exists.
Comment by External U.
17164 | April 11, 2013 04:08:38 PM GMT
To everyone interested in this thread, do note that there was a specific bug fix for IIS 404 custom error handlers, which came out this week in CF10 update 11. For more, see It only mentions it in passing ("8. Web Container/Tomcat - CGI.server_port, IIS custom error handlers"), but it is there. The other bug report here in this system, CF-3488063, has been updated by Adobe to indicate that it's fixed with this update. (I don't know if they just have overlooked this bug report, or if perhaps there is a difference.) But let me offer a word of warning, if anyone may apply the update and say "I still have the issue": please note that you MUST either update or rebuild the web connector for IIS. For more on that, see More specifically, if you look at the coldfusion10\config\wsconfig\[nn\ folder (where nn is a number, of which folders you have more than one), and your isapi_redirect.dll is not dated in May 2013, then you have NOT yet done the needed update and will still seem to have the problem. And be sure to update all of them, if you have more than one such folder under wsconfig. If after doing that, and restarting IIS perhaps, if you are still having the problem, then do report back here confirming that. Perhaps there may be something else to explain it, but we'd want to rule this issue out first.
Comment by External U.
17165 | July 12, 2013 10:01:04 PM GMT
I'm experiencing this EXACT same symptom using both CF 11 and CF 16 on Windows 2012 Server R2. I can surf directly to a URL that is a rather long URL with various parameters, and it works great and fast. But then if I surf to its "shortened" URL like which is a non-existent folder, it creates a 404 error that is handled via IIS's custom 404 error redirect to the same longer URL mentioned above (which is a .cfm page), I get the net::ERR_CONNECTION_RESET error every single time. Strangely it does not happen for all /fastlink pages that I have setup (each with a different link name). I've tried tracing it in the script but it's definitely not a script error ... the script croaks at random different points for no apparent reason. I looked at the Tomcat logs but see no logged information in association with this. Please re-open this bug report.
Comment by External U.
17166 | August 09, 2016 06:21:21 PM GMT
Claire, your issue may be related to the CF/web server connector configuration. I have a couple of things for you to consider which may help. First, can you confirm what the date is for the isapi_redirect.dll file in your coldfusion11\config\wsconfig\xx folder, where xx is a number (and if you have more than one numbered folder, what is the date for each)? If the date for that DLL is less than 2016, then despite your having "applied all the CF updates" (if you think you do), one problem is that you still have an old connector, and you need to update it. To do that involves "reconfiguring the connector", which for most people means running the CF "web server config" tool (the right one for each of 11 and 2016 in your case), and then remove and re-add your current connector. It can be a tricky operation for some, but I can guide you or help you recover from problems if you hit them. (See the consulting page at Second, while you are there in each numbered folder, look especially at the file, and look to see if you have these lines: iis_buffer_enable iis_skip_custom_errors_enable If so, what are their values (true or false)? The latter was introduced late last year as of CF11 update 7. You can read more about it at I'm not saying what the values should be for you, but I am proposing that you may want to read about it, and perhaps try reversing iis_skip_custom_errors_enable to see if it helps (and do confirm that it doesn't hurt anything else). Finally, note that when you change these connector files, you then need to recycle the app pools of the sites that are connected to that connector (for most people, it's easier simply to restart all of IIS) so that IIS loads in those new connector settings. Hope that's helpful. If perhaps you have an issue and write back here and I don't reply, please email me to bring it to my attention at, as I don't always notice the emails Adobe sends when these bugs are updated.
Comment by External U.
17167 | August 09, 2016 07:32:56 PM GMT
I checked the dates on my isapi_redirect.dll files and in all cases they were from 2016. The values in the properties files are: iis_buffer_enable= false iis_skip_custom_errors_enable= true Which are deliberately set this way for various reasons. I've read many of the varius forum posts about this article and it was supposedly fixed in CF10, but I'm not seeing that. To me the problem still exists in both CF11 and CF16. I tried all kinds of things to shake it out and overcome it but it was not possible. In the 404 custom error handler, I ended up having to simply redirect to the full URL equivalent when a surf to /someLinkName occurs. Adobe, please re-open this issue.
Comment by External U.
17168 | August 15, 2016 05:45:56 PM GMT