Thursday, May 1, 2008

Visual studio just -in -time debugger pop-up comes time to time

Problem description: Someone installed SQL Server 2005 and Visual Studio 2005, since these are installed they have started to get errors similar to the following:

...............................................................................................

Visual studio just -in -time debugger
...............................................................................................
An unhandled win32 exception occured in ieexplre.exe[528].

posiible debuggers:
New instance of visual studio 2005

.(combo button)set the currently selected debugger as the default.
.(combo button)manually choose the debugging engines

Do u want to debug using the selected debugger?

Yes No
...................................................................................................


Cause: Due to SQL 2005 seems like windows has decided to use Visual Studio debugger for the exceptions instead of sticking to Dr.Watson.

Resolution:
Just_in_time_debugger try to catch exceptions which are not being caught by the program or I could say missing some code. Some times these exceptions does not need to be caught (even though its not good practice for programmers) but because you have Just-In-Time debugger installed/configured it will not only catch it for internet explorer but for other applications as well. In short any application which will have exception which is not being caught you will get this error message. Click on when you see it. You do not need to debug IE.

There are few keys which controls Just-In-Time-Debugger try one of the following:

Please try one at a time only:

1. Go to command prompt using CMD command in run box.
on command prompt run the following Dr.Watson command command and restart computer

drwtsn32 -i

2. Use Regedit and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

Export Debugger hive and then delete it.

WARNING: this key might resolve this issue of debugger but It might not help you if you are trying to code something and looking for traping mishandled exceptions.

No comments: