Hi,
   I got a new hard drive with more gig. 
   I have a DNN environment that is already good to go. 

    Does anyone know what is making the Installation wizard come up even though I can right click on the default.aspx page to call up my dnn installation ?

     At first, when I did http://localhost/mydnn," target="_blank" rel="nofollow">http://localhost/mydnn," target="_blank" rel="nofollow">http://localhost/mydnn," target="_blank" rel="nofollow">http://localhost/mydnn, I go an error page saying that I needed to check the permissions of my dnn folder. I did that and added ASPNET and gave it all the permissions. 
    When I added ASPNET user, and then right clicked on the default.aspx inside VS2008, I got the 
home dnn page, and then the login page but could not log in. Somehow, the machinekey changed. 
    I went into the web.config and changed it back and I could login. 
 
  Now, when I do a http://localhost/mydnn," target="_blank" rel="nofollow">http://localhost/mydnn," target="_blank" rel="nofollow">http://localhost/mydnn," target="_blank" rel="nofollow">http://localhost/mydnn, the Installation wizard comes up.
  This is the message on the Installation wizard ... 
 The Auto option has been disabled as the DotNetNuke Application cannot connect to a valid SQL Server database. You can continue to use either of the other two Wizard options and configure the Database settings at the appropriate Wizard step.  

 I dont need the installation wizard, my DNN installation is already working. I just want my   http://localhost/mydnn   call up the home page ? 

If you are using Window 7, you might want to take a look at the tutorial released today as part of Issue 51.

You might also look inside of your web.config and double check that the configuration strings are ok.

Just to add a bit more, the problem is not an issue with the installer not being able to find a SQL server.  The problem is that something goes wrong when DotNetNuke starts, it decides that it isn't installed, and then it runs the installer.

This could be related to the SQL server, too.  This is why I suggested that you look at the connection strings.

  Thanks for your reply,
 
  I am using xp pro.
 
      I think the error message may have strayed us away from the point.

      The connection strings MUST be ok because I can login in when I right click on the default.aspx inside vs2008 and everything comes up ok.  But when I try to access it using the localhost mydnn url, I wants to install.

      I think the problem lies in IIS.
      When you install DNN , does it update something in the IIS ?
      Is the IIS "ONLY" reading from the web.config ?
      It is not seeing something that says it is already installed ?

 

No, installing DotNetNuke shouldn't change IIS.

If DotNetNuke runs the installer, that implies that IIS is working correctly.

I'm out of ideas, too ... 

I came across this error in Windows 7 and it was related to the connection string.

I would check the web.config file and see what it states for the connection string and that it has the correct settings for the SQL database

Sorry, I responded to this a few days ago. Guess I did not check to make sure the post took.
 
  Because of my Disk upgrade, I needed to add the ASPNET user to my database again. This is because I had to reinstall MSSQL and restore the database. The user probably fell out at some point. I just had to assign ASPNET USER to own the proper schema which was db_owner.
 
   In the post I thought I sent, I thanked you guys for the connection string clue,
   Thanks again.

   

ok great thanks for the info,