Thank you all for your responses, but I still am not able to get it working
jascht wrote
You want to migrate the database from one MSSQL Server to another?
In a nutshell... yes, that is what I want to accomplish.
mitchel.sellers@gmail.com wrote
If you are moving the db to another server you can do a backup from the one, and then a restore to the other.
You will then need to modify your connection strings in your DNN installation to reflect the settings for the new server.
The way I copied the datbase to the new server was to back it up and restore it. I did change the connection strings to point to the new server/database/user.
jascht wrote
You shouldn't forget the user / login for the new server (the stored user is from another instance).
The easiest way is to create a new login (databases->security->login) and add a new user with the new created login to your DNN database. Now grant every permission to your new user. To finish the migration the new user must be a member of the db_owner role.
I know from past experience that I can't use the same user when moving to a new server. I did set up a new user and gave it db_owner permissions as well as reader/writer.
***I believe I'm doing everything right, so I'm really scratching my head. I have other ASP.Net sites that I did the same thing with that are not DNN and they are working without problems, so I believe it's something DNN does. The only thing I can think of is the machine key, since I recall hearing it was in place as some kind of security measure. If it is the machine key causing my problem, I don't know how to get past it. I'm just grasping here since I haven't got a clue why it isn't working.