Alaska Software Inc. - Neverending story - is anybody can help ?
Username: Password:
AuthorTopic: Neverending story - is anybody can help ?
Adrian WykrotaNeverending story - is anybody can help ?
on Fri, 24 Oct 2008 09:58:53 +0200
It is happened every work day...

FATAL ERROR LOG
System-Error
SYS Thread-ID: 700
Module: EVM
Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
Call Stack of Thread 1 (636):
MYAPPEVENT(419)
MYMENU(260)
MAIN(0)
Call Stack of GUI Thread (784):
Call Stack of Thread 3 (1472):
Call Stack of Thread 4 (1096):
Call Stack of Thread 5 (1156):
Call Stack of Thread 6 (1424):
Call Stack of Thread 7 (2192):
Call Stack of Thread 8 (2236):
Call Stack of Thread 9 (2808):
Call Stack of Thread 10 (2744):
Call Stack of Thread 11 (3776):
Call Stack of Thread 12 (3200):
Call Stack of Thread 13 (2636):
Call Stack of Thread 14 (3048):
Call Stack of Thread 15 (3424):
Call Stack of Thread 16 (3356):
Call Stack of Thread 17 (3492):
Call Stack of Thread 18 (3676):
Call Stack of Thread 19 (3968):
Call Stack of Thread 20 (4428):
Call Stack of Thread 21 (3876):
Call Stack of Thread 22 (3852):
Call Stack of Thread 23 (3036):
Call Stack of Thread 24 (3820):
Call Stack of Thread 25 (4264):
Call Stack of Thread 26 (3988):
Call Stack of Thread 27 (4496):
Call Stack of Thread 28 (4252):
Call Stack of Thread 29 (3932):
Call Stack of Thread 30 (4208):
Call Stack of Thread 31 (4652):
MYAPPEVENT(419)
DEKRETACJAFK(383)
OPENPACZKA(242)
(B)Paczki(115)
@XBPPUSHBUTTON@I@HANDLEEVENT(935)
PACZKI(194)
DLL_PROC(282)
(B)GETTABMENU@0066(0)
Call Stack of Thread 32 (4136):
Call Stack of Thread 33 (2576):
Call Stack of Thread 34 (4476):
Call Stack of Thread 35 (4728):
Call Stack of Thread 37 (4160):
Call Stack of Thread 38 (5336):
Call Stack of Thread 39 (5256):
Call Stack of Thread 40 (5300):
File: C:\Advantec\Program.Exe
TimeStamp: 20081024 09:15
End of FATAL ERROR LOG.

415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
416: LOCAL nRet := 0, bErr := {|| NIL}
417: bErr := ErrorBlock({|e|Break(e)})
418: BEGIN SEQUENCE
419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
420: RECOVER
421:   nRet := 0
422:   oXbp := NIL
423: END SEQUENCE
424: ErrorBlock(bErr)
425: RETURN (nRet)
*

Alaska xBase 1.90.345
Z powaaniem/Best regards
Adrian Wykrota
www.advantec-software.com.pl
Andreas HerdtRe: Neverending story - is anybody can help ?
on Fri, 24 Oct 2008 10:51:05 +0200
Hallo Mr Wykrota,

According your information you are using Xbase++
build level 345. You need to update to the most
recent drop which is build level 346. If the problem
persists then please post those SL1 Preview related
issues to the SL1 news group.

Thanks in advance.

