Gurus,

I got DNN 6.0 running on GoDaddy in a subdirectory. It is not an upgrade. This was a completely need install to GoDaddy. (Please no GD comments, I know too well about the problems hosting.) But I did prevail and all was running fine on my in install for about 2 days. Then this afternoon it stopped.

When I try to launch any page within the site, http://www.neasoccer.com, it hangs for a LONG time then errors with this exception.

 Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Request timed out.]

Things I know:

• No files were FTP'd up so whatever happened it had to have been something changed through the interface. (I was in the process of building the web site's pages when this happened.)
• All the needed file permissions were set because I was working with the site adding pages, images, and such.
• The database is up and my connection string was working. I changed nothing so i assume all my Web.Config connections are still good.
• I did go to GoDaddy IIS 7.0 (ASP.net 4.0) control panel and clicked 'Recycle App Pool'.

My question is this. How do i even start to determine where the problem is?

 

most likely there is an issue with the database, does your hoster provide you with a tool to inspect table sized and modifiy table content?

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Well, it just started working later. I did nothing. As I was looking and looking for possible causes, a friend of mine called me to tell me the site was back up!

It was about 2 or 3 hours before it started working again. From the suggestions made here I assume something must have made the database unavailable for that period of time.

In the interest of helping the community:
* I just looked in the eventlog table. Nothing there other than the installation entries. The last entry was the creation of the admin user for the default website that was installed.
* The PortalAlias table did have my HttpAlias entered before the time of my error. So, i don't think that was the problem.

At any rate, since that time my site is up and running and we have begun building content. Thanks for the suggestions.

Thanks for the suggestions.