Hello,

I have a DotNetNuke-powered website working on a Windows XP machine with IIS6, SQL Server 2008 Express.  I'm in the process of porting it over to my new Windows 7 machine, which runs IIS7 and SQL Server 2008.  (This machine was originally configured using XAMPP for Windows, enabling php, apache and mysql development.  Due to this previous installation, IIS7 is configured to run on port 81 instead of the standard port 80.  This port mapping did not confuse the tutorial mentioned in the following paragraph, but I thought to mention it just in case..)

I have followed the instructions found at http://adefwebserver.com/dotnetnukehelp/DNN5_DevelopmentEnvironment/Default.htm.  This tutorial successfully set up my machine to run a standard DotNetNuke development environment, using a new database.

I need to use the existing database instead of the one produced from the tutorial.  I achieved this by altering the web.config file in the project, and by restoring a backup copy of the database onto the new machine.

These changes seem to work for me, as I can load the webpage and provide my log-in credentials without error.  When I attempt to log in to the system, the site redirects back to the home page, but does not show the DotNetNuke control panel.  The user credentials are confirmed to be validating (if I put in bad username/password, an error results).

Upon debugging the application, it appears that the controls for username and password contain some data when the post occurs, but this data is not being persisted properly.

Does anyone know how the built-in DotNetNuke log-in system should be persisting a successful log-in?  I have checked that I am receiving cookies where I would expect them, and cannot find any session data that would perform this.

Any help is greatly appreciated,
Thanks,
Ben

Hi Sebastien,

Thanks for your response.  I took a look at your suggested reading.  Up to this point, I have been following the final suggestion of setting the app pool to NETWORK SERVICE, as that was the method I was familiar with from IIS6.

A bit more debugging has exposed where I believe the problem lies.  On another Win7 machine, I have a successful import of the website up and running.  When stepping through the log-in process, the working machine cookies me with "portalAliasId" and "portalRoles".  On the machine that is not working, I am being cookied from the site, but these two log-in related cookies are not showing up at any stage.

The plot thickens....

In the IIS Setup you probably need to make sure that Windows auth is installed, it isn't by default.

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions