Home Dashboard Directory Help
Search

Just-In-Time debugging, operation attempted is not supported by Niklas Bergius


Status: 

Closed
 as Duplicate Help for as Duplicate


6
0
Sign in
to vote
Type: Bug
ID: 770786
Opened: 11/12/2012 2:33:02 AM
Access Restriction: Public
2
Workaround(s)
view
4
User(s) can reproduce this bug

Description

Using IIS8 on Windows 8, when trying to launch debugging on app start (with Debugger.Launch()) nothing happens and the event log says:

An unhandled Microsoft .NET Framework exception occurred in w3wp.exe [8040]. Just-In-Time debugging this exception failed with the following error: The operation attempted is not supported.
Details
Sign in to post a comment.
Posted by deadeye on 7/10/2014 at 4:44 AM
@Wili Whitelow
On my Windows 8.1 system, with VS2012 installed, the workaround functions as intended.
Posted by Wili Whitelaw on 10/18/2013 at 6:53 AM
Windows 8.1 breaks the workaround
Posted by Microsoft on 7/22/2013 at 1:42 PM
@btj-agilent, this is fixed in Visual Studio 2013 and you can try it out on Vs2013 Preview.
Posted by btj-agilent on 7/22/2013 at 1:35 PM
Does anyone happen to know what the "Duplicate" of this bug was, and if/when/how that one was fixed? Or, is hand-editing the registry actually the "permanent" solution?
Posted by David Beavonn on 5/21/2013 at 8:04 AM
I must agree with Ethan and deadeye that 8 works, and the other did not (x20 (32)). This is in the context of debugging .Net Windows services. (I'm not doing any IIS).


I should also add that Debugger.Break() causes major problems for me (as shown in the Windows application log). I had better luck with Debugger.Launch()
Posted by deadeye on 2/5/2013 at 4:11 AM
The registry key from Ethan works. Thanks.
Posted by Niklas Bergius on 1/22/2013 at 2:48 AM
Workaround works. Thank you.
Posted by Microsoft on 1/17/2013 at 4:10 PM
Thanks Ethan for confirmation and the reg key value which worked for you. reg key values mentioned in workaround is hex value.
@deadeye, can you please try out the reg value suggested by Ethan?
Posted by Ethan McGee on 1/17/2013 at 3:55 PM
The workaround is almost correct. Set the registry key to 8 rather than 20.
Posted by deadeye on 1/7/2013 at 7:52 AM
I tried out the workaround but nothing happened and the same exception occurs and logged in my eventlog.
Posted by Microsoft on 12/31/2012 at 12:37 AM
can you please try workaround and let us know if this fixes the issue you are seeing?
Posted by deadeye on 11/21/2012 at 9:11 AM
Hello, i can reproduce the same behavior, but not with IIS.
I use the "Debugger.Launch()" within my Service for simply attaching.

With Win7 the JITDebugger Windows appeared to me, under Win8 nothing happend and i have the same Exception in my Eventlog.
Posted by Microsoft on 11/15/2012 at 1:54 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 11/13/2012 at 12:10 AM
"Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a demo project. Please submit this information to us within 4 business days. We look forward to hearing from you with this information.
************************************************************
Please zip the file and use "FeedbackID-XXXXXX" as prefix of the file name.
************************************************************
You can use the following workspace to upload the file by IE: https://sftus.one.microsoft.com/choosetransfer.aspx?key=9415c965-6590-4d5f-8331-614ff9c106df
Password: Z1_)G37MTk
Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/12/2012 at 2:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by ewjnl on 12/8/2013 at 8:19 PM
I had to change the value to 0x8 - the same value as it was set to on another computer on which Debugger.Launch worked just fine.

I use VS2013, but I had VS2012 installed afterwards to get the VS2012 C++ toolset for a project that I hadn't worked on on this computer.
Posted by Anand Paranjape(MSFT) on 12/31/2012 at 12:36 AM
On Windows 8, open regedit and go to HKCR\AppID\{E62A7A31-6025-408E-87F6-81AEB0DC9347}"
for the ‘AppIDFlags’ registry value, set the flag 0x20 from the default value 0x28