Error in LATM log

Hello folks. I'm curious if anyone has had this error and was actually able to resolve it.
"latm.log error: Possible Causes: Insufficient Server Express licenses or not enough database users configured in ladb.cfg".

As the Lawson KB says, the error is misleading and could have an infinite numbers of causes. That's comforting. We've been getting this error more often lately, approximately once a month or so. I have a case open with Support but the possible fixes are more like guesses and are probably infinite also. We don't really have any other performance issues or problems on our system but this one causes it to lockup completely (can't even login). I used to restart everything but the last time I managed to stop and start latm via a command prompt (since I can't even login to LID when this happens) and that cleared it up.
We're behind a bit and on Windows 2003 running the 9.0.1.5 environment.
Any thoughts about this one? I realize your solution won't necessarily be mine but I'm curious anyway.

John Scocco

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

mkhalifa

We are an iSeries shop, but we used to get HR11 freezes when we exceeded the number of user licenses for Payroll. We had to run a call licsta to find out the license usage. Not sure if this helps, but the symptoms sound very familiar. We had to buy 5 more PR licenses and the issue went away.

richardd

We have had the same issue. We are also running Windows 2003. I have found that if I reboot the server once every 3 weeks, then the issue doesn't occur. I suspect that resources are being leaked and only get reclaimed by the restart.

unknown

We were on Window/SQL server and had the same issues. Rebooted weekly . Moved to AIX/oracle last Oct and no issues.

lbecker

Haven't seen that problem specifically, but I've generally been able to resolve any Server Express problems with one or both of these solutions:
Stop and Start the Cobol License Manager
Re-install the Cobol license

unknown

We have an unlimited license for our apps so its not that. Not even sure how I would stop and start the Cobol license manager as I usually stay away from that once its installed.
I've been debating about the reboot. I restart all the services every weekend but I suppose I could add a reboot. I seem to recall doing one the later part of December and then it happened in early Jan so who knows if that will work.
I really appreciate all the responses, especially since I never post here.

todd-brown

Verify the USERS and FOREIGN params in your $LAWDIR/system/ladb.cfg file. Might need to up those.

unknown

Users and foreign are well above the peak users that shows in the ladb log. Thanks.

aszeglin

We just had a whole lot of fun working with Server Express, but ours was on AIX. The start and stop should be easy, you should be able to do that from Windows services (you probably have a service called "Micro Focus License Manager".

On UNIX there's a number of useful commands you can run to list what's using licenses and how to refresh the license database. I'd start here for documentation on Server Express:

documentation.microfocus.com/.../3

lbecker

I thought about this again, and came up with another likely cause. Here is the scenario:
One user start GL95 for a large range of AU's and ACCTS, causing a full database scan. A second user also wants to run GL95, but his can't start until the first transaction is finished. If the wait exceeds latm.cfg OPENTIMEOUT, you should get this error.

If this is common error for a specific program, a fix is to run 'pgmtrndef' and set the "Number User" value to 1 for this program. This means start a new lacobrts process instead of waiting. Blank or 0 means wait. I use a value of 1 for AP20, AP21, AP25 and GL95.

Activate the changes with "tmmon" or use command
$ tmcontrol -lt

I would not change the default OPENTIMEOUT value without good reason. Mine is set to 240 seconds.

dscheppa

My OPENTIMEOUT is set the same at 240

Here are my settings
Configuration file for Lawson Transaction Manager
APPLICATIONS 300 /* # of unique programs that can be up at one time */
RUNAPPS 300 /* # of running programs processes at one time */
REMOTEMACHINES 1 /* # of remote machines in the network */
REMOTEPROGRAMS 10 /* # of remote programs for each remote machine */
TCPUSERS 5 /* # of waiting users per tcptm process */
PMUSERS 150 /* # of lapm users */
MINUPTIME 5 /* # of minutes an program stays up after being closed */
MAXUPTIME 10 /* # of minutes an program can sit idle */
OPENTIMEOUT 240 /* # of secs programs have to start or read msg before assumed dead */
LOOPTIMEOUT 60 /* # of mins programs have to execute before assumed looping */
QUEATTEMPTS 5 /* # of times a full que is checked before full status is accepted */
WAKEUPINTERVAL 1 /* interval in minutes that lapm does housekeeping */
TIMESTAMP LONG /* short or long latm log time stamp format */
DEBUG OFF /* whether to turn on debugging at startup */
USELATM ON /* whether to set USELATM file at startup */

lbecker

LOOPTIMEOUT 60 ?!?!!
You let your users be clocked for an hour?
I bet this is the same program giving the "Insufficient Licenses". I suggest using a batch program for that task.

I thought I was being the BOFH with LOOPTIMEOUT 13 (needed to release a large batch with AP25). They must have some really choice descriptions for Lawson at your shop.

dscheppa

You may be right. These settings were in place when I started working here. I will take your advice and change that to 10
Most our jobs run overnight through recurring def so users aren't affected with how long transactions take. Thanks for your advice there..

unknown

Jack. Please don't spend too many nights thinking about this...haha. Here's the thing. To me the timeout error in the latm.log is just a symptom of some other problem. My whole system locks up before that error appears in the log. You can't even login via LID. I understand the point you are making but I feel like it times out trying to open the program because the system as a whole is locked up. Now clearly it still functions somewhat because it writes that error. And I was able to stop and start latm from a command prompt on the server. But I'm not convinced a program running into a timeout issue actually causes my whole system to lock up. I might be wrong of course but those are my thoughts. Thanks Kathy for sharing your settings. I need to start hanging out here more.

ludovic-masuyer

Are you having similar problem to what is in KB Article 5429352?

unknown

The only thing I found with that article number in it was something do to with paging space growth on an AIX system. Not sure if that's what you meant but we're not on AIX.

lbecker

Had something a little bit comparable a few years ago. My users reported clocked screens and an unresponsive application. Websphere would use up 1 GB of memory, lock up all transactions, and write massive dump files as it died. But that didn't really impact LID or the Jobs Scheduler.

The solution was a LSFCT patch that had new jar files for Websphere.

Copyright © 2025 Infor. All rights reserved.