Information

Title	Client is terminated with error 6028

URL Name	P101352

Article Number	000151523

Environment	Product: Progress Version: 9.x Product: OpenEdge Version: 10.x, 11.x OS: All supported platforms

Question/Problem Description

Client running a program to add/update records in a database terminates with error 6028

Stack trace from _progres reads:

bfbind
rncrrun_check
rninterpret
umeDispatchEvent

Steps to Reproduce

Clarifying Information

There are no Non-Progress software touching the client-temp files directory at the time.

Error Message	SYSTEM ERROR: A/R block doesn't match caller's. Transaction inconsistency. (6028)

Defect Number

Enhancement Number

Cause

Memory corruption at the time of the application run resulted in an A/R block mismatch. The a/r unit (block) acts as place holder in the lbi file for a sub-transaction, resulting in transaction inconsistency when one of these units is not where it is expected to be.

Resolution

Address the memory corruption.

If the Progress client is lost in memory for whatever reason, then it is plausible that this kind of error may be produced.

If memory is reinitialized through a system reboot for example and the error persists, then it is most likely a physical problem where the lbi file resides or an issue with the application code that may be stuck in a recursive loop, causing unexpected lbi growth and eventually no longer having space available to address

Workaround

Notes

Progress Articles:

How to troubleshoot error 6028
Why are my lbi files growing substantially?

Keyword Phrase

Last Modified Date	11/20/2020 7:38 AM

Client is terminated with error 6028

Information