Upon using the installation wizard on the Run Database Installation Scripts page I am presented with a "Failure installing Database Scripts" problem with the following output:
Installing Database - Version 05.00.00...Success
Upgrading Database to Version 05.00.01...Success
Upgrading Database to Version 05.01.00...Success
Upgrading Database to Version 05.01.01...Success
Upgrading Database to Version 05.01.02...Success
Upgrading Database to Version 05.01.03...Success
Upgrading Database to Version 05.01.04...Success
Upgrading Database to Version 05.02.00...FAILURE ERROR: (see 05.02.00.log for more information)
Now if I try to reconnect to the IP where my DNN is installed I'm presented with the following page:
Domain Name Windows Server 2003 Does Not Exist In The Database
DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:
- 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.
- 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.
I'm running MS Windows Server 2003 Enterprise Editions SP2 on the server w/ my DNN installation and running the same OS on my SQL Server with the following info provided by the ABOUT option in SQL Server 2005 Management studio:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 8.0.6001.18702
Microsoft .NET Framework 2.0.50727.3603
Operating System 5.2.3790
---- the thing is... the PORTALS table doesn't have a PortalAlias field; and when I enter data into the PortalAliases Table with my IP for the DNN installation it says that it doesn't work; I get a red
! and it won't let me save my data in the table.
Help?