IPA Scheduling Error: actor_does_not_support_run_as

Has anyone encountered and solved an "actor_does_not_support_run_as" error when attempting to schedule an IPA Process Flow?

We have have just implemented Lawson 10. We are utilizing IPA to interface subsystems into the LAWSON GL, AP, and Cash Book modules. We've got our flows built and tested, manually executing the flow within the Rich Client without error. When scheduling the flow to run at fixed intervals we get the following error

Error: com.lawson.security.authen.SecurityAuthenException:
com.lawson.security.authen.LawsonUserContextImpl.security.authen.actor_does_not_support_run_
as
at
com.lawson.security.authen.LawsonUserContextImpl.setRunAsUserOnDuplicateContextForAsync(L
awsonUserContextImpl.java:1590)
at
com.lawson.security.authen.DataCtxUserCtxWrapper.setRunAsUserOnDuplicateContextForAsync(D
ataCtxUserCtxWrapper.java:465)

I can see a grey'd out check box on the Landmark Actor for "Enable Run As", but no ability to click. We were able to activate "Enable Run As" on the Lawson User Id, but the sync process did not update this Landmark Actor and we still experienced the same error.

Thanks in advance. We are very green with both lawson and IPA.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

Hey Nate hope all is well, I beleive you need to open up the LMKgrid cmd and run this command.

secadm actor enablerunas <actor name here>

You will need to restart the LPA service, let me know if you have any issues.

russel-cornelson

I saw this post come in while I was on Vacation, but I couldn't respond via my phone for some reason.

I just want to clarify the solution to this problem, the answer provided by Nathan "secadm actor enablerunas <actor>" where <actor> = User that owns the Grid java processes is a perfect solution for any client that is not using ISS security.

However, If your system has Landmark and LSF federated using ISS, you should resolve this by setting the <actor> to run as enabled in ISS's scwebadminapp.

1. search for "People" = actor running grid

2. click the edit pencil beside that actor

3. set RunAsEnabled = Yes*

If this is set to Yes, set it to No and save it, then set it to Yes and hit save again.

This solution is important, as if Landmark's user and this user is out of sync ... every time you make a change to this user it will push this setting over and recreate the original problem.

Copyright © 2025 Infor. All rights reserved.