Alaska Software Inc. - Frequent XPPFATAL
Username: Password:
AuthorTopic: Frequent XPPFATAL
Jack Duijf Frequent XPPFATAL
on Wed, 05 May 2010 10:13:46 +0200
Hello,

On of my customers uses a Xbase++ application on a Windows-2003 network.
Data acces is via ADSDBE only, 50 users.
Xbase++ 1.90 SL1 including all Hotfixes until date.
I receive verry frequently (sometimes 10 logs a day) the Xppfatal logs 
as shown below. (Callstack differs most of the time)

Most fequently fatals are:
1. Fatal error while shutdown.
2. Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41

What can i do to prevent these fatal errors?

Regards,
Jack Duijf

Fatal log 2.
\\aalb-fs\Wincalc\Wincalc32.EXE
Os : Windows XP 05.01 Build 02600 Service Pack 2
Computername : aalb-ws22 (512Mb)

Ontvangen : 05/05/2010 08:16:43

FATAL ERROR LOG
Fatal error while shutdown.

Fatal log 1.
\\aalb-fs\Wincalc\Wincalc32.EXE
Os : Windows XP 05.01 Build 02600 Service Pack 2
Computername : aalb-ws05 (1024Mb)

Ontvangen : 05/05/2010 09:23:43

FATAL ERROR LOG
Error within the error handling!
SYS Thread-ID: 1428
Module: EXE
Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
Call Stack of Thread 1 (512):
MAIN(91)
Call Stack of GUI Thread (700):
Call Stack of Thread 3 (1092):
_SY_STOPTEST(36)
Call Stack of Thread 4 (1128):
@DC_GETLIST@I@EVENTLOOP(3917)
@DC_GETLIST@I@READGUI(3647)
DC_READGUI(103)
MAINWINDOW(450)
WINCALC(972)
START_APP(100)
Call Stack of Thread 5 (1384):
Call Stack of Thread 6 (1428):
(B)DC_MergeBlocks(187)
@XBPBROWSE@I@HANDLEEVENT(1542)
@DC_XBPBROWSE@I@HANDLEEVENT(873)
@DC_GETLIST@I@EVENTLOOP(4388)
@DC_GETLIST@I@READGUI(3647)
DC_READGUI(103)
SY_DC_READ(102)
EDIT_ORDER(744)
(B)App_MenuOrders(822)
(B)Sy_MergeBlocks(724)
(B)Sy_MergeBlocks(724)
Call Stack of Thread 7 (1484):
@JD_MAGICHELPTHREAD@I@EXECUTE(67)
(B)@JD_MAGICHELPTHREAD@I@INIT@0000(36)
Call Stack of Thread 8 (1696):
@DC_GETLIST@I@EVENTLOOP(3917)
@DC_GETLIST@I@READGUI(3647)
DC_READGUI(103)
SY_DC_READ(102)
BESTELLINGEN_OPVRAGEN(82)
(B)App_MenuBestellingen(717)
(B)Sy_MergeBlocks(724)
(B)Sy_MergeBlocks(724)
File: \\aalb-fs\Wincalc\Wincalc32.EXE
TimeStamp: 20100505 09:23
End of FATAL ERROR LOG.
Andreas Gehrs-Pahl
Re: Frequent XPPFATAL
on Wed, 05 May 2010 11:01:58 -0400
Jack,

>On of my customers uses a Xbase++ application on a Windows-2003 network.
>Data acces is via ADSDBE only, 50 users.
>Xbase++ 1.90 SL1 including all Hotfixes until date.
>I receive verry frequently (sometimes 10 logs a day) the Xppfatal logs 
>as shown below. (Callstack differs most of the time)

This looks very similar to what Frans reported (in the Active-X NG). 
Maybe it's the weather in the Netherlands? 

But seriously, if you can reproduce this at will -- or at least very 
frequently -- maybe the Alaska guys can find a solution by studying your 
scenario. As the issue seems to affect a lot of developers and seems to
be more prevalent with complex(er) applications that use multi-threading
and/or Active-X components, it would appear that the problem will move 
higher on Alaska's priority list.

