0xC015000F: The activation context being deactivated is not the most recently activat
Hello All,
I was struck with a serious issue with my MFC dialog based project which uses COM.Until last week it worked well without any issues, but suddenly it gives the "0xC015000F: The activation context being deactivated is not the most recently activatated" error.
I have gone through lot of forums and knew that "afxAmbientActCtx = FALSE" statement inclusion under CWinApp::InitInstance() will avoid the issue.
I followed the same way, but still getting the same error.
Can anybody help me, this is very urgent task for me.
Thanks In Advance.
Re: 0xC015000F: The activation context being deactivated is not the most recently act
I encountered several times that error. It is caused by a bug in your application. You made some sort of mistake in one of the source files, more precisely in ANOTHER FILE THAN THE FILE WHERE THE ERROR IS REPORTED. This was the explanation I found long time ago on the MSDN, I cannot point at this time where exactly. The explanation was proven correct every time I encountered that error. It's really painful to find such a bug but you have no option than to look for it.
Re: 0xC015000F: The activation context being deactivated is not the most recently act
Originally Posted by badriprasad
Hello All,
I was struck with a serious issue with my MFC dialog based project which uses COM.Until last week it worked well without any issues, but suddenly it gives the "0xC015000F: The activation context being deactivated is not the most recently activatated" error.
I have gone through lot of forums and knew that "afxAmbientActCtx = FALSE" statement inclusion under CWinApp::InitInstance() will avoid the issue.
I followed the same way, but still getting the same error.
Can anybody help me, this is very urgent task for me.
Thanks In Advance.
OS: Windows XP, sp3
IDE: Visual Studio 2005, sp2
It's interesting you get that error on VS2005.
I had been on VS2005 until 2 weeks ago when I finally upgraded to VS2010.
As soon as I upgraded to VS2010, I started getting that error whenever a window in my MDI application closed. As you mentioned, adding the afxAmbientActCtx = FALSE; statement in the InitInstance() fixed the issue.
However, as far as I can tell, that fix is specifically for when the error appears in VS2010 - if you're getting it in VS2005, there probably is something else wrong.
Re: 0xC015000F: The activation context being deactivated is not the most recently act
Hello Cilu,
Thank you very much for your reply.
I installed the updates which you specified.Now I am getting a new error:
When I switch to any other window while debuggig my application, the app thrwos error saying that "First-chance exception at 0x7824a186 (mfc80d.dll) in Logix3200MDSnapOn.exe: 0xC0000005: Access violation reading location 0xfdfdff0d."
The error is thrown in wincore.cpp in AfxCallWndProc(CWnd* pWnd, HWND hWnd, UINT nMsg) function at line:
// delegate to object's WindowProc
lResult = pWnd->WindowProc(nMsg, wParam, lParam);
Any idea how to fix this, earlier my app has worked fine with same code.
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan
* The Best Reasons to Target Windows 8
Learn some of the best reasons why you should seriously consider bringing your Android mobile development expertise to bear on the Windows 8 platform.