All Batch Jobs Unable to Log In

We recently had an issue with a new install where all batch jobs were going into recovery with the error “Unable to log in <username>”.  The can often be attributed to an incorrect password in the BATCH privileged identity, but in this case it was due to a typo in lajs.cfg.  The “RUNUSERKEY” field was misspelled.  So, if you ever encounter this issue, you can save yourself some time and get a couple of sets of eyes on the lajs.cfg file!  After making the change, reboot the Lawson server or stop/start services. You should now be able to log in.