Activation context being deactivated ...

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi
I am using CodeJock 11.1.3 with Progress (OpenEdge 10.1B).  I get fairly random 'memory cannot be read' errors and I think have managed to narrow it down to the 'recalclayout()' docking pane method.  It throws a C015000F exception  I have found these comments on the internet concerning this exception:

If the activation context is on the stack, but not the top of the 
stack, Sxs throws exception STATUS_SXS_EARLY_DEACTIVATION (0xC015000F), with the message 'The activation context being deactivated is not the most recently activated one'.

'The most likely reason is that someone calls ActivateActCtx on entrance, but forgets to call DeactivateActCtx on exit. 

Does this mean anything to you CodeJock technicians?  Is there a known problem with recalclayout() ?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
muldoon96 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 16 February 2007 Status: Offline Points: 8	Post Options Post Reply Quote muldoon96 Report Post Thanks(0) Quote Reply Topic: Activation context being deactivated ... Posted: 01 May 2008 at 6:11am
	Hi I am using CodeJock 11.1.3 with Progress (OpenEdge 10.1B). I get fairly random 'memory cannot be read' errors and I think have managed to narrow it down to the 'recalclayout()' docking pane method. It throws a C015000F exception I have found these comments on the internet concerning this exception: If the activation context is on the stack, but not the top of the stack, Sxs throws exception STATUS_SXS_EARLY_DEACTIVATION (0xC015000F), with the message 'The activation context being deactivated is not the most recently activated one'. 'The most likely reason is that someone calls ActivateActCtx on entrance, but forgets to call DeactivateActCtx on exit. Does this mean anything to you CodeJock technicians? Is there a known problem with recalclayout() ?

Smucker Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 02 February 2008 Status: Offline Points: 156	Post Options Post Reply Quote Smucker Report Post Thanks(0) Quote Reply Posted: 01 May 2008 at 12:59pm
	I saw this error recently when I was trying to convert an enormous project (with many libraries and DLLs) from static linking to DLLs for MFC, MSVCRT and Codejock on VS 2005 (to take care of C file handle issues between the main application and Python scripts). I could not find a decent explanation of the issue anywhere, so I eventually gave up and went back to static linking (which I prefer anyway). IIRC, I was seeing the problem in MFC code unrelated to Codejock.