Under this folder - C:\Inetpub\wwwroot  is the aspnet_client folder - and the way we create usually DotNetNuke sites, doesn't put the aspnet_client folder in it, so you need to make sure on your installation you have this folder. When I'm doing packaged build for people, I usually add this to the folder, esppecially when you use the *create the folder, add the files and point to that folder in IIS* doesn't automatically add it, well it doesn't for my server, and perhaps others are different.

If you are running IIS on XPPro you should be able to always find it there and add to your working folder.

I believe this is a problem for alot of people who aren't aware that this is a necessary folder.

Yes DNN will work, but in one instance, there was an upgrade to the aspnet_client/systemweb/1_1_4322 folder - and this file - WebUIValidation.js was set as read only.. Now this might not mean alot, but it caused one of my previous trouble free sites, which has a complex custom module developed, and it when people tried to log into the site - the windows login window popped up and of course, you can imagine it was a nightmare to work out why this had occured.  

This was back in 2004 in the DNN 2.1.2 days, and nothing had changed on the server EXCEPT that update and who knows why, but the file being set with different permissions to previously caused this issue.

Then when migrating my sites physically from a Win2k machine to a Win2k3 machine, also cause some problems with errors and we had to replace the aspnet_client folder on all the sites.

This might give you an insight to something that is not a DNN issue, but it's lack of presence causes one!

Nina Meiers