Adrian Wykrota wrote:
> It is happened every work day...
> 
> FATAL ERROR LOG
> System-Error
> SYS Thread-ID: 700
> Module: EVM
> Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
> Call Stack of Thread 1 (636):
> MYAPPEVENT(419)
> MYMENU(260)
> MAIN(0)
> Call Stack of GUI Thread (784):
> Call Stack of Thread 3 (1472):
> Call Stack of Thread 4 (1096):
> Call Stack of Thread 5 (1156):
> Call Stack of Thread 6 (1424):
> Call Stack of Thread 7 (2192):
> Call Stack of Thread 8 (2236):
> Call Stack of Thread 9 (2808):
> Call Stack of Thread 10 (2744):
> Call Stack of Thread 11 (3776):
> Call Stack of Thread 12 (3200):
> Call Stack of Thread 13 (2636):
> Call Stack of Thread 14 (3048):
> Call Stack of Thread 15 (3424):
> Call Stack of Thread 16 (3356):
> Call Stack of Thread 17 (3492):
> Call Stack of Thread 18 (3676):
> Call Stack of Thread 19 (3968):
> Call Stack of Thread 20 (4428):
> Call Stack of Thread 21 (3876):
> Call Stack of Thread 22 (3852):
> Call Stack of Thread 23 (3036):
> Call Stack of Thread 24 (3820):
> Call Stack of Thread 25 (4264):
> Call Stack of Thread 26 (3988):
> Call Stack of Thread 27 (4496):
> Call Stack of Thread 28 (4252):
> Call Stack of Thread 29 (3932):
> Call Stack of Thread 30 (4208):
> Call Stack of Thread 31 (4652):
> MYAPPEVENT(419)
> DEKRETACJAFK(383)
> OPENPACZKA(242)
> (B)Paczki(115)
> @XBPPUSHBUTTON@I@HANDLEEVENT(935)
> PACZKI(194)
> DLL_PROC(282)
> (B)GETTABMENU@0066(0)
> Call Stack of Thread 32 (4136):
> Call Stack of Thread 33 (2576):
> Call Stack of Thread 34 (4476):
> Call Stack of Thread 35 (4728):
> Call Stack of Thread 37 (4160):
> Call Stack of Thread 38 (5336):
> Call Stack of Thread 39 (5256):
> Call Stack of Thread 40 (5300):
> File: C:\Advantec\Program.Exe
> TimeStamp: 20081024 09:15
> End of FATAL ERROR LOG.
> 
> 415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
> 416: LOCAL nRet := 0, bErr := {|| NIL}
> 417: bErr := ErrorBlock({|e|Break(e)})
> 418: BEGIN SEQUENCE
> 419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
> 420: RECOVER
> 421:   nRet := 0
> 422:   oXbp := NIL
> 423: END SEQUENCE
> 424: ErrorBlock(bErr)
> 425: RETURN (nRet)
> *
> 
> Alaska xBase 1.90.345


   Andreas Herdt
   Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------
Adrian WykrotaRe: Neverending story - is anybody can help ?
on Fri, 24 Oct 2008 13:15:51 +0200
Thank you, i will try on next week.

Z powazaniem/Best regards
Adrian Wykrota
www.advantec-software.com.pl

