Also give recreate wsconfig another try. Remove the cf instance from IIS and add the connection again... This helped me in the past with these weird IIS crashes.
Michael 2008/12/2 Gaulin, Mark <[EMAIL PROTECTED]> > Another easy thing to try: Drop and recreate your app pool. It sounds > stupid but we had one server where one app pool wasn't stable but all of > the other servers we had (running the same app) were fine. Recreating > the app pool resolved the issue. > > BTW, you should be seeing failures in your Event Viewer. Check them > out... You might find something useful in there... Even just knowing > when (exactly) the failures are happening can be useful. > > Thanks > Mark > > > >I don't know about MS 2003 too much, but in 2008 the app pools have two > > >related "Rapid-fail protection" settings that we had to tweak: the > >"maximum failures" and "failure interval". It appears that app pools > >can be set up to shut themselves down when IIS sees too many errors > >within a given amount of time. The defaults are 5 errors in 5 minutes, > > >which is not very forgiving. (We were generating http error responses > >on purpose and this triggered a shutdown until we figured out what was > >going on.) > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316105 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
