We are on a Windows 2003R2 server and whenever we attempt to run a batch job via jobdef we receive the following Error:

execjob(laStartProcess): Unable to log in domain\username
StartStep failed: The operation completed successfully.

Based on the lawson documention we saw that we had to add the following lines in our lajs.cgf file:
RUNALL OFF
RUNUSER domain\username /* User that batch jobs rus as */
RUNPWD mypassword /* Password for BATCHUSER */

Of course the lines above have our usernames and passwords

Other Lawson documentation stated that we had to have the Lawson groups in the "Log on as Batch Job" policy. We already had this in both the local policy and domain policy and was also double checked by our netwrok adminstrators. In addition we ran a small vbscript test just to make sure the policies were in effect.

Based on all of this we are still having the same error.

The only thing we could think of is that the password sync is not talking to the registry for some reason. But if that is the case how do we get it to sync.

Any thoughts? Any help is appreciated.

Are you on MSP4 and using the privileged user to run all batch jobs? In your jobdef, are you running any user tokens? I know in Windows user tokens won't run in jobdef unless you are logging in using the privileged account.

You may also want to try to re-sync the password in http://yourserver/sso/useratts.htm

Yes we are running user tokens. As far as being privileged account, the windows account is currently at an administrative level and in lawson its an Admin/super user. Is that what you ment by privilaged account?

We currently do not have access to http://yourserver/sso/useratts.htm as this is currently not set up on our test server. Is that a problem?

Any suggestions?

By privileged account, I meant in lajs.cfg, do you have an entry for RUNUSERKEY?

No we dont have this entry.

However, I do have more information which actual may change the response you've given me thus far. This is a ghost "copy" of production and is now our test system. Our production system did not have these lines at all and is working fine. So I am assuming we do not need them in our test server. Any thoughts?

By the way the test server is running under a different IP and ports.
All programs seem to be working except for submitting these jobs