Aug 24, 2005 09:12 PM|Ed_DeGagne|LINK
daniel, I mentioned when the keys first came out that there was no mention about them anywhere or what else needs to be there...
I hope everybody reads this. Do not overwrite your web.config. Of course always backup. Compare the two release.configs and make the changes. Even people experiened with dnn are making mistakes...
Backup your existing web.config before proceeding any further.
As described above, the zip package no longer includes a copy of web.config.
The reason for this will become clear when you read this section on Upgrading an existing DotNetNuke site (especially version 3.0.13).
As described above DotNetNuke version 3 added the memberRole prototype.
Three keys in the AppSettings control the password encryption for this component.
<add key="MachineValidationKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902" />
<add key="MachineDecryptionKey" value="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC" />
<add key="MachineValidationMode" value="SHA1" />
These keys may look innocuous enough, but if your MachineValidationKey and MachineDecryptionKey values are not the same as those above then you must be very careful, when setting up the web.config file for
In order to successfully upgrade you must follow the procedure outlined below
Make a back-up copy of your existing web.config file (web.config.backup).
We cannot emphasise enough how important it is that you have a backup.
If you lose the original value of the MachineKeys, then none of your users will be able to log in.
Once you are sure that you have safely backed up your web.config file, rename release.config to web.config.
Replace the following keys in your new web.config, with the values in your backup.
InstallationDate (this may not be present in web.config, so add the key that is in web.config.backup to web.config)
Make any other changes to web.config that you made to support additional providers etc.
You should now be able to browse to the site and trigger the Upgrade process.
Do not browse to your site unless you are sure that the MachineKeys in your new web.config are the same as they were in the old file that you backed-up.