If there were a PDR for the "frequent unexplained XppFatal logs at some
client sites" issue, I certainly would vote for it to be resolved as soon 
as possible!

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas_Gehrs-Pahl@CrimeCog.com
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---
Andreas HerdtRe: Frequent XPPFATAL
on Thu, 06 May 2010 17:05:54 +0200
Hi Jack,

As a matter of fact we have recently 
investigated into exactly the topic you 
are encountering in case 2. I have taken 
the opportunity to summarize our results 
in PDR 6289:

http://www.alaska-software.com/scripts/waa001.dll?WAA_PACKAGE=PUBLICDTS&WAA_FORM=DISPLAYPDR&PDRID=6289

As described in the PDR 6289 a hardware 
failure can be the cause of the problem, 
  in the other case (network deployment) 
the reason is a network drop down.

Please also note that spontaneous 
program terminations can also have its 
roots in in page errors. The PDR 5457 
has been updated accordingly.

Jack Duijf schrieb:
> Hello,
> 
> On of my customers uses a Xbase++ application on a Windows-2003 network.
> Data acces is via ADSDBE only, 50 users.
> Xbase++ 1.90 SL1 including all Hotfixes until date.
> I receive verry frequently (sometimes 10 logs a day) the Xppfatal logs 
> as shown below. (Callstack differs most of the time)
> 
> Most fequently fatals are:
> 1. Fatal error while shutdown.
> 2. Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
> 
> What can i do to prevent these fatal errors?
> 
> Regards,
> Jack Duijf
> 
> Fatal log 2.
> \\aalb-fs\Wincalc\Wincalc32.EXE
> Os : Windows XP 05.01 Build 02600 Service Pack 2
> Computername : aalb-ws22 (512Mb)
> 
> Ontvangen : 05/05/2010 08:16:43
> 
> FATAL ERROR LOG
> Fatal error while shutdown.
> 
> Fatal log 1.
> \\aalb-fs\Wincalc\Wincalc32.EXE
> Os : Windows XP 05.01 Build 02600 Service Pack 2
> Computername : aalb-ws05 (1024Mb)
> 
> Ontvangen : 05/05/2010 09:23:43
> 
> FATAL ERROR LOG
> Error within the error handling!
> SYS Thread-ID: 1428
> Module: EXE
> Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
> Call Stack of Thread 1 (512):
> MAIN(91)
> Call Stack of GUI Thread (700):
> Call Stack of Thread 3 (1092):
> _SY_STOPTEST(36)
> Call Stack of Thread 4 (1128):
> @DC_GETLIST@I@EVENTLOOP(3917)
> @DC_GETLIST@I@READGUI(3647)
> DC_READGUI(103)
> MAINWINDOW(450)
> WINCALC(972)
> START_APP(100)
> Call Stack of Thread 5 (1384):
> Call Stack of Thread 6 (1428):
> (B)DC_MergeBlocks(187)
> @XBPBROWSE@I@HANDLEEVENT(1542)
> @DC_XBPBROWSE@I@HANDLEEVENT(873)
> @DC_GETLIST@I@EVENTLOOP(4388)
> @DC_GETLIST@I@READGUI(3647)
> DC_READGUI(103)
> SY_DC_READ(102)
> EDIT_ORDER(744)
> (B)App_MenuOrders(822)
> (B)Sy_MergeBlocks(724)
> (B)Sy_MergeBlocks(724)
> Call Stack of Thread 7 (1484):
> @JD_MAGICHELPTHREAD@I@EXECUTE(67)
> (B)@JD_MAGICHELPTHREAD@I@INIT@0000(36)
> Call Stack of Thread 8 (1696):
> @DC_GETLIST@I@EVENTLOOP(3917)
> @DC_GETLIST@I@READGUI(3647)
> DC_READGUI(103)
> SY_DC_READ(102)
> BESTELLINGEN_OPVRAGEN(82)
> (B)App_MenuBestellingen(717)
> (B)Sy_MergeBlocks(724)
> (B)Sy_MergeBlocks(724)
> File: \\aalb-fs\Wincalc\Wincalc32.EXE
> TimeStamp: 20100505 09:23
> End of FATAL ERROR LOG.


   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
