FAQ's - APPX Software, Inc. : Trash :
584 - Diagnosing Strange and Generic Errors
Delete all of your Applications' EMs.
Rerun your problem scenario to see if the problem still occurs.
Set environment variable APPX_TRAILER_COUNT=40, then re-run the condition that generates the error.
This catches most APPX "stepping on memory" errors, by generating an "mm free() - corrupted trailer" message earlier in your problem scenario.
This can be set in the appx.env found in the data directory under the directory containing your APPX engine. (If you're running APPX/Server, any new APPX Application server session fired off from an APPX/Client after appx.env editing will have newly edited appx.env environment variables activated.)
Search for Design Discrepancies:
Run: 2.Application Design, 3.Utility, 6.Toolbox, 20.Source Analysis Menu, 1.Orphan Detection, 19.Run Each of the Above
Run: 2.Application Design, 3.Utility, 6.Toolbox, 11.Conversion Utilities, 4.Check for Duplicate ANO and EMs.
"No Lines Were Output" means the Application passes this test. If any Applications don't pass, perform:
Run: 11.Conversion Utilities, 2.Reset Process Date Add Fields.
Run: 11.Conversion Utilities, 6.Reset DD for full process.
Perform steps 4) thru 6) below.
Initialize the 4 compiled DD files (BITMAP, ELEMENT, FILE, INITIAL) and reprocess the Data Dictionary.
These can be initialized in System Administration, Design File Management, File Selection (select these four files), Initialize Files.
Restructure your enduser data.
This should go quickly - only the /Struct file date/time stamps will need to be reset, to match the newly compiled DD.)
Delete all of your Applications' EMs again.
Then rerun the scenario that causes the problem.
If your problem scenario still fails, and you're running on a Windows platform, send us your appx.stk 'appx.stk' is a stack dump, telling us something of what goes on inside APPX when cassert error messages occur. You'll find it in the same directory that your 'appx' or 'appx.exe' engine is located. If it is overly large, you may want to delete or rename it, then run your problem scenario one more time to get a clean dump.
Send to techsupp:
The appx.stk dump,
The version# of APPX under which you are running,
The release level of your Operating System,
A brief description of what the error looks like from the operator's perspective, and a brief description of the Application Design elementes in which the error occurred.
158 - Removing Inactive Sessions