JIT crash on startup
Brought to you by:
royosherove
Menu
▾
▴
#19 JIT crash on startup
open
nobody
None
5
2004-09-07
2004-09-07
Anonymous
No
The regulator started crashing on startup suddenly with
the a JIT debugger message "Class not registered". I
uninstalled and reinstalled, but it continued to get the
error until I uninstalled and manually deleted the
editor.config file.
Logged In: YES
user_id=1104469
The regulator was 2.0.3.0 was working since 9-25 and
suddenly began giving the "JIT Debugging Failed with the
Following error: Class not registered
Please check the documentation topic Just-in-time debugging
errors For more information." error.
I have a feeling, but am not certain, that this began after
the .NET framework 1.1 SP 1 release was installed. I'm going
to try rolling back and will post if it makes any difference.
Logged In: YES
user_id=1104469
Didn't have to rollback to pre Net 1.1 SP 1.
Had crashed a couple of time prior to the JIT error on \:
Read the buglist further and was able to reinstall after
deleting the entire program directory. I had only uninstalled
before, and like the other post stated, the left over files we
probably corrupt.
I appreciate the hard work you put into this program. It is
going to be an excelent tool when you kick the last few bugs.
Quite impressive so far.
BTW, Your version of DNN hangs Firefox: I think it is your
amazon link implemetation, FWIW.
Logged In: YES
user_id=1178158
It appears that the file format for settings.config has
changed from text to binary.
Resolution : Simply delete the setting.config file and it will be
recreated on the next normal exit from The Regulator.
Logged In: NO
I got similar behavior after entering an expression that The
Regulator didn't like -- the expression contained an
unescaped colon. It crashed and wouldn't run at all, even
after an uninstall/reinstall.
I removed both editor.config & settings.config and the
problem went away.
Logged In: YES
user_id=1291412
my regulator (regex tester) keeps on crashing with below
error ...
"Registered debugger is not available. An attempt to launch a
JIT debugger with the following command resulted in an error
code of 0x2(2).
Please check computer settings.
cordbg.exe !a 0xcfc
click on retry to wait ... cancel to abort ...
M$ .NET FrmWrk's runtime debugger (cordbg.exe) is failing
to start.
More on cordbg.exe (
http://winfx.msdn.microsoft.com/library/en-
us/dv_fxtools/html/8c77a7c5-fd9d-42bf-b557-
c06408821fec.asp )
if the JIT (Just In Time) Debug error annoy you too much then
it can be turn off by adding (if not pre-existing)
this "DbgJITDebugLaunchSetting" win registry (DWORD)
value , inside the below (key) location ...
HKLM\Software\Microsoft\.NETFramework and by setting its
data to 1 .
data 1 : simply return control. This results in a stack dump,
after which the process is terminated .
data 0 : prompt the user with these choices : (1) Continue:
This results in a stack dump and process termination. (2)
Attach a debugger: In this case, the runtime spawns the
debugger listed in the DbgManagedDebugger registry key. If
none, control is returned, and the process is terminated.
data 2 : spawn the debugger listed in the
DbgManagedDebugger registry key .
the default JIT debugger can be (manually) changed by
changing the data of the "debugger" value located at
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\AeDebug.
but none of those steps will solve (this real) problem, which is
existing somewhere else . may be it works when your
PC/station is loaded with many diferent developing tools or
something else . tried after deleting that editor.config file ,
also the regex.ini ,etc other files , didn't work .
even used "drwtsn32 -i" command at "run" to check / reinstall
the DrWattson debugger .
but my default debugger key's data is same as before ...
drwtsn32 -p %ld -e %ld -g
"the regulator" generating error as before.
had to use process killer to close this.
then i've installed the .net frmwork SDK (see the link below) ...
(as of today, August 26, 2005)
M$ .NET Framework Version 1.1 Redistributable Package ...
http://www.microsoft.com/downloads/details.aspx?
familyid=262D25E3-F589-4842-8157-
034D1E7CF3A3&displaylang=en
dotnetfx.exe v1.1 3/30/2004 English 23,698 KB
M$ .NET Framework 1.1 Service Pack 1 ...
http://www.microsoft.com/downloads/info.aspx?
na=47&p=4&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyI
d=262d25e3-f589-4842-8157-034d1e7cf3a3&u=details.aspx%
3ffamilyid%3dA8F5654F-088E-40B2-BBDB-A83353618B38%
26displaylang%3den
NDP1.1sp1-KB867460-X86.exe v1.0 5/31/2005 English
10,453 KB
M$ .NET Framework SDK Version 1.1 ...
http://www.microsoft.com/downloads/info.aspx?
na=22&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyI
d=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%
3d9b3a2ca6-3647-4070-9f41-a333c6b9181d%26DisplayLang%
3den
setup.exe v1.1 3/3/2005 English 108,757 KB
use the command "control sysdm.cpl" to open Control Panel
System Icon -> Advanced Tab -> Environment Variables ->
double click on System Varibles "Path" and
add ";C:\Program Files\Microsoft.NET\SDK\v1.1\Bin"
for the .net frmwrk 1.1 SDK . this will let other soft to find
debugger and other .net executable as well.
it will enable the "the regulator" to find that runtime debugger
cordbg.exe
then try to run the regulator again ...
it may display debug info like below ...
M$ Common Language Runtime Test Debugger Shell Version
1.1.4322.573
(cordbg) a 0x56c
Process 1388/0x56c created.
Warning: couldn't load symbols for
c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll
Warning: couldn't load symbols for
c:\windows\assembly\gac\system\1.0.5000.0__b77a5c561934
e089\system.dll
Warning: couldn't load symbols for
c:\windows\assembly\gac\system.drawing\1.0.5000.0__b03f5f
7f11d50a3a\system.drawing.dll
Warning: couldn't load symbols for C:\Program Files\The
Regulator\The Regulator2.0\Regulator.exe
Warning: couldn't load symbols for
c:\windows\assembly\gac\system.windows.forms\1.0.5000.0_
_b77a5c561934e089\system.windows.forms.dll
Warning: couldn't load symbols for c:\program files\the
regulator\the regulator2.0\regulator.sdk.dll
Warning: couldn't load symbols for c:\program files\the
regulator\the regulator2.0\syncfusion.tools.dll
Warning: couldn't load symbols for c:\program files\the
regulator\the regulator2.0\syncfusion.shared.dll
Warning: couldn't load symbols for
c:\windows\assembly\gac\system.design\1.0.5000.0__b03f5f7
f11d50a3a\system.design.dll
Warning: couldn't load symbols for
c:\windows\assembly\gac\system.xml\1.0.5000.0__b77a5c56
1934e089\system.xml.dll
Warning: couldn't load symbols for c:\program files\the
regulator\the regulator2.0\c1.win.c1command.dll
Warning: couldn't load symbols for c:\program files\the
regulator\the regulator2.0\c1.common.dll
Warning: couldn't load symbols for
c:\windows\assembly\gac\system.data\1.0.5000.0__b77a5c56
1934e089\system.data.dll
[thread 0x550] Thread created.
Unable to determine existence of prolog, if any
[thread 0x998] Thread created.
[thread 0x9dc] Thread created.
[thread 0x550] Unhandled exception generated: (0x04ca3518)
<System.TypeInitializationException>
_typeName=(0x04ca355c) "Regulator.SDK.AppContext"
_className=<null>
_exceptionMethod=<null>
_exceptionMethodString=<null>
_message=(0x04ca3778) "The type initializer
for "Regulator.SDK.AppContext" threw an exception."
_innerException=(0x04ca309c) <System.IO.IOException>
_helpURL=<null>
_stackTrace=(0x04ca3874) array with dims=[48]
_stackTraceString=<null>
_remoteStackTraceString=<null>
_remoteStackIndex=0x00000000
_HResult=0x80131534
_source=<null>
_xptrs=0x00000000
_xcode=0xe0434f4d
Thread 0x550 R --- Class initialization ---
(cordbg)
so now we have more info ... it is atleast getting the
cordbg.exe but still unable to load symbols from those 13
files.
and those files are not missing.
Logged In: YES
user_id=1291412
many thanks to the poster , who posted comment on 2005-04-
27 13:01
"the regulator" working ...
i've renamed both "editor.config" & "settings.config" to
editor.config.bak , settings.config.bak and then
problem went away.
but, amazingly, i've done this , before installing that SDK and
adding path , it didn't work !!!
time spent but at least learned something new
Logged In: NO
I had this same problem, and deleting the settings.config*
files did not work. I was able to resolve it by removing
the .NET 1.1 Framework, and only having .NET 2.0 Framework
installed. Then, I performed an admin install on the MSI,
which skips the check for the 1.1 Framework. Here's the
install command for an admin setup:
msiexec /a "RegulatorSetup.msi"