IIS Crashes
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > IIS server support > IIS Server > IIS Crashes




Pages (2): [1] 2 »   Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    IIS Crashes  
zorko79


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:25 AM

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







[ Post a follow-up to this message ]



    Re: IIS Crashes  
Paul King


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:25 AM

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
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
zorko79


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:25 AM

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 
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
Paul King


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:25 AM

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]







[ Post a follow-up to this message ]



    Re: IIS Crashes  
zorko79


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:26 AM

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
] 
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
Pat [MSFT]


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:26 AM

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 
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
zorko79


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 02:13 PM

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] 
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
Pat [MSFT]


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-23-04 10: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 
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
zorko79


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-24-04 07: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] 
>
>







[ Post a follow-up to this message ]



    Re: IIS Crashes  
Rui Couto


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
09-24-04 10: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
] 
>
>







[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 11:51 AM.      Post New Thread    Post A Reply      
Pages (2): [1] 2 »   Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register