«
»

Failed to access IIS metabase

By Chris Gaskell

If you have both ASP.NET 1.1 and 2.0 on your machine you may encounter this issue. Upon running your website (via http://localhost/xxxx), you may encounter the error page that reports:

Failed to access IIS metabase

If so, you may have installed IIS after installing the .NET framework. If that’s the case, try repairing your ASP.NET installation. You can do this in one of two ways:

  1. Control panel -> add remove programs -> .net install -> chnage/remove -> repair.
  2. At a command prompt -> aspnet_regiis -i

If however you’re like me and installed VS 2003 / VS 2005 after IIS follow these steps:

  1. Check that the appropriate ASP.NET version is associated with the virtual directory (Select VDIR –> Properties –> ASP.NET tab).

This entry was posted on 22 November, 2006 at 1:37 pm and is filed under ASP.NET, ASP.NET (C#), Debugging, Errors. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

11 Responses to “Failed to access IIS metabase”

  1. Lee Cunningham Says:
    20 January, 2007 at 3:28 am | Reply

    Thanks for the info. I had that issue tonight after installing IIS AFTER VS. I’ll try the repair.

  2. Tommy G Says:
    21 February, 2007 at 1:29 am | Reply

    Looking up the recommended hyperlink the web server gives out when this failure occurs had me downloading files and trying to create new permissions to it.

    With so many sites confusing learners like myself with drivel that doesn’t work, your blog is a breath of fresh area.

    Thank you so much, that was short, easy to understand and worked a treat.

  3. Chris Gaskell Says:
    21 February, 2007 at 1:05 pm | Reply

    Many thanks Tommy, your feedback is appreciated.

    Chris.

  4. Stefan H. Says:
    14 June, 2007 at 2:29 pm | Reply

    Your blog was very helpful for me too.
    Thanks a lot !
    Stefan

  5. Amirdha Gopal Says:
    31 July, 2007 at 9:40 am | Reply

    Thanks Chris for this clear explanation.

    Ur blog helped to solve the problem instantly.

    Good Explanation.

    Keep Blogging.

    Thanks,
    Gopal.

  6. Phil Duba Says:
    29 August, 2007 at 7:31 pm | Reply

    Thank you so much for this blog post. It has helped me get started on my path learning ASP .NET as this was the first error I came across trying to run samples in a book. Thanks again!

  7. mirage Says:
    4 September, 2007 at 11:44 pm | Reply

    I am blaying with blogengine.net blogging software on a local machine and had this error. going to the add remove programs and repairing the instalation for the .net framwork fixed this issue, which was a lot better than going through the microsoft error page. Thank you for such a great post.

  8. ian lea Says:
    13 October, 2007 at 10:52 pm | Reply

    worked for me but getting permissions is important too, see link
    http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/119/Installing-DotNetNuke-455-Locally.aspx

  9. Vinod Says:
    16 June, 2008 at 7:12 am | Reply

    Your blog has solved my problem. Thanks for the help

  10. sehnsucht Says:
    27 October, 2008 at 1:18 am | Reply

    ffs – why isn’t this on one of MS’s many stinking webpages. I’ve spent 3 hours trying to fix this, following one useless dead end after another. Thanks a million!

  11. Anoop Says:
    17 February, 2009 at 10:31 am | Reply

    Hi Chris,

    That was juz awesome… U made my day.. I was pulling my hair out from head… thanks a lot.. U rock!

    Have a great day !

    Thanks,
    Anoop

Leave a Reply