Uzytkownik <Andreas Herdt> napisal w wiadomosci 
news:7b3886a3$2e8b5681$833@news.alaska-software.com...
> Hallo Mr Wykrota,
>
> According your information you are using Xbase++
> build level 345. You need to update to the most
> recent drop which is build level 346. If the problem
> persists then please post those SL1 Preview related
> issues to the SL1 news group.
>
> Thanks in advance.
>
> Adrian Wykrota wrote:
>> It is happened every work day...
>>
>> FATAL ERROR LOG
>> System-Error
>> SYS Thread-ID: 700
>> Module: EVM
>> Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
>> Call Stack of Thread 1 (636):
>> MYAPPEVENT(419)
>> MYMENU(260)
>> MAIN(0)
>> Call Stack of GUI Thread (784):
>> Call Stack of Thread 3 (1472):
>> Call Stack of Thread 4 (1096):
>> Call Stack of Thread 5 (1156):
>> Call Stack of Thread 6 (1424):
>> Call Stack of Thread 7 (2192):
>> Call Stack of Thread 8 (2236):
>> Call Stack of Thread 9 (2808):
>> Call Stack of Thread 10 (2744):
>> Call Stack of Thread 11 (3776):
>> Call Stack of Thread 12 (3200):
>> Call Stack of Thread 13 (2636):
>> Call Stack of Thread 14 (3048):
>> Call Stack of Thread 15 (3424):
>> Call Stack of Thread 16 (3356):
>> Call Stack of Thread 17 (3492):
>> Call Stack of Thread 18 (3676):
>> Call Stack of Thread 19 (3968):
>> Call Stack of Thread 20 (4428):
>> Call Stack of Thread 21 (3876):
>> Call Stack of Thread 22 (3852):
>> Call Stack of Thread 23 (3036):
>> Call Stack of Thread 24 (3820):
>> Call Stack of Thread 25 (4264):
>> Call Stack of Thread 26 (3988):
>> Call Stack of Thread 27 (4496):
>> Call Stack of Thread 28 (4252):
>> Call Stack of Thread 29 (3932):
>> Call Stack of Thread 30 (4208):
>> Call Stack of Thread 31 (4652):
>> MYAPPEVENT(419)
>> DEKRETACJAFK(383)
>> OPENPACZKA(242)
>> (B)Paczki(115)
>> @XBPPUSHBUTTON@I@HANDLEEVENT(935)
>> PACZKI(194)
>> DLL_PROC(282)
>> (B)GETTABMENU@0066(0)
>> Call Stack of Thread 32 (4136):
>> Call Stack of Thread 33 (2576):
>> Call Stack of Thread 34 (4476):
>> Call Stack of Thread 35 (4728):
>> Call Stack of Thread 37 (4160):
>> Call Stack of Thread 38 (5336):
>> Call Stack of Thread 39 (5256):
>> Call Stack of Thread 40 (5300):
>> File: C:\Advantec\Program.Exe
>> TimeStamp: 20081024 09:15
>> End of FATAL ERROR LOG.
>>
>> 415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
>> 416: LOCAL nRet := 0, bErr := {|| NIL}
>> 417: bErr := ErrorBlock({|e|Break(e)})
>> 418: BEGIN SEQUENCE
>> 419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
>> 420: RECOVER
>> 421:   nRet := 0
>> 422:   oXbp := NIL
>> 423: END SEQUENCE
>> 424: ErrorBlock(bErr)
>> 425: RETURN (nRet)
>> *
>>
>> Alaska xBase 1.90.345
>
>
> -- 
>   Andreas Herdt
>   Alaska Software
>
> --------------------------------------------------------------------
>
> Technical Support:      support@alaska-software.com
>
> News Server:            news.alaska-software.com
> Homepage:               http://www.alaska-software.com
> WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm
>
> Fax European Office:    +49 (0) 61 96 - 77 99 99 23
> Fax US Office:          +1 (646) 218 1281
> --------------------------------------------------------------------
Charles Freeman Re: Neverending story - is anybody can help ?
on Wed, 26 Nov 2008 06:26:46 -0500
On Fri, 24 Oct 2008 10:51:05 +0200, Andreas Herdt wrote:

