NS_ERROR_NET_RESET: ColdFusion 10 and the continuing saga
Chad Stinner
Dan Wilson
--
Upcoming events: http://www.meetup.com/Triangle-Area-ColdFusion-Users-Group/
Follow us on Twitter: @tacfug
---
You received this message because you are subscribed to the Google Groups "TACFUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tacfug+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Chad Stinner
Dan Wilson
One of the steps starting in Update 5, (I think, but Charlie Arehart will soon jump in and clarify, I hope) is the web server connector needs to be dropped and rebuilt using the web server connector tool. Have you already done this?
DW
Chad Stinner wrote:
It's ColdFusion 10. It's installed on Windows 2008 Server (fully
patched), IIS 7.5 and ColdFusion is fully patched as well. My
understanding is he also followed Adobe's guide to locking down the CF
10 server.
So far what I've found is NS_ERROR_NET_RESET is sent by IIS.
It is triggered when the errorhandler.cfm attempts to display HTML. If
I redirect off this page it works. The .cfm page is fully processed
but when the html is passed back this error hops in stopping everything .
On Thu, Sep 12, 2013 at 9:09 AM, Dan Wilson <sipa...@gmail.com
<mailto:sipa...@gmail.com>> wrote:
Which version of ColdFusion is it?
DW
Chad Stinner <mailto:chads...@gmail.com>
Thursday, September 12, 2013 9:03 AM
Greetings Tacfuger's,
Has anyone ever encountered "NS_ERROR_NET_RESET" errors with
ColdFusion and IIS 7.5? This error would not display on a page,
but be sent from the web server. The resulting displayed error
would be "Connection Reset".
Our setup is simple.
IIS 7.5: Each site is configured to send 404 errors to
/errorhandler.cfm
When links like http://www.sitename. com/bob are entered, IIS does
indeed send it to errorhandler.cfm. errorhandler.cfm parses the
cgi and if a match is found it a redirect occurs. This part
works. If NO redirect is found, what's supposed to happen is HTML
is displayed.
Instead the webserver is sending a NS_ERROR_NET_RESET error AFTER
the html is rendered that makes the browser show "Connection Reset".
At this point, I'm am quite confident the individual who
installed ColdFusion did so in a very odd manner so I wouldn't be
surprised if that is the cause. However, I wanted to see if
anyone else had encountered this as Adobe Forums have nothing
about this.
Chad.
--
Upcoming events:< BR> http://www.meetup.com/Triangle-Area-ColdFusion-Users-Group/
Follow us on Twitter: @tacfug
---
You received this message because you are subscribed to the
Google Groups "TACFUG" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to tacfug+un...@googlegroups.com
<mailto:tacfug+un...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
--
Upcoming events:
http://www.meetup.com/Triangle-Area-ColdFusion-Users-Group/
Follow us on Twitter: @tacfug
---
You received this message because you are subscribed to the Google
&nb sp; Groups "TACFUG" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to tacfug+un...@googlegroups.com
<mailto:tacfug%2Bunsu...@googlegroups.com>.
Chad Stinner
Charlie Arehart
Hey guys, here I am. :-) So Chad, I think by “according to him”, you mean your guy doing the updates.
So it’s not so much that you need to do that web server connector rebuild on EVERY CF10 update, but that the Adobe technote for each will tell you if you need to either rebuild or update the web server connector after applying that update, and you’ve had to do it after about 4 of them.
Sadly, many people never notice that, and don’t do it. As such, the update is therefore incomplete and some improvement may not yet be fully implemented. Indeed, people often complain that “CF 10 is broken”, but it’s just that the person doing the update failed to read the technote which said they needed to update or rebuild the connector. :-(
And Chad, CF10 update 11 specifically added a fix related to CF pages serving as the 404 handler for IIS, but you do need to at least update the connector (or rebuild it if you never have for prior CF10 updates).
If you’re saying that your technician feels he has updated the connector appropriately, you can confirm this yourself (and for him). Look at the [cf10]\config\wsconfig folder, and in EACH numbered folder under that, and make sure that the isap_redirect.dll is dated at least May of this year. If it’s from last year, he has NOT rebuilt it and needs to.
If you have only one instance of CF, it’s just about opening the CF web server configuration tool, and “removing” and re-“add”ing the sites. If you have multiple instances, you now can’t add/remove sites for that instance in the “main” web server config tool. It has no value in the dropdown for instances. Instead, you have to open the wsconfig.exe inside each instance’s folders, at [cf10]\[instance]\runtime\bin.
And don’t forget to right-click and use “run as administrator” when running the tool, whether from Windows Explorer pointing to the wsconfig.exe or from the Windows Start menu pointing at the link for the tool.
Let us know what you find. If indeed, the connector is updated, then you may have some other issue. You mentioned that the person doing things “in a very odd manner”. There can be thins people do that cause problems. It can sometimes be a challenge trying to sort that out. Sometimes, people have punted and reinstalled IIS (not too painful if you don’t have a lot of sites, or as long as you know how to export and reuse site configurations) and then rebuilt the CF web server connector (which may be a single-click operation).
Hope that’s helpful.
/charlie
Chad Stinner
--
Charlie Arehart
Glad to help. And I’ve finally turned that into a blog entry, with more detail and organization:
CF911: Why you MUST update the web server connector for #ColdFusion 10, and may have missed it
http://www.carehart.org/blog/client/index.cfm/2013/9/13/why_you_must_update_cf10_webserver_connector
/charlie
From: tac...@googlegroups.com [mailto:tac...@googlegroups.com] On Behalf Of Chad Stinner
Sent: Friday, September 13, 2013 12:06 AM
To: tac...@googlegroups.com
Subject: Re: [tacfug] NS_ERROR_NET_RESET: ColdFusion 10 and the continuing saga
Thanks Charlie. I'll pass this on to him and see what happens. Thanks for the support on this.
On Thu, Sep 12, 2013 at 11:55 PM, Charlie Arehart <charli...@carehart.org> wrote:
Hey guys, here I am. :-) So Chad, I think by “according to him”, you mean your guy doing the updates.
So it’s not so much that you need to do that web server connector rebuild on EVERY CF10 update, but that the Adobe technote for each will tell you if you need to either rebuild or update the web server connector after applying that update, and you’ve had to do it after about 4 of them.
<snip>
Chad Stinner
--
Chad Stinner
Chad.
Charlie Arehart
Chad, you say you can’t “reproduce this issue with ColdFusion Standard on any other server I have access to”.
So are you saying that the one on which you’re having trouble is CF Enterprise? And more specifically, is this an issue with a site that has been connected to a specific instance (since creating new instances is an option in CF enterprise)? If so, are you sure you rebuilt the connector for that instance? It is something that must be done per instance.
As for your observation of adding the cfheader as a fix, have you looked at the response headers from the requests in question (with and without that cfheader) to see how they differ, such as with a tool like Firebug, Fiddler, Charles, or Chrome’s Developer Tools?
/charlie
From: tac...@googlegroups.com [mailto:tac...@googlegroups.com] On Behalf Of Chad Stinner
Sent: Tuesday, September 24, 2013 1:22 PM
To: tac...@googlegroups.com
Subject: Re: [tacfug] NS_ERROR_NET_RESET: ColdFusion 10 and the continuing saga
I wanted to update everyone on the progress.
At this point, I was able to convince our sysadmin to uninstall IIS 7.5 and ColdFusion 10 and install from scratch. Upon doing that, and patching coldfusion/IIS but doing nothing else... the same issue occurs. I am unable to reproduce this issue with ColdFusion Standard on any other server I have access to.