The Just-In-Time debugger was launched without necessary security permission

Question

We are working on vs 2010 windows 7, 32 bit and the project is running under target framework 3.5.

Now we are implementing credit card process in the website project

Answer 1

I don't know if your problem had the same cause, but I got this error when trying to debug my app (just pressing F5).

We got crazy trying to figure why the w3wp.exe was failing with this error when minutes before it was running fine.

After some investigation we realized that the real problem was in the code of the global.asax: it was throwing an stack overflow exception (pretty ironic for answering here) and that was crashing the w3wp.exe process before VS could attach it to begin debug.

Fixing the buggy code made the VS to run nicely again.

I see the question is from long ago, but I hope it helps somebody.

Answer 2

If you usually attach to process and debug but you can't (because you can't get the app to successfully run), run the app via Visual Studio and it'll break and show you the exception cause in some detail.

Answer 3

I believe an update to the latest version of VS and .NET Core 2.1 is what caused this for me.

Then for the first time, I noticed this setting. Setting it to 'Enabled' fixed it for me.

Answer 4

To solve this issue, let the dialog help you. Agree to launch an elevated debugger and debug your problem. You probably have some sort of configuration problem. Your real problem isn't whether or not the debugger is elevated, it's the fact you need a debugger at all. In other words the first sentence on the dialog is "you have a problem." All the other sentences are "I would like to help you with that problem; is that cool with you?"

Answer 5

In my case it was stackoverflow due to circular dependency injection

public class ServiceA : IServiceA
{
   public ServiceA(IServiceB serviceB){...}
}

public class ServiceB : IServiceB
{
   public ServiceB(IServiceA serviceA){...}
}

Answer 6

Please check for System.Diagnostics.Debugger.Launch(); or Debugger.Launch(); in the cs file. Commenting the code, starting the application worked fine for me.!