RE: IIS won't load ASP.NET, "specified metadata not found"

From: Lowell (Lowell_at_discussions.microsoft.com)
Date: 11/19/04 

Date: Thu, 18 Nov 2004 22:05:06 -0800

Good try, thanks!

But, been there, done that. I've also "repaired" the VS installation and
all it's prerequisites.

I have managed to get it working on another, somewhat similar system (same
OS, etc, different hardware) so I could do a copy--if I could figure out what
needed to get copied. What and where is this "metadata" anyway?

Thanks!

Lowell

"MikeL" wrote:

> Try uninstalling and reinstalling IIS. If that doesn't work, there may be
> some tools to rebuild a default metabase.
>
> "Lowell" wrote:
>
> > Windows XP SP2 + Symantec AV + VS 2003 with .NET Framework 1.1
> >
> > IIS won't load or run existing ASP.NET applications and VS can't create or
> > load web projects (HTTP/1.1 500 Server Error).
> >
> > Event System log shows a warning with the following attributes: User: N/A,
> > Source: W3SVC, Category: None, Event ID: 36, Description: The server failed
> > to load application '/LM/W3SVC'. The error was 'The specified metadata was
> > not found.'
> >
> > I found the MSDN articles for VS 6.0 and when you are trying to run both 1.0
> > and 1.1 Frameworks at the same time. Neither appears to apply in this case.
> > The mfc42.dll has the correct permissions ("Read & Execute" for
> > "IWAM_<Computername>") and I'm not using Framework 1.0 (although there is
> > that rump group of four files in the
> > <Windir>\Microsoft.NET\Framework\v1.0.3705 directory.
> >
> > The company I work for recently had us run some home-grown software to
> > "lock-down" our systems--I also had some other issues come up.
> > Unfortunately, that made it so I couldn't even load and run web pages that
> > had been working for months. Anyway, I've worked through almost everything
> > and I think this is the last issue.
> > --
> > Lowell

Relevant Pages

  • Re: Cant get past the "Welcome" screen
    ... but doesn't correct the registry damage. ... Userinit string value should be: ... Another "quickie" method of resolution is to load the Recovery Console (see ... This is particularly useful if you have an OEM installation ...
    (microsoft.public.windowsxp.general)
  • Re: Unable to log into account
    ... but doesn't correct the registry damage. ... Userinit string value should be: ... Another "quickie" method of resolution is to load the Recovery Console (see ... This is particularly useful if you have an OEM installation ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Cannot log in to a user
    ... The userinit value may have been corrupted by ... system registry, sometimes appending it, sometimes replacing it. ... Another "quickie" method of resolution is to load the Recovery Console (see ... This is particularly useful if you have an OEM installation ...
    (microsoft.public.windowsxp.basics)
  • Re: Help! XP will NOT Boot up!
    ... broken installation and change the CrashControl AutoReboot registry value. ... On the Registry menu, click Load Hive, and then open the System hive ... Control Set will be loaded depending on which boot option is chosen. ... The system just reverts back to the rebooting sequence. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Windows XP Sign on
    ... The userinit value may have been corrupted by ... system registry, sometimes appending it, sometimes replacing it. ... Another "quickie" method of resolution is to load the Recovery Console (see ... This is particularly useful if you have an OEM installation ...
    (microsoft.public.windowsxp.general)