> Hallo Mr Wykrota,
> 
> According your information you are using Xbase++
> build level 345. You need to update to the most
> recent drop which is build level 346. If the problem
> persists then please post those SL1 Preview related
> issues to the SL1 news group.
> 
> Thanks in advance.
> 
> Adrian Wykrota wrote:
>> It is happened every work day...
>> 
>> FATAL ERROR LOG
>> System-Error
>> SYS Thread-ID: 700
>> Module: EVM
>> Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
>> Call Stack of Thread 1 (636):
>> MYAPPEVENT(419)
>> MYMENU(260)
>> MAIN(0)
>> Call Stack of GUI Thread (784):
>> Call Stack of Thread 3 (1472):
>> Call Stack of Thread 4 (1096):
>> Call Stack of Thread 5 (1156):
>> Call Stack of Thread 6 (1424):
>> Call Stack of Thread 7 (2192):
>> Call Stack of Thread 8 (2236):
>> Call Stack of Thread 9 (2808):
>> Call Stack of Thread 10 (2744):
>> Call Stack of Thread 11 (3776):
>> Call Stack of Thread 12 (3200):
>> Call Stack of Thread 13 (2636):
>> Call Stack of Thread 14 (3048):
>> Call Stack of Thread 15 (3424):
>> Call Stack of Thread 16 (3356):
>> Call Stack of Thread 17 (3492):
>> Call Stack of Thread 18 (3676):
>> Call Stack of Thread 19 (3968):
>> Call Stack of Thread 20 (4428):
>> Call Stack of Thread 21 (3876):
>> Call Stack of Thread 22 (3852):
>> Call Stack of Thread 23 (3036):
>> Call Stack of Thread 24 (3820):
>> Call Stack of Thread 25 (4264):
>> Call Stack of Thread 26 (3988):
>> Call Stack of Thread 27 (4496):
>> Call Stack of Thread 28 (4252):
>> Call Stack of Thread 29 (3932):
>> Call Stack of Thread 30 (4208):
>> Call Stack of Thread 31 (4652):
>> MYAPPEVENT(419)
>> DEKRETACJAFK(383)
>> OPENPACZKA(242)
>> (B)Paczki(115)
>> @XBPPUSHBUTTON@I@HANDLEEVENT(935)
>> PACZKI(194)
>> DLL_PROC(282)
>> (B)GETTABMENU@0066(0)
>> Call Stack of Thread 32 (4136):
>> Call Stack of Thread 33 (2576):
>> Call Stack of Thread 34 (4476):
>> Call Stack of Thread 35 (4728):
>> Call Stack of Thread 37 (4160):
>> Call Stack of Thread 38 (5336):
>> Call Stack of Thread 39 (5256):
>> Call Stack of Thread 40 (5300):
>> File: C:\Advantec\Program.Exe
>> TimeStamp: 20081024 09:15
>> End of FATAL ERROR LOG.
>> 
>> 415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
>> 416: LOCAL nRet := 0, bErr := {|| NIL}
>> 417: bErr := ErrorBlock({|e|Break(e)})
>> 418: BEGIN SEQUENCE
>> 419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
>> 420: RECOVER
>> 421:   nRet := 0
>> 422:   oXbp := NIL
>> 423: END SEQUENCE
>> 424: ErrorBlock(bErr)
>> 425: RETURN (nRet)
>> *
>> 
>> Alaska xBase 1.90.345

The same error is present in 1.90.331; I see these EVM errors in my
client's error logs all the time. It appears that none of the
hotfix/rollups (through 345 at least) have addressed the problem. Andreas,
has it been fixed subsequent to 345?
Andreas HerdtRe: Neverending story - is anybody can help ?
on Wed, 26 Nov 2008 20:33:28 +0100
Hi Charles,

Mr Wykrota did not bring this issue to the SL1 newsgroup, yet.
Insofar I have no idea wheather the most recent SL1 drop solved
his problem.

Beside of this a comparable Fatal Error does not mean that the
reason for the error is comparable. There are many different
reasons for identical symptoms in this area:

  * (wrong) usage of DllCall
   usage of JazzAge
   wrong usage of CAPI
  * (wrong) usage of (bad) third party
     libs (including ActiveX components)
   bad coding patterns
   bad hardware
  * .....

This list surely can be expanded.

It turned out that in more then 99% of the cases where this
kind of log files is produced, the reason is one of those from
above. None of the reasons from above neccessarily is a problem
in the Xbase++ Runtime.

To be sure on this it is required that we qualify each individual
problem. For this it is required to have some reproducable scenario
in our Labs. I have to admit that building a scenario is not easy
in cases where the error occurs not very frequently.

On the other hand it also turned out that in almost all cases the
reason can be detected on the way to create such a scenario. This
is not too surprising. On the way to bring the issue to the point
most often the problem discloses itself.



Charles Freeman wrote:
> On Fri, 24 Oct 2008 10:51:05 +0200, Andreas Herdt wrote:
> 
>> Hallo Mr Wykrota,
>>
>> According your information you are using Xbase++
>> build level 345. You need to update to the most
>> recent drop which is build level 346. If the problem
>> persists then please post those SL1 Preview related
>> issues to the SL1 news group.
>>
>> Thanks in advance.
>>
>> Adrian Wykrota wrote:
>>> It is happened every work day...
>>>
>>> FATAL ERROR LOG
>>> System-Error
>>> SYS Thread-ID: 700
>>> Module: EVM
>>> Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
>>> Call Stack of Thread 1 (636):
>>> MYAPPEVENT(419)
>>> MYMENU(260)
>>> MAIN(0)
>>> Call Stack of GUI Thread (784):
>>> Call Stack of Thread 3 (1472):
>>> Call Stack of Thread 4 (1096):
>>> Call Stack of Thread 5 (1156):
>>> Call Stack of Thread 6 (1424):
>>> Call Stack of Thread 7 (2192):
>>> Call Stack of Thread 8 (2236):
>>> Call Stack of Thread 9 (2808):
>>> Call Stack of Thread 10 (2744):
>>> Call Stack of Thread 11 (3776):
>>> Call Stack of Thread 12 (3200):
>>> Call Stack of Thread 13 (2636):
>>> Call Stack of Thread 14 (3048):
>>> Call Stack of Thread 15 (3424):
>>> Call Stack of Thread 16 (3356):
>>> Call Stack of Thread 17 (3492):
>>> Call Stack of Thread 18 (3676):
>>> Call Stack of Thread 19 (3968):
>>> Call Stack of Thread 20 (4428):
>>> Call Stack of Thread 21 (3876):
>>> Call Stack of Thread 22 (3852):
>>> Call Stack of Thread 23 (3036):
>>> Call Stack of Thread 24 (3820):
>>> Call Stack of Thread 25 (4264):
>>> Call Stack of Thread 26 (3988):
>>> Call Stack of Thread 27 (4496):
>>> Call Stack of Thread 28 (4252):
>>> Call Stack of Thread 29 (3932):
>>> Call Stack of Thread 30 (4208):
>>> Call Stack of Thread 31 (4652):
>>> MYAPPEVENT(419)
>>> DEKRETACJAFK(383)
>>> OPENPACZKA(242)
>>> (B)Paczki(115)
>>> @XBPPUSHBUTTON@I@HANDLEEVENT(935)
>>> PACZKI(194)
>>> DLL_PROC(282)
>>> (B)GETTABMENU@0066(0)
>>> Call Stack of Thread 32 (4136):
>>> Call Stack of Thread 33 (2576):
>>> Call Stack of Thread 34 (4476):
>>> Call Stack of Thread 35 (4728):
>>> Call Stack of Thread 37 (4160):
>>> Call Stack of Thread 38 (5336):
>>> Call Stack of Thread 39 (5256):
>>> Call Stack of Thread 40 (5300):
>>> File: C:\Advantec\Program.Exe
>>> TimeStamp: 20081024 09:15
>>> End of FATAL ERROR LOG.
>>>
>>> 415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
>>> 416: LOCAL nRet := 0, bErr := {|| NIL}
>>> 417: bErr := ErrorBlock({|e|Break(e)})
>>> 418: BEGIN SEQUENCE
>>> 419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
>>> 420: RECOVER
>>> 421:   nRet := 0
>>> 422:   oXbp := NIL
>>> 423: END SEQUENCE
>>> 424: ErrorBlock(bErr)
>>> 425: RETURN (nRet)
>>> *
>>>
>>> Alaska xBase 1.90.345
> 
> The same error is present in 1.90.331; I see these EVM errors in my
> client's error logs all the time. It appears that none of the
> hotfix/rollups (through 345 at least) have addressed the problem. Andreas,
> has it been fixed subsequent to 345?


   Andreas Herdt
   Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------
Charles FreemanRe: Neverending story - is anybody can help ?
on Mon, 01 Dec 2008 17:13:01 -0500
On Wed, 26 Nov 2008 20:33:28 +0100, Andreas Herdt wrote:

> Hi Charles,
> 
> Mr Wykrota did not bring this issue to the SL1 newsgroup, yet.
> Insofar I have no idea wheather the most recent SL1 drop solved
> his problem.
> 
> Beside of this a comparable Fatal Error does not mean that the
> reason for the error is comparable. There are many different
> reasons for identical symptoms in this area:
> 
>   * (wrong) usage of DllCall
>   * usage of JazzAge
>   * wrong usage of CAPI
>   * (wrong) usage of (bad) third party
>      libs (including ActiveX components)
>   * bad coding patterns
>   * bad hardware
>   * .....
> 
> This list surely can be expanded.
> 
> It turned out that in more then 99% of the cases where this
> kind of log files is produced, the reason is one of those from
> above. None of the reasons from above neccessarily is a problem
> in the Xbase++ Runtime.
> 
> To be sure on this it is required that we qualify each individual
> problem. For this it is required to have some reproducable scenario
> in our Labs. I have to admit that building a scenario is not easy
> in cases where the error occurs not very frequently.
> 
> On the other hand it also turned out that in almost all cases the
> reason can be detected on the way to create such a scenario. This
> is not too surprising. On the way to bring the issue to the point
> most often the problem discloses itself.
> 
> 
> 
> Charles Freeman wrote:
>> On Fri, 24 Oct 2008 10:51:05 +0200, Andreas Herdt wrote:
>> 
>>> Hallo Mr Wykrota,
>>>
>>> According your information you are using Xbase++
>>> build level 345. You need to update to the most
>>> recent drop which is build level 346. If the problem
>>> persists then please post those SL1 Preview related
>>> issues to the SL1 news group.
>>>
>>> Thanks in advance.
>>>
>>> Adrian Wykrota wrote:
>>>> It is happened every work day...
>>>>
>>>> FATAL ERROR LOG
>>>> System-Error
>>>> SYS Thread-ID: 700
>>>> Module: EVM
>>>> Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
>>>> Call Stack of Thread 1 (636):
>>>> MYAPPEVENT(419)
>>>> MYMENU(260)
>>>> MAIN(0)
>>>> Call Stack of GUI Thread (784):
>>>> Call Stack of Thread 3 (1472):
>>>> Call Stack of Thread 4 (1096):
>>>> Call Stack of Thread 5 (1156):
>>>> Call Stack of Thread 6 (1424):
>>>> Call Stack of Thread 7 (2192):
>>>> Call Stack of Thread 8 (2236):
>>>> Call Stack of Thread 9 (2808):
>>>> Call Stack of Thread 10 (2744):
>>>> Call Stack of Thread 11 (3776):
>>>> Call Stack of Thread 12 (3200):
>>>> Call Stack of Thread 13 (2636):
>>>> Call Stack of Thread 14 (3048):
>>>> Call Stack of Thread 15 (3424):
>>>> Call Stack of Thread 16 (3356):
>>>> Call Stack of Thread 17 (3492):
>>>> Call Stack of Thread 18 (3676):
>>>> Call Stack of Thread 19 (3968):
>>>> Call Stack of Thread 20 (4428):
>>>> Call Stack of Thread 21 (3876):
>>>> Call Stack of Thread 22 (3852):
>>>> Call Stack of Thread 23 (3036):
>>>> Call Stack of Thread 24 (3820):
>>>> Call Stack of Thread 25 (4264):
>>>> Call Stack of Thread 26 (3988):
>>>> Call Stack of Thread 27 (4496):
>>>> Call Stack of Thread 28 (4252):
>>>> Call Stack of Thread 29 (3932):
>>>> Call Stack of Thread 30 (4208):
>>>> Call Stack of Thread 31 (4652):
>>>> MYAPPEVENT(419)
>>>> DEKRETACJAFK(383)
>>>> OPENPACZKA(242)
>>>> (B)Paczki(115)
>>>> @XBPPUSHBUTTON@I@HANDLEEVENT(935)
>>>> PACZKI(194)
>>>> DLL_PROC(282)
>>>> (B)GETTABMENU@0066(0)
>>>> Call Stack of Thread 32 (4136):
>>>> Call Stack of Thread 33 (2576):
>>>> Call Stack of Thread 34 (4476):
>>>> Call Stack of Thread 35 (4728):
>>>> Call Stack of Thread 37 (4160):
>>>> Call Stack of Thread 38 (5336):
>>>> Call Stack of Thread 39 (5256):
>>>> Call Stack of Thread 40 (5300):
>>>> File: C:\Advantec\Program.Exe
>>>> TimeStamp: 20081024 09:15
>>>> End of FATAL ERROR LOG.
>>>>
>>>> 415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
>>>> 416: LOCAL nRet := 0, bErr := {|| NIL}
>>>> 417: bErr := ErrorBlock({|e|Break(e)})
>>>> 418: BEGIN SEQUENCE
>>>> 419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
>>>> 420: RECOVER
>>>> 421:   nRet := 0
>>>> 422:   oXbp := NIL
>>>> 423: END SEQUENCE
>>>> 424: ErrorBlock(bErr)
>>>> 425: RETURN (nRet)
>>>> *
>>>>
>>>> Alaska xBase 1.90.345
>> 
>> The same error is present in 1.90.331; I see these EVM errors in my
>> client's error logs all the time. It appears that none of the
>> hotfix/rollups (through 345 at least) have addressed the problem. Andreas,
>> has it been fixed subsequent to 345?

