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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade from 4.7 to 5.6upgrade from 4.7 to 5.6
Previous
 
Next
New Post
1/6/2011 9:13 PM
 
I have created a staging area, backed everything up and am workijng strictly in a development invironment.

I copied workin dnn directory from production, set it up on stage and can access fine.

I copied the dB (sql server 2000) and am able to access it.

I am runung dotnet 4

This is the result of mu upgrade:


Upgrading DotNetNuke

Current Assembly Version: 05.06.00

Current Database Version: 04.07.00



Upgrade Status Report

00:00:00.031 - Upgrading to Version: 05.06.00
00:00:00.062 -   Executing Script: 04.08.00.SqlDataProvider Success
00:00:00.203 -   Executing Script: 04.08.01.SqlDataProvider Success
00:00:00.359 -   Executing Script: 04.08.02.SqlDataProvider Success
00:00:00.421 -   Executing Script: 04.09.00.SqlDataProvider Success
00:00:00.812 -   Executing Script: 04.09.01.SqlDataProvider Success
00:00:03.203 -   Executing Script: 05.00.00.SqlDataProvider Error! (see 05.00.00.log.resources for more information)
00:00:05.640 -   Executing Script: 05.00.01.SqlDataProvider Success
00: -   Executing Script: 05.01.00.SqlDataProvider Success
00:00:09.312 -   Executing Script: 05.01.01.SqlDataProvider Success
00:00:09.453 -   Executing Script: 05.01.02.SqlDataProvider Success
00:00:09.468 -   Executing Script: 05.01.03.SqlDataProvider Success
00:00:09.531 -   Executing Script: 05.01.04.SqlDataProvider Success
00:00:09.562 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log.resources for more information)
00:00:10.156 -   Executing Script: 05.02.01.SqlDataProvider Error! (see 05.02.01.log.resources for more information)
00:00:10.281 -   Executing Script: 05.02.02.SqlDataProvider Error! (see 05.02.02.log.resources for more information)
00:00:10.328 -   Executing Script: 05.02.03.SqlDataProvider Success
00:00:10.359 -   Executing Script: 05.03.00.SqlDataProvider Error! (see 05.03.00.log.resources for more information)
00:00:10.937 -   Executing Script: 05.03.01.SqlDataProvider Success
00:00:10.968 -   Executing Script: 05.04.00.SqlDataProvider Error! (see 05.04.00.log.resources for more information)
00:00:11.437 -   Executing Script: 05.04.01.SqlDataProvider Success
00:00:11.484 -   Executing Script: 05.04.02.SqlDataProvider Success
00:00:11.531 -   Executing Script: 05.04.03.SqlDataProvider Success
00:00:11.562 -   Executing Script: 05.04.04.SqlDataProvider Success
00:00:11.578 -   Executing Script: 05.05.00.SqlDataProvider Error! (see 05.05.00.log.resources for more information)
00:00:13.187 -   Executing Script: 05.05.01.SqlDataProvider Success
00:00:13.234 -   Executing Script: 05.06.00.SqlDataProvider Error! (see 05.06.00.log.resources for more information)
00:00:13.859 -   Executing Application Upgrades: 04.08.00 Success
00:00:13.859 -   Executing Application Upgrades: 04.08.01 Success
00:00:13.859 -   Executing Application Upgrades: 04.08.02 Success
00:00:13.859 -   Executing Application Upgrades: 04.09.00 Success
00:00:13.859 -   Executing Application Upgrades: 04.09.01 Success
00:00:13.859 -   Executing Application Upgrades: 05.00.00 Error!
00:00:13.968 -   Executing Application Upgrades: 05.00.01 Success
00:00:14.015 -   Executing Application Upgrades: 05.01.00 Error!
00:00:14.125 -   Executing Application Upgrades: 05.01.01 Success
00:00:14.203 -   Executing Application Upgrades: 05.01.02 Success
00:00:14.203 -   Executing Application Upgrades: 05.01.03 Success
00:00:15.078 -   Executing Application Upgrades: 05.01.04 Success
00:00:15.078 -   Executing Application Upgrades: 05.02.00 Error!
00:00:17.390 -   Executing Application Upgrades: 05.02.01 Error!
00:00:17.390 -   Executing Application Upgrades: 05.02.02 Success
00:00:17.390 -   Executing Application Upgrades: 05.02.03 Success
00:00:17.390 -   Executing Application Upgrades: 05.03.00 Error!
00:00:19.625 -   Executing Application Upgrades: 05.03.01 Success
00:00:19.625 -   Executing Application Upgrades: 05.04.00 Error!
00:00:21.015 -   Executing Application Upgrades: 05.04.01 Success
00:00:21.015 -   Executing Application Upgrades: 05.04.02 Success
00:00:21.015 -   Executing Application Upgrades: 05.04.03 Error!
00:00:21.015 -   Executing Application Upgrades: 05.04.04 Success
00:00:21.015 -   Executing Application Upgrades: 05.05.00 Error!
00:00:21.171 -   Executing Application Upgrades: 05.05.01 Success
00:00:21.171 -   Executing Application Upgrades: 05.06.00 Error!
00:00:21.593 -   Cleaning Up Files: 04.08.00 Success
00:00:21.593 -   Cleaning Up Files: 04.08.01 Success
00:00:21.593 -   Cleaning Up Files: 04.08.02 Error!
00:00:21.593 -   Cleaning Up Files: 04.09.00 Error!
00:00:21.609 -   Cleaning Up Files: 04.09.01 Success
00:00:21.609 -   Cleaning Up Files: 05.00.00 Error!
00:00:21.718 -   Cleaning Up Files: 05.00.01 Success
00:00:21.718 -   Cleaning Up Files: 05.01.00 Success
00:00:21.812 -   Cleaning Up Files: 05.01.01 Success
00:00:21.812 -   Cleaning Up Files: 05.01.02 Success
00:00:21.812 -   Cleaning Up Files: 05.01.03 Success
00:00:21.812 -   Cleaning Up Files: 05.01.04 Success
00:00:21.812 -   Cleaning Up Files: 05.02.00 Success
00:00:21.812 -   Cleaning Up Files: 05.02.01 Success
00:00:21.812 -   Cleaning Up Files: 05.02.02 Success
00:00:21.812 -   Cleaning Up Files: 05.02.03 Success
00:00:21.812 -   Cleaning Up Files: 05.03.00 Success
00:00:21.812 -   Cleaning Up Files: 05.03.01 Success
00:00:21.812 -   Cleaning Up Files: 05.04.00 Success
00:00:21.812 -   Cleaning Up Files: 05.04.01 Success
00:00:21.812 -   Cleaning Up Files: 05.04.02 Success
00:00:21.812 -   Cleaning Up Files: 05.04.03 Success
00:00:21.812 -   Cleaning Up Files: 05.04.04 Success
00:00:21.812 -   Cleaning Up Files: 05.05.00 Success
00:00:21.812 -   Cleaning Up Files: 05.05.01 Success
00:00:21.812 -   Cleaning Up Files: 05.06.00 Error!
00:00:21.812 -   Updating Config Files: 04.08.00 Success
00:00:21.812 -   Updating Config Files: 04.08.01 Success
00:00:21.812 -   Updating Config Files: 04.08.02 Success
00:00:21.828 -   Updating Config Files: 04.09.00 Success
00:00:21.828 -   Updating Config Files: 04.09.01 Success
00:00:21.828 -   Updating Config Files: 05.00.00 Success
00:00:21.828 -   Updating Config Files: 05.00.01 Success
00:00:21.828 -   Updating Config Files: 05.01.00 Error!
00:00:21.828 -   Updating Config Files: 05.01.01 Success
00:00:21.828 -   Updating Config Files: 05.01.02 Success
00:00:21.828 -   Updating Config Files: 05.01.03 Success
00:00:21.828 -   Updating Config Files: 05.01.04 Success
00:00:21.828 -   Updating Config Files: 05.02.00 Error!
00:00:21.921 -   Updating Config Files: 05.02.01 Error!
00:00:21.921 -   Updating Config Files: 05.02.02 Success
00:00:21.921 -   Updating Config Files: 05.02.03 Success
00:00:21.921 -   Updating Config Files: 05.03.00 Error!
00:00:21.921 -   Updating Config Files: 05.03.01 Success
00:00:21.921 -   Updating Config Files: 05.04.00 Success
00:00:21.921 -   Updating Config Files: 05.04.01 Success
00:00:21.921 -   Updating Config Files: 05.04.02 Success
00:00:21.921 -   Updating Config Files: 05.04.03 Success
00:00:21.921 -   Updating Config Files: 05.04.04 Success
00:00:21.921 -   Updating Config Files: 05.05.00 Error!
00:00:21.921 -   Updating Config Files: 05.05.01 Success
00:00:21.921 -   Updating Config Files: 05.06.00 Success
00:00:21.937 - Performing General Upgrades




Server Error in '/' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +70 DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, Version dataBaseVersion) +839 DotNetNuke.Services.Install.Install.UpgradeApplication() +949 DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +367 System.Web.UI.Control.OnLoad(EventArgs e) +91 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
 
New Post
1/7/2011 1:13 AM
 
Personally if I were upgrading from 4.7 to 5.6 I would go with this approach

4.7 to 4.9.5
4.9.5 to 5.6.0

You should also check out the Wiki

http://www.dotnetnuke.com/Resources/W...

and perhaps the suggested upgrade path (different than what I suggested)
http://www.dotnetnuke.com/Resources/W...

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
1/7/2011 11:46 AM
 
Thanks for taking a look....

It seems I am having issues because the DB is sql 2000....

What if I:

Install sql express

Import Data from 2000

Do a fresh Install of 5.6

Run the install on localhost
??
 
New Post
1/7/2011 11:58 AM
 
Installing Database - Version 05.00.00...FAILURE 400 - The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist.
 
New Post
1/7/2011 2:21 PM
 
I would recommend doing a backup/restore into SQL express rather than trying to transfer the data over.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade from 4.7 to 5.6upgrade from 4.7 to 5.6


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