I wrote an article how to install Dotnetnuke 4.x on a Windows 2003 SP 1 domain controller. Here is a "gotcha" I wanted to pass along thanks to Michael J. van Zwieten. Thanks a bunch for passing this along. I updated the article. Here is Michaels comments.
I finally found an article that worked for me…
After many hours of looking for the problem I discovered that when you use the configuration editors for asp.net 2.x they add an attribute to the configuration element of the web.config file.
I removed the Attribute and ran the website once again and much to my surprise the website compiled and ran all the installation scripts.
Here is the link to my original article.
Windows Server MVP – IIS
ASPInsider Member – MCP
Managed Complex Hosting
#1 in Service and Support