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
if this doesn't work than use this command
alternatively you can copy and paste this command into windows command prompt
this will fix your problem
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
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
Perfect, after several hours and pretty close to a full breakdown i found this lifesaver. 10 second fix thanks
ReplyDeleteI tried for hours in searching and trying others solutions but your's was prefect. Solved my problem.
ReplyDeleteThanks.
Thanks... perfect one
ReplyDeletethanks a lot!!!!!! :)
ReplyDeletemicrosoft help sucks!!!!!!!!!!!!!
thanks guys after 2 weeks of traiting you saved me :D
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.
ReplyDeletewhat is the UserName?
ReplyDeleteThanks !!!
ReplyDeleteThanks a lot. i have search so many pages but finally it works.
ReplyDeleteomg, fighting this for an hour and then your post just saved me!
ReplyDeleteThanks very much! It works great.
ReplyDeleteThanks!!
ReplyDeleteyet another very happy individual to find this page. You've saved me a great deal of time. Thanks!
ReplyDeletePerfect solution
ReplyDeleteTHANK YOU so much. It's perfect solution.
ReplyDeleteI tried both suggestions and I still get the "Failed to Access IIS metabase" error.
ReplyDeleteXP Pro SP2
ASP.NET 3.5
It's awesome!!!! I spent two month and now.... it's cool. Thanks
ReplyDeleteYou rock!
ReplyDeleteThanks a lot. I really worked
ReplyDeleteGREAT...it worked...
ReplyDeleteThanks A lot..It really helps me a lot...
ReplyDeleteThanks again..
Perfect !!
ReplyDeleteThank
-- danu sukmawijaya --
That fix was da sheeot!
ReplyDelete+1 Worked!
ReplyDeleteBravo!!!!!! Thanks you so much.
ReplyDeleteGreat Solution! I tried many recommended solutions in the net forum yours is great!
ReplyDeleteThanks!
Great Solution!! i re-imaged my machie and i was getting this error. you recommended solution worked like a charm.
ReplyDeleteThats perfect
ReplyDeleteyou are really cool....this helped a lot. Thanks.
ReplyDeleteThanks! Your solution works great.
ReplyDeleteExcellent fix.
ReplyDeleteAfterthought: It makes sense to install IIS before VS or SQL server...
Thanks!
Thanks a lot, worked like a charm
ReplyDeletePerfect prognosis, and cure.
ReplyDeleteIIS help did not show nada and after going through your command it worked in no time. Thanks a lot.
ReplyDeleteAwesome, worked great.
ReplyDeleteThank you!It really works!
ReplyDeleteThanks Dude!!
ReplyDeleteTHAT'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.
ReplyDeleteAwesome ..It worked...
ReplyDelete"%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" worked for me, thanks!
ReplyDeleteThanks a lot . It fixed my problem.
ReplyDeleteThank you so much. You saved me a lot of time and grief trying to troubleshoot this.
ReplyDeleteThanks a lpt Guys.....It Works Perfect
ReplyDeleteThank you Sir, like what others said, it was a quick fix. God bless everyone.
ReplyDeleteDamn! Thanks a lot, you've just made me save time!
ReplyDeletegreat Help. Thanks
ReplyDeletecool, it fixed the problem.
ReplyDeleteI 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.
ReplyDeleteAightaboy!
ReplyDeleteThank you so much!
ReplyDeleteThanks for the help. The last command prompt worked for me.
ReplyDeleteWaaaal thanks. It worked for me too yipeee!!!!
ReplyDeletethanks ,
ReplyDeleteactually run the commnad
aspnet_regiis -ga \aspnet
Thanks dude.It Worked
ReplyDeleteThanks a lot....!!!!!
ReplyDeleteit works perfectly.....
Anup
jakkass solutions..............
ReplyDeleteThanks a lot. I've found this after several hours of web search for the solution, but this one fixed my problem in seconds.
ReplyDeleteThanks !
Thanks, it's really helpful. I've found this after several hours of web search.
ReplyDeleteThanks again !
Super like mate.
ReplyDeleteTy!!
Yup..Its working fine..Thanx dude..Cheers
ReplyDeleteThan You... My Problem resolved...
ReplyDeleteyes.. u r the life saver...
ReplyDeletethanks
Thank you so much...
ReplyDeletegre8....
ReplyDeleteBest Regards
Harshal
IT really worked.. thnaks
ReplyDeleteIt worked, Thanks a lot..
ReplyDeleteThanks buddy. Worked like a charm.
ReplyDeletethank u a lot. it saves my time.....great
ReplyDelete10 out of 10
ReplyDeleteit was really helpfull in concise way
Worked for me also. Only changed it to latest version of .NET i.e. "v4.0.30319"
ReplyDeletethanks..
ReplyDeleteIt worked!!