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
Upgrade to LSF 9.0.0.9-need help huge production problem
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
200
Members:
0
Total:
200
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1351
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Upgrade to LSF 9.0.0.9-need help huge production problem
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Kay
Basic Member
Posts: 11
6/29/2011 11:14 AM
First, let me start with saying that I am totally 100% functional, so I am sure that when posting this question that I will leave off something important.
We have a problem that Lawson and Velocity have been unable to help us fix at this time. We upgraded our production environment to LSF 9.0.0.9 and our LP programs
plus the PR135 will not run. The error message reads: ERROR: execjob Process Died, 991538
WARNING: Job Step May Still Be Running, Check The Process Id From This Job Log
We rebooted the server last night....and have no jobs hanging, etc. We have done other things based on the recommendation of Lawson and Velocity....but nothing worked.
Has anyone else encountered this problem? We are running out of time because Payroll runs next Tuesday.
Roger French
Veteran Member
Posts: 545
6/29/2011 11:50 AM
Are all of those programs compiled correctly?
What version are the LP programs compared to other programs such as HR, Procurement and Financials? Are you licensed for the LP programs?
Does the problem happen both in LID and Portal?
Do other jobs/reports run OK?
I'm sure if you've got both Lawson and Velocity on it, some solution will come forth soon.
Kay
Basic Member
Posts: 11
6/29/2011 11:59 AM
Thank you for the information.
Yes, Velocity recompiled all programs. All jobs run okay, except for LP100, LP130,LP140 and PR135. The problem does occur in both LID and Portal.
Below is the summary from Velocity of all that has been done thus far:
This issue started after ESP 9 was applied for LSF900. It is duplicated in all product lines (DEV & TEST in the dev. environment and PROD in the production environment). It is affecting the production payroll, which has already been established. We have recompiled the programs, product line, recycled the environment, and last night recycled the entire server (which included PROD and DEV Lawson, DB and LDAP). We are processing the jobs through LID, so the Websphere application servers should not come into play.
John Henley
Senior Member
Posts: 3348
6/29/2011 12:01 PM
What platform are you on?
Do you have errors in lajs.log or ladb.log?
When you upgraded, did you recompile BSI tax factory?
Kay
Basic Member
Posts: 11
6/29/2011 12:33 PM
Thank you John for replying.
We are on AIX. I am not sure if they recompiled Tax Factory....but I will ask Velocity immediately.
As for the lajs.log or ladb.log errors....
Tue Jun 28 20:54:26 2011: Received Death Notification, Pid=967140
Tue Jun 28 20:54:26 2011: execjob Process Died, Pid=967140
Tue Jun 28 20:54:26 2011: WARNING: Running Job Removed From Running Queue.
Tue Jun 28 20:54:26 2011: Job Log Process Id Should Be Checked For Defunct Or Orphaned Process.
Tue Jun 28 20:54:26 2011: User Name = z925229, Job Name = PR135.OOOO, Job Number = 0000000151
No ladb errors.
Thanks so much!
Roger French
Veteran Member
Posts: 545
6/29/2011 1:18 PM
If it's only those specific jobs which are bombing out, can you create *new* versions of the those jobs and see if those new versions will run?
John Henley
Senior Member
Posts: 3348
6/29/2011 1:59 PM
What do you see in the 'examine log' for one of those failed jobs?
Are they listed in job scheduler as 'needs recovery' or as 'completed"
Kay
Basic Member
Posts: 11
6/29/2011 4:16 PM
Roger....Yes, our IT person created a copy of the PR135 in TEST and it ran.....but she is scared to do the same to the LP update jobs. She is sharing that information with Lawson to see if that helps to resolve the problem.
Thanks for replying!
Kay
Basic Member
Posts: 11
6/29/2011 4:18 PM
John...The jobs are listed as "needs recovery" in the job scheduler.
Thanks for replying!
Jeff White
Veteran Member
Posts: 83
6/29/2011 4:51 PM
What I would try at this point:
In the TEST productline, I would pgmdump on PR135, save off the PR135 source code files, and then remove the program in pgmdef. Then I would copy the PR135 source back in the the /prsrc directory and run the pgmload on the PR135. Just something I would try. Jeff
Kay
Basic Member
Posts: 11
6/29/2011 5:03 PM
Jeff -
Thank you....I am passing your suggestion on to the IT staff now.
Thank you again!
John Henley
Senior Member
Posts: 3348
6/29/2011 5:31 PM
What do you see in the 'examine log' ??
Kay
Basic Member
Posts: 11
6/29/2011 6:09 PM
Hi John....I will find out what is in the "examine log".
I can overhear the IT group and Lawson are on a Webex together. It sounds as if Lawson can see the reports behind the scenes but the User only sees the job ending in error in the Job Scheduler.....no output in the Print Manager.
I should have asked one of the IT guys to open post this question on Guru, so that we could respond quicker. I am a Functional Consultant working at this client on another project....When I heard that they upgraded their production environment and these errors popped up, I went into panic mode and tried to help by posting on Guru.
Thank you so much! I will check on the "examine log".
Kay
Basic Member
Posts: 11
6/29/2011 6:32 PM
Ok guys....
Here is an update on our emergency. Lawson found the problem....something was wrong with a PR135.cfg file. They removed it and the jobs ran....but when they put the config file back it broke the jobs. Lawson is going to give us new config files.
As a functional person, I am not sure I understand this.....but I know all of you will understand. I am just glad they finally found a resolution.
MANY THANKS to all you that replied to my question
.
Have a great evening!
Kay
You are not authorized to post a reply.