Macola32 Systext 198 Load Error

[ThunderForest]

Macola v7.105d
Netware 4.11, v3.30 client

Got a call this AM from a long-time user who suddenly began experiencing this error:

When loading Macola and before the password prompt, I get the following error:

Load Error: File 'Systext'
error code 198, pc=0, call=6, seg=0

I've removed and reinstalled the Netware client, removed and reinstalled Macola several times, as well as Pervasive. There doesn't seem to be any memory issues. Any ideas?

http://www.thunderforest.bizland.com

 

[MacolaHelp]

You can get these errors for a variety of reasons. Is it referencing an int or gnt file inside an Up.lbr? On rare occasions, program libraries can become corrupt, but if that is the case usually more than one user gets it. Have you checked the local/remote client pervasive settings? I have had to edit the registry at times to fix pervasive settings. An error 198 on a pervasive 7 server usually is a communications problem with the sql manager. If you have added users, you should check your communications peaks. There are some settings you can tweak on the server for both pervasive 7 & 2000. If you have rebooted the server recently, sql stop & sqlstart to reset btrieve for pervasive 7. If you have pervasive 2000, unload nwsqlmgr, unload odbc, load spxs & mgrstart to reset the sql communications layer. Occasionally virus software can cause these problems & you can turn down your sensitivity or add lbr files to the list of non-scanned files.

I have a netware 4.11 install w/psql 2000i sp3 & a combination of win95 & 98 clients. Any client that I installed novell client > 3.1 had load errors that I fought with for months, on both pervasive 7 & psql. Are you using spx? I assume so. The workstation probably had something else new installed that partially broke spx or overwrote some shared dll that macola wants to use.

The simplest, quickest fix I found was to use PWE for these client workstations & forget the old explorer. At one time, macola claimed using a root directory name > 6 characters caused this type of error. I reinstalled macola70 into macola without change. I used the novell unc32.exe to remove the novell client completely & removed pervasive & macola completely including registry settings.

Oddly enough, the microsoft client worked on the balance of the machines (win 95) using microsoft spxII. Go figure. I don't think there is a scientific or rational explanation. You just keep trying things until you find something that works & hope that it works for all the workstations.

And, ahem, if they still use v 6.2 or 6.3 for payroll integration to v7, being over the total user count can can this error. Pervasive knows you are over, but macola might not have all 10 registered. So instead of a user count exceeded message we get the nice, helpful message you found. If the client are still running 4.11, they are probably too cheap to pay for a lot of consulting time to figure it out, so try the PWE solution as a possible short cut.

There are several docs at the website about error 198 on terminal & citrix. Some suggestions from there might apply to your Netware issue, too. Good luck.

 

[ThunderForest]

Thanks for the info. This is really messy. I can get into PWE, but I get this when trying any menu selection:

Load Error: File 'BTR2FCD'
error code 198, pc=0, call=10, seg=0

http://www.thunderforest.bizland.com

 

[MacolaHelp]

Try checking your odbc data sources to be sure that you have the _data_##_isolve drivers installed for your macola data companies & electronics. Check regedit hkey\local\software\macola\versions to be sure the path is correct in the progression & pwe folders. Is your novell drive map rooted? If so, through login script or local windows drive map? Be sure you have a valid map to m:macola70 or however you designate @ dos prompt after login is completed. Check your path at a dos prompt after login to be sure you have a path to pvsw & c:\program files\common files\macola shared. Netware login scripts can override the autoexec.bat locally. Check the pervasive key in regedit hkey\local\software\pervasive to be sure you don't have 6.15 keys along with your v7 keys in this section. Did you ever run instmac\setup.exe (or whatever it was in 103d, I've forgotten)? If not, do so & try to install macola client again & run pwe.

Be sure you delete all orphan users from macola\users, all screen.tmp files from the data folder. Check for permissions on the local windows folder & the above macola shared & pvsw folders. Does your macsetup.cfg show btrieve server rather than local? Have you searched for & deleted any old wbtr*.dlls that might be left in windows or windows\system?

Might there be a memory leak on this workstation? Sometimes fdisk & reinstall the apps will solve these problems. You could also try that regclean utility first.

Did you get any errors on the pervasive client install? Can you butil a file on the macola db such as arslmfil.btr through the pervasive maintenance utility?

 

[MacolaHelp]

I thought of something else, too. I recently went to a site where they had installed a new PC & they were getting dos level fcb errors trying to launch macola. After some investigation, I discovered that the network fellow had installed macola to E (using unc pathing) instead of M on this workstation. Once I verified that administrator was indeed mapped to M: & reran the install, verified the changes in the registry & then relogged in as the user, we were okay. I'm sure you've checked this already, but this network fellow thought he had done it already, too. The shortcuts on the desktop were not updating to the correct drive mappings even then & I had to change manually, too. Hope you've figured it out already. But, just in case ...

 

