Thanks Bruce,
I still have errors
I deleted all the 5.02.1 DNN files on the server and my computer, deleted the database and created a new one. Downloaded 5.01.04 unzipped it made corrections in the web.conf and uploaded to the server.
Current Assembly Version: 05.01.04
Current Database Version: 05.00.01
Upgrade Status Report
00:00:00.031 - Upgrading to Version: 05.01.04
00:00:02.328 - Executing Script: 05.01.00.SqlDataProvider
Error! (see 05.01.00.log for more information)
00:00:27.062 - Executing Script: 05.01.01.SqlDataProvider
Success
00:00:30.859 - Executing Script: 05.01.02.SqlDataProvider
Success
00:00:32.093 - Executing Script: 05.01.03.SqlDataProvider
Success
00:00:34.484 - Executing Script: 05.01.04.SqlDataProvider
Success
00:00:40.843 - Executing Application Upgrades: 05.01.00
Success
00:00:49.999 - Executing Application Upgrades: 05.01.01
Success
00:00:49.999 - Executing Application Upgrades: 05.01.02
Success
00:00:49.999 - Executing Application Upgrades: 05.01.03
Success
00:00:51.093 - Executing Application Upgrades: 05.01.04
Success
00:00:51.093 - Cleaning Up Files: 05.01.00
Success
00:00:51.218 - Cleaning Up Files: 05.01.01
Success
00:00:51.218 - Cleaning Up Files: 05.01.02
Success
00:00:51.218 - Cleaning Up Files: 05.01.03
Success
00:00:51.218 - Cleaning Up Files: 05.01.04
Success
00:00:51.218 - Updating Config Files: 05.01.00
Success
00:00:51.234 - Updating Config Files: 05.01.01
Success
00:00:51.234 - Updating Config Files: 05.01.02
Success
00:00:51.234 - Updating Config Files: 05.01.03
Success
00:00:51.234 - Updating Config Files: 05.01.04
Success
00:00:51.234 - Performing General Upgrades
00:00:51.874 - Installing Optional Modules:
00:00:52.046 - Installing Package File HTML_Community_05.01.04_Install:
Success
00:01:09.499 - Installing Optional Skins:
00:01:09.499 - Installing Package File DNN-MinimalExtropySkin_01.00.04_Install:
Success
00:01:12.827 - Installing Optional Containers:
00:01:12.827 - Installing Package File DNN-MinimalExtropyContainer_01.00.04_Install:
Success
00:01:13.952 - Installing Optional Languages:
00:01:13.952 - Installing Optional Providers:
00:01:13.968 - Installing Package File AspNetMembershipProvider_05.01.03_Install:
Success
00:01:14.671 - Installing Package File CorePermissionProvider_05.01.01_Install:
Success
00:01:14.843 - Installing Package File DatabaseLoggingProvider_05.01.01_Install:
Success
00:01:14.999 - Installing Package File DNNMembershipProvider_05.01.03_Install:
Success
00:01:15.202 - Installing Package File DNNMenuNavigationProvider_05.01.00_Install:
Success
00:01:15.687 - Installing Package File DNNTreeNavigationProvider_05.01.00_Install:
Success
00:01:15.858 - Installing Package File FckHtmlEditorProvider_02.00.04_Install:
Success
00:01:41.639 - Installing Package File FileBasedCachingProvider_05.01.03_Install:
Success
00:01:42.186 - Installing Package File SchedulingProvider_05.01.00_Install:
Success
00:01:42.546 - Installing Package File SearchIndexProvider_05.01.00_Install:
Success
00:01:43.546 - Installing Package File SearchProvider_05.01.01_Install:
Success
00:01:43.858 - Installing Package File SolpartMenuNavigationProvider_05.01.00_Install:
Success
00:01:44.358 - Installing Optional AuthSystems:
00:01:44.530 - Installing Package File LiveID_01.00.01_Install:
Success
00:01:45.077 - Installing Package File OpenID_02.00.00_Install:
Success
00:01:45.452 - Installing Optional Packages:
Upgrade Complete
After click here I get this.
DotNetNuke Error
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.
- Return to Site