Andreas,

Thanks for the enumerated list. In my case, it would be especially useful
if you could provide some sort of differential diagnosis amongst these
selections. I know that I can eliminate a few of them. I don't use JazzAge,
and I doubt it is hardware because all of my clients experience this
problem. It's not likely that it is a bad DllCall or similar coding issue
because that should not create the highly intermittent error that we are
logging. What I can tell is that this much of the error message I am seeing
in 331 is identical to what Adrian is seeing in 345:

FATAL ERROR LOG
System-Error
SYS Thread-ID: 1748 
Module: EVM
Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40

Polling my clients the only feedback I get is that really fast typists have
the problem more often than slower ones. 

I'm not interested in pointing any fingers, I just want to find a fix or a
workaround so my clients no longer see fatal errors.

Charlie
Charles FreemanRe: Neverending story - is anybody can help ?
on Mon, 01 Dec 2008 17:27:39 -0500
On Wed, 26 Nov 2008 20:33:28 +0100, Andreas Herdt wrote:

> Hi Charles,
> 
> Mr Wykrota did not bring this issue to the SL1 newsgroup, yet.
> Insofar I have no idea wheather the most recent SL1 drop solved
> his problem.
> 
> Beside of this a comparable Fatal Error does not mean that the
> reason for the error is comparable. There are many different
> reasons for identical symptoms in this area:
> 
>   * (wrong) usage of DllCall
>   * usage of JazzAge
>   * wrong usage of CAPI
>   * (wrong) usage of (bad) third party
>      libs (including ActiveX components)
>   * bad coding patterns
>   * bad hardware
>   * .....
> 
> This list surely can be expanded.
> 
> It turned out that in more then 99% of the cases where this
> kind of log files is produced, the reason is one of those from
> above. None of the reasons from above neccessarily is a problem
> in the Xbase++ Runtime.
> 
> To be sure on this it is required that we qualify each individual
> problem. For this it is required to have some reproducable scenario
> in our Labs. I have to admit that building a scenario is not easy
> in cases where the error occurs not very frequently.
> 
> On the other hand it also turned out that in almost all cases the
> reason can be detected on the way to create such a scenario. This
> is not too surprising. On the way to bring the issue to the point
> most often the problem discloses itself.
> 
> 
> 
> Charles Freeman wrote:
>> On Fri, 24 Oct 2008 10:51:05 +0200, Andreas Herdt wrote:
>> 
>>> Hallo Mr Wykrota,
>>>
>>> According your information you are using Xbase++
>>> build level 345. You need to update to the most
>>> recent drop which is build level 346. If the problem
>>> persists then please post those SL1 Preview related
>>> issues to the SL1 news group.
>>>
>>> Thanks in advance.
>>>
>>> Adrian Wykrota wrote:
>>>> It is happened every work day...
>>>>
>>>> FATAL ERROR LOG
>>>> System-Error
>>>> SYS Thread-ID: 700
>>>> Module: EVM
>>>> Error Codes: EH: 4 Sub: 6(6) OS: 6 XPP: 40
>>>> Call Stack of Thread 1 (636):
>>>> MYAPPEVENT(419)
>>>> MYMENU(260)
>>>> MAIN(0)
>>>> Call Stack of GUI Thread (784):
>>>> Call Stack of Thread 3 (1472):
>>>> Call Stack of Thread 4 (1096):
>>>> Call Stack of Thread 5 (1156):
>>>> Call Stack of Thread 6 (1424):
>>>> Call Stack of Thread 7 (2192):
>>>> Call Stack of Thread 8 (2236):
>>>> Call Stack of Thread 9 (2808):
>>>> Call Stack of Thread 10 (2744):
>>>> Call Stack of Thread 11 (3776):
>>>> Call Stack of Thread 12 (3200):
>>>> Call Stack of Thread 13 (2636):
>>>> Call Stack of Thread 14 (3048):
>>>> Call Stack of Thread 15 (3424):
>>>> Call Stack of Thread 16 (3356):
>>>> Call Stack of Thread 17 (3492):
>>>> Call Stack of Thread 18 (3676):
>>>> Call Stack of Thread 19 (3968):
>>>> Call Stack of Thread 20 (4428):
>>>> Call Stack of Thread 21 (3876):
>>>> Call Stack of Thread 22 (3852):
>>>> Call Stack of Thread 23 (3036):
>>>> Call Stack of Thread 24 (3820):
>>>> Call Stack of Thread 25 (4264):
>>>> Call Stack of Thread 26 (3988):
>>>> Call Stack of Thread 27 (4496):
>>>> Call Stack of Thread 28 (4252):
>>>> Call Stack of Thread 29 (3932):
>>>> Call Stack of Thread 30 (4208):
>>>> Call Stack of Thread 31 (4652):
>>>> MYAPPEVENT(419)
>>>> DEKRETACJAFK(383)
>>>> OPENPACZKA(242)
>>>> (B)Paczki(115)
>>>> @XBPPUSHBUTTON@I@HANDLEEVENT(935)
>>>> PACZKI(194)
>>>> DLL_PROC(282)
>>>> (B)GETTABMENU@0066(0)
>>>> Call Stack of Thread 32 (4136):
>>>> Call Stack of Thread 33 (2576):
>>>> Call Stack of Thread 34 (4476):
>>>> Call Stack of Thread 35 (4728):
>>>> Call Stack of Thread 37 (4160):
>>>> Call Stack of Thread 38 (5336):
>>>> Call Stack of Thread 39 (5256):
>>>> Call Stack of Thread 40 (5300):
>>>> File: C:\Advantec\Program.Exe
>>>> TimeStamp: 20081024 09:15
>>>> End of FATAL ERROR LOG.
>>>>
>>>> 415: FUNCTION MyAppEvent(mp1, mp2, oXbp, nTime)
>>>> 416: LOCAL nRet := 0, bErr := {|| NIL}
>>>> 417: bErr := ErrorBlock({|e|Break(e)})
>>>> 418: BEGIN SEQUENCE
>>>> 419:   nRet := AppEvent(@mp1, @mp2, @oXbp, nTime)
>>>> 420: RECOVER
>>>> 421:   nRet := 0
>>>> 422:   oXbp := NIL
>>>> 423: END SEQUENCE
>>>> 424: ErrorBlock(bErr)
>>>> 425: RETURN (nRet)
>>>> *
>>>>
>>>> Alaska xBase 1.90.345
>> 
>> The same error is present in 1.90.331; I see these EVM errors in my
>> client's error logs all the time. It appears that none of the
>> hotfix/rollups (through 345 at least) have addressed the problem. Andreas,
>> has it been fixed subsequent to 345?

Andreas,

One last observation: In both my error message and Adrians, the OS Error is
6. My docs indicate that means invalid handle. Since this is in the event
manager, does that mean that the EVM is trying to send a message to a NIL
thread?

Charlie
James Loughner Re: Neverending story - is anybody can help ?
on Tue, 02 Dec 2008 00:27:52 -0500
It could be that like the random errors I see an event being processed
by the wrong thread.

Jim

Charles Freeman wrote:
> 
> Andreas,
> 
> One last observation: In both my error message and Adrians, the OS Error is
> 6. My docs indicate that means invalid handle. Since this is in the event
> manager, does that mean that the EVM is trying to send a message to a NIL
> thread?
> 
> Charlie