This error typically occurs when you install IIS after you have asp.net installed. It is a very simple fix.
Copy and paste this into the Run Command from the Start Menu.
%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
This will reinstall asp.net for use with IIS and in most cases fixes the error stated above.
That worked for me
ReplyDeleteThanks for the concise advice! I really appreciate it.
ReplyDeleteI have been reading bundles of microsoft articles to fix this issue. your post fixed it in less than a minute. Thank you
ReplyDeleteThank you very much. It solved my problem!
ReplyDeleteThat was really priceless tip.
ReplyDeleteWOW !
ReplyDeleteThat worked like a charm. Thank you!
ReplyDeleteWorked for me! Thanks!
ReplyDeleteYou, sir, are a flippin headache saver. I just wasted 30 minutes in command prompt hell, when all I could have done was hit your site. If I were next to you, I'd slap you five, you jive turkey.
ReplyDeleteDude.... you are tooo gud... Thanks a Ton !!!!!!!!!!!!!!!
ReplyDeleteif only I read this first
ReplyDeletethank you very much
Thank you - after going through the MS KB hell - I found your post and of course, it saved the day.
ReplyDeleteServes me right for running XP for web development, I guess.
Spent the past three hours trying different techniques recommended via MS KB, then found this page, and like others, 10 seconds and problem fixed. Thanks
ReplyDeleteWorked like a charm. Thanks!
ReplyDeletetanx very muchhhhhhhhhhhhhh
ReplyDelete:):X:*
Wow..that was soooooo easy. Thank you for the resource.
ReplyDeleteWorked great!
ReplyDeleteThanks a lot
Still no good for me.
ReplyDeleteAny other ideas?
You rock!
ReplyDeleteWhy couldn't Microsoft just tell me that?
Glad I found your site. The solution you suggested has saved me a week of on and off headaches!!!
ReplyDeleteThank You Thank You ThanK yOu sooooo much dude...
ReplyDeletethe first thing i did is to bookmark this site. it worked like magic. microsoft kb did not solve the problem. thank man.
ReplyDeleteDitto what everyone else said...shouldn't be so hard to find concise, accurate info
ReplyDeletetnx man thats work for me...
ReplyDeleteThanks! This did the trick!
ReplyDeleteThanks a ton.
ReplyDeleteI had spent whole trying to figure out.
Problem Solved!
ReplyDeleteThanks a lot!!
Amazing. Thank you for taking the time to post this and saving many a ton of time!
ReplyDeletegood fix!
ReplyDeleteExcellent - time saver tip. Thanks!
ReplyDeleteCrazy thing for me. We had to rename the server and then had issues. I tried to do the aspnet_regiis -ga, but that didn't help. The only thing that helped was aspnet_regiis -u. If I unregistered it, the webservices used ASPNET 2.0 just fine. if I register it again they break. Very frustrating issue.
ReplyDeleteBeing very skeptic of quick fixes, I doubted this fix. In the end I did give it a try and it worked wonderfully. Thank you!!!
ReplyDelete@Anonymous, I don't blame you for being a skeptic. Don't trust everything you read on the web, someone might tell you to do something stupid and open yourself up to attack. But I am glad you gave it a try, and even happier that it worked for you and SO many others.
ReplyDeleteAt my last job this came up on the support forums that I was apart of pretty frequently, so I used my post as a Canned response to the question.
thanks buddy, it really helped em out.. ;)
ReplyDeletecheers...
Gracias por la ayuda funciono
ReplyDeleteGracias por la ayuda funciono
ReplyDeleteTHANK YOU!
ReplyDeleteThank you very much dude... very nice...
ReplyDeleteThanks! Worked like a charm!
ReplyDeleteThanks a ton! That worked.
ReplyDeleteThanks a lot for the useful information.
ReplyDeleteThats working....
Thanks a lot...
ReplyDeleteWow,thank you very much for the quick fix...i have been reading bunch of micorosoft's useless suggestions
ReplyDeleteThanks again
didn't work for me.
ReplyDeleteany ideas??
@xjufox - No, I'm sorry I don't have any ideas right now. The only time I ran into the problem is when I installed IIS after I had installed the .Net framework. Also this command is only valid for .Net 2 and I am not sure it will work if you only have .Net 3 or .Net 3.5.
ReplyDeleteAlso as a side note I no longer work for a Windows shop, so I don't really have access to a Windows Server to play with it.
Thx! worked for me...
ReplyDeleteShort and simple. How sweet!
ReplyDeleteKeep up the good work!
I tried your solution and I still have the same error message "Failed to access IIS metabase". Could you tell me how to troubleshoot the problem?
ReplyDeleteMicrosoft gave a BS soution to do that involved downloading a script and running a long command from the CMD window. You solution fixed it in less time then it took to read the article. Good job.
ReplyDeletethanks a lot !!
ReplyDeletegenius
wow ;thanks
ReplyDeleteThank God for people like you. 4 IT guys gave up on it completely and you have just saved me with one short command!
ReplyDeleteThanks, this was spot-on advice!
ReplyDeleteYOU DA MAN!
ReplyDeletesimply brilliant....thanx boss
ReplyDeleteI'll even leave my name. You rock!!
ReplyDeleteI tore my hair out for an hour trying stuff before I found this post.
Always install IIS before .NET I guess.
Thank you soooo much.
Gary Parkin
Thank you so much!!!! I tried so many things and so many re-boots - to no avail.
ReplyDeleteThanks again.
Kusum
Thanks.. this solve my problem :)
ReplyDeleteThanks a million dude..
ReplyDeleteThank you. Your advice saved me who knows how much time crawling through the KB.
ReplyDeleteThanks Dude you have made my day
ReplyDeleteThanks for posting this solution.
ReplyDeleteThanks for being awesome.
ReplyDeleteThanks a LOT!!!!!!!!!!!!!!!!!!!!!!!!!!!!! So happy..............
ReplyDeleteSimple solution. Why does Microsoft not publish this on their website?
ReplyDeletehttp://support.microsoft.com/?kbid=267904
Thank you for the solution
ReplyDeleteThanks! Worked like charm!
ReplyDeleteThanks a lot!
ReplyDeleteabsolutely brilliant is this guy, thanks a lot mate
ReplyDeleteAfter many hours trying other solutions, your solution worked! Thank you very very much!
ReplyDeleteLike everyone else, I'd like to say thanks.
ReplyDeleteIt worked fr me
ReplyDeleteThanks for posting this, you've saved me a lot of going in circles trying to fix!!
ReplyDeleteAdd me to the list ! Thanks a lot, as said before I read a whole bunch of MS stuff before seeing your comment. And it worked
ReplyDeleteCheers from Chile,
Jean-Luc
You rock! This worked perfectly!
ReplyDeleteThank you so much for your advice. This issue also appears when moving a .NET 2003 project to .NET 2005 so it is good to keep in mind as well.
ReplyDeleteThank you!
Worked on XP as well!!!
ReplyDeleteThank you
thanx working fine
ReplyDeleteI too owe u some thanks! im new at this and when i saw that error after everything was working great in Visual studio i freaked lol. it looks like all complex just a asp config error tho. thanks a bunch!
ReplyDeleteHonestly, this needs to be posted on dotnetnuke.com site! Great fix.
ReplyDelete2 days of searching for a solution, 10 second fix found here
ReplyDeleteOne of the developers on my team contacted me with this error. We were at a loss and thought there were some larger internal problems with his new web service.
ReplyDeleteThis site came up as the first hit in Google and I was incredibly doubtful about the proposed solution - its never that easy.
Well we ran the reinstall and as the dev put it "HUZZAH!" - it really worked.
Thanks again for saving us a huge amount of time tracking the answer down.
thanks buddy it worked absolutely fine for me
ReplyDeleteThankQ
ReplyDeleteAbsolutely brilliant. I've been farting about with IIS, site security settings and manually adding windows and domain accounts to the metabase to no avail.
ReplyDeleteUntil I saw this tip! Instant fix!
Thanks Steve :D
Thanks, bro.
ReplyDeleteit's great solution.
Thank a lot. This work for me.
ReplyDeleteGreat job. Saved a lot of times and hassle. Thank you for the great tips.
ReplyDeleteAlex,
Great. Thank you for your tip in ths matter. Saved me a lots of time and hassle.
ReplyDeleteAlex,
Great. Thanks a lot. Worked perfectly. Saved me time and headach.
ReplyDeleteAlex
Fantastic, spent 1 hr on Microsoft site, to no avail. This took care of it in no time.
ReplyDeleteYOU ARE DA BOMB
ReplyDeletetrust me..., IT WORKS>>>> L-Men
ReplyDeleteone more fan of concise advice !
ReplyDeleteWorked for me as well. Thanks.
ReplyDeleteIt work for me as well and Thanks for sharing !!
ReplyDeleteThanks, You saved me.
ReplyDeleteYour the best...Really appreciate your post..Saved me so much time...
ReplyDeleteThanks a million, dude.
ReplyDeleteIf you have asp.net 4.0 installed, you might have to do it there too (I did). Good luck all, and thanks!
ReplyDeletedude it also works with .net 3.5....i tried it!!
ReplyDeleteThanks!!! It worked for me too :)
ReplyDelete