We help IT Professionals succeed at work.

The Just-In-Time debugger does not have permission to inspect the process's identity

viralypatel
viralypatel asked
on
Medium Priority
508 Views
Last Modified: 2012-05-12
I'm trying to invoke a console application from a web site using Process.Start

Executing the console application directly using command prompt has no issues. But when executing through the website using process.start i see the following error in the event viewer and the exe crashes. Cannot see any popup as the exe is running in the background.
======================================

Event Type:      Error
Event Source:      VsJITDebugger
Event Category:      None
Event ID:      4096
Date:            11/2/2011
Time:            1:10:11 PM
User:            systemname\ASPNET
Computer:      systemname
Description:
An unhandled exception ('System.Configuration.ConfigurationErrorsException') occurred in myexe.exe [2688]. Just-In-Time debugging this exception failed with the following error: The Just-In-Time debugger does not have permission to inspect the process's identity.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 36 00 04 80               6..¿    

===============================
Comment
Watch Question

Author

Commented:
I also see this error in event viewer every time along with the one mentioned above :
==========
EventType clr20r3, P1 myexe.exe, P2 1.0.0.0, P3 4eb10764, P4 system.configuration, P5 2.0.0.0, P6 4889de74, P7 1a6, P8 136, P9 ioibmurhynrxkw0zxkyrvfn0boyyufow, P10 NIL.
==========
Hello:
It seems that your app is using a config file with errors, or your app have not access to the file. If you are starting it from an asp.net app, be sure that the user which is running the app poll has at least read access to the config file.
Best regards.
Figured it out myself, the JIT debugger was because of unhandled execeptions in a few methods. Adding try catch blocks to each resolved the issue.

For the second issue in my comment above, had to register .net v2 using aspnet_regiis.exe

Author

Commented:
Figured it out myself. Closing the question.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.