Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade from 5.4.4 to 5.5?Upgrade from 5.4.4 to 5.5?
Previous
 
Next
New Post
9/7/2010 6:06 AM
 
Upgrading the source have the same procedure as for the install.  What package are you using for the upgrade ? 
 
New Post
9/7/2010 7:30 AM
 
Hi Matthias,

I have downloaded the full source package for dnn 5.5.0.
The intention is to do this as a fresh install of 5.5.0 that I will re-apply my custom modules to.
I do need to upgrade the old 5.4.4 database.

I copy the developer.config, rename as web.config and copy the connection strings and machine key from the old 5.4.4 web config.
IIS is re-pointed at the new  /Website subdirectory. I restart IIS and restart SQL Server.
I compile and run the new source project against the old 5.4.4 database with the "/Install/Install.aspx?mode=upgrade" url.
I'm using Windows XP, IIS6 and Visual Studio 2010, SQL Express 2008 and compiling against ASP.NET 3.5.

Is it normal for an upgrade from 5.4.4 to begin at installing 5.0 and continue on.
When I upgraded from 5.4.2 to 5.4.4 the upgrade started at 5.4.2, not 5.0.
It is like the upgrade is performing a full install instead of an upgrade.
I can post some screen shots tomorrow when I get in to work.

Colin


 
New Post
9/7/2010 7:05 PM
 
using the url: http://localhost/DotNetNuke_Community/Install/Install.aspx?mode=upgrade
I get the below dialog. It looks like it is installing, not upgrading ... any idea why?

Installing DotNetNuke

Version: 05.05.00



Installation Status Report

