Kbase P135012: 4GL/ABL: Client crashes creating a record and assigning a field.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/29/2010 |
|
Status: Verified
SYMPTOM(s):
4GL/ABL: Client crashes creating a record and assigning a field.
An unhandled win32 exception occurred in prowin32.exe [xxxx].
The error: 'An unhandled win32 exception occurred in prowin32.exe [xxxx].' is generated. Where xxxx is a number like 1044, 4080, 1920, etc.
Stack Trace reads:
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 102B593D 01:002B493D C:\Progress\OpenEdge\bin\prow32.dll
...
...
pam_get_item+BEEBD
The table has a WRITE and a DELETE database 4GL/ABL triggers.
The session uses the Trigger Location (-trig) client session startup parameter to point to the location of the .r procedure library (.pl) containing the database 4GL/ABL triggers.
Changing the target of the Trigger Location (-trig) client session startup parameter to point to the trigger directory eliminates the error.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Category: Language (4GL/ABL)
OpenEdge 10.1C
CAUSE:
The .r procedure library is corrupted or missing some files.
FIX:
1. Use the Trigger Location (-trig) client session startup parameter to point to the directory containing the database 4GL/ABL triggers.
2. Recompile and rebuild the .r procedure library (.pl) containing the database 4GL/ABL triggers and use the Trigger Location (-trig) client session startup parameter to point to the new library.
3. Include the location of the triggers in the session's PROPATH if the use of the Trigger Location (-trig) client session startup parameter is not desired.