Not sure of the cause of the error but the fact that the error is being written to the LogFailures.xml.resource file rather than to the EventLog table of the database is an indication that the DotNetNuke installation is unable to connect to the database.

When moving the site to localhost did you . . .

1. Backup and restore the remote site's MS SQL Server database to a localhost installation of MS SQL Server?
2. Did you create a new database user login for the restored database and grant it db_owner rights for both database schema and roles?
3. Did you modify both database connection strings in web.config to point to the new database server and any changes in database login credentials?
4. Before backing up the database on the remote host did you add a new Portal Alias for it's localhost url? Probably "localhost/BIUSABkUp/" or did you manually add the new alias to the PortalAlias table after restoring the database on localhost?
5. Did you grant full filesystem permissions including modify to the ASP.Net worker process (IIS Identity) account on the root folder of the localhost installation?
6. Have you looked at the LogFailures.xml.resources log file in the folder specified to see if there is more detailed error information logged? You can open the file in your browser after renaming it to remove the .resources extension.

---

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