00:00:00.015 - Installing Version: 05.00.00
00:00:00.015 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:06.406 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:07.953 - Installing MemberRole Provider:
00:00:07.953 -   Executing Script: InstallCommon
00:00:09.203 -   Executing Script: InstallMembership
00:00:10.156 -   Executing Script: InstallProfile
00:00:10.297 -   Executing Script: InstallRoles
00:00:10.859 - Upgrading to Version: 05.05.00
00:00:10.922 -   Executing Script: 05.00.01.SqlDataProvider Success
00:00:11.890 -   Executing Script: 05.01.00.SqlDataProvider Error! (see 05.01.00.log.resources for more information)
00:00:14.125 -   Executing Script: 05.01.01.SqlDataProvider Success
00:00:14.640 -   Executing Script: 05.01.02.SqlDataProvider Success
00:00:14.672 -   Executing Script: 05.01.03.SqlDataProvider Success
00:00:14.734 -   Executing Script: 05.01.04.SqlDataProvider Success
00:00:15.047 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log.resources for more information)
00:00:16.937 -   Executing Script: 05.02.01.SqlDataProvider Success
00:00:17.015 -   Executing Script: 05.02.02.SqlDataProvider Success
00:00:17.031 -   Executing Script: 05.02.03.SqlDataProvider Success
00:00:17.281 -   Executing Script: 05.03.00.SqlDataProvider Success
00:00:17.781 -   Executing Script: 05.03.01.SqlDataProvider Success
00:00:17.906 -   Executing Script: 05.04.00.SqlDataProvider Success
00:00:18.218 -   Executing Script: 05.04.01.SqlDataProvider Success
00:00:18.593 -   Executing Script: 05.04.02.SqlDataProvider Success
00:00:18.656 -   Executing Script: 05.04.03.SqlDataProvider Success
00:00:18.703 -   Executing Script: 05.04.04.SqlDataProvider Success
00:00:18.703 -   Executing Script: 05.05.00.SqlDataProvider Error! (see 05.05.00.log.resources for more information)
00:00:19.797 -   Executing Application Upgrades: 05.00.01 Success
00:00:20.187 -   Executing Application Upgrades: 05.01.00 Success
00:00:22.687 -   Executing Application Upgrades: 05.01.01 Success
00:00:22.687 -   Executing Application Upgrades: 05.01.02 Success
00:00:22.687 -   Executing Application Upgrades: 05.01.03 Success
00:00:23.344 -   Executing Application Upgrades: 05.01.04 Success
00:00:23.344 -   Executing Application Upgrades: 05.02.00 Success
00:00:23.453 -   Executing Application Upgrades: 05.02.01 Success
00:00:23.453 -   Executing Application Upgrades: 05.02.02 Success
00:00:23.453 -   Executing Application Upgrades: 05.02.03 Success
00:00:23.453 -   Executing Application Upgrades: 05.03.00 Success
00:00:24.015 -   Executing Application Upgrades: 05.03.01 Success
00:00:24.015 -   Executing Application Upgrades: 05.04.00 Success
00:00:24.390 -   Executing Application Upgrades: 05.04.01 Success
00:00:24.390 -   Executing Application Upgrades: 05.04.02 Success
00:00:24.390 -   Executing Application Upgrades: 05.04.03 Success
00:00:24.406 -   Executing Application Upgrades: 05.04.04 Success
00:00:24.406 -   Executing Application Upgrades: 05.05.00 Success
00:00:24.765 -   Cleaning Up Files: 05.00.01 Success
00:00:24.765 -   Cleaning Up Files: 05.01.00 Success
00:00:24.765 -   Cleaning Up Files: 05.01.01 Success
00:00:24.765 -   Cleaning Up Files: 05.01.02 Success
00:00:24.765 -   Cleaning Up Files: 05.01.03 Success
00:00:24.765 -   Cleaning Up Files: 05.01.04 Success
00:00:24.765 -   Cleaning Up Files: 05.02.00 Success
00:00:24.765 -   Cleaning Up Files: 05.02.01 Success
00:00:24.765 -   Cleaning Up Files: 05.02.02 Success
00:00:24.765 -   Cleaning Up Files: 05.02.03 Success
00:00:24.765 -   Cleaning Up Files: 05.03.00 Success
00:00:24.765 -   Cleaning Up Files: 05.03.01 Success
00:00:24.765 -   Cleaning Up Files: 05.04.00 Success
00:00:24.765 -   Cleaning Up Files: 05.04.01 Success
00:00:24.765 -   Cleaning Up Files: 05.04.02 Success
00:00:24.765 -   Cleaning Up Files: 05.04.03 Success
00:00:24.765 -   Cleaning Up Files: 05.04.04 Success
00:00:24.765 -   Cleaning Up Files: 05.05.00 Success
00:00:24.765 -   Updating Config Files: 05.00.01 Success
00:00:24.765 -   Updating Config Files: 05.01.00 Success
00:00:24.765 -   Updating Config Files: 05.01.01 Success
00:00:24.765 -   Updating Config Files: 05.01.02 Success
00:00:24.765 -   Updating Config Files: 05.01.03 Success
00:00:24.765 -   Updating Config Files: 05.01.04 Success
00:00:24.765 -   Updating Config Files: 05.02.00 Success
00:00:24.765 -   Updating Config Files: 05.02.01 Success
00:00:24.765 -   Updating Config Files: 05.02.02 Success
00:00:24.765 -   Updating Config Files: 05.02.03 Success
00:00:24.765 -   Updating Config Files: 05.03.00 Success
00:00:24.765 -   Updating Config Files: 05.03.01 Success
00:00:24.765 -   Updating Config Files: 05.04.00 Success
00:00:24.765 -   Updating Config Files: 05.04.01 Success
00:00:24.765 -   Updating Config Files: 05.04.02 Success
00:00:24.765 -   Updating Config Files: 05.04.03 Success
00:00:24.765 -   Updating Config Files: 05.04.04 Success
00:00:24.765 -   Updating Config Files: 05.05.00 Success
00:00:24.765 - Performing General Upgrades
00:00:24.812 - Loading Host Settings:
00:00:25.062 - Configuring SuperUser:
00:00:25.140 - Synchronizing Host Files:
00:00:26.562 - Executing Additional Scripts:
00:00:26.578 - Installing Optional Modules:
00:00:26.609 - Installing Optional Skins:
00:00:26.609 - Installing Optional Containers:
00:00:26.609 - Installing Optional Languages:
00:00:26.625 - Installing Optional Providers:
00:00:26.625 - Installing Optional AuthSystems:
00:00:26.625 - Installing Optional Packages:
00:00:26.640 -   Creating Portal: My Website
00:00:26.953 -   Error: A User Already Exists For the Username Specified. Please Register Again Using A Different Username. at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, UserInfo objAdminUser, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal) in D:\InetPub\wwwroot\DotNetNuke_Community_05.05.00_Source\Library\Entities\Portal\PortalController.vb:line 1457 at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, String FirstName, String LastName, String Username, String Password, String Email, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal) in D:\InetPub\wwwroot\DotNetNuke_Community_05.05.00_Source\Library\Entities\Portal\PortalController.vb:line 1251 at DotNetNuke.Services.Upgrade.Upgrade.AddPortal(XmlNode node, Boolean status, Int32 indent) in D:\InetPub\wwwroot\DotNetNuke_Community_05.05.00_Source\Library\Services\Upgrade\Upgrade.vb:line 1814
00:00:26.953 -   Portal failed to install:Error!

