Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Debugging / October 2003

Tip: Looking for answers? Try searching our database.

JIT debugging not working after installation of VS.NET 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Benoit - 23 Oct 2003 09:27 GMT
I have desinstalled VS.NET 2002 and VB6 in order to install VS.NET
2003. Everything is working properly, except when there is an
exception : I receive the message "JIT debugging failed with the
following error: 0x800405a6" in place of the normal message box
showing the exception message and stack trace.

I have tried to desinstall and re-install VS, but I still have the
same problem.

I also tried to desinstall and re-install VS.NET 2002, but the problem
keeps annoying me.

Does anybody know what I must do ?

Thanks,
Benoit
Andy Pennell [MSFT] - 23 Oct 2003 22:14 GMT
Have you tried Tools / Options / Debugging / JIT and disabling VS as the JIT debugger? That way the system should fall back to the default JIT debugger.

Signature

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.  
--------------------

> From: benoit.penelle@trasys.be (Benoit)
> Newsgroups: microsoft.public.vsnet.debugging
[quoted text clipped - 10 lines]
> NNTP-Posting-Date: Thu, 23 Oct 2003 08:27:25 +0000 (UTC)
> Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!diablo.theplanet.net!news.maxwell.syr.edu!
postnews1.google.com!not-for-mail
> Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.debugging:3862
> X-Tomcat-NG: microsoft.public.vsnet.debugging
[quoted text clipped - 15 lines]
> Thanks,
> Benoit
Penelle, Beno?t - 24 Oct 2003 15:28 GMT
Thanks for your answer, but I have tried and it does not solve the problem.

When I disable JIT debugging in the options, I receive the message "JIT
Debugging is disabled. To enable JIT Debugging, from Visual Studio .NET go
to Tools/Options/Debugging/JIT Sesstings". When I re-enable JIT debugging in
the options, I receive the "JIT debugging failed with the following error:
0x800405a6" message again.

Seems to me that maybe some registry/config settings are not reset when you
desinstall VS.NET ?

Any other idea ?

Benoit

> Have you tried Tools / Options / Debugging / JIT and disabling VS as the JIT debugger? That way the system should fall back to the default JIT
debugger.

originated.
> --------------------
> > From: benoit.penelle@trasys.be (Benoit)
[quoted text clipped - 11 lines]
> > NNTP-Posting-Date: Thu, 23 Oct 2003 08:27:25 +0000 (UTC)
> > Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!diablo.theplanet.net!news.maxwell.syr.edu!
> postnews1.google.com!not-for-mail
> > Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.debugging:3862
[quoted text clipped - 16 lines]
> > Thanks,
> > Benoit
Andy Pennell [MSFT] - 24 Oct 2003 22:12 GMT
You could try vs7jit.exe /regserver to re-register the key component.

Which JIT are you trying to enable (native/clr/script)?

Do you get the error when enabling the other JIT options?

Signature

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.  
--------------------

> From: "Penelle, Beno?t" <benoit.penelle@trasys.be>
> Newsgroups: microsoft.public.vsnet.debugging
[quoted text clipped - 62 lines]
> > > Thanks,
> > > Benoit
Penelle, Beno?t - 28 Oct 2003 08:43 GMT
Hi Andy,

I tried vs7jit.exe /regserver, but without success.

Here is the problem. I am working with a console application. On my PC, when
there is an exception, I receive a dialog box showing an error (JIT
debugging failed with the following error: 0x800405a6). On another PC, I
receive the correct dialog box asking me which debugger I want to use (An
exception 'System.Exception' has occurred in ConsoleApp.exe. Possible
Debuggers:... Do you want to debug using the selected debugger ?).

What do I have to do to correct the configuration of my PC, knowing that
desinstall/reinstall of VS.NET and the .NET Framework doesn't work ?

Thanks,
Benoit

> You could try vs7jit.exe /regserver to re-register the key component.
>
> Which JIT are you trying to enable (native/clr/script)?
>
> Do you get the error when enabling the other JIT options?

originated.
> --------------------
> > From: "Penelle, Beno?t" <benoit.penelle@trasys.be>
[quoted text clipped - 41 lines]
> > > > NNTP-Posting-Date: Thu, 23 Oct 2003 08:27:25 +0000 (UTC)
> > > > Path:

cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
> > e.de!diablo.theplanet.net!news.maxwell.syr.edu!
> > > postnews1.google.com!not-for-mail
[quoted text clipped - 17 lines]
> > > > Thanks,
> > > > Benoit

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.