Hi All.

I don't know what happened but my site is down at all.
It runs on my local Win2003 Server with SQL2005 and worked fine so far.

Two weeks ago i installed the nice Gallery Module from DNNInfo and added some albums with a bunch of pictures in it and all was fine.

Today i added some more pictures and.....boom.

Either i run into a Request timed out, or when i increase the value executiontimeout (e.g. to 3600 !!!) in the httpruntime section of the web.config the site "loads forever" in IE.

I tested it from my notebook in the same LAN, from my workstation in the same LAN and even locally on the server.

I also restarted the whole machine....nothing.

What could take so much time in the first load to make this happen?
What could i do to bring it back up and running?

Thanks in advance for any helpful and quick response!

New Information:

I copied the whole install-folder and the DB to my local notebook. Same behaviour!!!

Another test-web, not dnn, just plain asp does come up. Either on the notebook or on the server.

What the hack is running before showing up default.aspx? This might cause the time out.

The point is, that this module runs now for 3 weeks or so and holds 20 different albums of pictures distributed on several pages, so the module is used 6 or 7 times.

In one of these modules i wanted to add one additional album (to the existing one) and since then.....

I already deleted the uploaded pictures and albums from the DB, and copied the original module files from the zip-file directly into the right folders (all were exactly the same size and date) and started again with no luck.

I'm wondering what is happening prior to show the default.aspx. Any file-check or file-sync? What taks takes such a long time?

I'm now on my notebook with all the files and the DB hoping that this would be faster then over the LAN with a dedicated server.

I've had similar problems, different modules.  No one could give me an answer.

The CMS/.net/iis either is so complicated you don't know where the error could be logged, or there aren't sufficient tools available to track the error down.

I deleted everything including the databases, used a different database name and different directory path for the dnn install.   .Net makes it almost impossible to simply 'delete everything' and start over.

Overall, DNN is extremely fragile in this way.  When it works, it's okay.  When it doesn't you are pretty screwed.  That doesn't take away from it's popularity.  It's more a corrolary to its popularity.