Failed to access IIS metabase, VS2005 RC

Failed to access IIS metabase, VS2005 RC

• Hristo Serafimov

  I had the same problem : I installed VS (and .NET framework) before installing IIS and just reparing the .NET framework from the add/remove program worked without having to unistall and reinstall. Try repairing firt .. it may save you some time.
  

• gps

  Make sure that Windows Authentication is enabled for the Virtual Directory in IIS.  You will get this error if it is unchecked.  To see if it's enabled, click on the Directory Security tab, click Edit under Access control, and place a check in the Intergrated Windows Security box.  You MUST restart IIS for the changes to take effect!
  
  

• gagandce

  Hi,
  in my case this error was caused by the fact that i had installed IIS AFTER .NET2.0 . Therefore the rights of the ASPNET user had not been set correctly.
  I fixed this by uninstalling (not repairing) the .NET Framework completely and then reinstalling it (no reboot necessary on WinXP). After that i had to set :NET 2.0 again as the Standard .NET Version in IIS and my error-message was gone.
  Hope this helps.
  
  greetings
  fenrir
  
  

• amzayle

  So annoying...
  
  I was trying to fix this on a Windows 2000,
  
  I think the Microsoft article did not dot help...
  C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ga ASPNET
  and a restart (looks like the utility did not take the command...)
  
  
  Eventually: IIS -> Web Site -> Operators -> Add -> ASPNET -> BINGO
  

  
  
  

• jms04081974

  Mark Fussell wrote:

  1) Is IIS installed on the machine (From a command prompt NET START - Is IIS Admin service present in the list) 2) Is ASP.NET installed  - Run aspnet_iisreg.exe /lv from the VS command line prompt 3) For 2) is the default install for ASP.NET v2.0 as opposed to v1.1 ( the running version is marked with the (root)value). If not then then run aspnet_iisreg.exe /i /e If none of the above can you provide more info Thanks. Mark Fussell WSE Program Manager

  
  
  Not to be nit-picky.. but this doesn't work..
  
  C:\WINNT\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis /i /e
  Some options specified are not compatible. Use aspnet_regiis / to see all options.
  

• Brian Patrick

  gameprix1,
  Thanks for the response. I checked Authentication Method Window for my IIS. The Intergated Windows Security box is checked. I think it is enabled as default. I also checked the Authentication mode in the ASP.NET Configuration Settings Window under the ASP.NET Tag in site properties. It is Window. It seems asp files work but not aspx files.
  Bong

  
  

• Cahyo Sasongko

  i face the same problem , but i have installed the .net framework after the iis ,
  and by the way , the time tracker sample is working very good and without any problem !
  

• tubefeed

  Mark,
  I am creating a test web site in my local W2K SP4 IIS with "the Microsoft Visual Studio 2005 Version 8.0.50727.7  (RTM.050727-0700) Microsoft .NET Framework Version 2.0.50727 Microsoft Visual Web Developer 2005 Express  76872-000-0000011-00123. I have the similar error message, "Failed to access IIS metabase"
   Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.
  The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC).
  Stack Trace:
  

  [HostingEnvironmentException: Failed to access IIS metabase.] System.Web.Configuration.MetabaseServerConfig.MapPathCaching(String siteID, VirtualPath path) +671 System.Web.Configuration.MetabaseServerConfig.System.Web.Configuration.IConfigMapPath.MapPath(String siteID, VirtualPath vpath) +9 System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull) +174 System.Web.CachedPathData.GetConfigPathData(String configPath) +395 System.Web.CachedPathData.GetConfigPathData(String configPath) +260 System.Web.CachedPathData.GetVirtualPathData(VirtualPath virtualPath, Boolean permitPathsOutsideApp) +166 System.Web.Configuration.RuntimeConfig.GetLKGRuntimeConfig(VirtualPath path) +187

  I visited the doc. http://support.microsoft.com/ kbid=267904. that was suggested by the error message. However, when I ran "aspnet_regiis –ga <WindowsUserAccount>" from Command Prompt, aspnet_regiis is not recognized.
  I downloaded and ran the metaacl.exe to add my account to the list and then restart the IIS, but I still have the problem.
  I also based on another web site to change the Machine.config
  <system.web>   <processModel autoConfig="true"/>  to
  <system.web>   <processModel userName="SYSTEM"/> 
  and restart IIS. I still have the same error message.
  
  Can you help
  
  Bong
  

• TigerMan90

  Where exactly is the "Operators" set up in IIS   I see no dialog to do so in IIS.
  

• TMHerring

  FWIW, I tried absolutely everything in this thread and a whole lot more. Nothing worked until I reinstalled the .NET Framework 2.0:
  Add/Remove Programs->Microsoft .NET Framework 2.0->Change/Remove->Reinstall.
  
  Despite the warning that I would need to reboot, it worked without doing so.
  
  YMMV
  
  -Wackyspat
  
  

• Wolfgang Rues

  Yovav wrote:

  So annoying... I was trying to fix this on a Windows 2000, I think the Microsoft article did not dot help... C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ga ASPNET and a restart (looks like the utility did not take the command...) Eventually: IIS -> Web Site -> Operators -> Add -> ASPNET -> BINGO

  
  
  Alright.. this works...
  
  Now tell me why.. because this feels like a nasty hacky kludge to me and a maintenance nightmare.
  
  The server is running Windows 2000 Server, has several deployed and working ASP 1.1 applications on it.
  
  The server also has several other web sites on it, some running ColdFusion MX.  ASP.Net 2.0 was installed on the machine. 
  
  I ran : aspnet_regiis -iru
  Then : aspnet_regiis -s W3SVC/1/Root/<appPath>
  
  The 1.1 applications continued to work fine.  The 2.0 application failed with the metabase error until ASPNet was made an operator for the site.  Afterwords, both the 1.1 applications and the 2.0 applications work fine.
  
  Why
  
  

• jamaddox

  I am sorry for the late response Mark, but I have been busy the last few days and have put this problem aside for a while. I did try your suggestions, but they did not help. I suspect the cause of the problem is that VS 2005 RC was installed before IIS. Now, I am awaiting the official release very soon, so I have decided to not care about this before that and install everything from scratch when I am getting the official release.

  
  
  

• Hans Geurtsen

  1. If that is the case, you can check a couple of these options.  It should all be there, but you never know!
     
  2. Right-click on the virtual directory (or Default Web Site), go to properties and click on the Configuration button.  Under the Mappings Tab, make sure .aspx and other .NET related extentions are listed.  If not, I believe you'll have to run the aspnet_regiis.exe utility.
     
  3. This shouldn't affect your problem, but it might.  Under the Documents Tab, it seems you have to manually add  index.aspx or default.aspx.  Again, this probably isn't causing your problem UNLESS you are not supplying the page name in the address bar when navigating.
     
  4. If you're using Windows 2003, make sure you've enabled ASP.NET in IIS Manager.
     
  5. Lastly, make sure the ASPNET account has proper rights for the directory and it's subs. 

  
  
  

• Mark Ramey

  1) Is IIS installed on the machine (From a command prompt NET START - Is IIS Admin service present in the list)
  2) Is ASP.NET installed  - Run aspnet_iisreg.exe /lv from the VS command line prompt
  3) For 2) is the default install for ASP.NET v2.0 as opposed to v1.1 ( the running version is marked with the (root)value). If not then then run aspnet_iisreg.exe /i /e
  
  If none of the above can you provide more info
  
  Thanks. Mark Fussell
  WSE Program Manager
  
  
• Failed to access IIS metabase, VS2005 RC