In regards to your browser showing a list of files when you browsed to localhost/DotNetNuke, make sure that in IIS you have specified Default.aspx as the default page for the DotNetNuke application.

In regards to the IIS Metabase error, that is usually an indication that IIS was installed AFTER ASP.Net was installed. The usual cure is to re-register ASP.Net running (from a command prompt) the aspnet_regiis tool for the appropriate version of ASP.Net you wish to register. I see from your stack trace that you have installed ASP.Net 4.0. Therefore, the command to run would be:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis -i

For information on aspnet_regiis and its various options for ASP.Net 4.0, please see: http://msdn.microsoft.com/en-us/libra...

The other possible cause of the IIS metabase error is that you have not granted the ASP.Net worker process account (ASPNET on IIS 5) full control on the root folder of the site installation and all child folders.

---

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

The problem still persists.

 The Default page is not loading.