Pat
Mon May 10 10:31:34 CDT 2004
A hang is not a crash. A crash is a termination of the process.
So, run IISState as:
iisstate -p <pid of w3wp.exe> <enter>
Pat
"Nate Jones" <nate@natejones.net> wrote in message
news:a96401c4363f$6ff010e0$a501280a@phx.gbl...
> David,
>
> Thank you much for your quick reply. I did notice from
> searching the newsgroups, how many have commented on the
> use of IIS State. I have downloaded it, and will attempt
> to produce a dump to post here for others to look at, as
> you suggested.
>
> Also, thanks for taking the time to share your views on
> licensing and support. I would have to agree with you,
> as they are two seperate avenues.
>
> One thing I quickly noticed when reading through the IIS
> State help files is that it requires the PID of the IIS
> process. At present, I remotely control the server via
> RDC. However, when I login (as an admin), and view the
> Task Manager, many of the processes (including IIS) are
> not visible. Is this just a "feature" of RDC for
> security reasons? Or, is there a way to discover the PID
> of IIS using another method? From what I can see, with
> out the PID, IIS State cannot help me.
>
> Also, when IIS "locks up", as I have mentioned, would
> this be considered a hard crash ("hc") or a soft crash
> ("sc")?
>
> I can get physical access to the machine, with a bit of
> effort, but would prefer to simply manage it remotely, if
> possible.
>
> Thanks, again, for your time in replying. I hope to one
> day be on the same level as many who post here.
>
> -Nate
>
> 800-519-9091 Work
> 866-815-3366 Home
>
>
> >-----Original Message-----
> >You can use IIS State to diagnose what is causing IIS
> to "Lock up", and post
> >its log file here for analysis. This is the same sort
> of tool that
> >Microsoft PSS will ask you to run anyway; we allow you
> to do it yourself and
> >will even help you analyze what's going wrong and
> sometimes provide
> >workaround/fixes -- all for free.
> >
> >
http://www.iisfaq.com/default.aspx?view=P197
> >
> >My suspicion is that some of your web pages are slowly
> tying up IIS threads,
> >which over time results in IIS running out of resources
> to handle requests,
> >at which point you see it "lock up". We'll need to use
> IIS State to
> >diagnose what is actually tying up IIS, which can then
> help suggest how you
> >may fix the issue.
> >
> >The reason why you do not see any event messages
> about "locking up" is
> >simple -- it is theoretically impossible to detect a
> locking situation with
> >100% accuracy. I am not going to give you a false
> impression that it can be
> >done -- because any attempt will either have false
> positives or false
> >negatives -- even when users expect the impossible.
> Why? Let's just say
> >that it is not possible to distinguish from an external
> perspective between
> >a long-running operation that will eventually finish and
> another
> >long-running operation that is locked up. Only the
> thread that is doing the
> >operation can determine with 100% accuracy, but it's
> currently tied-up on
> >that long-running operation and cannot tell you whether
> it's locked or not.
> >
> >
> >FYI:
> >I feel compelled to say the following to clarify some of
> your
> >misconceptions. I do this with only positive intentions.
> >
> >A license to use a particular software does not imply
> support. It's like a
> >driver's license gives you the right to drive, but it
> doesn't mean the
> >license comes with a car to drive -- you still have to
> buy/maintain the car.
> >
> >In your case, you have constructed a custom server
> package after purchasing
> >the various licenses, so the assumption is that YOU will
> take care of
> >supporting the combination of server software. If you
> cannot... then you
> >either must pay some professionals (in this case, you
> chose Microsoft PSS
> >for some reason even when most of your software does not
> involve Microsoft),
> >or change your server package to a supported one that
> fits your needs.
> >
> >I mean, this is not different from any other industry --
> if you modify your
> >car engine, the assumption is that you are responsible
> for those
> >modifications... and if you find that you have engine
> knocks later on but
> >you cannot take care of it, then you either need to pay
> a car shop to take
> >care of it, or you get another car that has the
> modifications and is
> >supported.
> >
> >You cannot buy a car, make modifications, and expect the
> car manufacturer to
> >support your modifications for free...
> >
> >--
> >//David
> >IIS
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >//