I've been running DNN successfully on my dedicated production server for over 6 years now and have no problems with it. Recently, I backed up all the DNN and content files (4GB) as well as the DNN Db (600MB) on my Windows 2003 64-bit production server (IIS 6).  I restored them all on my Windows 7 64-bit desktop development machine (IIS 7). Both machines are running on SQL Server 2005 Express Edition 64-bit. I'm using standard DNN authentication on both. None of the DNN core or any modules have been modified.

I followed all the standard procedures. I only had to change the name of the server in the web.config file. After some minor tweaking, everything worked great except that I cannot log into any of my portals using any credentials (users, admins, host). I've cleared all forms of cache and yet dispite hitting it from multiple computers and browsers, I cannot log into any portal on my Windows 7 desktop edition. When I try logging in anywhere, it looks normal except after the login is submitted, it goes back to the home page of the given portal and I'm not logged in.

I've spent the past few days trying every conceivable variation of the process of migrating everything over (I've been an IT professional/programmer for 28 years so it's pretty basic stuff for me). I've googled everything I could think of and tried every recommendation I could find on any forum to no avail. I've uninstalled and reinstalled everything multiple times and although hundreds of DNN pages all behave perfectly on dozens of portals I cannot log in to any portal with any credentials. No error messages are getting logged in the EventLog table during login attempt. So, I have nothing else to go by. It is storing cookies on my local browser containing the sessionid and other typical information.

If anyone has any recommendations, I would sincerely appreciate it.

Thanks, John

Hi,

I am in a similar position but slightly different problem. I can install a new dotnetnuke site on my local PC (Windows 7/IIS 7/SQL Server 2008 Express Edition) and it works perfectly fine. Have you tried this?

But my production site (DNN 4.9) from Windows 2003 Server/IIS 6 environment has given me headaches. At random instances for logged in users the website crawls down until it gives timeout errors. At times at login itself.

I have tried changing the default application pool setting in IIS 7 to run under Network Service, disabled my AVG Antivirus and Windows Firewall but to no avail. Had some some success after clearing the cache for the DSLocalizator module used on the site but at times it makes no difference.

My guess is some module/functionality in the production site has compatibility problems with Windows 7/IIS 7 environment. Would be glad to find a solution.

Regards
Arif Shah.