Alex Angas
Alex Angas

Reputation: 60047

Why am I often getting error 0x8007000e when debugging a project in Visual Studio?

I have a Visual Studio 2008 project that is proving difficult to debug. I need to attach to IIS 7 to debug it. At least 50% of the time I get the following error shortly after attaching to w3wp.exe:

---------------------------
Microsoft Visual Studio
---------------------------
A fatal error has occurred and debugging needs to be terminated.
For more details, please see the Microsoft Help and Support web site.
HRESULT=0x8007000e. ErrorCode=0x0.
---------------------------
OK   
---------------------------

It then terminates w3wp.exe.

I don't get this problem with any other solution. Any ideas on how to fix this please?

Upvotes: 6

Views: 9356

Answers (3)

C.L.
C.L.

Reputation: 452

Had the same issue when I was working with web services based application. I used Visual Studio 2012 + Win 7 (32bit) OS.

NONE of the solutions that I found with google has worked for me (wasn't a RAM or disk space problem).

The only solution that worked for me: installing Win 7 64 bit OS.

Just backup your data & install 64bit OS + apply latest Win Updates.

Upvotes: 1

Robert H
Robert H

Reputation: 11730

This is also an issue with Visual Studio 2012 on a console project. Oddly enough the same projects in Visual studio 2010 do not cause the same issue.

Whereas it didn't provide the information I needed, I found that you can launch without debugging and then attach the debugger to the process to gain access to your breakpoints without triggering the error.

For what its worth, I have noticed in a few posts online that people who are experiencing the issue tend to have multiple projects within the solution (including the OP).

Upvotes: 2

tidwall
tidwall

Reputation: 6949

If you Google this error you'll find a lot of information about it.

0x8007000e = The application is out of memory. Perhaps your computer does not have enough RAM and/or disk space.

Upvotes: 7

Related Questions