Installation Complete



Click Here To Access Your Portal

 
New Post
9/7/2010 11:23 PM
 
It is definitely doing a new install rather than upgrade from DNN 5.04.04, most likely because you did not transfer the objectQualifier value from the existing web.config to the new web.config (which you renamed from development.config). That is one of the reasons that when upgrading you should never manually try modify the new web.config (either included in an install package or renamed from development.config or release.config in a source package). The upgrade process (since version 4.06.02) will automatically modify your existing web.config.

If you look at your database you will most likely find tables of the same name but having different objectQualifier prefixes - for example: dbo.DNN_Modules and dbo.Modules. Because the tables beginning with the prefix "aspnet_" are shared among installs with different objectQualifiers, there will be only one of each of those tables. Which, I believe is the cause of the duplicate username error you also received when the install tried to create the new portal.

If you have backups of the files AND database prior to the upgrade attempt, I would recommend that you restore the backups then repeat the upgrade without modifying or otherwise copying over your existing web.config.

Also, when doing a source upgrade I feel safer first deleting all of the source code folders - BuildScripts, DotNetNuke.Web, Library, Modules, and Tests then copying fresh folders from the extracted source package. That eliminates the possibility that some source files/child folders might have been deleted or their folder structure changed in the new source version. I then copy the contents of the extracted Website folder of the source package (without renaming development.config or release.config to web.config) over the existing Website folder contents then proceed as usual with triggering the upgrade.

Finally, if you have made any changes to the .sln VS solution file - and in particular have changed the IIS website URL - you will have to re do that change in the new solution file before opening the project in VS.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
9/8/2010 2:58 AM
 
Thank you William, it worked a treat.
Lesson learned, trust the system to upgrade the web.config.
Here is what I ended up doing.
  1. Backup everything, database and original source.
  2. Make a fresh 5.05.05 source directory with brand new source code.
  3. Copy in the old web.config. Make sure that Autoupgrade is set to False.
  4. Copy in any Custom Desktop Modules and any installed 3rd party modules (iWeb)
  5. Copy in any custom App_Code files (iWeb)
  6. Copy the /bin DLL's as needed (Telerik.Web.UI.dll versioning error)
  7. Re-point IIS to the new directory structure of the fresh install
  8. Re-Start IIS and re-start SQL.
  9. Load everything up into Visual Studio and run the upgrade from the /install/install.aspx?mode=upgrade url. Wait for DNN to do its thing.
  10. Copy across any skins and containers as required.
Bliss.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade from 5.4.4 to 5.5?Upgrade from 5.4.4 to 5.5?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out