--------------------------------------------------------------------
Jack Duijf Re: Frequent XPPFATAL
on Thu, 06 May 2010 18:38:31 +0200
Hello Andreas,

Thank you for your reply.
If you need more error logs for refference, I have plenty....
Unfortunaly i am unable to read PDR 6289 (Not public availeble).

I wil try some of the suggestions as layed-out in PDR 5457.
- SET OPTIMIZE OFF (I do not use filters)
- Add /o:nospeed as a compiler option.

Regards,
Jacl Duijf



Op 6-5-2010 17:05, Andreas Herdt schreef:
> Hi Jack,
>
> As a matter of fact we have recently investigated into exactly the topic
> you are encountering in case 2. I have taken the opportunity to
> summarize our results in PDR 6289:
>
> http://www.alaska-software.com/scripts/waa001.dll?WAA_PACKAGE=PUBLICDTS&WAA_FORM=DISPLAYPDR&PDRID=6289
>
>
> As described in the PDR 6289 a hardware failure can be the cause of the
> problem, in the other case (network deployment) the reason is a network
> drop down.
>
> Please also note that spontaneous program terminations can also have its
> roots in in page errors. The PDR 5457 has been updated accordingly.
>
> Jack Duijf schrieb:
>> Hello,
>>
>> On of my customers uses a Xbase++ application on a Windows-2003 network.
>> Data acces is via ADSDBE only, 50 users.
>> Xbase++ 1.90 SL1 including all Hotfixes until date.
>> I receive verry frequently (sometimes 10 logs a day) the Xppfatal logs
>> as shown below. (Callstack differs most of the time)
>>
>> Most fequently fatals are:
>> 1. Fatal error while shutdown.
>> 2. Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
>>
>> What can i do to prevent these fatal errors?
>>
>> Regards,
>> Jack Duijf
>>
>> Fatal log 2.
>> \\aalb-fs\Wincalc\Wincalc32.EXE
>> Os : Windows XP 05.01 Build 02600 Service Pack 2
>> Computername : aalb-ws22 (512Mb)
>>
>> Ontvangen : 05/05/2010 08:16:43
>>
>> FATAL ERROR LOG
>> Fatal error while shutdown.
>>
>> Fatal log 1.
>> \\aalb-fs\Wincalc\Wincalc32.EXE
>> Os : Windows XP 05.01 Build 02600 Service Pack 2
>> Computername : aalb-ws05 (1024Mb)
>>
>> Ontvangen : 05/05/2010 09:23:43
>>
>> FATAL ERROR LOG
>> Error within the error handling!
>> SYS Thread-ID: 1428
>> Module: EXE
>> Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
>> Call Stack of Thread 1 (512):
>> MAIN(91)
>> Call Stack of GUI Thread (700):
>> Call Stack of Thread 3 (1092):
>> _SY_STOPTEST(36)
>> Call Stack of Thread 4 (1128):
>> @DC_GETLIST@I@EVENTLOOP(3917)
>> @DC_GETLIST@I@READGUI(3647)
>> DC_READGUI(103)
>> MAINWINDOW(450)
>> WINCALC(972)
>> START_APP(100)
>> Call Stack of Thread 5 (1384):
>> Call Stack of Thread 6 (1428):
>> (B)DC_MergeBlocks(187)
>> @XBPBROWSE@I@HANDLEEVENT(1542)
>> @DC_XBPBROWSE@I@HANDLEEVENT(873)
>> @DC_GETLIST@I@EVENTLOOP(4388)
>> @DC_GETLIST@I@READGUI(3647)
>> DC_READGUI(103)
>> SY_DC_READ(102)
>> EDIT_ORDER(744)
>> (B)App_MenuOrders(822)
>> (B)Sy_MergeBlocks(724)
>> (B)Sy_MergeBlocks(724)
>> Call Stack of Thread 7 (1484):
>> @JD_MAGICHELPTHREAD@I@EXECUTE(67)
>> (B)@JD_MAGICHELPTHREAD@I@INIT@0000(36)
>> Call Stack of Thread 8 (1696):
>> @DC_GETLIST@I@EVENTLOOP(3917)
>> @DC_GETLIST@I@READGUI(3647)
>> DC_READGUI(103)
>> SY_DC_READ(102)
>> BESTELLINGEN_OPVRAGEN(82)
>> (B)App_MenuBestellingen(717)
>> (B)Sy_MergeBlocks(724)
>> (B)Sy_MergeBlocks(724)
>> File: \\aalb-fs\Wincalc\Wincalc32.EXE
>> TimeStamp: 20100505 09:23
>> End of FATAL ERROR LOG.
>
>
Andreas HerdtRe: Frequent XPPFATAL
on Fri, 07 May 2010 09:28:14 +0200
Hi Jack,

