Hello,
was wondering if anyone can help me. We have a generic super user login for lawson that 3 of us have access to. All of our reports run off this user name automatically at night (IE: pa100 etc.) Per sarbanes we had to change the password for this log on...so IS did that for me yesterday. Problem was today when I came in the reports did not run last night - so I logged in under the generic log on and recovered the reports...then they were fine. Is there something else
that I am supposed to do or do I have to synch this up somehow or somewhere?

Thanks!
Nathalie

Nathalie:

You didn't mention what OS you're using - windows or unix. We're on unix here - not sure what windows would do differently. What password did they change for you: os level (for lid), portal or a database password? Did the overnight jobs go into Needs Recovery? What was the error message in the examine log?

-GW

Oh sorry...we are on Windows. I had IS change it on the user side. Then I logged onto LID with it, but didn't do anything other then that. The reports that automatically run went into needs recovery so once I logged on and recovered them they were fine.
Does that help? I don't remember the error message...
thanks
Nathalie

I'm guessing if you perform the steps in KB Article#85718 it will resolve your issue.

Basically this will configure your system so that all batch jobs will run as a specific user that you define. The reports still go to the correct print manager and jobs are listed under the correct user in the job scheduler and you won't have to worry about passwords synching up.

The KB's about using the RUNALL & RUNUSER params don't explain it completely. I just found this out this morning. The RUNALL and RUNUSER params work independently, sort of... It was explained to me and to GSC in the early days when it first came out that the RUNALL was a switch to turn on using the RUNUSER account. This isn't so. It has sinced been explained correctly, but not documented complete with how it works. The RUNALL=ON only tells the system to run the batch jobs as the RUNUSER account and will not give access to any ENV tokens and utilities. This also affects how recuring jobs are submitted. They told me today, that there really shouldn't be any case where RUNALL SHOULDN'T be set to OFF. Now, there still is an issue when a Portal user changes their password and can't print to any LAWSON Defined printers. There is a new param to put in the lajs.cfg and it is: REGISTERIOSPWD=OFF. This has something to do with turning off calling the routine to save the info to the registry. Call GSC to get the whole skinny on the explanation of the handicap of how it handles user credintials in Windows until Ver 9. Brady was very informative.

The documentation isn't complete? It doesn't explain everything?? You have to call Lawson to get things configured correctly???

I'm shocked. Shocked!! :o