Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MacExe.exe abnormal program termination

Status
Not open for further replies.
Jul 17, 2003
66
US
I just upgraded from 7.6.300 to 7.6.300b and I get an error when I try to open a few screens.

When trying to open the Vendor Maintenance screen I get a Microsoft Visual C++ Runtime Library box that says

Runtime Error!
Program m:\macsql\MacExe.exe
abnormal program termination

Then a MSL System Warning box come up that says

Abnormal Cleanup of MacSqlconnman in MacMSS.dll, No Server Exit Op provided! Some Client and Server resources may be left in an unknown state.

When I try to open Enter Transactions in Bank Book I get similar error in a different format. I get a box titled COBOL ERROR REPORT

JMW0001I-I THE ERROR OCCURRED IN "M:\macsql\MacExe.exe".
'08/05/2005'
Cannot call program 'BBTRXENT', code=0x7e pgm=macexe

Then it creates a log file.

I tested alot of other screens and so far only these two error out. Any help would be appreciated but I suspect that come Monday morning I'm gonna have Macola on the phone in one ear and my users yelling at me in the other ear. In other words, a typical Macola upgrade.

 
The BBTRXENT error means that Macola cannot find the program to allow you to enter Bank Book Transactions. Typicaly this means you either do not own the Bank Book module, or when the program was installed, someone intentionally did not install the Bank Book module, even though you do own it, or the module has never been setup.

Can you confirm that you own the module and are using it?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
 
With 7.6.300 and later, particularly in OE, I have seen the C++ runtime error caused by bad data in a record. Previous versions ignored the bad records, but 7.6.300 chokes on them. If you look at the tables tied to the screen and return all rows, you may see records containing empty fields or gibberish characters.

Make a backup of the tables and then start looking for bad records.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top