Failed to access IIS metabase ASP.NET

Failed To Access IIS Metabase Error In ASP.NET, If You are getting "Failed to access IIS metabase" error while browsing asp.net site or aspx page in IIS server then you may have installed IIS Server after installing the .NET framework.

If that's the case, try running to repair your ASP.NET installation and set up all of the appropriate ISAPI extension mappings.

Open visual studio command prompt and type this command

aspnet_regiis -ga \username
username is usually aspnet


if this doesn't work than use this command
aspnet_regiis -i

alternatively you can copy and paste this command into windows command prompt

%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

this will fix your problem



70 comments:

  1. Perfect, after several hours and pretty close to a full breakdown i found this lifesaver. 10 second fix thanks

    ReplyDelete
  2. I tried for hours in searching and trying others solutions but your's was prefect. Solved my problem.

    Thanks.

    ReplyDelete
  3. Thanks... perfect one

    ReplyDelete
  4. thanks a lot!!!!!! :)

    microsoft help sucks!!!!!!!!!!!!!

    thanks guys after 2 weeks of traiting you saved me :D

    ReplyDelete
  5. Thanks a lot your the best it worked as you said but just for note this even works if first installed iis and then frame work.

    ReplyDelete
  6. what is the UserName?

    ReplyDelete
  7. Thanks a lot. i have search so many pages but finally it works.

    ReplyDelete
  8. omg, fighting this for an hour and then your post just saved me!

    ReplyDelete
  9. Thanks very much! It works great.

    ReplyDelete
  10. yet another very happy individual to find this page. You've saved me a great deal of time. Thanks!

    ReplyDelete
  11. THANK YOU so much. It's perfect solution.

    ReplyDelete
  12. I tried both suggestions and I still get the "Failed to Access IIS metabase" error.

    XP Pro SP2
    ASP.NET 3.5

    ReplyDelete
  13. It's awesome!!!! I spent two month and now.... it's cool. Thanks

    ReplyDelete
  14. Thanks a lot. I really worked

    ReplyDelete
  15. GREAT...it worked...

    ReplyDelete
  16. Thanks A lot..It really helps me a lot...
    Thanks again..

    ReplyDelete
  17. Perfect !!
    Thank

    -- danu sukmawijaya --

    ReplyDelete
  18. That fix was da sheeot!

    ReplyDelete
  19. Bravo!!!!!! Thanks you so much.

    ReplyDelete
  20. Great Solution! I tried many recommended solutions in the net forum yours is great!

    Thanks!

    ReplyDelete
  21. Great Solution!! i re-imaged my machie and i was getting this error. you recommended solution worked like a charm.

    ReplyDelete
  22. you are really cool....this helped a lot. Thanks.

    ReplyDelete
  23. Thanks! Your solution works great.

    ReplyDelete
  24. Excellent fix.

    Afterthought: It makes sense to install IIS before VS or SQL server...

    Thanks!

    ReplyDelete
  25. Thanks a lot, worked like a charm

    ReplyDelete
  26. IIS help did not show nada and after going through your command it worked in no time. Thanks a lot.

    ReplyDelete
  27. Awesome, worked great.

    ReplyDelete
  28. Thank you!It really works!

    ReplyDelete
  29. THAT'S WHAT I'M TALKIN' ABOUT!!!! YOU THE MAN!!! I've spent almost three hours this morning trying to figure this one out.....I have an IIS textbook I've never used because it's useless.....nothing on this. Same with Microsoft. Can't thank you enough.

    ReplyDelete
  30. Awesome ..It worked...

    ReplyDelete
  31. "%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" worked for me, thanks!

    ReplyDelete
  32. Thanks a lot . It fixed my problem.

    ReplyDelete
  33. Thank you so much. You saved me a lot of time and grief trying to troubleshoot this.

    ReplyDelete
  34. Thanks a lpt Guys.....It Works Perfect

    ReplyDelete
  35. Thank you Sir, like what others said, it was a quick fix. God bless everyone.

    ReplyDelete
  36. Damn! Thanks a lot, you've just made me save time!

    ReplyDelete
  37. cool, it fixed the problem.

    ReplyDelete
  38. I CURSE the person who wrote the error message that comes with this error directing you to go to the most UNHELPFUL "knowledge base" article there ever could be. And I wish the person who wrote THAT dies in his own vomit.

    ReplyDelete
  39. Thank you so much!

    ReplyDelete
  40. Thanks for the help. The last command prompt worked for me.

    ReplyDelete
  41. Waaaal thanks. It worked for me too yipeee!!!!

    ReplyDelete
  42. thanks ,
    actually run the commnad
    aspnet_regiis -ga \aspnet

    ReplyDelete
  43. Thanks dude.It Worked

    ReplyDelete
  44. Thanks a lot....!!!!!
    it works perfectly.....

    Anup

    ReplyDelete
  45. jakkass solutions..............

    ReplyDelete
  46. Thanks a lot. I've found this after several hours of web search for the solution, but this one fixed my problem in seconds.
    Thanks !

    ReplyDelete
  47. Thanks, it's really helpful. I've found this after several hours of web search.
    Thanks again !

    ReplyDelete
  48. Super like mate.
    Ty!!

    ReplyDelete
  49. Yup..Its working fine..Thanx dude..Cheers

    ReplyDelete
  50. Than You... My Problem resolved...

    ReplyDelete
  51. yes.. u r the life saver...

    thanks

    ReplyDelete
  52. Thank you so much...

    ReplyDelete
  53. IT really worked.. thnaks

    ReplyDelete
  54. Thanks buddy. Worked like a charm.

    ReplyDelete
  55. thank u a lot. it saves my time.....great

    ReplyDelete
  56. 10 out of 10
    it was really helpfull in concise way

    ReplyDelete
  57. Worked for me also. Only changed it to latest version of .NET i.e. "v4.0.30319"

    ReplyDelete
  58. thanks..
    It worked!!

    ReplyDelete