Rtp36 (OpenInsight 16-Bit Specific)
At 18 AUG 2002 10:10:18PM Mark B wrote:
Hi All
Sorry for the limited information on this one.
We have a client that has reported the following error message, however they are unable to provide a specific process or pattern to cause it. No other clients have reported it and we are unable to reproduce it.
The error they reported is ENG0031 RTP36 Stack Overflow.
After a search I now know that RTP36 refers to the Lock Processor. On it's own, this doesn't really solve the problem.
Any other thoughts?
TIA
Mark
At 20 AUG 2002 09:26AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Would appear to be some sort of invalid handle or a slight memory blip. Can the client readily reproduce this?
World Leaders in all Things RevSoft
At 20 AUG 2002 09:28AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Would appear to be some sort of invalid handle or a slight memory blip. Can the client readily reproduce this?
World Leaders in all Things RevSoft
At 20 AUG 2002 08:18PM Mark B wrote:
They can reproduce it in the sense that it happens regularly from the one window.
They can't readily reproduce it by knowingly following a specific pattern.
There are suggestions that it occurs when swapping between two particular combo boxes. One displays a list of names from a common variable, the other calls the popup_year function.
Having said that, I and others have still not been able to reproduce it ourselves.
Using OI 3.7.2 on Win 98 SE
Mark
At 21 AUG 2002 09:00AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Interesting, since POPUP_YEAR does not call lock, and loading values from a common should not call lock either. Since this is an OE error, not a Windows error, it's most likely some form of corrupt handle or bad call to the lock opcode. Can they force the error to occur? If you start and LH2.LOG file and have then generate the error, you can look at the lock call being made. The file and key might give an idea on where to look.
Could there be an MFS that's sitting around? Perhaps some locks are not getting unlocked and the local lock table is filling up.
World Leaders in all Things RevSoft
At 22 AUG 2002 06:58PM Mark B wrote:
Thanks Sprezz
I will get back to you some time next week when I have had a chance to create the log file and test.
Unfortunately this client is interstate with no way of dialling in and our interstate rep is up here with us this week.
Makes things a little bit difficult.
Thanks again for your suggestions
Mark