Monday, February 18, 2008

Failed to access IIS metabase.

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.

105 comments:

Anonymous said...

That worked for me

dan90266 said...

Thanks for the concise advice! I really appreciate it.

NightCrawler said...

I have been reading bundles of microsoft articles to fix this issue. your post fixed it in less than a minute. Thank you

Anonymous said...

Thank you very much. It solved my problem!

George Asfour said...

That was really priceless tip.

Anonymous said...

WOW !

Anonymous said...

That worked like a charm. Thank you!

Anonymous said...

Worked for me! Thanks!

Tim G. said...

You, 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.

Anonymous said...

THANKS!!!!! I had it fixed within 10 seconds of finding this post.

Stupid f-ing Microsuck!!! Why couldn't they just tell me this???

Anonymous said...

Dude.... you are tooo gud... Thanks a Ton !!!!!!!!!!!!!!!

Anonymous said...

Genius!

Anonymous said...

if only I read this first

thank you very much

Andrew MacNeill said...

Thank you - after going through the MS KB hell - I found your post and of course, it saved the day.

Serves me right for running XP for web development, I guess.

B said...

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

Anonymous said...

Worked like a charm. Thanks!

Solmaz said...

tanx very muchhhhhhhhhhhhhh
:):X:*

Ashley said...

Wow..that was soooooo easy. Thank you for the resource.

Anonymous said...

Worked great!
Thanks a lot

Anonymous said...

Still no good for me.
Any other ideas?

John said...

You rock!
Why couldn't Microsoft just tell me that?

Anonymous said...

Glad I found your site. The solution you suggested has saved me a week of on and off headaches!!!

vighna said...

Thank You Thank You ThanK yOu sooooo much dude...

Anonymous said...

the first thing i did is to bookmark this site. it worked like magic. microsoft kb did not solve the problem. thank man.

Anonymous said...

Ditto what everyone else said...shouldn't be so hard to find concise, accurate info

רועי said...

tnx man thats work for me...

slade73 said...

Thanks! This did the trick!

Anonymous said...

Thanks a ton.
I had spent whole trying to figure out.

Gonza said...

Problem Solved!

Thanks a lot!!

Bryan said...

Amazing. Thank you for taking the time to post this and saving many a ton of time!

Anonymous said...

good fix!

Gad Hazum said...

Excellent - time saver tip. Thanks!

Anonymous said...

Crazy 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.

Anonymous said...

Being very skeptic of quick fixes, I doubted this fix. In the end I did give it a try and it worked wonderfully. Thank you!!!

Steve.Lippert said...

@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.

At 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.

zain said...

thanks buddy, it really helped em out.. ;)
cheers...

Cabs said...

Gracias por la ayuda funciono

Cabs said...

Gracias por la ayuda funciono

Anonymous said...

THANK YOU!

Ralph G. said...

Thank you very much dude... very nice...

Laurie said...

Thanks! Worked like a charm!

Salil said...

Thanks a ton! That worked.

Ram said...

Thanks a lot for the useful information.
Thats working....

Vivek said...

Thanks a lot...

Priya said...

Wow,thank you very much for the quick fix...i have been reading bunch of micorosoft's useless suggestions
Thanks again

xjufox said...

didn't work for me.

any ideas??

Steve.Lippert said...

@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.

Also 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.

Anonymous said...

Thx! worked for me...

kundan_bhaduri said...

Short and simple. How sweet!
Keep up the good work!

Anonymous said...

Thanks a lot

Anonymous said...

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?

Zero 3 Computers said...

Microsoft 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.

Uteeme Arshad said...

thanks a lot !!
genius

Anonymous said...

wow ;thanks

Anonymous said...

Thank God for people like you. 4 IT guys gave up on it completely and you have just saved me with one short command!

Dimitar said...

Thanks, this was spot-on advice!

Anonymous said...

YOU DA MAN!

Anonymous said...

simply brilliant....thanx boss

Anonymous said...

I'll even leave my name. You rock!!
I 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

Anonymous said...

Thank you so much!!!! I tried so many things and so many re-boots - to no avail.
Thanks again.
Kusum

သဥၨာ - Thinzar said...

Thanks.. this solve my problem :)

Amit Shah said...

Thanks a million dude..

James said...

Thank you. Your advice saved me who knows how much time crawling through the KB.

Bhanu Prakash said...

Thanks Dude you have made my day

Anonymous said...

Thanks for posting this solution.

Anonymous said...

Thanks for being awesome.

Anonymous said...

Thanks a LOT!!!!!!!!!!!!!!!!!!!!!!!!!!!!! So happy..............

Anonymous said...

Simple solution. Why does Microsoft not publish this on their website?

http://support.microsoft.com/?kbid=267904

Anonymous said...

Thank you for the solution

Anonymous said...

Thanks! Worked like charm!

Anonymous said...

Thanks a lot!

Anonymous said...

absolutely brilliant is this guy, thanks a lot mate

Anonymous said...

After many hours trying other solutions, your solution worked! Thank you very very much!

Anonymous said...

Like everyone else, I'd like to say thanks.

Gani said...

It worked fr me

Brad Isaac said...

Thanks for posting this, you've saved me a lot of going in circles trying to fix!!

Anonymous said...

Add 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

Cheers from Chile,

Jean-Luc

Ted Augustyn said...

You rock! This worked perfectly!

Anonymous said...

Thank 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.

Thank you!

Anonymous said...

Worked on XP as well!!!

Thank you

Arpit said...

thanx working fine

Anonymous said...

I 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!

elronino said...

Honestly, this needs to be posted on dotnetnuke.com site! Great fix.

Anonymous said...

2 days of searching for a solution, 10 second fix found here

J. said...

One 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.

This 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.

Anonymous said...

thanks buddy it worked absolutely fine for me

Anonymous said...

ThankQ

Phil said...

Absolutely brilliant. I've been farting about with IIS, site security settings and manually adding windows and domain accounts to the metabase to no avail.

Until I saw this tip! Instant fix!

Thanks Steve :D

mukesh said...

Thanks, bro.
it's great solution.

Anonymous said...

Thank a lot. This work for me.

Anonymous said...

Great job. Saved a lot of times and hassle. Thank you for the great tips.

Alex,

Anonymous said...

Great. Thank you for your tip in ths matter. Saved me a lots of time and hassle.

Alex,

Anonymous said...

Great. Thanks a lot. Worked perfectly. Saved me time and headach.

Alex

Solar said...

Fantastic, spent 1 hr on Microsoft site, to no avail. This took care of it in no time.

alfi said...

YOU ARE DA BOMB

penjahat kelamin said...

trust me..., IT WORKS>>>> L-Men

Tavari said...

one more fan of concise advice !

Anonymous said...

Worked for me as well. Thanks.

Anonymous said...

It work for me as well and Thanks for sharing !!

Anonymous said...

Thanks, You saved me.

Anonymous said...

Your the best...Really appreciate your post..Saved me so much time...

Anonymous said...

Thanks a million, dude.

Anonymous said...

If you have asp.net 4.0 installed, you might have to do it there too (I did). Good luck all, and thanks!

Anonymous said...

dude it also works with .net 3.5....i tried it!!

Anonymous said...

Thanks!!! It worked for me too :)