The best way to do this is to use a keep alive service such as host-tracker.com or pingdom.com which will allow you to have regular requests to the site which will prevent ASP.NET from shutting down the worker process which is what causes the delay.

If you have full access to the server you can modify the setting for shutdown after _ minutes of inactivity.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Hi Rae,

Opem IIS and expand the server name. It should show multiple folders, one which is called Application Pools. If you haven't setup a custom application pool for your site it will be the default pool you need to access. Right click on the application pool icon and go to the performance tab. The first item should say "Shutdwon worker process after _ minutes of inactivity". You can eitherc hange this number or uncheck the box. Be warned, by making this number too high or unchecking the box your server will use more memory for the sites. This is fine if you have only a few sites on the server or lots of memory. I would suggest you also create a seperate application pool for each DNN site as it will give better overall performance.

Good Luck,

Stephen Durant