My post to this newsgroup was to early.
The PDR description now is online.

Jack Duijf schrieb:
> Hello Andreas,
> 
> Thank you for your reply.
> If you need more error logs for refference, I have plenty....
> Unfortunaly i am unable to read PDR 6289 (Not public availeble).
> 
> I wil try some of the suggestions as layed-out in PDR 5457.
> - SET OPTIMIZE OFF (I do not use filters)
> - Add /o:nospeed as a compiler option.
> 
> Regards,
> Jacl Duijf
> 
> 
> 
> Op 6-5-2010 17:05, Andreas Herdt schreef:
>> Hi Jack,
>>
>> As a matter of fact we have recently investigated into exactly the topic
>> you are encountering in case 2. I have taken the opportunity to
>> summarize our results in PDR 6289:
>>
>> http://www.alaska-software.com/scripts/waa001.dll?WAA_PACKAGE=PUBLICDTS&WAA_FORM=DISPLAYPDR&PDRID=6289 
>>
>>
>>
>> As described in the PDR 6289 a hardware failure can be the cause of the
>> problem, in the other case (network deployment) the reason is a network
>> drop down.
>>
>> Please also note that spontaneous program terminations can also have its
>> roots in in page errors. The PDR 5457 has been updated accordingly.
>>
>> Jack Duijf schrieb:
>>> Hello,
>>>
>>> On of my customers uses a Xbase++ application on a Windows-2003 network.
>>> Data acces is via ADSDBE only, 50 users.
>>> Xbase++ 1.90 SL1 including all Hotfixes until date.
>>> I receive verry frequently (sometimes 10 logs a day) the Xppfatal logs
>>> as shown below. (Callstack differs most of the time)
>>>
>>> Most fequently fatals are:
>>> 1. Fatal error while shutdown.
>>> 2. Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
>>>
>>> What can i do to prevent these fatal errors?
>>>
>>> Regards,
>>> Jack Duijf
>>>
>>> Fatal log 2.
>>> \\aalb-fs\Wincalc\Wincalc32.EXE
>>> Os : Windows XP 05.01 Build 02600 Service Pack 2
>>> Computername : aalb-ws22 (512Mb)
>>>
>>> Ontvangen : 05/05/2010 08:16:43
>>>
>>> FATAL ERROR LOG
>>> Fatal error while shutdown.
>>>
>>> Fatal log 1.
>>> \\aalb-fs\Wincalc\Wincalc32.EXE
>>> Os : Windows XP 05.01 Build 02600 Service Pack 2
>>> Computername : aalb-ws05 (1024Mb)
>>>
>>> Ontvangen : 05/05/2010 09:23:43
>>>
>>> FATAL ERROR LOG
>>> Error within the error handling!
>>> SYS Thread-ID: 1428
>>> Module: EXE
>>> Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
>>> Call Stack of Thread 1 (512):
>>> MAIN(91)
>>> Call Stack of GUI Thread (700):
>>> Call Stack of Thread 3 (1092):
>>> _SY_STOPTEST(36)
>>> Call Stack of Thread 4 (1128):
>>> @DC_GETLIST@I@EVENTLOOP(3917)
>>> @DC_GETLIST@I@READGUI(3647)
>>> DC_READGUI(103)
>>> MAINWINDOW(450)
>>> WINCALC(972)
>>> START_APP(100)
>>> Call Stack of Thread 5 (1384):
>>> Call Stack of Thread 6 (1428):
>>> (B)DC_MergeBlocks(187)
>>> @XBPBROWSE@I@HANDLEEVENT(1542)
>>> @DC_XBPBROWSE@I@HANDLEEVENT(873)
>>> @DC_GETLIST@I@EVENTLOOP(4388)
>>> @DC_GETLIST@I@READGUI(3647)
>>> DC_READGUI(103)
>>> SY_DC_READ(102)
>>> EDIT_ORDER(744)
>>> (B)App_MenuOrders(822)
>>> (B)Sy_MergeBlocks(724)
>>> (B)Sy_MergeBlocks(724)
>>> Call Stack of Thread 7 (1484):
>>> @JD_MAGICHELPTHREAD@I@EXECUTE(67)
>>> (B)@JD_MAGICHELPTHREAD@I@INIT@0000(36)
>>> Call Stack of Thread 8 (1696):
>>> @DC_GETLIST@I@EVENTLOOP(3917)
>>> @DC_GETLIST@I@READGUI(3647)
>>> DC_READGUI(103)
>>> SY_DC_READ(102)
>>> BESTELLINGEN_OPVRAGEN(82)
>>> (B)App_MenuBestellingen(717)
>>> (B)Sy_MergeBlocks(724)
>>> (B)Sy_MergeBlocks(724)
>>> File: \\aalb-fs\Wincalc\Wincalc32.EXE
>>> TimeStamp: 20100505 09:23
>>> End of FATAL ERROR LOG.
>>
>>


   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
