I'm curious to know how DNN creates the Machine Key that it puts in the web.config file. What information is used in creating this key?

The reason I ask is because I'm having a problem moving the database from one SQL Server to another. The site doesn't work when I move it. I'm thinking it's the key that is the problem.

Someone recommended that I create a new DNN with a new database to get the machine key created, then copy my desired old site and database over top of the new ones, leaving the site key in the web.config. I haven't tried yet. I would think that there might be an easier way.

I'd like to know what info goes into the key so I can focus on those items to fix my problem.

That's actually what has me confused... I originally tried to just copy the entire website (changing only the connection string) and restore the database backup to the new server. I set up a new user in the database as db_owner and used this user in the connection string. I made sure the file permissions were wide open and I even made sure the portal alias was in the db for the test website's new location. It didn't work. The site just hangs indefinitely.

Obviously it's seeing something as different, otherwise I think it should just work.

I see in your signature that your company does DNN support. Are you (or anyone else that can figure this out) willing and able to do a little contracting to help me figure this out?

I'm really in a desparate situation. I need to know that when I rebuild the current database server that the database is on that I will be able to put all databases back on it and have everything work again. So far, I can't even get the DNN sites working on the temporary database server.