3
Vote

IIRF works only when IIS Site logging is enabled

description

This has happened to me of multiple sites: if I disable site logging IIRF starts to fail. 95% of the time I get page not found and every once in a while IIRF will catch a request. I've tested this theory very well and I am positive that this is the case. When this happens IIRF does not log anything, as if requests are not even reaching it. I can give you more details if you tell me what are you looking for.
 
At first I though that the sites in IIS are getting corrupted somehow so I started recreating them. As soon as I did that IIRF would start working again, until I saw a pattern where I would disable site logging and IIRF stops working.

comments

tiggi wrote Jun 30, 2010 at 3:20 PM

Let me know what I can do to help?

Cheeso wrote Jan 11, 2011 at 12:44 AM

I don't know the problem here. It could be that URLs are being satisfied from the cache. I'll research the problem and see what I can do to fix it. In the meantime you have a good workaround: enable IIS Site logging.

davenicoll wrote Feb 16, 2011 at 1:38 PM

Just adding my name to the list - I've got this problem too. Using latest x64 build of IIRF and Windows Server 2003 x64 with IIS6. Enabling logging with default options on sites using the filter worked.

CodeJamo wrote May 17, 2011 at 3:38 PM

Wow! This issue should be escalated & not considered "low" impact. We run ColdFusion on top of IIS & generate our own log files (since IIS6 is only capable of logging "script_name" and not "path_info".) This issue matched the scenario we encountered when loading any resource in SSL mode would return a different random file (js, css, etc) during each load. This was causing many dependent libraries to not load properly. We tested this using 2.1.1.26 and discovered that we had to enable "Site Logging" for each website and then disable "Log Visits" on directories. NOTE: This may be an IIRF issue while in SSL.

Sign in to add a comment or to set email notifications