tracker issue : CF-3850393

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

Custom 404 IIS Pages

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): Christopher Tauer / Christopher Tauer (Chris.Tauer)

Created: 11/11/2014

Components: Installation/Config, Connector

Versions: 11.0

Failure Type: Crash

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Critical / All users will encounter

Locale/System: ALL / Windows 7

Vote Count: 0

Problem Description:  I have ColdFusion 11 Enterprise Update 2 installed on my stage server.  Windows Server 2008 R2 Standard running IIS 7.  I went into IIS for my website and created a custom error page pointed to /404.cfm.  When the error page is being called I keep getting an error in Firefox saying the Connection Was Reset.  At one point, the contents of 404.cfm would load, for a moment, then the connection reset error would show up.  Now, All I get is the connection reset error.  I switched to a 404.htm error page and it loads just fine.  But for some reason, IIS is having a hard time trying load the .cfm file.  We went from CF 9 to CF 11.  In CF 9, the 404.cfm error page worked great. 

Steps to Reproduce:

Create custom error page in IIS 7 and point it to 404.cfm and see if you can view the contents of the page.

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

Watson Bug ID:	3850393

External Customer Info:
External Company:  
External Customer Name: Chris.Tauer
External Customer Email:  
External Test Config: My Hardware and Environment details:

ColdFusion 11 Enterprise Update 2

Windows Server 2008 R2 




I saw some blogs about this issue in CF 10 and it looked like an update was sent out to resolve the issue. We went from CF 9 to CF 11 and I cannot get IIS to show any .cfm error pages. Everything else seems to work fine.
Comment by External U.
10151 | November 11, 2014 07:16:17 PM GMT
@Chris, Thanks for logging this bug. You are right that we have rolled out a fix for this but since it was not reproduced on our side we were waiting for customer response. Now as you are still facing this issue, can you please send us the logs so that we can investigate further. We will be needing these information: 1. Connector logs with debug enabled 2. FREB logs 3. IDNA trace/dump file Our support team will be in touch with you shortly to assist you in taking all these logs.
Comment by Milan C.
10152 | November 12, 2014 02:14:41 AM GMT
@Chris, we have sent you an email. Please respond to the same.
Comment by Anit K.
10153 | November 12, 2014 12:11:38 PM GMT
Waiting for logs / dumps from the customer.
Comment by Immanuel N.
10154 | November 17, 2014 11:20:26 PM GMT
Hi, if you would like to do a screen share or a google hangout I can show you what's happening then I can send you any logs at that point. Let me know if you time to do a google hangout tomorrow.
Comment by External U.
10155 | November 21, 2014 12:52:46 AM GMT
@Chris, We don't need a screen sharing session here. I have sent you an email. Once you respond to the same, we will get in touch with you for the logs.
Comment by Anit K.
10156 | November 21, 2014 10:10:09 AM GMT
Will be closing this bug since a repro case was not available. Will reopen the bug if this issue is reported again.
Comment by Immanuel N.
10157 | December 09, 2014 04:01:06 AM GMT