Failed to access IIS metabase

Failed to access IIS metabase

• Robert Neal

  I am having the same problem "Failed to access IIS metabase".  I tried the repair tool for .Net 2.0 Framework, but it did not work.  I tried uninstalling the whole fremework amd downloaded and installed a fresh copy form the micrsoft website and I still get the same error.
  
  If there are any other solutions can anyone let me know
  

• arnie

  Hi Mark,

  Thanks a lot.Ur suggestion was valuable. It worked.I repaired the .net framework 2.0 and restarted the machine.It was working fine.

  Thank you

  
  
  

• Pankaj Arora

  I used your idea and it worked... thanks a lot!!!
  
  

• larryfran

  Perfect! Ran into the same problem, did a repair on .NET 2.0 framework and now the app's working gr8.
  Thanks for the input!
  
  

• paulfl

  Hi,

  Could you please post the stack trace for the exception that you see It would be useful to know where the exception is getting thrown.

  It sounds like you have created a web service that is hosted on IIS. When you say "it works fine" do you mean that you can browse to the service using IE or hit F5 from the service project and see the service in IE

  I'm not sure I understand exactly what you mean by a "web client." Have you created a separate application project that has a generated proxy type for communicating with the service Did you generate this proxy type using wsdl.exe or the Add Web Reference dialog

  Thanks for you patience.

  Daniel Roth

  
  
  

• Raman Iyer

  USE aspnet_regiis -i

  DETAILS:

  If you're like me and have both ASP.NET 1.1 and 2.0 on your machine (along with the associated Visual Studio 2003 and 2005 products because you can't help but write software in both environments) you may encounter this issue. Upon running your website (via http://localhost/xxx or something like that), 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 running to repair your ASP.NET installation and set up all of the appropriate ISAPI extension mappings.

  aspnet_regiis -i

  If, however, you're like me and had IIS already installed, and you installed VS 2003 and then VS 2005, and then set up a 1.1 virtual directory / website, simply check that the appropriate ASP.NET version is associated with it (Select VDIR --> Properties --> ASP.NET tab).

  "aspnet_regiis -i" once again was successful! However, the directory it is located in was not included a system path previously, so just note that you may have to run this from the "WINDOWS\Microsoft.NET\Framework\vX.X.XXXXX" directory (with the X's being your version number)

  Cesar Augusto

  
  
  

• Marcio DTP

  This solved my issue:

  http://www.cs.nyu.edu/~vs667/articles/asp_metabase_error/index.php

  
  

• badwiring

  The only that work for me, was:
  
  Go to IIS Admin
  Rigth Click on Default Web Site
  Go to Operator Tab
  Add the ASPNET user on the list
  
  Works Fine!
  
  
  

• Anat Oren

  Which version of IIS Admin are you using

  Strangely enough I do not have this 'Operator' Tab.

  
  

• Jnnet

  Hi Daniel,

  I am running the following basic code for ASP.NET website project. Just a button and a label

  using System;

  using System.Data;

  using System.Configuration;

  using System.Web;

  using System.Web.Security;

  using System.Web.UI;

  using System.Web.UI.WebControls;

  using System.Web.UI.WebControls.WebParts;

  using System.Web.UI.HtmlControls;

  public partial class _Default : System.Web.UI.Page

  {

  protected void Page_Load(object sender, EventArgs e)

  {

  }

  protected void Button1_Click(object sender, EventArgs e)

  {

  Label1.Text = "Lets see if this works";

  }

  }

  When I run this from Debug->Start Without Debugging - I get the following error

  Server Error in '/WebSiteTest' Application.

• Arnie_Mac

  Hi.
  
  Had a similar problem and, following this thread, discovered that the culprit was re-installing IIS after installing .NET Framework 2.0.
  
  If this applies to you, you can fix the problem via Control Panel > Add/Remove Programs > Add/Remove .NET Framework 2.0 > Repair .Net Framework 2.0 (no need to reboot in my case).
  
  There are some other suggestions in that thread but none applied to me so I can't vouch for them. I suggest you try the above first as it appears to be the most straightforward of the solutions offered.
  
  --
  Hope that helps.
  Mark
  
  
  

• tripl3z3ro

  Thank you, this last fix worked wonderfully for me. Quick and simple.
  
  

• James Clark

  I fit the description for this thread very nicely, except there isn't an Operators tab in IIS 5.1 on Windows XP Pro.

  So there's no way to make the ASPNET account an "operator".

  Already spent over a day on this.

  Hint: Adding ASPNET to the Adminsitrators group "works", but I'd rather not make this a permanent solution.

  Unfortunately "Failed to access IIS metabase" doesn't say exactly what resource had the problem (metabase.bin, or some folder associated with the metabase).

  
  
  

• Padmaja B

  The above tweak worked for me too on windows 2000 server.

  Would be interested to know any side affects of doing the above..as earlier only administrators are the only group specified as operators.

  
  
• Failed to access IIS metabase