Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
LATM crashing again and again
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
JarrettHPH
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
5209
People Online:
Visitors:
284
Members:
0
Total:
284
Online Now:
New Topics
Lawson S3 HR/Payroll/Benefits
Post Tax Benefit Plan Table
11/14/2024 9:16 PM
Hi, totally new to Laswon. I have a repor
Lawson S3 Procurement
ED501 Error: Map 850 not supported by /law/c15vda/lawson/test10/edi/bin/laws_out_91
11/12/2024 3:47 PM
Tried runnning ED501 and getting the atathced erro
Lawson S3 HR/Payroll/Benefits
Error
11/6/2024 9:54 PM
When I try to enroll a retiree in 72.1 health plan
Infor ERP (Syteline)
Syteline: New Data Maintenance Wizard (Error) Need help
11/1/2024 4:24 PM
Hi, I need help with an error on syteline while us
Dealing with Lawson / Infor
Implementing Lawson v10 with Cerner Surginet, Case Cart Picking, and Quick Adds for the OR
10/29/2024 4:20 PM
Hi Everyone, I am wondering if there is any org
Lawson S3 HR/Payroll/Benefits
Canada Tax Calculation (Federal and Provincial) Issue
10/23/2024 5:00 AM
Initially, we had problem with CPP2 calculation is
Lawson S3 HR/Payroll/Benefits
CA Section 125 401k Plan
10/22/2024 10:13 PM
Does anyone have any recommendations on how to fac
S3 Systems Administration
Running AC120 deleted records from ACMASTER table
10/22/2024 3:40 PM
We recently ran the AC120 as normal and somehow it
Lawson S3 Procurement
RQ13 Approval Info
10/17/2024 2:12 PM
When a Requisition is approved on RQ13, what table
S3 Customization/Development
Read and Write CSV file COBOL
10/9/2024 2:53 PM
Does anyone have a quik example of a program that
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3291
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1372
Roger French
1315
mark.cook
1244
Forums
Filtered Topics
Unanswered
Unresolved
Announcements
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
LATM crashing again and again
Please
login
to post a reply.
3 Replies
0
Subscribed to this topic
27 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
prithwee
Basic Member
Posts: 20
3/15/2006 9:41 PM
What are the most common causes of LATM crashing again and again? We are having issues. I will attach a sample LATM log file. Please help. I have a hunch that is has to do something with process Flow.
Wed Mar 15 15:30:02 2006: ERROR: Exited with error code 1
Wed Mar 15 15:38:06 2006: Timeout on opening application, removing application
Wed Mar 15 15:38:06 2006: Pid=2117756, Program Code=GL00 DataArea/DataID TEST
Wed Mar 15 15:38:06 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:38:06 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:38:06 2006: Terminating process, 2117756
Wed Mar 15 15:38:06 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=2117756
Wed Mar 15 15:38:06 2006: Program Code = GL00 , DataArea/DataID = TEST
Wed Mar 15 15:38:06 2006: ERROR: Exited with error code 1
Wed Mar 15 15:45:49 2006: latm (PrcPMDeath): Dead message removed from lacobrts message buffer
Wed Mar 15 15:45:49 2006: latm (PrcDeath): Received death notification of lapm, Uid=14, Pid=3891372
Wed Mar 15 15:45:49 2006: Appending lapm log, /e0hk/test/apps/system/joblog/lapm.3891372 to latm log
Wed Mar 15 15:45:49 2006: latm (AppendLog): Start of lapm log
File TEST/ACACCTCAT.OpenDBView error is Driver failed (54).
OpenDBView error is Driver failed (54).
File TEST/ADDRDATA.OpenDBView error is Driver failed (54).
OpenDBView error is Driver failed (54).
Wed Mar 15 15:45:49 2006: latm (AppendLog): End of lapm log
Wed Mar 15 15:45:53 2006: latm (PrcPMDeath): Dead message removed from lacobrts message buffer
Wed Mar 15 15:45:53 2006: latm (PrcDeath): Received death notification of lapm, Uid=68, Pid=3195114
Wed Mar 15 15:45:53 2006: Appending lapm log, /e0hk/test/apps/system/joblog/lapm.3195114 to latm log
Wed Mar 15 15:45:53 2006: latm (AppendLog): Start of lapm log
File TEST/ACACCTCAT.OpenDBView error is Driver failed (54).
OpenDBView error is Driver failed (54).
Wed Mar 15 15:45:53 2006: latm (AppendLog): End of lapm log
Wed Mar 15 15:47:32 2006: latm (PrcPMDeath): Dead message removed from lacobrts message buffer
Wed Mar 15 15:47:32 2006: latm (PrcDeath): Received death notification of lapm, Uid=35, Pid=4800536
Wed Mar 15 15:47:32 2006: Appending lapm log, /e0hk/test/apps/system/joblog/lapm.4800536 to latm log
Wed Mar 15 15:47:32 2006: latm (AppendLog): Start of lapm log
File TEST/ACACTIVITY.OpenDBView error is Driver failed (54).
OpenDBView error is Driver failed (54).
Wed Mar 15 15:47:32 2006: latm (AppendLog): End of lapm log
Wed Mar 15 15:47:48 2006: latm (jeeReallocTP): RUNAPPS Hit Max, table reallocated.
Wed Mar 15 15:48:24 2006: Timeout on opening application, removing application
Wed Mar 15 15:48:24 2006: Pid=5955618, Program Code=AC10 DataArea/DataID TEST
Wed Mar 15 15:48:24 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:48:24 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:48:24 2006: Terminating process, 5955618
Wed Mar 15 15:48:24 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=5955618
Wed Mar 15 15:48:24 2006: Program Code = AC10 , DataArea/DataID = TEST
Wed Mar 15 15:48:24 2006: ERROR: Exited with error code 1
Wed Mar 15 15:48:24 2006: Timeout on opening application, removing application
Wed Mar 15 15:48:24 2006: Pid=5460056, Program Code=RW00 DataArea/DataID TEST
Wed Mar 15 15:48:24 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:48:24 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:48:24 2006: Terminating process, 5460056
Wed Mar 15 15:48:24 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=5460056
Wed Mar 15 15:48:24 2006: Program Code = RW00 , DataArea/DataID = TEST
Wed Mar 15 15:48:24 2006: ERROR: Exited with error code 1
Wed Mar 15 15:50:26 2006: Timeout on opening application, removing application
Wed Mar 15 15:50:26 2006: Pid=4083740, Program Code=WF46 DataArea/DataID LOGAN
Wed Mar 15 15:50:26 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:50:26 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:50:26 2006: Terminating process, 4083740
Wed Mar 15 15:50:26 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=4083740
Wed Mar 15 15:50:26 2006: Program Code = WF46 , DataArea/DataID = LOGAN
Wed Mar 15 15:50:26 2006: ERROR: Exited with error code 1
Wed Mar 15 15:50:26 2006: Timeout on opening application, removing application
Wed Mar 15 15:50:26 2006: Pid=4083740, Program Code=WF46 DataArea/DataID LOGAN
Wed Mar 15 15:50:26 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:50:26 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:50:26 2006: Terminating process, 4083740
Wed Mar 15 15:50:26 2006: ERROR: waitpid() failed on process 4083740.
Wed Mar 15 15:50:26 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=4083740
Wed Mar 15 15:50:26 2006: Program Code = WF46 , DataArea/DataID = LOGAN
Wed Mar 15 15:50:26 2006: ERROR: Stopped due to a signal 54
Wed Mar 15 15:50:26 2006: SIGNAL: Unknown
Wed Mar 15 15:50:26 2006: Timeout on opening application, removing application
Wed Mar 15 15:50:26 2006: Pid=5460056, Program Code=WF46 DataArea/DataID LOGAN
Wed Mar 15 15:50:26 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:50:26 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:50:26 2006: Terminating process, 5460056
Wed Mar 15 15:50:26 2006: ERROR: waitpid() failed on process 5460056.
Wed Mar 15 15:50:26 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=5460056
Wed Mar 15 15:50:26 2006: Program Code = WF46 , DataArea/DataID = LOGAN
Wed Mar 15 15:50:26 2006: ERROR: Stopped due to a signal 54
Wed Mar 15 15:50:26 2006: SIGNAL: Unknown
Wed Mar 15 15:50:26 2006: Timeout on opening application, removing application
Wed Mar 15 15:50:26 2006: Pid=5955618, Program Code=WF46 DataArea/DataID LOGAN
Wed Mar 15 15:50:26 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:50:26 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:50:26 2006: Terminating process, 5955618
Wed Mar 15 15:50:26 2006: ERROR: waitpid() failed on process 5955618.
Wed Mar 15 15:50:26 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=5955618
Wed Mar 15 15:50:26 2006: Program Code = WF46 , DataArea/DataID = LOGAN
Wed Mar 15 15:50:26 2006: ERROR: Stopped due to a signal 54
Wed Mar 15 15:50:26 2006: SIGNAL: Unknown
Wed Mar 15 15:50:26 2006: Timeout on opening application, removing application
Wed Mar 15 15:50:26 2006: Pid=4083740, Program Code=GL90 DataArea/DataID TEST
Wed Mar 15 15:50:26 2006: Possible causes: Insufficient Server Express licenses or
Wed Mar 15 15:50:26 2006: not enough database users configured in ladb.cfg.
Wed Mar 15 15:50:26 2006: Terminating process, 4083740
Wed Mar 15 15:50:26 2006: ERROR: waitpid() failed on process 4083740.
Wed Mar 15 15:50:26 2006: latm (PrcTPCrash): Received death notification of lacobrts, Uid=-1, Pid=4083740
Wed Mar 15 15:50:26 2006: Program Code = GL90 , DataArea/DataID = TEST
Wed Mar 15 15:50:26 2006: ERROR: Stopped due to a signal 54
Wed Mar 15 15:50:26 2006: SIGNAL: Unknown
prithwee
Basic Member
Posts: 20
3/16/2006 3:51 PM
I have a feeling that it was due to Process Flow. Just want to share some knowledge with you all which I gathered during this issue. If you have processflow with lots of nodes/activities and are using those variables, they get stored in WFACTVAR table. That table can grow huge. Everyone of my work unit creates approx. 2500 lines in that table since the flow is highly customized and does lots of things. Make it sure that your AUTO-PURGE is on and to e on the safe side, run WF140 and WF100 daily.
I am not sure if that crashed LATM but I think it did.
I have one mor equestion. WF140 and WF100 have date parameters. How can I schedule this flow so that the date automatically gets updated to today's date.
John Henley
Posts: 3353
3/16/2006 8:32 PM
To have WF100/WF140 run with today's date you could modify them to just plug system date into that parameter. Alternatively, you could write a separate program that called 900-CREATE-AND-SUBMIT-JOB to create a unique job each time it is run w/ the thru date filled in with system date. Then set this separate program as a daily recurring job.
BTW, even without the PF problems you think you're having with LATM, your system doesn't look very stable.
Alex Tsekhansky
Veteran Member
Posts: 92
3/18/2006 4:28 PM
Hello, Prithwee!
The error messages suggest a variety of issues. In most cases the message means what is says - you have a problem with COBOL licensing. The most common issue - not enough licenses, or the license namager database got corrupted. You can easily monitor usage of COBOL licenses with APPTRACK.
Please
login
to post a reply.