Forum posts for iexplore.exe

VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed

So I am using Win7 x64 with VS2010 and have installed the IE10 Win7 Preview and ReSharper 6.1.

When I attempt to Start Debugging, I receive the following:


'Attaching the Script debugger to process '[1111] iexplore.exe' on
machine 'MINE' failed. A debugger is already attached.'


I can click OK and look at attached debug sessions - [1111] is grayed out and there is another instance of iexplore.exe with my solution title. I can attach manually and it works fine.

I thought maybe since there were two iexplore.exe pids there would be something wrong, there are not two tabs or windows open and I disabled automatic crash recovery.

Tried this:
Attaching the Script debugger to process '[XXXX] IEXPLORE.EXE' on machine 'NAME' failed

Did not work.

Any ideas?

View complete forum thread with replies

Other posts related to iexplore.exe

See Related Forum Messages: Follow the Links Below to View Complete Thread

How can I find programatically where iexplore.exe is?
Strange ProcessorAffinity issue with IEXPLORE.exe
iexplore.exe process opens but I can't see it
Batch file to terminate all instances of IExplore.exe
Debugging SHDocVw.InternetExplorer.Quit not closing iexplore.exe process
Process.Start(“IExplore.exe”); <— Is this reliable?
VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed
How to capture keystrokes of iexplore.exe only?
Process.Start(“IEXPLORE.EXE”) immediately fires the Exited event after launch.. why?
Unhandled exception at 0x75619617 (KernelBase.dll) in iexplore.exe
Process.Kill does not seem to work with iexplore.exe
invoke iexplore.exe in already launched instance using ShellExecuteEx
Run iexplore.exe invisibly
Attaching the Script debugger to process '[XXXX] IEXPLORE.EXE' on machine 'NAME' failed
Can I pass the -f parameter to iexplore.exe when using Watir?

What is the carbon footprint of your coffee?

Is it low? Is it high? Can this things really kill the planet Earth? Maybe the answer will surprise you. Maybe not.