Application "Hangs" and then Returns Error Message

[goodner]

Have a large system written in Clarion 5b using the latest Pervasive Transactional Processing for record management. There are currently hundreds of clients and the system has been around for many years now. Since this past summer there are two clients who are reporting the system occasionally “hangs” and then returns the following error: “ffb.exe has encountered a problem and needs to be closed.” FFB.EXE is the parent application for one module. The error can happen in anyone of the system’s modules and thus other application names are listed when the error occurs in other places. The hang-up can occur when performing data entry or running reports – there does not appear to be any rhyme or reason as to when the error occurs.

Both clients are network users and their workstations are running Windows XP (some stations at Service Pack 3 others at SP2). Both clients also are running duel core processors.

The Window’s Event Viewer shows the following application error when data entry is being performed: “Faulting application ffb.exe, version 0.0.0.0, faulting module c5runx.dll, version 0.5.2.0, fault address 0x0001b115.” When a report is being run the following error displays: “Hanging application ffb.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.”

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 9/8/2008
Time: 1:37:58 AM
User: N/A
Computer: NEWDELL
Description:
Faulting application ffb.exe, version 0.0.0.0, faulting module c5runx.dll, version 0.5.2.0, fault address 0x0001b115.

Or…

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 9/8/2008
Time: 3:41:05 PM
User: N/A
Computer: NEWDELL
Description:
Hanging application ffb.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.


I thought the dual core processor might be causing a problem so I have modified ffb.exe using imagecfg.exe to run on a single processor. This does not appear to make any difference.

Does anyone have any ideas? Any help would be appreciated!

Kevin Goodner
Automated Accounting Systems, Inc.

 

[ShankarJ]

Hi Kevin,

The error message "ffb.exe has encountered a problem and needs to be closed." is the XP way of showing a GPF (General Protection Fault). If the problem has surfaced recently after some "Windows Updates", it is possible that some API call from your application is failing and hence the GPF. Invalid Data because of corruptions, memory leaks, changing properties of objects before they are open or come into scope (example :: issuing a Window{PROP:Text} = '...' before the window is open), etc are some of the reasons for GPF's. Normally, using the fault address 0x0001b115 and searching the function entry points in the <Application>.MAP file would give you an idea as to what RTL funtion is failing. Unluckily, it is a trial an error process as C5's RT libraries are not uptodate with today's OS unlike C6.3 & C7.

Regards