JIT error

JIT error

Anonymous
Not applicable
1,376 Views
11 Replies
Message 1 of 12

JIT error

Anonymous
Not applicable
Can anybody tell me why this happens?

See the end of this message, instead of this dialog box, for details on invoking
just-in-time (JIT) debugging.

************** Exception Text **************
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Resources.MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "BindAllXrefs.frmMain.resources" was correctly embedded or linked into assembly "BindAllXrefs" at compile time, or that all the satellite assemblies required are loadable and fully signed.
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream)
at System.Resources.ResourceManager.GetObject(String name)
at BindAllXrefs.frmMain.InitializeComponent() in C:\MyWorkFiles\BindAllXrefs\frmMain.vb:line 141
at BindAllXrefs.frmMain..ctor() in C:\MyWorkFiles\BindAllXrefs\frmMain.vb:line 68
at BindAllXrefs.Commands.Bind() in C:\MyWorkFiles\BindAllXrefs\frmMain.vb:line 12
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, SignatureStruct sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at AcMgCommandClass.Invoke(AcMgCommandClass* , gcroot<:REFLECTION::METHODINFO __gc="">* mi)
at Autodesk.AutoCAD.Runtime.SEHExceptionFilter.InvokeWorker()
at Autodesk.AutoCAD.Runtime.ExceptionFilter.Invoke()


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50215.44 (beta2.050215-4400)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50215/mscorlib.dll
----------------------------------------
AcDbMgdHost
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcdbMgdHost.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50215.44 (beta2.050215-4400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50215.44 (beta2.050215-4400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50215.44 (beta2.050215-4400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50215.44 (beta2.050215-4400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
acmgd
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/acmgd.DLL
----------------------------------------
acdbmgd
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/acdbmgd.DLL
----------------------------------------
AecDtlDb47
Assembly Version: 4.7.302.0
Win32 Version: 4, 7, 302, 0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AecDtlDb47.DLL
----------------------------------------
AecDtlDbUI
Assembly Version: 4.7.302.0
Win32 Version: 4.7.302.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AecDtlDbUI.DLL
----------------------------------------
AecDtlDbLib
Assembly Version: 4.7.302.0
Win32 Version: 4.7.302.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AecDtlDbLib.DLL
----------------------------------------
AcDxUi
Assembly Version: 16.2.77.0
Win32 Version: 16.2.77.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcDxUi.DLL
----------------------------------------
AcDx
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcDx.DLL
----------------------------------------
AcDxUi.resources
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/en-US/AcDxUi.resources.DLL
----------------------------------------
AcMgdShared
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcMgdShared.DLL
----------------------------------------
AcLayer
Assembly Version: 16.2.77.0
Win32 Version: 16.2.77.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcLayer.DLL
----------------------------------------
AcLayer.resources
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/en-US/AcLayer.resources.DLL
----------------------------------------
AcCustomize
Assembly Version: 16.2.77.0
Win32 Version: 16.2.77.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcCustomize.DLL
----------------------------------------
acmgdinternal
Assembly Version: 16.2.77.0
Win32 Version: 16.2.77.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/acmgdinternal.DLL
----------------------------------------
AcMNUParser
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/AcMNUParser.DLL
----------------------------------------
AcCustomize.resources
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/en-US/AcCustomize.resources.DLL
----------------------------------------
BzLocation
Assembly Version: 16.2.54.0
Win32 Version: 16.2.54.0
CodeBase: file:///C:/Program%20Files/Autodesk%20Building%20Systems%202006/BzLocation.DLL
----------------------------------------
BindAllXrefs
Assembly Version: 1.0.2426.16478
Win32 Version: 1.0.2426.16478
CodeBase: file:///C:/MyWorkFiles/BindAllXrefs/bin/BindAllXrefs.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50215.44 (beta2.050215-4400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:





When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Thanks
0 Likes
1,377 Views
11 Replies
Replies (11)
Message 2 of 12

Anonymous
Not applicable
I've just faced this JIT problem, and it seems a lot of people are having this problem, and no one knows just what to do about it. Why doesn't Autodesk have an answer for it? To say it's a Microsoft problem is bogus, I'm having the problem with AutoCAD. Autodesk needs to say "this is how you resolve JIT issues".
0 Likes
Message 3 of 12

Anonymous
Not applicable
There's no such thing as a "JIT problem". The "JIT error" dialog appears when your program crashes because of a bug.

The problem is in your code, and you shouldn't expect Autdesk (or Microsoft) to tell you what's wrong with your code.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009
http://www.acadxtabs.com

wrote in message news:5889369@discussion.autodesk.com...
I've just faced this JIT problem, and it seems a lot of people are having this problem, and no one knows just what to do about it. Why doesn't Autodesk have an answer for it? To say it's a Microsoft problem is bogus, I'm having the problem with AutoCAD. Autodesk needs to say "this is how you resolve JIT issues".
0 Likes
Message 4 of 12

Anonymous
Not applicable
Last I checked Autodesk gives us these apis for free. Why should they have to teach us to use the
languages to attack them?

wrote in message news:5889369@discussion.autodesk.com...
I've just faced this JIT problem, and it seems a lot of people are having this problem, and no one knows just what to do about it.
Why doesn't Autodesk have an answer for it? To say it's a Microsoft problem is bogus, I'm having the problem with AutoCAD. Autodesk
needs to say "this is how you resolve JIT issues".
0 Likes
Message 5 of 12

Anonymous
Not applicable
There's the rub, I'm not writing any code. I just added a tool to a ribbon panel. Isn't that something ACAD is suppose to be able to do? Or is that considered code writing

This is the second time it's occurred. The first time was because a Tech from Dell removed the battery from my computer. When he put it back in, ACAD didn't work. I finally found out the clock in my taskbar was not set right. I reset the clock and all was good. Why? I don't know.

This time I discovered that ACAD would work if I clicked on the file. Go figure, why did it work opening it that way? So I deleted my shortcut to ACAD and made a new one. Guess what? It worked!

I don't know what the "Bug" is, but is there something that can be done to prevent the continual crashing after the initial crash? It use to be when a crash occurred you could just shut it down and fire it back up again. Now it punishes you till you figure it out.
0 Likes
Message 6 of 12

Anonymous
Not applicable
I don't know what an apis is, and I don' know what this language is that attacks them, but I paid for AutoCAD and Windows. I also paid for a seat that included upgrades and I thought a little support. I'm not asking to be taught anything, just helped out a little with problem. In searching the web, I only found a lot of people asking questions. My problem is strictly on AutoCAD, nothing else is effected. AutoCAD is the only program that has had this problem. I was just thinking, Maybe there's a reason?
0 Likes
Message 7 of 12

Anonymous
Not applicable
Since you posted to a programming group we assumed this happened while programming. I have been using the last three beta versions
and now the release version and have yet to see this while customizing the ribbon via the cui.
wrote in message news:5889539@discussion.autodesk.com...
I don't know what an apis is, and I don' know what this language is that attacks them, but I paid for AutoCAD and Windows. I also
paid for a seat that included upgrades and I thought a little support. I'm not asking to be taught anything, just helped out a
little with problem. In searching the web, I only found a lot of people asking questions. My problem is strictly on AutoCAD, nothing
else is effected. AutoCAD is the only program that has had this problem. I was just thinking, Maybe there's a reason?
0 Likes
Message 8 of 12

Anonymous
Not applicable
btw... Try the AutoCAD 2009 group - I haven't seen any jit error complaints though.

"Paul Richardson" wrote in message news:5889540@discussion.autodesk.com...
Since you posted to a programming group we assumed this happened while programming. I have been using the last three beta versions
and now the release version and have yet to see this while customizing the ribbon via the cui.
wrote in message news:5889539@discussion.autodesk.com...
I don't know what an apis is, and I don' know what this language is that attacks them, but I paid for AutoCAD and Windows. I also
paid for a seat that included upgrades and I thought a little support. I'm not asking to be taught anything, just helped out a
little with problem. In searching the web, I only found a lot of people asking questions. My problem is strictly on AutoCAD, nothing
else is effected. AutoCAD is the only program that has had this problem. I was just thinking, Maybe there's a reason?
0 Likes
Message 9 of 12

Anonymous
Not applicable
Sorry, didn't know this a programming forum. I came to it by looking in the ACAD help files. I thought it was weird that they posed the problem in help and then didn't answer the question. First timer here, so I will bow out gracefully.
0 Likes
Message 10 of 12

Anonymous
Not applicable
kvnbrn-

Your not the only one experiencing this issue in 2009.
0 Likes
Message 11 of 12

Anonymous
Not applicable
That was my second time having that kind of error, It resolved after updating .NET. I don't know if that is the actual solution, but I tell my people to keep there computers updated now.
0 Likes
Message 12 of 12

Anonymous
Not applicable

The upgrade of .Net did not work. I also tried all versions of .Net individually.

 

I am still having this error every time when starting Autocad 2008.

 

I agree with you...The answers from Autodesk employees are very frustating. They just blame it on Windows. But strange is that no other application has this problem.

0 Likes