Issue with running job after moving from Linux to Windows

We are moving from Linux/Oracle DB to Windows/SQL Server Database. I am trying to run a Lawson job that runs a simple "listusermap" command. At first I was trying to run a user token (that executes a script) and that wasn't working either. However, I AM able to successfully execute a job that runs a standard Lawson 4GL program (CU201).

I'm getting the error below - we are working with Infor support - but we aren't making any progress and this is a showstopper issue at this point - has anyone else gone through this issue and if so, how did you resolve it? Thanks in advance for any ideas or suggestions. - Laura

BEGIN: Job Submitted: Thu Jan 27 07:41:35 2022

Step 1: AAATEST Started. . . . .: Thu Jan 27 07:41:36 2022
Token Command. . . . . .: listusermap
execjob(laStartProcess): Unable to log in BHSen21704
StartStep failed: The operation completed successfully.

Elapsed Time: 00:00:02

END: Job Ended: Thu Jan 27 07:41:37 2022

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Accepted answers

All comments

unknown

Looks similar to the message our users would get running a batch job from a Lawson multi-step job, where their network password has been updated, but they did not update their batch job password, and the multi-step job can no longer log them on to the app server to execute batch jobs. Have you tried using the sso/useratts.htm (users run as a bookmark here) to Reset Job Password?

laura-patenaude

I'm not sure - I'll follow up on that. But if that was happening - wouldn't they not be able to run any batch jobs at all? They are able to run batch jobs for 4GL programs - those are successful. It just seems to be batch jobs that run environment or user tokens that fail.

unknown

We have a KB article for this scenario:
1587738 - Batch Job failed: execjob(laStartProcess): Unable to log in Domainuser
On Windows, if you are running a job that runs a script or tokendef user form, your Environment Identity password must be set to the correct password.

Please review the article for the resoltuion.

laura-patenaude

Thanks Laurie. I know Sree Potluri (our Lawson Sys Admin) was given a KB article from Lawson, that addressed this issue, but I don't think this is the one she was given. I'm going to follow up with her.

laura-patenaude

That makes sense - because this is only happening on our new Windows server.

unknown

You're welcome, and I want to clarify.. this is only an issue for the Windows platform, no other platform that Infor Lawson runs on requires the user's environment identity password to be the correct password **EDIT** For those following this and for LPatenaude, the "Correct password" requirement only pertains to custom scripts/user tokens setup in tokendef, when running delivered Infor Lawson programs, users do not need the correct password stored on their environment Identity because we have the BATCH privileged account setup in lajs.cfg. Here is a link to our new public documentation site, this link takes you right to the Windows Lawson System Foundation Core Technology Installation guide in the Post Install section labeled "Creating and Configuring a Privileged Identity for Batch Jobs", it explains this need for "Windows Only" setup:
https://docs.infor.com/lsf/10.0/en-us/lsfwinolh/default.html?helpcontent=lsflsrdag_op/xti1546287691434.html&hl=runuserkey

laura-patenaude

Thanks again - I just wanted to let everyone know that going into ISS and entering my password again in both the Password and Confirm Password boxes, for the Environment Identity DID resolve this issue. It's somewhat disconcerting because does this mean that we have to go through and do this for EVERY user that is loaded into our new Windows system? Was something missed when the install was done a few weeks ago? And if we have to go through and re-enter all the passwords - what happens when a user changes their password? We are SSO and ADFS. I will discuss with our Lawson System Admin when she returns to the office on Tuesday.

Copyright © 2025 Infor. All rights reserved.