|
Home > Archive > IIS Server > September 2004 > IIS Crashes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| zorko79 2004-09-22, 9:25 pm |
| Hi,
Our IIS 5.0 crashes without a reason now and then. Sometimes within an hour,
sometimes after a week. Have analyzed a dump file with windbg.
This is the result:
****************************************
************************************
***
* *
* Exception Analysis *
* *
****************************************
************************************
***
****************************************
*********************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
****************************************
*********************************
FAULTING_IP:
NTDLL!KiUserExceptionDispatcher+e
77f9ff6e 0ac0 or al,al
EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 77f96be3 (NTDLL!RtlDispatchException+0x00000006)
ExceptionCode: c00000fd (Stack overflow)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 01092ff4
BUGCHECK_STR: c00000fd
DEFAULT_BUCKET_ID: APPLICATION_FAULT
PROCESS_NAME: inetinfo.exe
ERROR_CODE: (NTSTATUS) 0xc00000fd - A new guard page for the stack cannot be
created.
RECURRING_STACK: From frames 0x1 to 0x4
THREAD_ATTRIBUTES:
LAST_CONTROL_TRANSFER: from 77f9ff6e to 77f96be3
STACK_TEXT:
01093058 77f9ff6e 01093070 0109308c 01093070 NTDLL!RtlDispatchException+0x6
01093058 64722d32 01093070 0109308c 01093070
NTDLL!KiUserExceptionDispatcher+0xe
WARNING: Frame IP not in any known module. Following frames may be wrong.
01093354 77f96ba7 01093418 010cf434 01093434 0x64722d32
01093378 77f96c42 01093418 010cf434 01093434 NTDLL!ExecuteHandler+0x26
01093400 77f9ff6e 01093418 01093434 01093418 NTDLL!RtlDispatchException+0x76
01093400 64722d32 01093418 01093434 01093418
NTDLL!KiUserExceptionDispatcher+0xe
010936fc 77f96ba7 010937c0 010cf434 010937dc 0x64722d32
01093720 77f96c42 010937c0 010cf434 010937dc NTDLL!ExecuteHandler+0x26
010937a8 77f9ff6e 010937c0 010937dc 010937c0 NTDLL!RtlDispatchException+0x76
010937a8 64722d32 010937c0 010937dc 010937c0
NTDLL!KiUserExceptionDispatcher+0xe
01093aa4 77f96ba7 01093b68 010cf434 01093b84 0x64722d32
01093ac8 77f96c42 01093b68 010cf434 01093b84 NTDLL!ExecuteHandler+0x26
01093b50 77f9ff6e 01093b68 01093b84 01093b68 NTDLL!RtlDispatchException+0x76
01093b50 64722d32 01093b68 01093b84 01093b68
NTDLL!KiUserExceptionDispatcher+0xe
01093e4c 77f96ba7 01093f10 010cf434 01093f2c 0x64722d32
01093e70 77f96c42 01093f10 010cf434 01093f2c NTDLL!ExecuteHandler+0x26
01093ef8 77f9ff6e 01093f10 01093f2c 01093f10 NTDLL!RtlDispatchException+0x76
01093ef8 64722d32 01093f10 01093f2c 01093f10
NTDLL!KiUserExceptionDispatcher+0xe
010941f4 77f96ba7 010942b8 010cf434 010942d4 0x64722d32
01094218 77f96c42 010942b8 010cf434 010942d4 NTDLL!ExecuteHandler+0x26
010942a0 77f9ff6e 010942b8 010942d4 010942b8 NTDLL!RtlDispatchException+0x76
010942a0 64722d32 010942b8 010942d4 010942b8
NTDLL!KiUserExceptionDispatcher+0xe
0109459c 77f96ba7 01094660 010cf434 0109467c 0x64722d32
010945c0 77f96c42 01094660 010cf434 0109467c NTDLL!ExecuteHandler+0x26
01094648 77f9ff6e 01094660 0109467c 01094660 NTDLL!RtlDispatchException+0x76
01094648 64722d32 01094660 0109467c 01094660
NTDLL!KiUserExceptionDispatcher+0xe
01094944 77f96ba7 01094a08 010cf434 01094a24 0x64722d32
01094968 77f96c42 01094a08 010cf434 01094a24 NTDLL!ExecuteHandler+0x26
010949f0 77f9ff6e 01094a08 01094a24 01094a08 NTDLL!RtlDispatchException+0x76
010949f0 64722d32 01094a08 01094a24 01094a08
NTDLL!KiUserExceptionDispatcher+0xe
01094cec 77f96ba7 01094db0 010cf434 01094dcc 0x64722d32
01094d10 77f96c42 01094db0 010cf434 01094dcc NTDLL!ExecuteHandler+0x26
01094d98 77f9ff6e 01094db0 01094dcc 01094db0 NTDLL!RtlDispatchException+0x76
01094d98 64722d32 01094db0 01094dcc 01094db0
NTDLL!KiUserExceptionDispatcher+0xe
01095094 77f96ba7 01095158 010cf434 01095174 0x64722d32
010950b8 77f96c42 01095158 010cf434 01095174 NTDLL!ExecuteHandler+0x26
01095140 77f9ff6e 01095158 01095174 01095158 NTDLL!RtlDispatchException+0x76
01095140 64722d32 01095158 01095174 01095158
NTDLL!KiUserExceptionDispatcher+0xe
0109543c 77f96ba7 01095500 010cf434 0109551c 0x64722d32
01095460 77f96c42 01095500 010cf434 0109551c NTDLL!ExecuteHandler+0x26
010954e8 77f9ff6e 01095500 0109551c 01095500 NTDLL!RtlDispatchException+0x76
010954e8 64722d32 01095500 0109551c 01095500
NTDLL!KiUserExceptionDispatcher+0xe
010957e4 77f96ba7 010958a8 010cf434 010958c4 0x64722d32
01095808 77f96c42 010958a8 010cf434 010958c4 NTDLL!ExecuteHandler+0x26
01095890 77f9ff6e 010958a8 010958c4 010958a8 NTDLL!RtlDispatchException+0x76
01095890 64722d32 010958a8 010958c4 010958a8
NTDLL!KiUserExceptionDispatcher+0xe
01095b8c 77f96ba7 01095c50 010cf434 01095c6c 0x64722d32
01095bb0 77f96c42 01095c50 010cf434 01095c6c NTDLL!ExecuteHandler+0x26
01095c38 77f9ff6e 01095c50 01095c6c 01095c50 NTDLL!RtlDispatchException+0x76
01095c38 64722d32 01095c50 01095c6c 01095c50
NTDLL!KiUserExceptionDispatcher+0xe
FOLLOWUP_IP:
NTDLL!KiUserExceptionDispatcher+e
77f9ff6e 0ac0 or al,al
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: NTDLL!KiUserExceptionDispatcher+e
MODULE_NAME: NTDLL
IMAGE_NAME: NTDLL.DLL
DEBUG_FLR_IMAGE_TIMESTAMP: 4060ef9b
STACK_COMMAND: .ecxr ; kb
BUCKET_ID: c00000fd_NTDLL!KiUserExceptionDispatcher
+e
Followup: MachineOwner
---------
Can anyone help me please....it is urgent!!
/Zorko
| |
| Paul King 2004-09-22, 9:25 pm |
| Whats your disk space usage like?
Also Im assuming your running IIS under NT judging by the log file - is this
updated to Sp3a?
Regards
Paul.
"zorko79" <zorko792002@yahoo.se> wrote in message
news:e56FjTKoEHA.3252@TK2MSFTNGP11.phx.gbl...
> Hi,
> Our IIS 5.0 crashes without a reason now and then. Sometimes within an
hour,
> sometimes after a week. Have analyzed a dump file with windbg.
>
> This is the result:
>
****************************************
************************************[vbc
ol=seagreen]
> ***
>
> * *
>
> * Exception Analysis *
>
> * *
>
>[/vbcol]
****************************************
************************************[vbc
ol=seagreen]
> ***
>
> ****************************************
*********************************
>
> *** ***
>
> *** ***
>
> *** Your debugger is not using the correct symbols ***
>
> *** ***
>
> *** In order for this command to work properly, your symbol path ***
>
> *** must point to .pdb files that have full type information. ***
>
> *** ***
>
> *** Certain .pdb files (such as the public OS symbols) do not ***
>
> *** contain the required information. Contact the group that ***
>
> *** provided you with these symbols if you need this command to ***
>
> *** work. ***
>
> *** ***
>
> *** Type referenced: ntdll!_PEB ***
>
> *** ***
>
> ****************************************
*********************************
>
> FAULTING_IP:
>
> NTDLL!KiUserExceptionDispatcher+e
>
> 77f9ff6e 0ac0 or al,al
>
> EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
>
> ExceptionAddress: 77f96be3 (NTDLL!RtlDispatchException+0x00000006)
>
> ExceptionCode: c00000fd (Stack overflow)
>
> ExceptionFlags: 00000000
>
> NumberParameters: 2
>
> Parameter[0]: 00000001
>
> Parameter[1]: 01092ff4
>
> BUGCHECK_STR: c00000fd
>
> DEFAULT_BUCKET_ID: APPLICATION_FAULT
>
> PROCESS_NAME: inetinfo.exe
>
> ERROR_CODE: (NTSTATUS) 0xc00000fd - A new guard page for the stack cannot[/vbcol]
be
> created.
>
> RECURRING_STACK: From frames 0x1 to 0x4
>
> THREAD_ATTRIBUTES:
>
> LAST_CONTROL_TRANSFER: from 77f9ff6e to 77f96be3
>
> STACK_TEXT:
>
> 01093058 77f9ff6e 01093070 0109308c 01093070
NTDLL!RtlDispatchException+0x6
>
> 01093058 64722d32 01093070 0109308c 01093070
> NTDLL!KiUserExceptionDispatcher+0xe
>
> WARNING: Frame IP not in any known module. Following frames may be wrong.
>
> 01093354 77f96ba7 01093418 010cf434 01093434 0x64722d32
>
> 01093378 77f96c42 01093418 010cf434 01093434 NTDLL!ExecuteHandler+0x26
>
> 01093400 77f9ff6e 01093418 01093434 01093418
NTDLL!RtlDispatchException+0x76
>
> 01093400 64722d32 01093418 01093434 01093418
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 010936fc 77f96ba7 010937c0 010cf434 010937dc 0x64722d32
>
> 01093720 77f96c42 010937c0 010cf434 010937dc NTDLL!ExecuteHandler+0x26
>
> 010937a8 77f9ff6e 010937c0 010937dc 010937c0
NTDLL!RtlDispatchException+0x76
>
> 010937a8 64722d32 010937c0 010937dc 010937c0
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01093aa4 77f96ba7 01093b68 010cf434 01093b84 0x64722d32
>
> 01093ac8 77f96c42 01093b68 010cf434 01093b84 NTDLL!ExecuteHandler+0x26
>
> 01093b50 77f9ff6e 01093b68 01093b84 01093b68
NTDLL!RtlDispatchException+0x76
>
> 01093b50 64722d32 01093b68 01093b84 01093b68
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01093e4c 77f96ba7 01093f10 010cf434 01093f2c 0x64722d32
>
> 01093e70 77f96c42 01093f10 010cf434 01093f2c NTDLL!ExecuteHandler+0x26
>
> 01093ef8 77f9ff6e 01093f10 01093f2c 01093f10
NTDLL!RtlDispatchException+0x76
>
> 01093ef8 64722d32 01093f10 01093f2c 01093f10
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 010941f4 77f96ba7 010942b8 010cf434 010942d4 0x64722d32
>
> 01094218 77f96c42 010942b8 010cf434 010942d4 NTDLL!ExecuteHandler+0x26
>
> 010942a0 77f9ff6e 010942b8 010942d4 010942b8
NTDLL!RtlDispatchException+0x76
>
> 010942a0 64722d32 010942b8 010942d4 010942b8
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 0109459c 77f96ba7 01094660 010cf434 0109467c 0x64722d32
>
> 010945c0 77f96c42 01094660 010cf434 0109467c NTDLL!ExecuteHandler+0x26
>
> 01094648 77f9ff6e 01094660 0109467c 01094660
NTDLL!RtlDispatchException+0x76
>
> 01094648 64722d32 01094660 0109467c 01094660
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01094944 77f96ba7 01094a08 010cf434 01094a24 0x64722d32
>
> 01094968 77f96c42 01094a08 010cf434 01094a24 NTDLL!ExecuteHandler+0x26
>
> 010949f0 77f9ff6e 01094a08 01094a24 01094a08
NTDLL!RtlDispatchException+0x76
>
> 010949f0 64722d32 01094a08 01094a24 01094a08
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01094cec 77f96ba7 01094db0 010cf434 01094dcc 0x64722d32
>
> 01094d10 77f96c42 01094db0 010cf434 01094dcc NTDLL!ExecuteHandler+0x26
>
> 01094d98 77f9ff6e 01094db0 01094dcc 01094db0
NTDLL!RtlDispatchException+0x76
>
> 01094d98 64722d32 01094db0 01094dcc 01094db0
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01095094 77f96ba7 01095158 010cf434 01095174 0x64722d32
>
> 010950b8 77f96c42 01095158 010cf434 01095174 NTDLL!ExecuteHandler+0x26
>
> 01095140 77f9ff6e 01095158 01095174 01095158
NTDLL!RtlDispatchException+0x76
>
> 01095140 64722d32 01095158 01095174 01095158
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 0109543c 77f96ba7 01095500 010cf434 0109551c 0x64722d32
>
> 01095460 77f96c42 01095500 010cf434 0109551c NTDLL!ExecuteHandler+0x26
>
> 010954e8 77f9ff6e 01095500 0109551c 01095500
NTDLL!RtlDispatchException+0x76
>
> 010954e8 64722d32 01095500 0109551c 01095500
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 010957e4 77f96ba7 010958a8 010cf434 010958c4 0x64722d32
>
> 01095808 77f96c42 010958a8 010cf434 010958c4 NTDLL!ExecuteHandler+0x26
>
> 01095890 77f9ff6e 010958a8 010958c4 010958a8
NTDLL!RtlDispatchException+0x76
>
> 01095890 64722d32 010958a8 010958c4 010958a8
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01095b8c 77f96ba7 01095c50 010cf434 01095c6c 0x64722d32
>
> 01095bb0 77f96c42 01095c50 010cf434 01095c6c NTDLL!ExecuteHandler+0x26
>
> 01095c38 77f9ff6e 01095c50 01095c6c 01095c50
NTDLL!RtlDispatchException+0x76
>
> 01095c38 64722d32 01095c50 01095c6c 01095c50
> NTDLL!KiUserExceptionDispatcher+0xe
>
>
>
> FOLLOWUP_IP:
>
> NTDLL!KiUserExceptionDispatcher+e
>
> 77f9ff6e 0ac0 or al,al
>
> SYMBOL_STACK_INDEX: 1
>
> FOLLOWUP_NAME: MachineOwner
>
> SYMBOL_NAME: NTDLL!KiUserExceptionDispatcher+e
>
> MODULE_NAME: NTDLL
>
> IMAGE_NAME: NTDLL.DLL
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 4060ef9b
>
> STACK_COMMAND: .ecxr ; kb
>
> BUCKET_ID: c00000fd_NTDLL!KiUserExceptionDispatcher
+e
>
> Followup: MachineOwner
>
> ---------
>
> Can anyone help me please....it is urgent!!
>
> /Zorko
>
>
| |
| zorko79 2004-09-22, 9:25 pm |
| Hi,
Thank you for your answer. We are using IIS 5.0 on a win2000 server with the
latest servicepacks and patches.
/Zorko
"Paul King" <kin0363k@hotmail.com> wrote in message
news:415179d8$0$22749$db0fefd9@news.zen.co.uk...
> Whats your disk space usage like?
>
> Also Im assuming your running IIS under NT judging by the log file - is
this
> updated to Sp3a?
>
> Regards
> Paul.
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:e56FjTKoEHA.3252@TK2MSFTNGP11.phx.gbl...
> hour,
>
****************************************
************************************[vbc
ol=seagreen]
>[/vbcol]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************
****************************************
*********************************[vbcol=
seagreen]
cannot[vbcol=seagreen]
> be
> NTDLL!RtlDispatchException+0x6
wrong.[vbcol=seagreen]
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
> NTDLL!RtlDispatchException+0x76
>
>
| |
| Paul King 2004-09-22, 9:25 pm |
| You don't happen to have a Compaq server with the Insight Manager agent
running?
Regards
Paul.
"zorko79" <zorko792002@yahoo.se> wrote in message
news:uyCyJZKoEHA.3252@TK2MSFTNGP11.phx.gbl...
> Hi,
> Thank you for your answer. We are using IIS 5.0 on a win2000 server with
the
> latest servicepacks and patches.
>
> /Zorko
>
> "Paul King" <kin0363k@hotmail.com> wrote in message
> news:415179d8$0$22749$db0fefd9@news.zen.co.uk...
> this
>
****************************************
************************************[vbc
ol=seagreen]
>[/vbcol]
****************************************
************************************[vbc
ol=seagreen]
> ****************************************
*********************************
> ****************************************
*********************************
> cannot
> wrong.
>
>[/vbcol]
| |
| zorko79 2004-09-22, 9:26 pm |
| Hi,
No it is running on a Dell server with no strange software. Just IIS 5.0,
JRun 3.1 and JRun4, SQLServer7.0.
/Zorko
"Paul King" <kin0363k@hotmail.com> wrote in message
news:41517c22$1$32130$db0fefd9@news.zen.co.uk...
> You don't happen to have a Compaq server with the Insight Manager agent
> running?
>
> Regards
> Paul.
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:uyCyJZKoEHA.3252@TK2MSFTNGP11.phx.gbl...
> the
is
an[vbcol=seagreen]
>
****************************************
************************************[vbc
ol=seagreen]
>
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************
****************************************
*********************************[vbcol=
seagreen]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
>
>
| |
| Pat [MSFT] 2004-09-22, 9:26 pm |
| You need to get the symbols set correctly, b/c the log is inconclusive (it
is basically just showing the OS handling the exception).
From the command window in WinDBG (after loading the dump file):
..symfix <enter>
..reload <enter>
!analyze <enter>
Post the log.
pat
"zorko79" <zorko792002@yahoo.se> wrote in message
news:ev0aBhKoEHA.132@TK2MSFTNGP09.phx.gbl...
> Hi,
> No it is running on a Dell server with no strange software. Just IIS 5.0,
> JRun 3.1 and JRun4, SQLServer7.0.
>
> /Zorko
>
> "Paul King" <kin0363k@hotmail.com> wrote in message
> news:41517c22$1$32130$db0fefd9@news.zen.co.uk...
> is
> an
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> ****************************************
*********************************
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
>
>
| |
| zorko79 2004-09-23, 9:13 am |
| Hi,
Thank you for your advise. Now I got a hint of whats wrong. This is what
came out of analazys.
*** WARNING: Unable to verify checksum for jrun.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
jrun.dll -
*** WARNING: Unable to verify checksum for jrun.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
jrun.dll -
*** WARNING: Unable to verify checksum for jrun.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
jrun.dll -
*** WARNING: Unable to verify checksum for jrun.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
jrun.dll -
*** WARNING: Unable to verify checksum for jrun.dll
Is this true? Is i something wrong with the jrun.dll or did not the analazys
completed ok?
/Zorko
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:ejOs1mMoEHA.2492@TK2MSFTNGP12.phx.gbl...
> You need to get the symbols set correctly, b/c the log is inconclusive (it
> is basically just showing the OS handling the exception).
>
> From the command window in WinDBG (after loading the dump file):
> .symfix <enter>
> .reload <enter>
> !analyze <enter>
>
> Post the log.
>
>
> pat
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:ev0aBhKoEHA.132@TK2MSFTNGP09.phx.gbl...
5.0,[vbcol=seagreen]
file -[vbcol=seagreen]
within[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
***[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
(NTDLL!RtlDispatchException+0x00000006)[
vbcol=seagreen]
stack[vbcol=seagreen]
be[vbcol=seagreen]
>
>
| |
| Pat [MSFT] 2004-09-23, 5:54 pm |
| It just means that the symbols for the dll were not located. It has nothing
to do with the dll's functionality, symbols are just a 'map' of the offsets
in the file. So, if there is a function 'foo' in the dll, the debugger can
give it the name 'jrun!foo' instead of jrun!+0349.
The checksum is a compile time option (again, no effect on the running of
the dll) that embeds a crc into the dll for debugging purposes.
Can you post the rest of the output?
Pat
"zorko79" <zorko792002@yahoo.se> wrote in message
news:%23HlkL1SoEHA.3792@TK2MSFTNGP11.phx.gbl...
> Hi,
> Thank you for your advise. Now I got a hint of whats wrong. This is what
> came out of analazys.
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> jrun.dll -
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> jrun.dll -
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> jrun.dll -
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> jrun.dll -
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> Is this true? Is i something wrong with the jrun.dll or did not the
> analazys
> completed ok?
>
> /Zorko
>
>
>
>
>
>
>
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
> news:ejOs1mMoEHA.2492@TK2MSFTNGP12.phx.gbl...
> 5.0,
> file -
> within
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> ***
> ****************************************
*********************************
> (NTDLL!RtlDispatchException+0x00000006)
> stack
> be
>
>
| |
| zorko79 2004-09-24, 2:50 am |
| Hi,
I am sorry. I wrote "analyze" instead of "!analyze" last time. When I
started over and reanalyzed again I gote following result. Something is
still wrong with the symbol path?
****************************************
************************************
***
* *
* Exception Analysis *
* *
****************************************
************************************
***
Use !analyze -v to get detailed debugging information.
****************************************
*********************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
****************************************
*********************************
Probably caused by : NTDLL.DLL ( NTDLL!KiUserExceptionDispatcher+e )
Followup: MachineOwner
---------
I found ntdll.pdb but when I point out that file I get following errror
"WARNING: C:\symbols\ntdll.pdb\4035165E1\ntdll.pdb is not accessible"
Thanks for your time!!
Zorko
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:uTY%23uNZoEHA.896@TK2MSFTNGP12.phx.gbl...
> It just means that the symbols for the dll were not located. It has
nothing
> to do with the dll's functionality, symbols are just a 'map' of the
offsets
> in the file. So, if there is a function 'foo' in the dll, the debugger
can
> give it the name 'jrun!foo' instead of jrun!+0349.
>
> The checksum is a compile time option (again, no effect on the running of
> the dll) that embeds a crc into the dll for debugging purposes.
>
> Can you post the rest of the output?
>
>
> Pat
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:%23HlkL1SoEHA.3792@TK2MSFTNGP11.phx.gbl...
for[vbcol=seagreen]
for[vbcol=seagreen]
for[vbcol=seagreen]
for[vbcol=seagreen]
server[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
path[vbcol=seagreen]
***[vbcol=seagreen]
to[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
may[vbcol=seagreen]
>
>
| |
| Rui Couto 2004-09-24, 5:51 pm |
| I Have the sme problem and have a compaq server, and have lot os compaq
stuff running but not the Insight Manager agent
Any idea of wahts happening ?
thanks
"Paul King" <kin0363k@hotmail.com> wrote in message
news:41517c22$1$32130$db0fefd9@news.zen.co.uk...
> You don't happen to have a Compaq server with the Insight Manager agent
> running?
>
> Regards
> Paul.
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:uyCyJZKoEHA.3252@TK2MSFTNGP11.phx.gbl...
> the
is
an[vbcol=seagreen]
>
****************************************
************************************[vbc
ol=seagreen]
>
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************
****************************************
*********************************[vbcol=
seagreen]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
NTDLL!ExecuteHandler+0x26[vbcol=seagreen
]
>
>
| |
| Pat [MSFT] 2004-09-24, 5:51 pm |
| The correct order is:
1) Load the dump
2) .symfix <enter>
3) .reload <enter>
4) !analyze <enter>
If you recently applied a hotfix, there is the possibility that the symbols
have not been replicated to the ms symbol server yet (there is a lag of a
few days), but your previous post had the symbols, so I don't know why they
didn't get picked up here.
Pat
"zorko79" <zorko792002@yahoo.se> wrote in message
news:%23eb8RjfoEHA.3172@TK2MSFTNGP10.phx.gbl...
> Hi,
> I am sorry. I wrote "analyze" instead of "!analyze" last time. When I
> started over and reanalyzed again I gote following result. Something is
> still wrong with the symbol path?
>
> ****************************************
************************************
> ***
>
> * *
>
> * Exception Analysis *
>
> * *
>
> ****************************************
************************************
> ***
>
> Use !analyze -v to get detailed debugging information.
>
> ****************************************
*********************************
>
> *** ***
>
> *** ***
>
> *** Your debugger is not using the correct symbols ***
>
> *** ***
>
> *** In order for this command to work properly, your symbol path ***
>
> *** must point to .pdb files that have full type information. ***
>
> *** ***
>
> *** Certain .pdb files (such as the public OS symbols) do not ***
>
> *** contain the required information. Contact the group that ***
>
> *** provided you with these symbols if you need this command to ***
>
> *** work. ***
>
> *** ***
>
> *** Type referenced: ntdll!_PEB ***
>
> *** ***
>
> ****************************************
*********************************
>
> Probably caused by : NTDLL.DLL ( NTDLL!KiUserExceptionDispatcher+e )
>
> Followup: MachineOwner
>
> ---------
>
> I found ntdll.pdb but when I point out that file I get following errror
>
> "WARNING: C:\symbols\ntdll.pdb\4035165E1\ntdll.pdb is not accessible"
>
> Thanks for your time!!
>
> Zorko
>
>
>
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
> news:uTY%23uNZoEHA.896@TK2MSFTNGP12.phx.gbl...
> nothing
> offsets
> can
> for
> for
> for
> for
> server
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> path
> ***
> to
> ****************************************
*********************************
> may
>
>
| |
| Pat [MSFT] 2004-09-27, 2:48 am |
| Do you have a .dmp file as well? You could analyze it and see what is
happening. Similar symptom (i.e. a blue screen) can be caused by different
things though they may look similar.
Pat
"Rui Couto" <rcouto@techlado.com> wrote in message
news:%23wrWIJmoEHA.3464@tk2msftngp13.phx.gbl...
>I Have the sme problem and have a compaq server, and have lot os compaq
> stuff running but not the Insight Manager agent
>
> Any idea of wahts happening ?
>
> thanks
>
> "Paul King" <kin0363k@hotmail.com> wrote in message
> news:41517c22$1$32130$db0fefd9@news.zen.co.uk...
> is
> an
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> ****************************************
*********************************
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
>
>
| |
| zorko79 2004-09-27, 2:48 am |
| Hi again,
Have once again started from beginning and followed your description for
running dbg. I even tried with another dump file and I still get the same
error. Any ideas? This is the last result.
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\temp\crashdump\1984-1087448984.dmp]
User Mini Dump File with Full Memory: Only application data is available
Windows 2000 Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Product: Server
Debug session time: Thu Jun 17 08:09:45 2004
System Uptime: 2 days 0:14:14.117
Process Uptime: 0 days 0:10:50.000
Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
.............................................................................
.....................
(7c0.d64): Access violation - code c0000005 (!!! second chance !!!)
eax=00000063 ebx=0000000b ecx=0168f240 edx=00000000 esi=01618161
edi=0168f214
eip=7800fc9a esp=0168ef9c ebp=0168ef9c iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000202
msvcrt!_output+0x7d5:
7800fc9a 8802 mov [edx],al ds:0023:00000000=??
0:016> .symfix
No downstream store given, using C:\Program Files\Debugging Tools for
Windows\sym
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
0:016> .reload
.............................................................................
.....................
0:016> !analyze
****************************************
************************************
***
* *
* Exception Analysis *
* *
****************************************
************************************
***
Use !analyze -v to get detailed debugging information.
****************************************
*********************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
****************************************
*********************************
*** WARNING: Unable to verify checksum for jrun.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
jrun.dll -
Probably caused by : msvcrt.dll ( msvcrt!_output+7d5 )
Followup: MachineOwner
---------
/Zorko
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:OabEcGnoEHA.1272@TK2MSFTNGP09.phx.gbl...
> The correct order is:
>
> 1) Load the dump
> 2) .symfix <enter>
> 3) .reload <enter>
> 4) !analyze <enter>
>
> If you recently applied a hotfix, there is the possibility that the
symbols
> have not been replicated to the ms symbol server yet (there is a lag of a
> few days), but your previous post had the symbols, so I don't know why
they
> didn't get picked up here.
>
>
> Pat
>
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:%23eb8RjfoEHA.3172@TK2MSFTNGP10.phx.gbl...
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
****************************************
*********************************[vbcol=
seagreen]
of[vbcol=seagreen]
symbols[vbcol=seagreen]
symbols[vbcol=seagreen]
symbols[vbcol=seagreen]
symbols[vbcol=seagreen]
inconclusive[vbcol=seagreen]
IIS[vbcol=seagreen]
Sometimes[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
information.[vbcol=seagreen]
not[vbcol=seagreen]
that[vbcol=seagreen]
command[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
the[vbcol=seagreen]
>
>
| |
| Pat [MSFT] 2004-09-27, 5:55 pm |
| Can you type:
kb <enter> (after you get the symbols lined up, etc.)?
Thanks,
Pat
"zorko79" <zorko792002@yahoo.se> wrote in message
news:OtpR0bFpEHA.3428@TK2MSFTNGP11.phx.gbl...
> Hi again,
> Have once again started from beginning and followed your description for
> running dbg. I even tried with another dump file and I still get the same
> error. Any ideas? This is the last result.
>
> Microsoft (R) Windows Debugger Version 6.3.0017.0
>
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>
> Loading Dump File [C:\temp\crashdump\1984-1087448984.dmp]
>
> User Mini Dump File with Full Memory: Only application data is available
>
> Windows 2000 Version 2195 (Service Pack 4) MP (2 procs) Free x86
> compatible
>
> Product: Server
>
> Debug session time: Thu Jun 17 08:09:45 2004
>
> System Uptime: 2 days 0:14:14.117
>
> Process Uptime: 0 days 0:10:50.000
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
>
> Executable search path is:
>
> ............................................................................
> ....................
>
> (7c0.d64): Access violation - code c0000005 (!!! second chance !!!)
>
> eax=00000063 ebx=0000000b ecx=0168f240 edx=00000000 esi=01618161
> edi=0168f214
>
> eip=7800fc9a esp=0168ef9c ebp=0168ef9c iopl=0 nv up ei pl nz na pe nc
>
> cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000202
>
> msvcrt!_output+0x7d5:
>
> 7800fc9a 8802 mov [edx],al ds:0023:00000000=??
>
> 0:016> .symfix
>
> No downstream store given, using C:\Program Files\Debugging Tools for
> Windows\sym
>
> Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
>
> 0:016> .reload
>
> ............................................................................
> ....................
>
> 0:016> !analyze
>
> ****************************************
************************************
> ***
>
> * *
>
> * Exception Analysis *
>
> * *
>
> ****************************************
************************************
> ***
>
> Use !analyze -v to get detailed debugging information.
>
> ****************************************
*********************************
>
> *** ***
>
> *** ***
>
> *** Your debugger is not using the correct symbols ***
>
> *** ***
>
> *** In order for this command to work properly, your symbol path ***
>
> *** must point to .pdb files that have full type information. ***
>
> *** ***
>
> *** Certain .pdb files (such as the public OS symbols) do not ***
>
> *** contain the required information. Contact the group that ***
>
> *** provided you with these symbols if you need this command to ***
>
> *** work. ***
>
> *** ***
>
> *** Type referenced: ntdll!_PEB ***
>
> *** ***
>
> ****************************************
*********************************
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> jrun.dll -
>
> Probably caused by : msvcrt.dll ( msvcrt!_output+7d5 )
>
> Followup: MachineOwner
>
> ---------
>
> /Zorko
>
>
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
> news:OabEcGnoEHA.1272@TK2MSFTNGP09.phx.gbl...
> symbols
> they
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> ****************************************
*********************************
> of
> symbols
> symbols
> symbols
> symbols
> inconclusive
> IIS
> Sometimes
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> information.
> not
> that
> command
> ****************************************
*********************************
> the
>
>
| |
| zorko79 2004-09-28, 3:29 am |
| Hi,
I run the command after .symfix , .reload and !analyze and last kb
This is the result dump1:
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\temp\crashdump\3304-1087847358.dmp]
User Mini Dump File with Full Memory: Only application data is available
Windows 2000 Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Product: Server
Debug session time: Mon Jun 21 22:49:19 2004
System Uptime: 6 days 14:53:53.789
Process Uptime: 4 days 14:38:31.000
Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
.............................................................................
.................................
(ce8.bf4): Stack overflow - code c00000fd (!!! second chance !!!)
eax=010933f0 ebx=01093070 ecx=0109308c edx=77f96dae esi=01093418
edi=00000002
eip=77f96be3 esp=01092ff8 ebp=01093058 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
NTDLL!RtlDispatchException+0x6:
77f96be3 53 push ebx
0:031> .symfix
No downstream store given, using C:\Program Files\Debugging Tools for
Windows\sym
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
0:031> .reload
.............................................................................
.................................
0:031> !analyze
****************************************
************************************
***
* *
* Exception Analysis *
* *
****************************************
************************************
***
Use !analyze -v to get detailed debugging information.
****************************************
*********************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
****************************************
*********************************
Probably caused by : NTDLL.DLL ( NTDLL!KiUserExceptionDispatcher+e )
Followup: MachineOwner
---------
0:031> kb
ChildEBP RetAddr Args to Child
01093058 77f9ff6e 01093070 0109308c 01093070 NTDLL!RtlDispatchException+0x6
01093058 64722d32 01093070 0109308c 01093070
NTDLL!KiUserExceptionDispatcher+0xe
WARNING: Frame IP not in any known module. Following frames may be wrong.
01093354 77f96ba7 01093418 010cf434 01093434 0x64722d32
01093378 77f96c42 01093418 010cf434 01093434 NTDLL!ExecuteHandler+0x26
01093400 77f9ff6e 01093418 01093434 01093418 NTDLL!RtlDispatchException+0x76
01093400 64722d32 01093418 01093434 01093418
NTDLL!KiUserExceptionDispatcher+0xe
010936fc 77f96ba7 010937c0 010cf434 010937dc 0x64722d32
01093720 77f96c42 010937c0 010cf434 010937dc NTDLL!ExecuteHandler+0x26
010937a8 77f9ff6e 010937c0 010937dc 010937c0 NTDLL!RtlDispatchException+0x76
010937a8 64722d32 010937c0 010937dc 010937c0
NTDLL!KiUserExceptionDispatcher+0xe
01093aa4 77f96ba7 01093b68 010cf434 01093b84 0x64722d32
01093ac8 77f96c42 01093b68 010cf434 01093b84 NTDLL!ExecuteHandler+0x26
01093b50 77f9ff6e 01093b68 01093b84 01093b68 NTDLL!RtlDispatchException+0x76
01093b50 64722d32 01093b68 01093b84 01093b68
NTDLL!KiUserExceptionDispatcher+0xe
01093e4c 77f96ba7 01093f10 010cf434 01093f2c 0x64722d32
01093e70 77f96c42 01093f10 010cf434 01093f2c NTDLL!ExecuteHandler+0x26
01093ef8 77f9ff6e 01093f10 01093f2c 01093f10 NTDLL!RtlDispatchException+0x76
01093ef8 64722d32 01093f10 01093f2c 01093f10
NTDLL!KiUserExceptionDispatcher+0xe
010941f4 77f96ba7 010942b8 010cf434 010942d4 0x64722d32
01094218 77f96c42 010942b8 010cf434 010942d4 NTDLL!ExecuteHandler+0x26
######## dump 1 end #########
######### dump2 begin #########
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\temp\crashdump\1984-1087448984.dmp]
User Mini Dump File with Full Memory: Only application data is available
Windows 2000 Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Product: Server
Debug session time: Thu Jun 17 08:09:45 2004
System Uptime: 2 days 0:14:14.117
Process Uptime: 0 days 0:10:50.000
Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
.............................................................................
.....................
(7c0.d64): Access violation - code c0000005 (!!! second chance !!!)
eax=00000063 ebx=0000000b ecx=0168f240 edx=00000000 esi=01618161
edi=0168f214
eip=7800fc9a esp=0168ef9c ebp=0168ef9c iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000202
msvcrt!_output+0x7d5:
7800fc9a 8802 mov [edx],al ds:0023:00000000=??
0:016> .symfix
No downstream store given, using C:\Program Files\Debugging Tools for
Windows\sym
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
0:016> .reload
.............................................................................
.....................
0:016> .analyze
^ Syntax error in '.analyze'
0:016> !analyze
****************************************
************************************
***
* *
* Exception Analysis *
* *
****************************************
************************************
***
Use !analyze -v to get detailed debugging information.
****************************************
*********************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
****************************************
*********************************
*** WARNING: Unable to verify checksum for jrun.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
jrun.dll -
Probably caused by : msvcrt.dll ( msvcrt!_output+7d5 )
Followup: MachineOwner
---------
0:016> kb
ChildEBP RetAddr Args to Child
0168ef9c 7800fd15 00000063 0168f240 0168f214 msvcrt!_output+0x7d5
0168efb8 7800fc62 01618160 0000000c 0168f240 msvcrt!_output+0x850
0168f228 780238dc 0168f240 01617666 0168f274 msvcrt!_output+0x75e
0168f260 016125b2 00000000 01617664 01618160 msvcrt!sprintf+0x2e
WARNING: Stack unwind information not available. Following frames may be
wrong.
01618170 6d74682f 0000006c 75746572 6e696e72
jrun_1610000!HttpFilterProc+0xce2
74786574 00000000 00000000 00000000 00000000 0x6d74682f
########### dump 2 end #############
/Zorko
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:OtssfhLpEHA.1296@TK2MSFTNGP12.phx.gbl...
> Can you type:
>
> kb <enter> (after you get the symbols lined up, etc.)?
>
> Thanks,
>
> Pat
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:OtpR0bFpEHA.3428@TK2MSFTNGP11.phx.gbl...
same[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
****************************************
*********************************[vbcol=
seagreen]
for[vbcol=seagreen]
a[vbcol=seagreen]
is[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
****************************************
*********************************[vbcol=
seagreen]
errror[vbcol=seagreen]
running[vbcol=seagreen]
is[vbcol=seagreen]
the[vbcol=seagreen]
Just[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
do[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
>
>
| |
| Paul King 2004-09-28, 5:55 pm |
| All I know is that I done a Yahoo search for the error msg and there was a
reference to the Insight agent - I wonder if this is related.
Regards
Paul.
"Rui Couto" <rcouto@techlado.com> wrote in message
news:#wrWIJmoEHA.3464@tk2msftngp13.phx.gbl...
> I Have the sme problem and have a compaq server, and have lot os compaq
> stuff running but not the Insight Manager agent
>
> Any idea of wahts happening ?
>
> thanks
>
> "Paul King" <kin0363k@hotmail.com> wrote in message
> news:41517c22$1$32130$db0fefd9@news.zen.co.uk...
with
> is
within[vbcol=seagreen]
> an
>
****************************************
************************************[vbc
ol=seagreen]
>
****************************************
************************************[vbc
ol=seagreen]
> ****************************************
*********************************
***
***[vbcol=seagreen]
> ****************************************
*********************************
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
> NTDLL!ExecuteHandler+0x26
>
>
| |
| Pat [MSFT] 2004-09-28, 5:55 pm |
| This is a bug in JRun.dll. Basically, it is passing bad parameters into a
CRT function that ultimately causes a crash. Check for an update.
Thanks,
Pat
"zorko79" <zorko792002@yahoo.se> wrote in message
news:OZZSD1RpEHA.556@tk2msftngp13.phx.gbl...
> Hi,
> I run the command after .symfix , .reload and !analyze and last kb
>
> This is the result dump1:
>
> Microsoft (R) Windows Debugger Version 6.3.0017.0
>
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>
> Loading Dump File [C:\temp\crashdump\3304-1087847358.dmp]
>
> User Mini Dump File with Full Memory: Only application data is available
>
> Windows 2000 Version 2195 (Service Pack 4) MP (2 procs) Free x86
> compatible
>
> Product: Server
>
> Debug session time: Mon Jun 21 22:49:19 2004
>
> System Uptime: 6 days 14:53:53.789
>
> Process Uptime: 4 days 14:38:31.000
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
>
> Executable search path is:
>
> ............................................................................
> ................................
>
> (ce8.bf4): Stack overflow - code c00000fd (!!! second chance !!!)
>
> eax=010933f0 ebx=01093070 ecx=0109308c edx=77f96dae esi=01093418
> edi=00000002
>
> eip=77f96be3 esp=01092ff8 ebp=01093058 iopl=0 nv up ei pl nz na pe nc
>
> cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
>
> NTDLL!RtlDispatchException+0x6:
>
> 77f96be3 53 push ebx
>
> 0:031> .symfix
>
> No downstream store given, using C:\Program Files\Debugging Tools for
> Windows\sym
>
> Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
>
> 0:031> .reload
>
> ............................................................................
> ................................
>
> 0:031> !analyze
>
> ****************************************
************************************
> ***
>
> * *
>
> * Exception Analysis *
>
> * *
>
> ****************************************
************************************
> ***
>
> Use !analyze -v to get detailed debugging information.
>
> ****************************************
*********************************
>
> *** ***
>
> *** ***
>
> *** Your debugger is not using the correct symbols ***
>
> *** ***
>
> *** In order for this command to work properly, your symbol path ***
>
> *** must point to .pdb files that have full type information. ***
>
> *** ***
>
> *** Certain .pdb files (such as the public OS symbols) do not ***
>
> *** contain the required information. Contact the group that ***
>
> *** provided you with these symbols if you need this command to ***
>
> *** work. ***
>
> *** ***
>
> *** Type referenced: ntdll!_PEB ***
>
> *** ***
>
> ****************************************
*********************************
>
> Probably caused by : NTDLL.DLL ( NTDLL!KiUserExceptionDispatcher+e )
>
> Followup: MachineOwner
>
> ---------
>
> 0:031> kb
>
> ChildEBP RetAddr Args to Child
>
> 01093058 77f9ff6e 01093070 0109308c 01093070
> NTDLL!RtlDispatchException+0x6
>
> 01093058 64722d32 01093070 0109308c 01093070
> NTDLL!KiUserExceptionDispatcher+0xe
>
> WARNING: Frame IP not in any known module. Following frames may be wrong.
>
> 01093354 77f96ba7 01093418 010cf434 01093434 0x64722d32
>
> 01093378 77f96c42 01093418 010cf434 01093434 NTDLL!ExecuteHandler+0x26
>
> 01093400 77f9ff6e 01093418 01093434 01093418
> NTDLL!RtlDispatchException+0x76
>
> 01093400 64722d32 01093418 01093434 01093418
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 010936fc 77f96ba7 010937c0 010cf434 010937dc 0x64722d32
>
> 01093720 77f96c42 010937c0 010cf434 010937dc NTDLL!ExecuteHandler+0x26
>
> 010937a8 77f9ff6e 010937c0 010937dc 010937c0
> NTDLL!RtlDispatchException+0x76
>
> 010937a8 64722d32 010937c0 010937dc 010937c0
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01093aa4 77f96ba7 01093b68 010cf434 01093b84 0x64722d32
>
> 01093ac8 77f96c42 01093b68 010cf434 01093b84 NTDLL!ExecuteHandler+0x26
>
> 01093b50 77f9ff6e 01093b68 01093b84 01093b68
> NTDLL!RtlDispatchException+0x76
>
> 01093b50 64722d32 01093b68 01093b84 01093b68
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 01093e4c 77f96ba7 01093f10 010cf434 01093f2c 0x64722d32
>
> 01093e70 77f96c42 01093f10 010cf434 01093f2c NTDLL!ExecuteHandler+0x26
>
> 01093ef8 77f9ff6e 01093f10 01093f2c 01093f10
> NTDLL!RtlDispatchException+0x76
>
> 01093ef8 64722d32 01093f10 01093f2c 01093f10
> NTDLL!KiUserExceptionDispatcher+0xe
>
> 010941f4 77f96ba7 010942b8 010cf434 010942d4 0x64722d32
>
> 01094218 77f96c42 010942b8 010cf434 010942d4 NTDLL!ExecuteHandler+0x26
>
> ######## dump 1 end #########
>
> ######### dump2 begin #########
>
> Microsoft (R) Windows Debugger Version 6.3.0017.0
>
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
>
> Loading Dump File [C:\temp\crashdump\1984-1087448984.dmp]
>
> User Mini Dump File with Full Memory: Only application data is available
>
> Windows 2000 Version 2195 (Service Pack 4) MP (2 procs) Free x86
> compatible
>
> Product: Server
>
> Debug session time: Thu Jun 17 08:09:45 2004
>
> System Uptime: 2 days 0:14:14.117
>
> Process Uptime: 0 days 0:10:50.000
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
>
> Executable search path is:
>
> ............................................................................
> ....................
>
> (7c0.d64): Access violation - code c0000005 (!!! second chance !!!)
>
> eax=00000063 ebx=0000000b ecx=0168f240 edx=00000000 esi=01618161
> edi=0168f214
>
> eip=7800fc9a esp=0168ef9c ebp=0168ef9c iopl=0 nv up ei pl nz na pe nc
>
> cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000202
>
> msvcrt!_output+0x7d5:
>
> 7800fc9a 8802 mov [edx],al ds:0023:00000000=??
>
> 0:016> .symfix
>
> No downstream store given, using C:\Program Files\Debugging Tools for
> Windows\sym
>
> Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
>
> 0:016> .reload
>
> ............................................................................
> ....................
>
> 0:016> .analyze
>
> ^ Syntax error in '.analyze'
>
> 0:016> !analyze
>
> ****************************************
************************************
> ***
>
> * *
>
> * Exception Analysis *
>
> * *
>
> ****************************************
************************************
> ***
>
> Use !analyze -v to get detailed debugging information.
>
> ****************************************
*********************************
>
> *** ***
>
> *** ***
>
> *** Your debugger is not using the correct symbols ***
>
> *** ***
>
> *** In order for this command to work properly, your symbol path ***
>
> *** must point to .pdb files that have full type information. ***
>
> *** ***
>
> *** Certain .pdb files (such as the public OS symbols) do not ***
>
> *** contain the required information. Contact the group that ***
>
> *** provided you with these symbols if you need this command to ***
>
> *** work. ***
>
> *** ***
>
> *** Type referenced: ntdll!_PEB ***
>
> *** ***
>
> ****************************************
*********************************
>
> *** WARNING: Unable to verify checksum for jrun.dll
>
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> jrun.dll -
>
> Probably caused by : msvcrt.dll ( msvcrt!_output+7d5 )
>
> Followup: MachineOwner
>
> ---------
>
> 0:016> kb
>
> ChildEBP RetAddr Args to Child
>
> 0168ef9c 7800fd15 00000063 0168f240 0168f214 msvcrt!_output+0x7d5
>
> 0168efb8 7800fc62 01618160 0000000c 0168f240 msvcrt!_output+0x850
>
> 0168f228 780238dc 0168f240 01617666 0168f274 msvcrt!_output+0x75e
>
> 0168f260 016125b2 00000000 01617664 01618160 msvcrt!sprintf+0x2e
>
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
>
> 01618170 6d74682f 0000006c 75746572 6e696e72
> jrun_1610000!HttpFilterProc+0xce2
>
> 74786574 00000000 00000000 00000000 00000000 0x6d74682f
>
> ########### dump 2 end #############
>
> /Zorko
>
>
> "Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
> news:OtssfhLpEHA.1296@TK2MSFTNGP12.phx.gbl...
> same
> ............................................................................
> ............................................................................
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> ****************************************
*********************************
> for
> a
> is
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> ****************************************
*********************************
> errror
> running
> is
> the
> Just
> ****************************************
************************************
> ****************************************
************************************
> ****************************************
*********************************
> do
> ****************************************
*********************************
>
>
| |
| zorko79 2004-09-29, 3:09 am |
| Hi,
Thank you Pat!! I will search for an update for JRun.
/Zorko
"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:ucn$hvXpEHA.2684@TK2MSFTNGP11.phx.gbl...
> This is a bug in JRun.dll. Basically, it is passing bad parameters into a
> CRT function that ultimately causes a crash. Check for an update.
>
>
> Thanks,
>
> Pat
>
> "zorko79" <zorko792002@yahoo.se> wrote in message
> news:OZZSD1RpEHA.556@tk2msftngp13.phx.gbl...
.............................................................................[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
****************************************
*********************************[vbcol=
seagreen]
wrong.[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
****************************************
*********************************[vbcol=
seagreen]
for[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
SRV**http://msdl.microsoft.com/download/symbols[vbcol=seagreen]
.............................................................................[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
****************************************
*********************************[vbcol=
seagreen]
symbols[vbcol=seagreen]
why[vbcol=seagreen]
When[vbcol=seagreen]
Something[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
***[vbcol=seagreen]
***[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
NTDLL!KiUserExceptionDispatcher+e )[vbcol=seagreen]
the[vbcol=seagreen]
This[vbcol=seagreen]
file):[vbcol=seagreen]
the[vbcol=seagreen]
with[vbcol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
************************************[vbc
ol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
***[vbcol=seagreen]
symbols)[vbcol=seagreen]
group[vbcol=seagreen]
****************************************
*********************************[vbcol=
seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
0x64722d32[vbcol=seagreen]
>
>
|
|
|
|
|