Is it not necessary to modify the Machine Key Validation codes that come with the standard DNN install to those of your host server?

Thanks

Ron

Your web.config file's machine keys settings must match the database. So, if you are moving DotNetNuke installation from one location to another, you'll need to move the machine keys (along with any other custom settings in the web.config file).

When you create a new installation and/or new database, it's not necessary that you use "old" machine key settings.

To follow this up: so if you are moving localhost to live - your web.config file is already set up correctly with the machine keys for your installation.

All you need to edit in the web.config file is the database connection string, when you transfer all of your files and database to the live site the machine keys will then work for the new live database.

The same goes for live to localhost. The machine keys are already set for the live site, so you just need to transfer all of the files and database on the live site to a localhost installation and the MachineKeys will then match the restored database.

The only time you need to transfer your machinekeys is if you are upgrading and you are using a new web.config file.

If you start 'experimenting'  just make sure you keep a copy of your web.config file so that you do not you lose the original machine key settings.

Thanks,

It could be a permissions problem. - If you use the installation wizard you can click on a link to check the permissions before you initiate the installation, so I would double check those permissions.

This tutorial is for a localhost installation, but there is a video on there which demonstrates the installation wizard:
How to install DotNetNuke 4.5 to Windows XP Pro with IIS