My terminals show...."This program has performed and illegal operation

[AlohaErnest]

My server is running XP SP3, with Aloha v5.3.44. Fresh Windows and Aloha install in the server, and my terminals show...

....This program has performed an illegal operation...

it happens after the terminal reads a 'reading requirement rule'

here is the debout from the terminal..

ct 27, 16:57:27 Synchronize Data Local DOB is 10/27/2008 in C:\Aloha\DATA\ALOHA.INI (10 27 2008)
Oct 27, 16:57:28 Begin reading data...
Oct 27, 16:57:35 Read in 23 employees
Oct 27, 16:57:35 Number of color bits is 8, Physical Memory 66609152 bytes
Oct 27, 16:57:35 NOT using EGI display
Oct 27, 16:57:36 Check For Unregistered applications...
Oct 27, 16:57:36 Don't need to start VBOINST.EXE
Oct 27, 16:57:36 WARNING: in ConditionRunTZDST() - File Not Found: C:\Aloha\BIN\.\TZDSTAdj.exe
Oct 27, 16:57:36 Don't need to start TZDSTAdj.exe
Oct 27, 16:57:36 Done reading data.
Oct 27, 16:57:37 firing 11:00:00 SET BAR MENU 3
Oct 27, 16:57:37 firing 11:00:00 SET SERVER MENU 1
Oct 27, 16:57:37 firing 16:00:00 SET BAR MENU 4
Oct 27, 16:57:37 firing 16:00:00 SET SERVER MENU 2
Oct 27, 16:57:37 Begin reading transaction log...
Oct 27, 16:57:37 Done reading transaction log.
Oct 27, 16:57:37 ErrFatal - Generating a stack trace
Oct 27, 16:57:37 //=====================================================
Oct 27, 16:57:37 Exception code: C0000005 ACCESS_VIOLATION
Oct 27, 16:57:37 //=====================================================
Oct 27, 16:57:37 Exception code: C0000005 ACCESS_VIOLATION
Oct 27, 16:57:37 Fault address: 0053A25B 01:0013925B C:\ALOHA\BIN\IBER.EXE
Oct 27, 16:57:37 Registers:
Oct 27, 16:57:37 EAX:00000000 EBX:01C1FFB8 ECX:00000000 EDX:00000000 ESI:8160535C EDI:81618E40
Oct 27, 16:57:37 CS:EIP:0137:0053A25B
Oct 27, 16:57:37 SS:ESP:013F:01C1F398 EBP:01C1F3D8
Oct 27, 16:57:37 DS:013F ES:013F FS:2577 GS:0000
Oct 27, 16:57:37 Flags:00010202
Oct 27, 16:57:37 version 5.3.44.608
Oct 27, 16:57:37 Operating system is Windows 95 (BuildNumber 67109975, Platform 1, Version 4.0, B)
Oct 27, 16:57:37 Call stack:
Oct 27, 16:57:37 Address Frame Logical addr Module
Oct 27, 16:57:37 0053A25B 01C1F3D8 0001:0013925B C:\ALOHA\BIN\IBER.EXE
Oct 27, 16:57:37 00539CA8 01C1F7E8 0001:00138CA8 C:\ALOHA\BIN\IBER.EXE
Oct 27, 16:57:37 00539B99 01C1F7F4 0001:00138B99 C:\ALOHA\BIN\IBER.EXE
Oct 27, 16:57:37 BFF9A637 01C1FAA8 0002:00022637 C:\WINDOWS\SYSTEM\KERNEL32.DLL
Oct 27, 16:57:37 BFF8683E 01C1FFC8 0002:0000E83E C:\WINDOWS\SYSTEM\KERNEL32.DLL
Oct 27, 16:57:37 BFF84253 8160535C 0002:0000C253 C:\WINDOWS\SYSTEM\KERNEL32.DLL
Oct 27, 16:57:37 Begin looping through registered threads...
Oct 27, 16:57:37 End looping through registered threads.
Oct 27, 16:57:37
Oct 27, 16:57:37 Z:\Aloha\DATA\TRANS.LOG is already closed. File handle is 0.

 

[Shift4SMS]

This is just a guess but generally stack related errors indicates an out of memory condition. Depending on the O/S and the language used to develop the application, the out of memory condition may be a logical limit as opposed to a physical limit (some languages for example have a 4Mb usable limit even though your machine may have gigabytes of free RAM).

Again, just guessing, the log that was just read in prior to the exception may be too large to handle.

Steve Sommers

http://www.shift4.com

-- Creators of $$$ ON THE NET(tm) payment processing services

Blog:

http://shift4sms.blogspot.com

 

[posknowitall]

Try deleting the trans.log if you are not in a live situation