This is the first time I've actually attempted an upgrade.

What do I do?  I've looked all over and can't find instructions on how to upgrade.

Thanks.

Jeff,

Ok, I just upgraded my site BEFORE reading your post here.  After I posted my request, I found this information in the About --> Documentation --> FAQ about upgrading.  It has different information.

"Is it easy to upgrade?  Yes.  First, backup your database before upgrading to a new version.  Unzip the newer version over the old, and the application will automatically execute the necessary database scripts."

So I simply did that.  I unzipped the files for the 4.5.1 upgrade on my local machine, FTP'd them to the live site and loaded my web site.  The upgrade succeeded except for a Sql provider.

Upgrade Message:

Upgrading DotNetNuke
Current Assembly Version: 04.05.01
Current Database Version: 04.05.00


Upgrade Status Report
00:00:00.015 - Upgrading to Version: 4.5.1
00:00:00.015 -   Executing Script: 04.05.01.SqlDataProvider Error! (see 04.05.01.log for more information)
00:00:00.203 - Performing General Upgrades
00:00:00.296 - Installing Module File HTML_04.05.00_Install:  Success
00:00:00.625 - Installing Module File Links_03.03.07_Install:  Success
Upgrade Complete


Click Here To Access Your Portal

My site is up and running fine, except when I log in as Host and try to access the Host Settings I get an error page.  So essentially I have no access to the Host Settings page.

But other wise the upgrade worked. 

I did not modify the release.config file to be the new web.config file and I didn't do anything with the machine keys either.  I literally just FTP'd the unzipped files to the server and loaded the site and it worked.

If I should be doing more than that, there should be a specific page that outlines the exact upgrade procedure to follow in order to not make a mistake.

Thank you for your response, and I'm glad it worked.  www.kingwilder.com

I've upgraded without changing the web.config before, but the 4.5 to 4.5.1 changed at least the path for the FCKEditor (I think I read that at least...) so I used release.config.  The connection string is critical to change, unless the default connection string worked for you.  The machine keys are used in the password encryption, so those are important as well.  Also, any changes made to web.config for any modules would need to be copied over.  You basically merge the release.config with your web.config to get the new web.config.

Jeff