Hello,
I just did a fresh install of 5.4.4. The installation seems to have worked fine, and the site pulls up with the default skin and the standard homepage content. However, when I click on Register or Login those pages are empty. The skin is still displaying, but in the middle of the page where the login form is supposed to be, there is just an empty area. I checked the source, and the form is not there, so it's not display issue. The icon_authentication_32.gif is there, but that's it.

Any suggestions?

Thanks,
Donald

I had the exact same thing happen on a fresh 5.4.4 install. Furthermore, after I refreshed the Home page, the only content that shows is the word "Sponsors", The rest of the content area is blank. I tried closing the browser, clearing the cache, iisreset... nothing.

The site was working initially and I didn't change anything after the install. However, I did start a new module project in VS2010 using this site and that's when I noticed this behaviour. I didn't do anything with the project, just generated from the template and ran it. I used this blog post as a guide. After reading the comments at the bottom of that page, I noticed a reference to this problem. Part of the setup process required creating a virtual directory for the new module. The virtual Directory structure started with DesktopModules, which blocked the actual physical folder by the same name. Once I deleted the virtual folder in IIS, the physical DesktopModules re-appeared and now the site is functioning properly again.

BTW, I also had to delete the web.config file that was generated in the new module project. So those are two gotchas when developing modules in VS2010.

I've solved this problem.

When I did the installation, I had deleted all files in the website and replaced them with the new files from the installation package. And I deleted the database and this database was created as new.

In IIS I didn't remove the existing website. Even after restarting IIS and stpping and starting the website and the application pool, the problem was still there.

I've removed the website from IIS, deleted the database again, replaced all files from the website and started from scratch again.

First I copied the files from the installation package,
Second I created the new database and set securityrights for the DotNetNuke user.
Then I created a new website in IIS  (app pool: Classic .NET AppPool)
Started the localhost website and after the installation routines the website came up with full functionality.

I think the key in this solution was starting with a new website in IIS.