--------------------------------------------------------------------
Jack Duijf Re: Frequent XPPFATAL
on Fri, 07 May 2010 20:20:01 +0200
Hello Andreas,

Thank you verry much for the explanation described in PDR 6289.
The scenarion 2 does fits the customer situation.

I wil contact Alaska Support

Regards,
Jack Duijf

Op 7-5-2010 9:28, Andreas Herdt schreef:
> Hi Jack,
>
> My post to this newsgroup was to early.
> The PDR description now is online.
>
> Jack Duijf schrieb:
>> Hello Andreas,
>>
>> Thank you for your reply.
>> If you need more error logs for refference, I have plenty....
>> Unfortunaly i am unable to read PDR 6289 (Not public availeble).
>>
>> I wil try some of the suggestions as layed-out in PDR 5457.
>> - SET OPTIMIZE OFF (I do not use filters)
>> - Add /o:nospeed as a compiler option.
>>
>> Regards,
>> Jacl Duijf
>>
>>
>>
>> Op 6-5-2010 17:05, Andreas Herdt schreef:
>>> Hi Jack,
>>>
>>> As a matter of fact we have recently investigated into exactly the topic
>>> you are encountering in case 2. I have taken the opportunity to
>>> summarize our results in PDR 6289:
>>>
>>> http://www.alaska-software.com/scripts/waa001.dll?WAA_PACKAGE=PUBLICDTS&WAA_FORM=DISPLAYPDR&PDRID=6289
>>>
>>>
>>>
>>> As described in the PDR 6289 a hardware failure can be the cause of the
>>> problem, in the other case (network deployment) the reason is a network
>>> drop down.
>>>
>>> Please also note that spontaneous program terminations can also have its
>>> roots in in page errors. The PDR 5457 has been updated accordingly.
>>>
>>> Jack Duijf schrieb:
>>>> Hello,
>>>>
>>>> On of my customers uses a Xbase++ application on a Windows-2003
>>>> network.
>>>> Data acces is via ADSDBE only, 50 users.
>>>> Xbase++ 1.90 SL1 including all Hotfixes until date.
>>>> I receive verry frequently (sometimes 10 logs a day) the Xppfatal logs
>>>> as shown below. (Callstack differs most of the time)
>>>>
>>>> Most fequently fatals are:
>>>> 1. Fatal error while shutdown.
>>>> 2. Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
>>>>
>>>> What can i do to prevent these fatal errors?
>>>>
>>>> Regards,
>>>> Jack Duijf
>>>>
>>>> Fatal log 2.
>>>> \\aalb-fs\Wincalc\Wincalc32.EXE
>>>> Os : Windows XP 05.01 Build 02600 Service Pack 2
>>>> Computername : aalb-ws22 (512Mb)
>>>>
>>>> Ontvangen : 05/05/2010 08:16:43
>>>>
>>>> FATAL ERROR LOG
>>>> Fatal error while shutdown.
>>>>
>>>> Fatal log 1.
>>>> \\aalb-fs\Wincalc\Wincalc32.EXE
>>>> Os : Windows XP 05.01 Build 02600 Service Pack 2
>>>> Computername : aalb-ws05 (1024Mb)
>>>>
>>>> Ontvangen : 05/05/2010 09:23:43
>>>>
>>>> FATAL ERROR LOG
>>>> Error within the error handling!
>>>> SYS Thread-ID: 1428
>>>> Module: EXE
>>>> Error Codes: EH: 5 Sub: -1073741818(c0000006) OS: 0 XPP: 41
>>>> Call Stack of Thread 1 (512):
>>>> MAIN(91)
>>>> Call Stack of GUI Thread (700):
>>>> Call Stack of Thread 3 (1092):
>>>> _SY_STOPTEST(36)
>>>> Call Stack of Thread 4 (1128):
>>>> @DC_GETLIST@I@EVENTLOOP(3917)
>>>> @DC_GETLIST@I@READGUI(3647)
>>>> DC_READGUI(103)
>>>> MAINWINDOW(450)
>>>> WINCALC(972)
>>>> START_APP(100)
>>>> Call Stack of Thread 5 (1384):
>>>> Call Stack of Thread 6 (1428):
>>>> (B)DC_MergeBlocks(187)
>>>> @XBPBROWSE@I@HANDLEEVENT(1542)
>>>> @DC_XBPBROWSE@I@HANDLEEVENT(873)
>>>> @DC_GETLIST@I@EVENTLOOP(4388)
>>>> @DC_GETLIST@I@READGUI(3647)
>>>> DC_READGUI(103)
>>>> SY_DC_READ(102)
>>>> EDIT_ORDER(744)
>>>> (B)App_MenuOrders(822)
>>>> (B)Sy_MergeBlocks(724)
>>>> (B)Sy_MergeBlocks(724)
>>>> Call Stack of Thread 7 (1484):
>>>> @JD_MAGICHELPTHREAD@I@EXECUTE(67)
>>>> (B)@JD_MAGICHELPTHREAD@I@INIT@0000(36)
>>>> Call Stack of Thread 8 (1696):
>>>> @DC_GETLIST@I@EVENTLOOP(3917)
>>>> @DC_GETLIST@I@READGUI(3647)
>>>> DC_READGUI(103)
>>>> SY_DC_READ(102)
>>>> BESTELLINGEN_OPVRAGEN(82)
>>>> (B)App_MenuBestellingen(717)
>>>> (B)Sy_MergeBlocks(724)
>>>> (B)Sy_MergeBlocks(724)
>>>> File: \\aalb-fs\Wincalc\Wincalc32.EXE
>>>> TimeStamp: 20100505 09:23
>>>> End of FATAL ERROR LOG.
>>>
>>>
>
>