Very funny, I can take WAMP server and install it plus install Drupal in under 10 minutes. I've been fighting with this DNN6 piece of crap for 3 hours and still can't even get past numerous problems.

All the docs I've read and the video I viewed says to install it in a directory off the webroot. I want it in the webroot, what's the big deal?

It won't connect to my DB during one attempt, the next attempt I get this error:

The current identity (IIS APPPOOL\Default Web Site) does not have write access to 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files'.

I just don't get it why there are so many problems installing this thing. Why anyone would even want to go through these headaches is beyond me. Why doesn't someone just create a simple installer for it?

There is a simple installer -  http://www.microsoft.com/web/gallery/install.aspx?appid=dotnetnuke_iis  

The windows platform installer does EVERYTHING you need to install dnn on a windows computer including downloading and installing  ms sql 2008 express if needed -- basically hit INSTALL - and its all done in about 10 minutes (download times may vary)

The error you are reporting is related to how you have setup your application pool - the USER that you set as the OWNER of your application pool - needs to have read write permission to the asp.net temp folder - that's what the message is saying.

If you are doing an install on win 7 you should leave the AppPoolUser as the application pool owner - since it automatically gets granted access to the asp.net temp folders . . . then just grant AppPoolUser read write permissions to you root.

If you really want to set up your OWN application pool user then simply go to the folder reported in the error and grant your user full permissions - C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files
This has nothing to do with DNN - and would be the same error regardless of whatever asp.net application you tried to run on the website you are trying to configure.

Westa

WIth regard to the FOLDER you put dnn in - i put dnn in a folder where ever I like on the system ...  what you should NOT do however is put dnn in a sub folder of an existing iis web application - this is what causes problems - basically where web application is best defined as a web site that has a web.config file in its root folder.   If you put dnn in a sub folder of such a site - you potentially get into all sorts of asp.net inheritance issues.

I create a folder in the drive root - c:\dnnsites\  and the each site is a sub folder below that - c:\dnnsites\wwwsomesitecom\
Then open IIS - create a web site - and set my folder as the physical path - nothing more to it.

I eventually got it done using the installer but after I'd gone through numerous headaches with SQL Server and IIS issues. This is entirely too difficult for a "free" product.

But I guess that's what Microsoft zealots deserve.

I also don't like that it takes up to 3 hrs just for any posts on this forum to even show up. What if someone that knows the answer to my question is online at the same time I post the question?

This forum is bogus.