Michael,

Thanks, I understand.

Using a real ftp program shows the /PerryM folder but using MS Internet explorer does not show /PerryM.

Thanks again and I'm off to ftp and install; I hope.

 

Perry

---

Perry

Given the problems I had, I think installed and deleted my site, including all files, folders, and SQL database, six or eight times.  I think can safely say I saw the same errors being discussed here. 

I think I can also safely say, that the problem isn't in the site, and if you followed Michaels instructions  (http://www.northernstarsolutions.com/Troubleshooting/GodaddyHosting/tabid/61/Default.aspx), you should be all set. 
As I said, I saw each of the errors.  Every one of them was related to an error the *I* made in the web.config file. (Other then the siteurls.config file that needs to be copied from the 'config' folder to the root). 

Sorry of this is too simplistic, but I want to make sure I state the obvious here. 

In ASP, you can 'comment out' code by enclosing the code in a string of characters:

<!-- This is a comment!  --> 

The stock release.config, that you have to rename to web.config, is a little confusing, as it's set up to use SQL Server Express, not SQL Server.  The stock release.config code is this below in blue.  My comments regarding the code are in red.

    <!-- Connection String for SQL Server 2005 Express -->  This whole line is a comment
This starts the LIVE code -- note that the datasource is SQLExpress!  
  <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2000/2005     Note the beginning comment block '<!--'
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
   -->   Here's where the comment block stops
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->   Another comment line
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>  Again, live SQLExpress code
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    --> The SQL Server code block is commented out

One more interesting note:  I tried changing the default install to use the "Small Business' config - it didn't like that, so I don't recommend changing anything here!
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <!--  Alternative Install Templates (included in package)
    <add key="InstallTemplate" value="Club.install.config" />
    <add key="InstallTemplate" value="Personal.install.config" />
    <add key="InstallTemplate" value="SmallBusiness.install.config" />
    -->

******************
Here's my 'live' connection string section.  If you read my other post, the other problem I had is that I did a copy & paste of the server name from the GoDaddy portal.  It inserted an extra linefeed, that was only visible when I printed the web.config.  On screen it looked fine!

  <connectionStrings>
    <!-- Connection String for SQL Server 2005 Express -->
    <!-- <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />   -->
    <!-- Connection String for SQL Server 2000/2005 -->
    <add name="SiteSqlServer" connectionString="Server=whsql-v06.prod.mesa1.secureserver.net;Database=DB_XXXXX;uid=xxxxxxx;pwd=xxxxxxx;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->
    <!-- <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/> -->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules    -->
    <add key="SiteSqlServer" value="Server=whsql-v06.prod.mesa1.secureserver.net;Database=DB_XXXXX;uid=xxxxxxx;pwd=xxxxxxxx;"/>

So, check the comment blocks, make sure your server, database, user, and PW are defined in BOTH keys.  Double check for those pesky line feeds and comment blocks. 

Follow Michaels page for setting permissions on the folders & setting up the SQL server, let the site create the stuff, and upload. 

It was only after I printed the web.configs from both mine and Michael's setup, that I saw the problem with the connection string! 

I hope this helps!

Steve

Well I’ve abandoned the idea of putting DNN on my “root” GoDaddy account – I spent the entire day messing around with dozens of different ways of doing it with no luck.  Hats off to anyone who can do this.

 

So I created a folder called “dnn” with my GoDaddy Hosting Manager CP and gave it ALL permissions (Read, Write, Web, Browse, and SetRoot).  Copied DNN over and began to install.

 

Made it thru the 4.0.0 install and clicked the link to automatically upgrade to 4.02.

 

Then got the following error message:

 

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:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

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) +3797    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 

 

Anyone know what my next step is?

 

Thanks for any help,

 

Perry

---

Perry