Re: "Failed to access IIS metabase." error with ASP.NET 2.0



What happens if you use "machine" for the username ?

userName="machine" password="AutoGenerate"

?

You can't just omit the username, btw.
You need *some* user identified as the user.

If you wish to, you can use a domain account:

<processModel userName="domain\username" password="password" />

This must be a domain account, but remember that both the
Web server and the database server will need to authenticate that user.

Setting the username to "machine" should work fine in most scenarios.



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:FB72854A-1190-45AF-A405-FC082DC3DAB9@xxxxxxxxxxxxxxxx
I am getting the "Failed to access IIS metabase." error message trying to hit
an ASP.NET 2.0 application on my development box.

I installed things in the natural order. I can't recall if I installed IIS
(5.1) before or after .NET 1.1 and Visual Studion 2003 (installed 3 years
ago), but this same box had (and still has) ASP.NET 1.1 applications that run
just fine.

Recently, I installed Visual Studio 2005. When I hit an ASP.NET 2.0
application I get the "Failed to access IIS metabase." error message.

If I set the userName to SYSTEM in the processModel of the machine.config
file, the appliaction works just fine. Omitting the userName attribute gives
me the error. From reading other posts, this is indicative of a permissions
problem. So, without specifying the userName, I tried the application while
running filemon, but I don't see any file access getting denied like I
expected to see based on the posts I have read.

I have run:

aspnet_regiis -i

and

aspnet_regiis -ga ASPNET

and neither of them resolves the problem. I have also tried uninstalling
and reinstalling .NET 2.0, as well as a repair install, and that didn't fix
anything either.

What do I do next?

Thanks!


.



Relevant Pages

  • Re: Trend CSM 3.0 will not push to XP clients
    ... "hillservices\administrator does not have administrator privileges" and If I ... The username and/or password may be invalid...." ... >> was trying to install to an XP Pro SP2 client with the Microsoft Firewall ... >> or the target computer is running Windows XP using simple file sharing. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend CSM 3.0 will not push to XP clients
    ... The username and/or password may be ... >>> and I am trying to remotely install to XP Pro SP2 clients using the ... >>> was trying to install to an XP Pro SP2 client with the Microsoft ... >>> or the target computer is running Windows XP using simple file sharing. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend CSM 3.0 will not push to XP clients
    ... Hi Greg when you enter the username are you entering it in the form ... > and I am trying to remotely install to XP Pro SP2 clients using the ... > was trying to install to an XP Pro SP2 client with the Microsoft Firewall ... > the target computer is running Windows XP using simple file sharing. ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS 4 Security
    ... >password protected web site is hosted using IIS 4 w/o ... If it is IIS4 totally unpatched, ... definitely buffer overflows in every http method in a stock install of IIS4 ... >require username and pass then a malformed URL will be ...
    (Focus-Microsoft)
  • Re: "not installed for the current user" error:Office suddenly wont o
    ... the simplest solution is to uninstall all ... log off your user account. ... three visible ones should be "all users", "your old username", "the new ... Install office and the problem should be fixed. ...
    (microsoft.public.office.misc)