Another thing changed is the machineValidation and machineEncryption keys, but those won't do you any good from another config file since they are randomly generated.

It's really best to start with the release.config on a fresh install.  And even on an upgrade if you move all your custom modifications into it.

OK, here we go...

Using a CLEAN install of DotNetNuke 04.05.05 on a completely clean server, we are having the following issues...

• Initially when I tried to login at the default DotNetNuke page (using either admin or host accounts), I received an error message, which I have screen capped below:
  
  
• Now, however, I am simply looped back to the main page with no error message, no successful portal entry.  Repeat tries yield the same result.
• I have tried registering for a new username and logging in with it, but this just continually loops me, as well.
• release.config contains one set of machine keys, yet web.config contains an entirely different set.  Why is this, and which set do we use?  We have tried changing the web.config keys to reflect release.config, and this does not resolve the issue.
• Again, this is a NEW install on a server that had been completely wiped clean.  We have tried deleting the cache, restarting IIS, and rebooting the server.  Nothing we have tried has provided any resolve.