I have found it difficult to move a site to local using just the database and not BOTH the database and the actual site files backup. For that approach to work at all it is essential that the local DNN framework version match that of the database restored from the production site.  I would suggest downloading the correctly matching version of the framework from the DNN CodePlex site where all legacy versions are available and installing it with a fresh database. Make sure that you use the same databaseOwner and objectQualifier strings in the web.config as was used on the production site. Once the new install is working I would then 1) install any modules using the same version as those on the production site, 2) restore the production database, 3) add the alias for the local install to the PortalAlias table, and 4) make any necessary changes to the two connection strings.

I would also suggest first running the application as you now have it setup with FireFox rather than IE as Firefox gives a more descriptive error message - in particular if there is a redirection loop preventing the site from being displayed.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Found solution to my problem. Opened the  site in FF and found a different error:

"Firefox has detected that the server is redirecting the request for this address in a way that will never complete."

Uncommented  the line "<add key="UsePortNumber" value="true" />" and that solved the problem :)