View Full Version: Multi-step Job Problem

LawsonTalk > LSF 9.0 (NEW!!) > Multi-step Job Problem



Title: Multi-step Job Problem


xqqqme - November 16, 2007 09:48 PM (GMT)
I have a multi-step job that won't run for our users.
I can run it fine and my users can submit the job through lid and have it run fine.
This does run fine for the users in 8.0.3.
There is no error in the joblog, the 1st step completes then it hangs while executing the 2nd step which is a vbs script to send e-mail.
Any help will be appreciated.

Thanks!

Keith_G_Thompson - November 17, 2007 06:06 AM (GMT)
Check execute permissions on the script and / or related files the script might call.

To rest that theory you might try temporarily adjusting your O/S level security and/or the users O/S security to see if you can get it to where you can't run the job properly, or they can.

Also, try having the user(s) run just that step and see if it completes to help isolate the problem.

shane pennington - November 20, 2007 01:03 AM (GMT)
I presume your are LSF 9 since you referenced 803 as though it were in your past.

Are the users having problems CheckLS=yes users? If so, try testing one of them by making them CheckLS=No. I suspect you're dealing with an issue (PT 166806) I identified over a year ago where CheckLS=Yes users are not able to submit jobs defined to Custom Tokens.

Lawson is QA'ing the solution for the umpteenth time, and has once again promised the solution in the next week or two.

My hopes are not high as I identified this issue late December-2006 while I was in St Paul, and even though it's been Priority-2 since day-1, it is still not resolved.

If this is not your scenario, I apologize. Please give us more details and tell us what security configurations you've tested trying to get this to work. (e.g. CheckLS=No, LAUA Security Officer, etc...)

xqqqme - November 21, 2007 05:13 PM (GMT)
OK - I got this figured out finally!
It wasn't a LSF 9 problem but an issue with the new server we have LSF 9 installed on.
There was a registry entry missing. Once I added 2 keys back into the registry, Wscript worked fine.
Just in case somebody else has this problem this is what I added:

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Script Host
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Script Host\Settings

That was all - didn't need to add key values.
Hope this helps somebody else.




Hosted for free by InvisionFree