I downloaded the dnn 5.4.4 community edition and installed it on my laptop which works fine. I copied the same installation files to my live site for installation after updating the correct connection string of live server. When I hit the url it starts normally and installation wizard starts however when I reach "Run Database Installation Scripts" screen it shows the first line "Installing Database - Version 05.00.00..." and then never return back. It continues to show the progress bar (I wait for more than 30 minutes). When I saw the database in the server tables and stored procedures were created. If I hit the url again it shows me the following.

1. Web Server Processing
   
   • When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
   • Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
   • The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.
   
   
   
2. HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )
   
   • The Request URL is parsed based on the "/" character
   • A Domain Name is constructed using each of the relevant parsed URL segments.
     
     Examples:
     
     URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
     URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
     URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
     URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
     URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory
     
     
   • Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.
     
     Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.
     
     Example:
     
     URL: http://localhost/DotNetNuke/default.aspx
     URL: http://MACHINENAME/DotNetNuke/default.aspx
     URL: http://209.32.134.65/DotNetNuke/default.aspx
     PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke
     
     Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above.

Anyone have idea of what is happening?

DotNetNuke added the domain Alias to its database table "PortalAlias" on the install.  So the default should be gone on a live page as http://www.domain.com or on using a virtual directory as http://www.domain.com/virtualdirectory.  Installing with its IP address is not recommenaded!

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN

Sounds to me like it could be a database access rights issue. Make sure that you have set the database to give access rights to the application pool user, if you are using a hosting provider. Are you using a hosting provider, or do you have direct access to the live server?

Also, note that in the config.sys there are two places that the database connection string needs to be put in, one for the legacy modules.

Comment Added by Aarsys:
Please notice the file is named as web.config  and not config.sys !!   The web.config file is a configuration file due to IIS.  The config.sys is used to windows applications.