Unhandled exceptions are caught by the Visual Studio JIT debugger instead of Dr. Watson or a third-party debugger after you install certain versions of SQL Server 2005
Symptoms
Consider the following scenario:You use the Dr. Watson program or a third-party debugger to catch unhandled exceptions that may occur when a program is running.You install one of the following Microsoft products:SQL Server 2005 Standard EditionSQL Server 2005 Developer EditionSQL Server 2005 Enterprise EditionSQL Server 2005 Workgroup EditionAny product that contains one of the previously listed products
(For example, you install Microsoft Windows Small Business Server 2003 R2 Premium Edition.)In this scenario, later unhandled exceptions are caught by the Microsoft Visual Studio just-in-time (JIT) debugger. For example, if a Data Execution Prevention (DEP) exception occurs, a dialog box appears that requires user intervention to either start JIT debugging or ignore the exception.
Resolution
This issue occurs because the SQL Server 2005 installation process calls the Visual Studio installation process. The Visual Studio installation process changes the default application debugger to the Visual Studio JIT debugger. This change occurs regardless of which debugger you previously used. You do not receive any notification that this change has occurred.
