Should we still be using 1.2?

Jun 7, 2010 at 3:20 PM

Hi-

I've recently been having issues on my production server where IIS seems to be getting pummeled with this exception (below). I have looked over these threads to try to be sure it was not already answered. I saw something about 2.0 fixing the IIS metabase. I'm not sure this issue is the same. We've been running 1.2 for quite a while flawlessly. However, the number of sites in IIS has increased and each one uses the re-writer.  First the exception. This will eventually make is to where I need to cycle the web publishing services to get my sites coming back up.

------------
Event Type:    Information
Event Source:    Application Error
Event Category:    (100)
Event ID:    1004
Date:        6/7/2010
Time:        9:40:19 AM

Description:
Reporting queued error: faulting application w3wp.exe, version 6.0.3790.3959, faulting module IsapiRewrite4.dll, version 0.0.0.0, fault address 0x00005123.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6c707041 74616369 206e6f69 6c696146
0010: 20657275 77337720 78652e70 2e362065
0020: 37332e30 332e3039 20393539 49206e69
0030: 69706173 72776552 34657469 6c6c642e
0040: 302e3020 302e302e 20746120 7366666f
0050: 30207465 35303030 333231
---------------

I've read a number of threads about 2.0 fixing the IIS metabase etc., but before I made a dramatic change to my production server, I wanted to ask thoughts on upgrading from 1.2 to 2.0 or 2.1? Has anyone ever seen anything like this?  I'm running ColdFusion on a Windows Server (still 32-bit I'm assuming) and SQL databases. Thanks for any info.

Jason