BTW, I'm sure that lots of people experience problems with IIS that
look similar and come up with the same search query, but I pretty much
ignore them because I doubt there is some common underlying "problem"
within IIS causing them. Because if it was a common problem, it would
be well known by now.
In my experience, just about all these "problems" end up being caused
by user-specific circumstances outside of IIS. Random file corruption
on the hard drive. Random system configuration changes unknown to the
user and uncontrollable by IIS. Etc. That's not to say that IIS does
not have setup bugs, but those are well known.
I find the largest cause of mysterious IIS "failures" to be related to
Personal Security programs attempting to corrupt and otherwise hinder
IIS from functioning on XP Pro. Or some security lockdown from Group
Policy. Or people claiming the "default images" that their
organizations give them access to is "default" when it is far from it.
They all look like "IIS is not working" and are pretty hard to detect
and correct.
The only sure approach is to simply debug the symptoms and hopefully
something obvious emerges. Since we are dealing with arbitrary changes
in the system, the solution may be as arbitrary as reinstalling the OS
at the most extreme.
"Cassini working" adds nothing because you already said HTML serves
fine, which tells me IIS is working fine to handle HTTP protocol --
which is all Cassini does -- so there is no net-gain of information.
If you want to troubleshoot, then please provide the information I
asked for.
- search through %windir%\IIS6.log to look for "fail" (as the top of
that log file suggests). I want to verify if there was a setup failure
which you skipped over
- You may want to indicate what does happen when you try to run ASP.Net
apps, and what happens when you try to run ASP apps. The Error response
page returned from trying to run those apps, as well as IIS log entries
corresponding to the failing requests will be useful. As well as any
event log messages during the requests. And you want to configure
ASP.Net to dump detailed custom errors.
Don't bother making random configuration changes or run programs to
troubleshoot because that's just blind guessing and can hinder
troubleshooting by destroying system state and make a hard problem even
harder.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
d_elph wrote:
> David, Thank you for your reply.
>
> HP did install Norton antivirus on that PC, which I removed,
> reinstalled IIS, ran aspnet_regiis, etc.., but it didn't help. IIS runs
> html files but doesn't run asp.net apps.
> BTW, based on my googling it seems like lots of people experience the
> same problem, I just couldn't find the solution.
> Cassini web server runs fine on this PC.
> Any suggestions?
>
> Thank you
>
> Vadim
>
>
> David Wang wrote:
> > Something running on your computer corrupted IIS configuration or
> > setup. Has nothing to do with w3svc.dll. Check %windir%\IIS6.log for
> > any "fail" in the log file.
> >
> > You'll need to check if your computer manufacturer supports running IIS
> > on your PC - many PC manufacturers or Personal Security software like
> > McAfee/Symantec intentionally disable IIS from functioning on XP Pro.
> > So, you need to determine if you are affected by that decision and if
> > you are affected, either find a PC that is not affected or ask your PC
> > manufacturer how to fix it.
> >
> > IIS runs perfectly well on XP Media Center published by Microsoft.
> > However, since most PC manufacturers customize/restrict Windows and
> > then resell their versions as "Microsoft Windows", you have to ask your
> > PC manufacturer why this does not work. They may give you run-arounds,
> > etc, but the facts are that it worked when Microsoft handed it to the
> > PC manufacturers, but it doesn't work when PC manufacturers handed it
> > to you...
> >
> >
> >
> > //David
> > http://w3-4u.blogspot.com
> > http://blogs.msdn.com/David.Wang
> > //
> >
> >
> >
> > Vadim wrote:
> > > Hi,
> > >
> > > I am installing my development stuff on a brand new windows xp media center
> > > machine.
> > > I have a strange problem with IIS, it refuses to run any aspx page, bombs
> > > out with 500 Internal error:
> > >
> > > I have found the following error in the Event viewer: Event ID 36
> > > 'The server failed to load application /LM/w3svc. The error was: the
> > > specified metadata was not found.
> > >
> > > Both IIS and w3svc.dll are ver. 5.1.2600.2180.
> > >
> > > Can anybody please advise on how to solve this?
> > >
> > > Thank you,
> > >
> > > Vadim >> Stay informed about: IIS problem on Win XP: can no tload w3svc.dll 
FAQ
Profile
Private Messages
Log in
