Open IIS Manager and find the Application Pool being used by your DNN site. If not sure, just expand the Application Pools node and look in each app pool for the one that lists your DNN site. Then right click and open properties for that app pool. On the Recycling tab, unselect all recycle options. On the Performance tab, unselect "Shutdown worker process after being idle..."

Now your light traffic web site will not have to go through the compilation process when a new user comes after 20 min of no activity. That should solve your problem with performance.

If you wish, make a new app pool and call it "AppPoolNoRecycle" and give it the settings above, leaving the default app pool with default settings. Then go the the DNN web site in IIS and change the Application Pool value on the Home Directory tabl to use AppPoolNoRecycle. That way the same web server can have both high traffic apps and low traffic apps.

Now, as far as the install error for the Reports module, I have this exact problem. However, I need a better explanation of how to fix it. Can anyone tell me what the real problem is? The last thing I want to do right now is uninstall/reinstall IIS on my production web server which is hosting about a dozen web sites. I hope someone can tell me what the real problem is so I can fix it without reinstalling IIS. Thanks.

Thank you for replying. Are there some steps I can take to manually install the reports module?

I did set DNN to run in Medium trust before the install. I'd be glad to repeat the steps in full trust to see if that makes a difference. Is there a setting I can change to make DNN repeat the installation?

BTW, I'm not sure which other thread you were referring to because that link doesn't point to a specific thread.