The change of the ASP.NET version if I recall correctly causes a quick IIS reset to apply the change.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Hi Mitchell,

  Perhaps it will help if I explain myself better. We have got two portals under a DNN installation  namely www.domainname.com/portal0 and www.domainname.com/portal1 respectively.

We want to point another domain name to the second portal. So instead of going through www.domainname.com/portal1 we'll use the new domain name. We setup a new website under IIS and each time we setup this instance, it affects another application which runs on the same server under IIS. Basically, it keeps asking us for the admin username and password as if we had windows authentication ticked (which we don't).

After much effort of trying to resolve this, we deleted the DNN instance we just installed under IIS and the other application was up and running again and we can't seem to see why this is affecting other application. Bearing in mind that it has a separate app pool.

Any idea?

Thanks