I've followed all the documentation and read suggestions for help with installing a new domain name as a second parent portal.  And it didn't work.  The domain name is active, it is aggregated throughout the internet and correctly points to my web host account.  I created the portal as a parent portal.  It's basically set up as www.mouthfulofmoonlight.com as the portal that was installed during initial installation.  This resides in the root of my web host account.  I created a directory called "testportal" as the second portal located at www.mouthfulofmoonlight.com/testportal/.  It can be accessed just fine with that url.  I also assigned the portal alias's of www.dnnstyle.com and "dnnstyle.com".  In IIS, I set the path for "dnnstyle.com" to point to the "testportal" directory.  As far as I know, that's it, right?

Also, when first creating the portal, I chose the "dotnetnuke" template, however, there were no files except images transferred over to the "testportal" directory.  I did add the "default.aspx" "default.aspx.vb" and "subhost.aspx" files manually to the directory.  Should there be some other files located there?  Does the parent portal, if in a different location other than "/portals/xx" need to have it's own web.config file?  I set the "custom errors" to "off" so I could see error messages about what was going on, but that did not do anything.  I still get the error message that tells you to turn off the custom errors to see more info.  Crazy stuff, and I am totally confused about all of this.  Should I delete the portal and start over?  Or is there a setting somewhere that I missed?

Thanks for any advice or help,

Rick

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke