IIS State as Schedules Task

No of course not, but it will as long as it is not restarted and that is all
that matters. The only way to run IISState on a server that you control via
TS is by configuring it as a scheduled task. The process will first change
after IIS crashes and then I have the info I need.


"Jerry III" <jerryiii RemoveThis @hotmail.com> wrote in message
news:%23WYTZ8zrDHA.2464@TK2MSFTNGP12.phx.gbl...
 > Do you REALLY think IIS will always have the same process id?
 >
 > Jerry
 >
 > "ja" <na RemoveThis @noemail.com> wrote in message
 > news:OmXFq3trDHA.2464@TK2MSFTNGP12.phx.gbl...
  > > Why doesn't the following work in scheduler? Is my syntax incorrect?
  > >
  > > "C:\winnt\system32\cmd.exe C:\iisstate\iisstate -p 3204 -hc"
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS State as Schedules Task 

But iisstate is nothing but a simple debugger and it will take IIS down
every time it runs. So it will get a new process id after the first run (you
can't detach a debugger in Win32). If you want to get the info at a crash
time you need to setup iisstate as a debugger for that process so it's
called when it crashes. And I'm not sure if you can setup a debugger on a
per-process basis.

Jerry

"ja" <na.RemoveThis@noemail.com> wrote in message
news:#zif0F3rDHA.2304@tk2msftngp13.phx.gbl...
 > No of course not, but it will as long as it is not restarted and that is
all
 > that matters. The only way to run IISState on a server that you control
via
 > TS is by configuring it as a scheduled task. The process will first change
 > after IIS crashes and then I have the info I need.
 >
 >
 > "Jerry III" <jerryiii.RemoveThis@hotmail.com> wrote in message
 > news:%23WYTZ8zrDHA.2464@TK2MSFTNGP12.phx.gbl...
  > > Do you REALLY think IIS will always have the same process id?
  > >
  > > Jerry
  > >
  > > "ja" <na.RemoveThis@noemail.com> wrote in message
  > > news:OmXFq3trDHA.2464@TK2MSFTNGP12.phx.gbl...
   > > > Why doesn't the following work in scheduler? Is my syntax incorrect?
   > > >
   > > > "C:\winnt\system32\cmd.exe C:\iisstate\iisstate -p 3204 -hc"
   > > >
   > > >
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS State as Schedules Task 

In my case it only takes IIS down when there is a hard crash (I have set
the -hc attribute) and when that happens IIS restarts anyway.
My IIS crashes aproximately once every 24 hours and I suspected a DLL that I
have installed, but just wanted to confirm it.
I actually got lucky and confirmed my suspision by logging on with my
servers RAC and staying logged on while running IIS State on the process in
question.

"Jerry III" <jerryiii DeleteThis @hotmail.com> wrote in message
news:eEd9KT4rDHA.2360@TK2MSFTNGP09.phx.gbl...
 > But iisstate is nothing but a simple debugger and it will take IIS down
 > every time it runs. So it will get a new process id after the first run
(you
 > can't detach a debugger in Win32). If you want to get the info at a crash
 > time you need to setup iisstate as a debugger for that process so it's
 > called when it crashes. And I'm not sure if you can setup a debugger on a
 > per-process basis.
 >
 > Jerry
 >
 > "ja" <na DeleteThis @noemail.com> wrote in message
 > news:#zif0F3rDHA.2304@tk2msftngp13.phx.gbl...
  > > No of course not, but it will as long as it is not restarted and that is
 > all
  > > that matters. The only way to run IISState on a server that you control
 > via
  > > TS is by configuring it as a scheduled task. The process will first
change
  > > after IIS crashes and then I have the info I need.
  > >
  > >
  > > "Jerry III" <jerryiii DeleteThis @hotmail.com> wrote in message
  > > news:%23WYTZ8zrDHA.2464@TK2MSFTNGP12.phx.gbl...
   > > > Do you REALLY think IIS will always have the same process id?
   > > >
   > > > Jerry
   > > >
   > > > "ja" <na DeleteThis @noemail.com> wrote in message
   > > > news:OmXFq3trDHA.2464@TK2MSFTNGP12.phx.gbl...
   > > > > Why doesn't the following work in scheduler? Is my syntax incorrect?
   > > > >
   > > > > "C:\winnt\system32\cmd.exe C:\iisstate\iisstate -p 3204 -hc"
   > > > >
   > > > >
   > > >
   > > >
  > >
  > >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS State as Schedules Task