[dgillz]

Make sure you have no directories under the Macola root that start "data" except your actual data directories.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

dgilsdorf@trianglepartners.com

 

[abaldwin]

In addition to checking for files or folders that start with the letters "data" as dgillz suggested I would bet also that you have files that start with the letter "o". Delete or move them out as well.

Andy

Andy Baldwin

 

[ThunderForest]

No "Data" folders or files, other than ..\data_00, etc... I do have files beginning with the letter "o", but they've been there since 11/2000.

oc25.dll
ocxfix.exe
ocxfix.wri
odbc.dll, and other odb*.* files.

http://www.thunderforest.bizland.com

 

[dgillz]

JD-

There is no version 7.105d. I think you mean 7.5.103d. Please check this version for me. Also please advise if this is Pervasive or MS SQL.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

dgilsdorf@trianglepartners.com

 

[ThunderForest]

Sorry bout the typo. It is 7.5.103d. We use Pervasive 7.

http://www.thunderforest.bizland.com

 

[dgillz]

Do you have an email address? I have a couple of documents to email you.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

dgilsdorf@trianglepartners.com

 

[ThunderForest]

Thanks. Just sent it to dgilsdorf@trianglepartners.com.

http://www.thunderforest.bizland.com

 

[MacolaHelp]

PWE uses ddfs. Are yours dated 4/12/2001? What are the properties on the program icon & do they match the company setup? Might this user have disconnected their drive mappings & inadvertently remapped incorrectly at the workstation?

 

[ThunderForest]

Under ..\Macola70\PWE the DDFs are dated 8/30/99. Is something a miss here? Not sure what to compare PWE.Exe properties to (75.103.0004).

http://www.thunderforest.bizland.com

 

[MacolaHelp]

D:\macola\103\Macola32.exe

(Properties after right click on the program icon for macola.) Start in would be d:\macola\103 in my example. 75.103.004 sounds like the version inside macola, which would correspond to 103d.

If you have the updated dtupdate.zip of 4/16/2001 in the default folder, you can extract the correct ddfs into the data folder. If not in default, try checking your 103d update cd for dtupdate or a ddf zip update file.

If all else fails, post your email & I will send you the correct ddfs for 103d. Macola made a major change to ddfs in this version when they added rma & po requisition.

You also must run setup from instmac in order for pwe to run correctly. This would be after you get the correct ddfs in place.

 

[ThunderForest]

I un and reinstalled the Netware client 3.30 and the original problem mysteriously went away. Now I get the Load Error File ALLOCMAC, error code 198 pc=0 call=6 seg=0. This isn't the first time this has happened to me. Uninstalling and reinstalling, etc. etc. etc. seems to resolve the problem.

My dtUpdate.Zip is dated 5/25/99. The DDFs are dated 5/19/99. I began getting DDF inconsistencies ever since I installed the latest StarShip upgrade for January, and a SAS upgrade soon after. I began getting this type of Netware error at that time as well:

1-28-03 9:30:01 am: NWMKDE-7.16-0
Severity = 1
MKDE-103: System Error: 116.5.0 File: SYS:MACOLA70/DATA_02/IMORDHST.BTR

and have been plagued with these ever since. By implementing the 4/12/01 DDFs, will this have any effect on current operations of StarShip and SAS?

Giving answers before they're asked
is why I go to Tek-Tips.

http://www.thunderforest.bizland.com

 

[MacolaHelp]

You need the 103d ddfs for pwe to run properly. Check w/Exact New Jersey to see if they modified the generic macola ddfs. If they did, you'll need to get from them. Did you find your service pack D CD so you can get the ddfs out of the dtupdate.zip? Otherwise, someone will have to send them to you. Macola probably will if you have current maintenance. Starship reads & writes to the macola files through odbc, so in that sense the ddfs are necessary. Updating the ddfs to the correct version will not break Starship. Starship doesn't update macola ddfs during install or update unless you pointed the starship programs to the macola data directory in error. Even if you did so, your data_00 ddfs should have been intact with the 103d ddfs if your macola update was installed by overwriting the ddfs during the process.

I, too, have had that novell client experience. Some workstations work w/varying versions of novell 3x client. Some wouldn't work w/novell client & had to use microsoft instead. I've had more load errors on 98 workstations w/novell servers using spx whose server name is > 15 characters than other WS/server configurations. There was a known pervasive 2000 sp2 issue with the 15 character limit, fixed in p2000i service packs 3 & 4. Sounds like it's time to upgrade your pervasive and macola, too. You should at least get to service pack f. 7.6.100 came out at the time they stopped novell 4.11 support, so it was never tested on NW 4.11. Don't know if you should go that far.

Are you sure the SAS update you installed is supposed to work with 103d? If not, that might be your problem. The current version at the beginning of this year was 7.6.100a.