Yes I have questions. If PlanA is possible, that I can have one DNN site for 3 unique portal domain names, my questions are:

1. How do I develop this on my local host since I only have one unique domain name there?
2. Could you give me a bit of an outline on how to proceed within DNN?
3. Is a GoDaddy URL alias sufficient to map a 2nd and 3rd unique domain to the site hosting by the first domain? Iow, do I merely alias www.portaltwo.com to www.portalone.com?

The benefits of GoDaddy shared hosting are lots of disk space and transfer bandwidth for very cheap and resonable performance. On the other hand their support is not very good but I could easily see that elsewhere as well. I have tried putting a single portal at GoDaddy without success so far by uploading my local portal files with a new web.config file. Installation starts but then fails with an unhandled exception after a complaint that portal 0 already exists but how else would one upload a localhost portal to put it into production?

Do you have a hosting service to recommend that better supports DNN as well as being inexpensive?

Thanks, Dave

1) I guess I want a copy on my local host so I can debug any changes to my portals and then upload the new files to the website rather than update the live production site. Is this not normal or proper procedure for DNN or most any site maintenance?

2) I installed the lastest version 4.3.5 on my local machine and got a simple local site working. Weird that isntall had a lot of version 3 upgrade messages however. Is that normal?

3) You uploaded a copy of your local version? hope not... you should create teh db blank then copy the files from dotnetnuke, not your local site. that error is teh first time the db is hit. so prolly a db related problem. Since you have already run the site locally, I assume you have teh connection string correct.

I then FTP'd the files from c:\inetpup\wwwroot\portalone to my GoDaddy root dir at d:\myuserid hoping to create a portal site in the GoDaddy root. Following some instructions on how to do this, I also uploaded a web.config with the proper connection strings and objectQualifier prefix and then hit my site which did an install but failed in a couple aspects even though in the end it said installation complete. I could see where the database was created just fine and had lots of tables, views and SPs that had my DNN prefix. The failures were 1) a complaint about portal 0 already existing during install which I hoped was not fatal and was due to my uploading from my local machine where I had defined a portal 0 and 2) an unhandled exception as mentioned below after I hit the portal access link shown after the installation complete message. Seems like DNN could improve exception handling behaviour during this initial install phase.

Will also look around for GoDaddy alternatives as I'm not happy with their attitude or support capability. Especially their attitude.

Thanks, Dave

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]

   DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +125

   DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +83

   DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +5768

   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64