AFAIK the option impersonate=true means that the asp.net worker process will run in the identity of the logged on (windows)user, so i guess thats the reason you are getting the error.

It's somewhat strange to use that setting in a web hosting environment.. it would mean your visitors would all have to have a valid windows account on the machine the site is running on. Account security should be put in place by running the site in its own pool, and use a dedicated account to run all processes in that pool, that way, the asp.net process can never access anything it is not supposed to access on the server

cheers,

Erik

DNN Blog | Twitter: @erikvb | LinkedIn:

Hi,

I'm running on Server Intellect and I'm getting exactly the same odd behavior. The first time that the DNN v4.3.1 starts or resets (i.e., if I make a change to the web.config or I load a new module) - I get prompted for a windows authentication and it bombs out to an ASP.NET error page. It's actually quite annoying (along with the inability to remember users and the fact that the page background image shows in all of the rich text editor windows), and almost makes me want to go back to v3.2.

I'm using a using my 3.2 installation with the 4.3.1 upgrade package placed over top of it and the web.config that came with the v4.3.1 package - with only the connection strings and the password/machine keys changed.

If someone figures this out, I would really appreciate the assistance.