RE: "Failed to access IIS metabase" on XP
- From: "Clint" <cmueller@xxxxxxxxxxxxx>
- Date: Fri, 10 Feb 2006 07:47:30 -0800
Steven,
I'm sorry, I made a mistake in my previous post. If I grant ASPNET
permissions to metabase.bin, the applications still error with the "Failed to
access..." error. I forgot to remove ASPNET from the Administrators group
when I ran that test.
The programs still run if aspnet_wp runs as SYSTEM, though.
Clint
"Steven Cheng[MSFT]" wrote:
Hi Clint,.
Welcome to the ASPNET newsgroup.
From your description, you've originally installed ASP.NET 1.0 and 1.1 on
your XP machine which works correctly. After you installed .net framework
2.0/ASP.NET 2.0 on it, any ASP.NET applications no longer work and report
"Failed to access IIS metabase..." error. Also, if you remove ASP.NET 2.0,
the 1.0 and 1.1 web application can work correctly. If there is anything I
misunderstand, please feel free let me know.
Based on my experience, the problem is likely involved by the new installed
.net framework 2.0 and should be a environment specfic issue. Before you
perform a thorough reinstall, I think we can try the following steps:
1. Revert the machine to your original status(remove the 2.0 and ensure 1.0
and 1.1 works), then reinstall the .net framework 2.0 and configure the
default site to use 2.0 (perform iisreset).
2. After that try run a simple asp.net 2.0 web page at IIS root site to see
whether it report the same error.
3. If the same error occur, try change the ASP.NET worker process account
from the default "machine\ASPNET" account to Local System account. This can
be configured in machine.config(in .net 2.0's framework folder) through the
<processModel> element. Since 2.0 hidden the default configuration for
<processModel> you need to explicitly add the configuration (just change
the username attribute to "SYSTEM"). Here is the msdn reference which have
mentioend the .net 2.0's default configuration of <processModel>, you can
modify the machine.config according to it:
#processModel Element (ASP.NET Settings Schema)
http://msdn2.microsoft.com/en-us/library/7w2sway1.aspx
After change the machine.config, save and perform IIS reset, after that,
try running the asp.net web app again.
4. If still not work, this is not likely a simple permission issue and
there may has some serious problem with the .net 2.0's intallation. If it
start work, the problem is likely a permission issue, so that we can swtich
back the processModel setting and try using filemon tool to monitor the
file access failures to find the file which cause the permission error.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
- Follow-Ups:
- RE: "Failed to access IIS metabase" on XP
- From: Steven Cheng[MSFT]
- RE: "Failed to access IIS metabase" on XP
- References:
- RE: "Failed to access IIS metabase" on XP
- From: Steven Cheng[MSFT]
- RE: "Failed to access IIS metabase" on XP
- Prev by Date: RE: "Failed to access IIS metabase" on XP
- Next by Date: Re: get an output value from a stored procedure using sqlDataSource
- Previous by thread: RE: "Failed to access IIS metabase" on XP
- Next by thread: RE: "Failed to access IIS metabase" on XP
- Index(es):
Relevant Pages
|