Jobs not executing - going into limbo LSF 9.0.1.12

We recently applied LSF ESP 9.0.1.12 and had one of our users report that had issues with submitting jobs - said the job was submitted successfully but it really hadn't. Was not executing at all - not in active jobs, needs waiting and completed. We had only one user reporting the issue but now that we have had several other users move to Windows 7, they are all encountering the issue. There is an LSF patch created for the fix but we do not want to install the patch without thorough testing. Has anyone else run into this and how did you get around it?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

moellerg

Are these "old" jobs from a previous ESP? Have the users try creating brand new jobs and submit them. See if that makes a difference.

unknown

we had the same issue with existing jobs..we created new jobs - if you want the same job name, printscreen the parameters and delete the job and add a new job with the same job name. it worked for us.

unknown

When you applied the ESP, what was the last patch number you included with the ESP? Also, what patch number is the fix included in? We are testing ESP12 now. I would like to know if we have the fix included in our testing. We applied through LSF 09000112P26092.

Thanks!

unknown

We found that going from each newer release required user to delete and recreate their jobs.

unknown

By "release" do you mean major release (8.0.1 to 9.0.0 to 9.0.1) or minor release (9.0.1.10 to 9.0.1.12)? We have never deleted/recreated user jobs between 9.0.1.3 to 9.0.1.10.

unknown

We are moving from 9.0.1.11 to 9.1.1.12. We currently are not having the issues you are mentioning. When ESP are downloaded, they do not include the most recent patches since the ESP bundle was created. Those are downloaded separately and applied at the same time as the ESP. We applied 7 LSF and 10 XML patches at the same time as the ESP.

unknown

I meant major releases.

deanna-plant

Creating new jobs is not fixing the issue for us. It appears if you wait for 20ish minutes before running the job again, it actually submits. If submitted before that 20 minutes, it goes into limbo. We did not have this issue when users were on XP workstations...only since they have moved to Windows 7. Odd!

com_proactive_201104.pdf

Copyright © 2025 Infor. All rights reserved.