Olga,
If your server is crashing or hanging you might want to
download our ReJuvin8 tool. It's free for the first
15-days. It can keep your site running despite problems.
It's designed to detect problems then restart or reboot.
It can restart ANY programs, services, or processes in
precise order. It doesn't fix bugs but it does give you some
breathing room while you are finding them. ReJuvin8 also
gives you email and telephone alert messages and graphic
status reports.
It can also test, alert, and report on URLs running anywhere
on any server on your net connection. So if you use multiple
servers you can use them to watch each other, too.
ReJuvin8 has both an automatic and a custom mode. In the
auto mode you make all the settings by pointing and
clicking. This will handle most applications.
The custom mode uses heartbeat synch files to get absolute
detection that key processes are working. Tools and
instructions are provided to help you do this. We also offer
customization as a contract service.
Charles
Get ReJuvin8 at: <a style='text-decoration: underline;' href="http://www.rejuvin8.net?ac=ch1" target="_blank">http://www.rejuvin8.net?ac=ch1</a>
"Olga" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:C4395241-0219-403A-8162-0408094012B2@microsoft.com...
> I got a responce on my message posted earlier:"This log has not running
ASP pages (hung or otherwise). So, either the
> pages are running in MTX.exe (i.e. OOP) or the service had been restarted
before IISState was run."
>
> We had to reboot our web rever once again. This time I made sure I ran
iisstate first and then rebooted the server. I ran iisstate on InetInfo.exe
and on mtx.exe. Could anybody please help to identify what the problem is
from the log files?
> Thanks, Olga
> Opened log file 'C:\iisstate\output\IISState-110.log'
>
> ***********************
> Starting new log output
> IISState version 3.2
>
> Mon Nov 17 13:36:49 2003
>
> OS = NT4
> Executable: inetinfo.exe
> PID = 110
>
> Note: Thread times are formatted as HH:MM:SS.ms
>
> ***********************
> Thread ID: 0
> System Thread ID: 64
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.10
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0006fd44 77f0d291 ntdll!NtReadFile+0xb
> 01 0006fdb0 77dd8a35 KERNEL32!ReadFile+0x1a6
> 02 0006fde4 77dd8481 ADVAPI32!ScGetPipeInput+0x28
> 03 0006fe48 77dd829e ADVAPI32!ScDispatcherLoop+0x46
> 04 0006fe6c 0100182c ADVAPI32!StartServiceCtrlDispatcherA+0x82
> 05 0006fea4 010015d5 inetinfo!StartDispatchTable+0x61
> 06 0006ff70 01001e7f inetinfo!main+0x2a5
> 07 0006ffc0 77f1bb7c inetinfo!mainCRTStartup+0xff
> 08 0006fff0 00000000 KERNEL32!BaseProcessStart+0x40
>
> Thread ID: 1
> System Thread ID: 6d
> Kernel Time: 0:0:0.30
> User Time: 0:0:0.110
> Thread Status: Thread is in a WAIT state.
> Thread Type: Other
> # ChildEBP RetAddr
> 00 0085fe2c 77f1cf95 ntdll!NtWaitForSingleObject+0xb
> 01 0085fe54 77f04f44 KERNEL32!WaitForSingleObjectEx+0x73
> 02 0085fe64 683a18fe KERNEL32!WaitForSingleObject+0xf
> 03 0085fe80 0100175d iisadmin!ServiceEntry+0x11b
> 04 0085ffa8 77dd8c15 inetinfo!InetinfoStartService+0xfb
> 05 0085ffb8 77f04eeb ADVAPI32!ScSvcctrlThreadA+0xe
> 06 0085ffec 00000000 KERNEL32!BaseThreadStart+0x51
>
> Thread ID: 2
> System Thread ID: c9
> Kernel Time: 0:0:0.80
> User Time: 0:0:0.0
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
for INFOCOMM.dll -
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00dffd28 77f1d15e ntdll!ZwWaitForMultipleObjects+0xb
> 01 00dffd80 77e7ae4d KERNEL32!WaitForMultipleObjectsEx+0xef
> 02 00dffddc 77e7ae92 USER32!MsgWaitForMultipleObjectsEx+0x127
> 03 00dffdf8 685992a3 USER32!MsgWaitForMultipleObjects+0x1d
> WARNING: Stack unwind information not available. Following frames may be
wrong.
> 04 0023e604 00000000 INFOCOMM!IIS_SERVICE::StartServiceOperation+0xd4
>
> Thread ID: 3
> System Thread ID: 31
> Kernel Time: 0:0:0.30
> User Time: 0:0:0.270
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
for ISATQ.dll -
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00e3fe9c 77f1d15e ntdll!ZwWaitForMultipleObjects+0xb
> 01 00e3fef4 77e7ae4d KERNEL32!WaitForMultipleObjectsEx+0xef
> 02 00e3ff50 77e7ae92 USER32!MsgWaitForMultipleObjectsEx+0x127
> 03 00e3ff6c 68624ab9 USER32!MsgWaitForMultipleObjects+0x1d
> WARNING: Stack unwind information not available. Following frames may be
wrong.
> 04 00000001 00000000 ISATQ!ScheduleAdjustTime+0x116
>
> Thread ID: 4
> System Thread ID: 5b
> Kernel Time: 0:0:0.10
> User Time: 0:0:0.30
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00e7fe9c 77f1d15e ntdll!ZwWaitForMultipleObjects+0xb
> 01 00e7fef4 77e7ae4d KERNEL32!WaitForMultipleObjectsEx+0xef
> 02 00e7ff50 77e7ae92 USER32!MsgWaitForMultipleObjectsEx+0x127
> 03 00e7ff6c 68624ab9 USER32!MsgWaitForMultipleObjects+0x1d
> WARNING: Stack unwind information not available. Following frames may be
wrong.
> 04 00000001 00000000 ISATQ!ScheduleAdjustTime+0x116
>
> Thread ID: 5
> System Thread ID: 4d
> Kernel Time: 0:0:0.20
> User Time: 0:0:0.10
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00ebff54 77f0c2a0 ntdll!NtRemoveIoCompletion+0xb
> 01 00ebff84 686272c6 KERNEL32!GetQueuedCompletionStatus+0x27
> WARNING: Stack unwind information not available. Following frames may be
wrong.
> 02 00ebffb8 77f04eeb ISATQ!AtqBandwidthGetInfo+0x5e6
> 03 00ebffec 00000000 KERNEL32!BaseThreadStart+0x51
>
> Thread ID: 6
> System Thread ID: cf
> Kernel Time: 0:0:0.170
> User Time: 0:0:0.270
> Thread Type: HTTP Listener
> # ChildEBP RetAddr
> 00 00efff54 77f0c2a0 ntdll!NtRemoveIoCompletion+0xb
> 01 00efff84 686272c6 KERNEL32!GetQueuedCompletionStatus+0x27
> WARNING: Stack unwind information not available. Following frames may be
wrong.
> 02 00efffb8 77f04eeb ISATQ!AtqBandwidthGetInfo+0x5e6
> 03 00efffec 00000000 KERNEL32!BaseThreadStart+0x51
>
> Thread ID: 7
> System Thread ID: d0
> Kernel Time: 0:0:0.0
> User Time: 0:0:0.0
> Thread Type: Other
> # ChildEBP RetAddr
> 00 00f3ff30 77f1d15e ntdll!ZwWaitForMultipleObjects+0xb
> 01 00f3ff88 685a7e98 KERNEL32!WaitForMultipleObjectsEx+0xef
> WARNING: Stack unwind information not available. Following frames may be
wrong.
> 02 685b35a0 000b55e8 INFOCOMM!TS_OPEN_FILE_INFO::MakeStrongETag+0x7eb
> 03 00096b10 685b35a0 0xb55e8
> 04 00097320 00096b10 INFOCOMM!MB::GetMultisz+0x649c
> 05 00097af8 00097320 0x96b10
> 06 000982d0 00097af8 0x97320
> 07 00098aa8 000982d0 0x97af8
FAQ
Search
Profile
Private Messages
Log in
