Do not copy the upgrade package files into a temp folder in your web space. Hopefully that approach did not trigger any upgrade changes - from the message you received it appears that the installer protected your site from an incorrect upgrade.

Here's a quick list of the steps I like to follow when upgrading:

1. Download the latest upgrade package zip.
2. "Unblock" the downloaded upgrade package - right click on it's file icon, select properties from the context menu, click on the "Unblock" button.
3. Extract the upgrade package zip folders/files into a temporary folder on your local system. Do not manually extract any .zip files contained within folders of the upgrade package.
4. Create a backup of the existing DNN installation's file system.
5. Create a backup of the existing DNN installation's MS SQL Server database.
6. If your site is public, place a html file named "App_Offline.htm" containing at least 512 characters in the root website folder to temporarily take the site offline to users while performing the next step.
7. Upload via FTP or other access all folders/files from the extracted upgrade package on top of the existing site's folders and files. Content that you have created, modules you have installed, etc. will not be overwritten. When prompted to overwrite an existing folder or file answer OK or YES.
8. Remove or rename the App_Offline.htm file if you placed one in the root website folder.
9. Browse to the website triggering the upgrade wizard which will prompt for host password and take care of everything from that point on. NOTE: If auto-upgrade has been disabled in the AppSettings section of web.config, you will need to browse to "<yourdomain>/Install/Install.aspx?mode=upgrade" to trigger the upgrade.

 

---

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