BCRose
 Nuke Master Posts:131

 |
| 01/30/2010 9:53 AM |
|
Is there any special things I need to be aware of when upgrading my DNN version. I want to go from DNN 5.0.1 to the lastest version.
I have been looking for tutorials on this site but have found none that refers to upgrading 5.0.0 to a newer version, just from 4.x versions to 5.x versions. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/30/2010 9:57 AM |
|
First, make good backups. Copy the UPGRADE package over your existing web directory. Browse to the site to kick off the upgrade. If you want a little more control on when the upgrade happens, set autoupgrade to false in web.config. Then, you will have to browise to Install/install.aspx to start the upgrade. This tutorial ought to be close to accurate: How to Upgrade DotNetNuke (Auto Merge Method) (v4.6.2 to v5+) |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/30/2010 1:12 PM |
|
oh boy...This is why I didn't want to upgrade. Do you know what this error means and how to fix it? http://golf.securedata.ca I can't log in since upgrade.... |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/30/2010 1:23 PM |
|
If you did make a good backup, you can always restore the database and web directory. I'd probably do that, and then I would install the backup on a local computer to investigate the upgrade problem.
If you want to try to diagnose the problem first, you'll need to get into the EventLog table in the database. Use SQL Server Management Studio Express or other tools that might be available to you. You'll find a more detailed description of the error message, though I assume it is the login module. Is that what is on that page?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/30/2010 1:32 PM |
|
Yes, there was a log in module and other modules only available once logged in. The main login function (top right) does not work either. |
|
|
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/30/2010 1:51 PM |
|
The event log error is as follows...but it means little to me...It seems to have problems with the HTML/Textwriter module? Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.at DotNetNuke.UI.Modules.ModuleHost.RenderContents(HtmlTextWriter writer)at System.Web.UI.WebControls.WebControl.Render(HtmlTextWriter writer)at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter)at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)at |
|
|
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/30/2010 4:17 PM |
|
Problem solved. I did not make the necessary changes to the web.config file. All is well. People like me should not be editing web.config files |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/30/2010 10:57 PM |
|
Glad you got this fixed.
What changes did you have to make to web.config?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/30/2010 11:12 PM |
|
The upgrade has a new web.config file that has two new providers so I had to use it. I had tried to use my old web.config and that was why the errors occured. I then had to update the database connection string and machine keys and validation keys. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/31/2010 7:07 AM |
|
Did you use the Upgrade package and the auto-merge failed?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/31/2010 10:21 AM |
|
Yes, I used the 5.2.2 Upgrade package and followed the instructions on Lee's video. Failed. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/31/2010 11:57 AM |
|
Did that include manually editing web.config? (Just trying to sort out what might have gone awry.)
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
 Nuke Master Posts:131

 |
| 01/31/2010 12:11 PM |
|
No, I never touched the web.config file while upgrading. The problem occured when running /Install/Install.aspx?mode=Install Nothing happened, browser window just remained blank. But site was corrupted. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 01/31/2010 12:13 PM |
|
That's interesting. I've never encountered problems like this with the autoupgrade process.
You should report this (support.dotnetnuke.com) so that it can be investigated and fixed.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
BCRose
 Nuke Master Posts:131

 |
| 02/03/2010 12:31 AM |
|
Posted By Joseph Craig on 31 Jan 2010 12:13 PM That's interesting. I've never encountered problems like this with the autoupgrade process.
You should report this (support.dotnetnuke.com) so that it can be investigated and fixed.
I am pretty certain it was my fault. I just don't know enough about this yet to know what I did wrong. |
|
|
|
|