>>On the application pool properties I'd be inclined to use the third option and pick a quiet time for the recycling to occur. The default of recycling every 29 hours is not so good because it will often recycle at busy times.
>
>Good point
>
>>Also, for current purposes. why not set the LogEventOnRecycle to 255 and catch all of the options.....
>
>I am not using that log. I have a custom log. Basically, as I log at the application level, whenever the application ends, it will establish a log. However, I am not sure I can get the reason of the shutdown by using that approach. Is this why you mention this LogEventOnRecycle Event Viewer approach so I could get additional details?

Yes. Since the only recycling option you have set up can't be responsible for the frequent recycling that you are experiencing then I'd suspect a problem such as a memory leak. The IIS log might provide more info on that.

Or an alternative approach which gets some internals from HttRuntime in the Application End:
http://aspalliance.com/902