The problem seems to be the virtual software EasyCGI is using. I'm not very happy with EasyCGI right now:

1. I get kicked off their shared server, due my DNN site's CPU usage. Their support guy calls me up having no idea what DNN is. He just said you can't run that site anymore until I fix it. How am I supposed to fix a DNN site on a shared server I don't know. It takes me 4 hours to upload a DNN install. I guess I need business class broadband.

2. I prepay for a virtual hosting account, thinking this would be less maintenance than fully dedicated. I then suddenly cannot login to the server anymore and it takes 2 days to get access back.

3. I then find that the app pool crashes in .NET 2.0 after spending 2 weeks setting everything up. I figured the top $99/m hosting package could at least run ONE DNN site, but no! I also thought that possibly I'd get priority support if I paid for a larger package and prepaid, and that is also false.

So, after all this, I'm back to my trusty dedicated server. I just decided to upgrade to a new server at ServerBeach.

I was only trying to make my life simpler by setting up clients on shared hosting, but now I realize (for DNN sites) that if something goes wrong, you cannot even attempt to fix it. On most shared hosting you cannot even restore/backup the database.

So after a month in limbo, my final solution is to use dedicated hosting for DNN sites. None of this shared or fake virtual hosting.

---

Jason Honingford - Web & Software Developer
www.PortVista.com