Hello here's my scenario: I have installed DNN 4.0.3 (but tryed with 3.2.2 with same results) on a pc with Win XP Pro, IIS 5, MS Sql 2005 Express edition.

I'm new to DNN so just to let you know I have edited in the web.config file the following lines only:

<appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=127.0.0.1,1320;Initial Catalog=dnn;User  ID=testuser;Password=testuser2006" /></appSettings>

and

<connectionStrings>
    <!-- Connection String for SQL Server 2005 Express -->
    <add name="SiteSqlServer" connectionString="Data Source=127.0.0.1,1320;Initial Catalog=dnn;User ID=testuser;Password=testuser2006" providerName="System.Data.SqlClient" />
      </connectionStrings>

The installation went fine: no error. Unfortunately when I login - by doing http://localhost/dnn - with the host or admin accounts, I get all the functionalities except the action, admin, and host menu (the options on the solpart menu horizontal bar). The control panel is there and works fine. I have tryed to fresh install a couple of times - going to version 3.2.2 also - but still get the same results. Any help will be appreciated.

Thanks,

Eugenio

I have a different problem in similar environment on my local machine........XP Pro, DNN 4.0.3, SQL Server 2005 Express.

The only way i can seem to install it is using the VSI template (file system only.....if i create a virtual directory and choose HTTP i get an error for ASP.NET permission which i have set). Anyway installation works fine and i see the portal from my asp.net server URL i.e. http://localhost:xxxx/dnn How can i access the same site using my localhost e.g. http://localhost/dnn Everytime i try to access it through my local host it begins the installation again and gives an error that i can not connect to the database.

The default portal is installed as http://localhost:xxxx/dnn so i tried adding an alias as http://localhost/dnn but still it doesn't make a difference.

There must be something basic i am missing here. The documentation ends when installation is succesfull. But that doesn't mean i'll have to open VWD everytime i want to access the portal.