Re: userName="machine" didn't work
- From: "Juan T. Llibre" <nomailreplies@xxxxxxxxxxx>
- Date: Tue, 23 Jan 2007 15:44:07 -0400
I hate to tell you this, but you have conflicting ASP.NET versions
installed on your computer, including a beta version :
Version Information: Microsoft .NET Framework Version:2.0.50727.42;
ASP.NET Version:2.0.50727.210
That could very well be the source of your problems.
You should try to resolve that by uninstalling all currently installed 2.0
versions of the .Net Framework, and reinstalling the released version
( the redistributable will do fine ).
Get the 32-bit redistributable at :
http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en
If you have a 64-bit machine, there's a link
at the bottom of that page for the 64-bit versions.
re:
my machine.config looked like this after install:
<processModel autoConfig="true"/>
Odd...
Here's what my machine.config entry for processModel looks like :
<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="00:00:05"
requestLimit="Infinite" requestQueueLimit="5000" restartQueueLimit="10" memoryLimit="60"
webGarden="false" cpuMask="0xffffffff" userName="machine" password="AutoGenerate" logLevel="Errors"
clientConnectedCheck="00:00:05" comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:03:00" responseRestartDeadlockInterval="00:03:00" autoConfig="true"
maxWorkerThreads="20" maxIoThreads="20" minWorkerThreads="1" minIoThreads="1"
serverErrorMessageFile="" pingFrequency="Infinite" pingTimeout="Infinite" maxAppDomains="2000" />
If you are set on using a Windows or a domain account,
instead of the default provided, you can run :
aspnet_regiis -ga <WindowsUserAccount>
substituting the Windows or domain user account you write
into the processModel section of machine.config.
That will grant read access to the IIS metabase to the account specified.
*However* ( and I stress this ), uninstalling all versions of ASP.NET 2.0
(including the Beta Version:2.0.50727.210 which you currently have installed,
and installing just the released version ( 2.0.50727.42 ) should have you in
clover in almost no time at all.
The release version's install routine will set you up with
a correct processModel configuration you can use.
Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Joe Rattz" <JoeRattz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3DF1E427-6936-4741-A9F5-69B32E439211@xxxxxxxxxxxxxxxx
Thanks for responding. Boy, you really had me excited that specifying the
userName as machine was going to solve my problem, but it didn't.
First, let me mention that the processModel section of my machine.config
looked like this after install:
<processModel autoConfig="true"/>
Was I supposed to know to add the userName attribute? Or did something not
install properly? The only reason I know of the userName attribute is from
the research I did trying to resolve this problem. My assumption was that by
leaving it off, it would default to ASPNET.
Regardless, I tried what you suggested, and it didn't work. Here is what my
processModel section looked like:
<processModel userName="machine" password="AutoGenerate" autoConfig="true"/>
Here is the exact error:
Server Error in '/Northwind' Application.
--------------------------------------------------------------------------------
Failed to access IIS metabase.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
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). For information on modifying metabase
permissions, please see http://support.microsoft.com/?kbid=267904.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[HostingEnvironmentException: Failed to access IIS metabase.]
System.Web.Configuration.MetabaseServerConfig.MapPathCaching(String
siteID, VirtualPath path) +3500378
System.Web.Configuration.MetabaseServerConfig.System.Web.Configuration.IConfigMapPath.MapPath(String
siteID, VirtualPath vpath) +9
System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath
virtualPath, Boolean permitNull) +163
System.Web.CachedPathData.GetConfigPathData(String configPath) +382
System.Web.CachedPathData.GetConfigPathData(String configPath) +243
System.Web.CachedPathData.GetApplicationPathData() +68
System.Web.CachedPathData.GetVirtualPathData(VirtualPath virtualPath,
Boolean permitPathsOutsideApp) +3393699
System.Web.Configuration.RuntimeConfig.GetLKGRuntimeConfig(VirtualPath
path) +189
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET
Version:2.0.50727.210
.
- Follow-Ups:
- Re: userName="machine" didn't work
- From: Joe Rattz
- Re: userName="machine" didn't work
- References:
- Re: "Failed to access IIS metabase." error with ASP.NET 2.0
- From: Juan T. Llibre
- userName="machine" didn't work
- From: Joe Rattz
- Re: "Failed to access IIS metabase." error with ASP.NET 2.0
- Prev by Date: Re: How to customize "server too busy" error page?
- Next by Date: Re: [Ann] Yet another Ajax Widgets library...
- Previous by thread: userName="machine" didn't work
- Next by thread: Re: userName="machine" didn't work
- Index(es):
Relevant Pages
|
