Hi all,

After running DNN 4 and 5 for years installing DNN7 on a fresh new environment. Win2008R2 + ASP.net 4.0 pipeline + SQL 2008. ASP.net and DBO permissions are set.

The install went ok, no errors during install. Site runs, all pages load ok. However when trying to login, trying to search or try to use retrieve password function a "Collection is read-only" exception is thrown, see below.

I tried to disable friendly urls (had a similar issue in DNN5), but no luck. Also tried without postback, also no luck. Searched the forums, found a similar occurence, however without a solution. Found an article on integrated pipeline mode which can cause this, but disabling prevents DNN7 to load at all. See http://support.microsoft.com/kb/2605401/en-us?sd=rss&spid=14855 

Any idea what to do to get this resolved?

Thanks, Jan

Server Error in '/' Application.

---

Collection is read-only.

Stack Trace: 

[NotSupportedException: Collection is read-only.] System.Collections.Specialized.NameObjectCollectionBase.BaseSet(String name, Object value) +8933626 System.Web.HttpServerVarsCollection.SynchronizeServerVariable(String name, String value) +237 System.Web.Hosting.IIS7WorkerRequest.GetServerVarChanges(HttpContext ctx) +663 System.Web.Hosting.IIS7WorkerRequest.SynchronizeVariables(HttpContext context) +12623479 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +647

The story still goes on. A clean re-install had no effect.

I read that in IIS7.5 some ASP.net permissions had changed. The DNN wiki indicates that the new App-pool virtual user has to be granted modify rights. A link to a DNN-blog article can be found in various places, but it somehow (and sadly) removed from dnn website.
After reading this article I asked my hosting provider to setup ASP.net permissions according this article, which is done by them. However this did not change the error, still getting the "Collection is readonly" exception when trying to login, retrieve passwd, or use search function.

So the question here knows anybody a specific setting in IIS7.5 (or ASP.net 4.0) which can cause this, and which should be modified to get this fixed?