Hello

I am currently running DNN 4.3.4, I wish to upgrade to the latest 4.3.5 release.

1. I have backed up my dnn 4.3.4 files
2. Made a backup of the web.config file in 4.3.4 in uploaded back into root.
3. Edit the 4.3.4 web.config file
   <add key="AutoUpgrade" value="true" />
   to
   <add key="AutoUpgrade" value="false" />
4. Uploaded the edited web.config back into site root
5. Check that site is still accessible -  ok
6. Edited the release.config to reflect database, install date and machine keys
7. Uploaded the 4.3.5 dotnetnuke.dll file to bin folder
8. Checked site is still accessible - NO Instead of displaying:

This site is currently Unavailable
Please check back later

I see this error page:

DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.

9. I tried this with both the install and the upgrade version of 4.3.5. Same Result.
10. I uploaded my backed up DNN.dll (4.3.4) file into the bin and site available again.

Consequently I have not gone ahead with the upgrade.

Any thoughts on this?

Lynn

Hello Shadowpdx

Your steps should be

1. Backup site
2. Rename web.config to another name - I usually use web.config.old (if necessary - it is not always necessary to use a new web.config.  I usually do if there is a major upgrade)
3. Unzip the upgrade to the proper folder
4. Rename release.config to web.config (if necessary)
5. Copy the necessary lines to the new web.config from the old one (if necessary)
6. Navigate to the site to trigger the upgrades
7. Access your portal

I successfully caried out steps  1-5

Your steps are wrong.  First - why did you do this?

Edit the 4.3.4 web.config file
<add key="AutoUpgrade" value="true" />
to
<add key="AutoUpgrade" value="false" />

I did this because I was following an upgrade tutorial, the instructions are:

Hello Shadowpdx

 I don’t have that facility available with my server to take it off line.

Changing the auto upgrade to "false" is a precaution to prevent somebody triggering off the install process half way through uploading the new files.

The uploaded files contains: the new web.config, (formally edited release.config) this will overwrite the original web.config but not the web_backup.config (originally web.config)

Then when all files are uploaded: navigate to URL and personally trigger the upgrade.

After upgrade ok: Go to the new web.config  edit to the original:
<add key="AutoUpgrade" value="true" />  for normal site use.

I am just wondering if the problem could be that the DNN “This site is currently Unavailable.  Please call back later” file is just missing in. DNN 4.3.4.  Or perhaps it is just missing from mine.

Can anybody confirm:

• With <add key="AutoUpgrade" value="false" />
• Uploaded upgrade dotnetnuke.dll (4.3.5) file into the bin folder of DNN 4.3.4, prior to the full file upgrade.
• navigate to the website

 Do you see: “This site is currently Unavailable.  Please call back later” or not

Thanks.

Lynn