Hello Shadowboxdx

My current version is DNN 4.3.4.

So far I have sucessfully completed steps

1. Unzip the contents of the upgrade version to my own PC Folder ready to upload into my website root
2. Renamed web.config to webbackup.config
3. Edited Auto Upgrade to False in web.config
4. Transfered the neccessary setting to the release.config file
5. Rename the release.config to web.config

I got stuck at tutorial #10 (mentioned earlier ) and have not proceeded any further, thinking that I had encountered a problem.

I will proceed with the upgrade, as you have suggested.

But I will wait until morning, because it is late for me (UK) now and I want to be able to concentrate fully on what I am doing.

Thanks for all your help and suggestions.  I will let you know of the progress I make.

Lynn

Hello

I went ahead with the upgrade as the original tutorial I was following was for DNN 3.2.2 and as suggested this may not be relevant for v-4.

I have:
Backed up my original site:

Carefully transfered the following settings from original web.config (DNN 4.3.4) to new (Release.config in DNN 4.3.5) renamed it web.config

1. Both lines of code which contain the database connections:

"Server=*****
Database=*****
uid=*****
pwd=*****"

2. Original Install date: <add key="InstallationDate" value="****" />

3. The Validation and decryption key settings:

validationKey="*******"

decryptionKey="*******"
        
4.Uploaded new DNN Install over the old files.

5. After files uploaded. In the URL address bar:

http://www.mysite.com/Install/Install.aspx?mode=Install

To trigger the installation process.

But instead I saw this error:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

Lynn