the script debugger failed to connect to the target process. Adebugger is already attached

Question

Windonws 7 64-bit and VS2010

In F12 developer tools for IE11 on Windonws 7 64-bit and VS2010, when I click the Debugger tool icon or press Ctrl + 3 to open the tool, I'm not able to debug my java-script files.

When I click the Debugger tool icon, i'm presented with the message in the screenshot above & I can't see the javacsript files my current page calls, so I'm unable to debug my javascript code.

Any one knows why I could be getting this message? I have tried everything mentioned at the following link with out success. VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed

Answer 1

I was encountering this problem with VS 2012 & Win 7 and also VS2013 and Win8.1:

Perplexed for half a day, looking up things online, finally figured it out myself.

Learn the difference between these in Visual Studio: F5 vs (Ctr+Shift+W)

F5 will engage VS debugger and you will get the:

"The script debugger failed to connect to the target process. A debugger is already attached"

when using the F12 Developer Tool in I.E. 11 or whatever version.

However, if you use the V.S. command: View in Browser(Ctrl+Shift+W) this will run the script and allow I.E's script debugger(F12 Dev Tool) to engage and work.

Answer 2

You should use ctrl+F5 instead of F5 so your application runs without debugging

Answer 3

I see this post is referred to Windonws 7 64-bit and VS2010, but I am using Windows 10 32 bit and VS Professional 2012 along with IE 11. I got the same message as shown in screenshot:

IE 11 Error message

How I resolved this problem(after starting Debugging):

• went to debug tab in VS
• then windows
• select processes

There you will see two processes attached one will be "IIS" and second will be "IE.exe" with description "script". Detach the second one and then hit F12 in IE where your code is running.

Answer 4

The easier way for me was:

1. Run project(F5) in Firefox (or any other browser, not IE).
2. Copy adress.
3. Close Firefox (project will keep running, atleast did in myn).
4. Open IE and input address manually (ex: http://localhost:58100/) by pasting what you copied in '2.'.
5. IE Debugger should work at this point.

Answer 5

When I did iisreset from command prompt, I could resolve this issue.

Open CMD in admin mode -> type IISRESET -> enter