I have been using this great product since 2003. These days, installation takes days and days of my time. I need help, here are a few of the problems; 

1. The authentication bug is back, and this time I can't even log into the entire site to change the ribbon-bar setting. Frankly, I like the way the new editor looks, but have to switch back to old school every time.

2. Finally got my site at http://209.200.96.73/  (URL fcchammond.org) running this morning, only to be met with the authentication loop at log in, and when I added this solution:   modules runallmanagedmodulesforallrequests="true" my whole site now gives me an error as you see below. I changed it back, and it still gives me the error.

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

 3. Yesterday,  I consulted support at my host because I could not get an install up and was told the web.config file was bad. Specifically, line 98:   

I doubt this was really the problem but with so many bugs going on I just don't know.

4. IIS and this app are not playing well together. Combined with my terrible web host and the way their system gives me all sorts of permission problems, denies me access to IIS to iron out any potential isses, etc., I have to slog through a couple of days worth of issues. This used to not be the case, until I hit version 7xx.  While I know this is not always a DNN problem, per se, I do think that some notes on the many issue surrounding IIS that I am finding, might be in order.

 Beth Vest

fcchammond.org

based on your problems you main issue is that your server is missing this patch - http://support.microsoft.com/kb/980368 -this is required for sites with extentionless url's (which the advanced url provider uses in DNN). Note: the runAllManagedModulesForAllRequests "fix" is not a real fix, it simply forces all requests through the pipeline and in fact hurts performance. If you have that patch (or are running a more modern version of IIS), you do not need to use runAllManagedModulesForAllRequests.

This will resolve the 404 issues post-install and also any service request failures (which are simply 404's under the cover also).

As to why an install would run again, typically that would indicate that the web application could not connect to the database and as such assumes it's an installation. The other possibility is that the web.config does not contain the right connection details - this could happen if your permissions are invalid e.g. the user that the application pool runs under does not have read, write and modify permissions for web.config

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

no problem - as to the wizard running again this can also happen if there is no connectivity between the webserver and the database server e.g. there is a routing or network problem. Over the years there have been a few people reporting such problems with their hosting provider, but they always turned out to be temporary (and often related to a failing/failed piece of network hardward such as a router/firewall), perhaps that's what you saw. If you don't see it again that would be a confirmation that it was a temporary network issue with the host

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US