Export (0) Print
Expand All

Just-In-Time Debugging Errors

The following error messages can occur when you are trying to do Just-In-Time debugging.

  • An unhandled win32 exception occurred in <program>. Just-In-Time debugging this exception failed with the following error: The logged in user did not have access to debug the crashing application.

    This message indicates that an attempt to do Just-In-Time debugging failed because the user does not have proper access permissions. For more information, see Remote Debugging Permissions.

    To debug ASP.NET, you must have Administrator privileges on the machine where ASP.NET runs, unless the ASP.NET worker process is running under the account you are debugging from. For more information about ASP.NET security requirements, see ASP.NET Debugging: System Requirements.

  • Unable to attach to the crashing process. The specified program is not a Windows or MS-DOS program.

    This error occurs when you try to attach to a process running as another user under Windows 2000.

    To fix this problem, open the Attach to Process dialog box from the Debug menu and find the crashing process in the Available Processes list. If you do not know the name of the crashing process, look at the Visual Studio Just-In-Time Debugger dialog and note the process ID. Select the process in the Available Processes list and click Attach. In the Visual Studio Just-In-Time Debugger dialog, click No to dismiss the dialog box.

  • Debugger could not be started because no user is logged on.

    This error occurs if you attempt to do Just-In-Time debugging on a machine where there is no user logged onto the console. As a result, there is no session in which to display the Just-In-Time debugging dialog box.

    To fix this problem, log onto the machine.

  • JIT Debugging failed with the following error: 0x80040003.

    This error occurs if you attempt to use Visual Studio 6.0 as the Just-In-Time debugging debugger for the desktop process, usually explorer.exe. Visual Studio 6.0 does not support the debugging of the desktop process.

    To fix this problem, use Visual Studio to debug the desktop process.

  • Class not registered.

    This error indicates that the debugger tried to create a COM class that should be registered, but is not, probably due to an installation problem.

    To fix this problem, use the setup disk to reinstall or repair your Visual Studio installation.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft