IISState Not Logging?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Paul Widner (paul_widner_at_hotmail.com)
Date: 09/09/04 

Date: Thu, 9 Sep 2004 08:26:34 -0700

We've been having problems with the IISState debugger. We have it running
on two web servers. Both machines have had IIS crashes several times since
we started using the debugger, but we haven't gotten any debug output. We
go to look at the directories after the crashes and there are no dump files.
I checked the permissions on the directories, and "everyone" has full
access. I also checked the console output and the debugger is running and
seeing events happen. We are using the correct command-line to start it:

iisstate -p <pid> -d -hc -sc

Any thoughts?

Thanks,
Paul Widner

Relevant Pages

  • Re: Remote debugging from Vista to XP64
    ... these two machines for the local VS debugger and "Visual Studio Remote ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.debugging)
  • [Full-Disclosure] Trustworthy Computing Mini-Poll
    ... TCPA won't help the spam situation. ... Only specially licensed machines can run a debugger. ... Why on earth would I pay money for such a deliberately, ...
    (Full-Disclosure)
  • Re: Breakpoints not working in VS 2003 using VB.
    ... the first time this has happened. ... breakpoints encountered trigger, but after that, none of my other breakpoints ... Also, when the breakpoints stop working, the debugger seems to lose ... The had replaced the old machines with new ones, because of debugging problems similar to your problems with the old machines that were not that old. ...
    (microsoft.public.dotnet.general)
  • Debugger GUI only working on some machines
    ... Three of us are attempting to use the debugger on our own machines ... run theProgram.exe - The GUI flashes up on the screen and goes away ... two showed no differences), the logicals look the same, the .exes and ...
    (comp.os.vms)
  • Re: panic: vm_fault: fault on nofault entry, addr: fffffe0007e8e000
    ... > machines (these packages build successfully if I retry): ... Debugger() at Debugger+0x38 ...
    (freebsd-current)