AD:lawson account lock out

I've done this before. Somewhere that you enter the Lawson password during an install it is entered incorrectly. It can be very, very difficult to find. Check the install logs and/or properties files on all you Lawson software looking for an incorrect entry. It's generally a bad idea for the Lawson AD ID to lock out from the Lawson point of view, though the network admin requires it of all IDs.

It is also possible that one of the Lawson admins is entering it wrong when system checking. If it's happening consistently I'd doubt that to be the case.

make sure no one write auto ftp/sftp/scp with embeding pwd. ttry to set account NEVER lockout, and see what happens.

We have had this same issue for years and have never been able to get to the bottom of it. We actually wrote a script on the iseries that runs in ROBOT and will automatically re-enable the Lawson id if and when it gets disabled. It works great.

We had the same issue. The below step solved our lockout issue:

 

"The issue with the folks at purchasing and MM was a setting for printing PO's we set it to batch and that fixed their issue.   The resolution was:
Create the LAWDIR/system/webrpt.cfg with the following line, then stopped and started lajs.
RUNUSERKEY BATCH"

Would you mind sharing how in the world you figured that one out?

The users that were getting locked out were all in purchasing and the service account that kept getting locked out was running WH jobs.  One thing the user ID’s all had in common was they sent jobs to the printer.  We were then able to work with infor and they gave us the resolution.  (see attached)

Cool! Thank!

This is a long shot, but I wanted to see if anyone could help us. We are running Lawson version 9.0.1.13 right now and are in the process of upgrading to version 10 - but we have all of a sudden began experiencing the Lawson user Lockout similar to that metioned in this forum.

I tried the recommended steps, and then after, all of our "autoprint" jobs began going into recovery that weren't under our Lawson user. Therefore we had to delete the webrtp.cfg file that we put out there to allow all other jobs to run and autoprint. We are running the jobs, and simply unlocking the user as it locks to keep things running - but there has to be a fix. We have been working with infor with no luck. Any suggestions?

Unfortunately, it depends on what you're using the Lawson user for. IPA Configuration Sets (Lawson, File Access, System Command) is common, as well as LBI back-office or OLEDB connections. Of course it could be someone trying to log in as Lawson.