If you are receiving an IPA (Infor Process Automation) Memory Alert of type WU Alloc when an IPA flow runs, and you have made every attempt to optimize your flow, you can increase the alert threshold. Note that this fix will only work for on-premises customers. To increase the alert threshold, you will need to open a Landmark command window and run the following command:
paadm cfgprm update –tenant ALL –dataarea ALL –category Metrics –name “Work Unit Memory Threshold” –type MiB –value <new threshold>
The record will either be created (if this has never been done before), or updated. It should look like the screenshot below.
User is trying to submit a requisition when clicking Special / Service and getting error:
“Requested delivery date cannot be less than today’s date” even though the requested delivery date was not less than today’s date. See workaround below.
Workaround: If the user enters the Requesting Location and Requested Delivery Date then clicks the Special / Service button (without entering any other info). It creates the requisition. They then can go into it and modify it, adding all additional information. See example screenshot:
NOTE: The above resolution is a workaround, you’ll have to consult with Infor to get this resolved on the application level. Nogalis also offers a team of consultants under a single MSP service plan if this is something you need future support for as we also handle communications through Infor.
https://www.nogalis.com/wp-content/uploads/2026/01/How-to-fix-Lawson-RQC-Error-Requested-delivery-date-cannot-be-less-than-todays-date.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2026-01-16 08:41:282026-01-12 11:52:01How to fix Lawson RQC Error – Requested delivery date cannot be less than today’s date
If you get this page, just keep refreshing until the page loads
Go to Scheduling > By Process Definition
If the Process Name isn’t listed, you’ll need to add a trigger
Click the add icon
Select the Process
Work Title is required
Click the save button after selecting a workflow and entering the work title
To run the process, right-click on the Process Trigger, and select “Start”
To view the process update and log, go to Administration > Work Units > Work Units
Double-click the work unit to open the admin panel. The “Log” tab is the most useful. It’s best to click “Open” on the log and it will download to a text file.
https://www.nogalis.com/wp-content/uploads/2026/01/Running-an-IPA-Workflow-from-ProcessFlowAdministrator.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2026-01-09 08:44:222026-01-05 12:49:29Running an IPA Workflow from ProcessFlowAdministrator
Please note: This reboot sequencing requirement only applies IF the DB server is rebooted. If the DB server is not rebooted, you can reboot the other servers in any order
Follow this process to ensure the Lawson system comes up clean when a DB server is rebooted:
Reboot the DB server BEFORE the other servers.
Wait for the DB server to be completely up before rebooting any of the Application servers.
Once DB server is up and running reboot Lawson application server and the Landmark Server
The main concern is that the DB server must be up and running for all other Lawson applications to connect to the DB.
https://www.nogalis.com/wp-content/uploads/2026/01/Reboot-Order-–-Lawson-Application-and-Landmark-and-DB-servers.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2026-01-06 08:39:562026-01-05 12:43:51Reboot Order – Lawson Application and Landmark and DB servers
When logging into Lawson via a federated system and SAML configuration, a SAML response is received from Azure and that is all Lawson cares about when authenticating.
Users may see an error like this if the ID differs from the SAML configuration:
Authentication Failure
Unable to create a session. Contact your system administrator and provide this information along with the tracking id: <long hash code ID for Infor to debug>
How to debug:
Once you’re in Lawson, any app issues are related to Lawson internally.
Open the json or XML file in Notepad++ and search for <NameID Format=
Search for your known user name:
That’s it! This is what is being returned from SAML response on the Azure side. You’ll have to work with the network team to coordinate on the proper ID for the user to use in Lawson.
https://www.nogalis.com/wp-content/uploads/2025/12/How-to-debug-login-issues-in-Lawson-with-SAML-Tracer-Tool.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2026-01-02 08:01:162026-01-09 11:43:29How to debug login issues in Lawson with SAML Tracer Tool
Follow the steps below to learn how to find logs for users that are getting an error when logging into Lawson.
First, look for errors on the LTR Grid (Local Technology Runtime) by going to applications/STSRuntimeService and click on the lower left hand corner number as shown below:
Next, search for code in the error message to determine why it is erroring out. (suggestion: use the Find function to detect the errors in the logs faster)
You IT should be notified of these errors in the logs and be able to resolve it quickly to allow user access the next time they log in.
https://www.nogalis.com/wp-content/uploads/2025/12/How-to-find-logs-for-Users-getting-error-logging-into-lawson.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2025-12-30 12:51:022025-12-29 13:00:57How to find logs for Users getting error logging into Lawson
Summary: When trying to replace a cert with a new imported PFX cert, we get the error below (whether we select delete old cert/signers or not).
“Failed to load due to the following error: keystore file exists, but is empty”, specifically complaining about the root-key.p12 file in the path below.
IMPORTANT: make sure this file is empty before proceeding else it could be a different issue. Backup the entire VM before proceeding.
Potential resolution to above error:
Go to the specified directory and delete the root-key.p12 file.
Press okay again and it will complain about the default-signers.p12 file, then go into that directory and delete it as well.
Press okay again and it may re-generate the default-signers.p12 file, delete it once more and try again.
If it keeps throwing the error, save to master and see if it updates anyways.
Other potential solution to the above issue (Updated 2025):
In the Websphere CA Certification Installation.docx word doc, go to Step 4 and follow instructions on generating and propagating the web server plug-ins. We did this before doing the steps above and this may have resolved the issue as well.
LBI Websphere cert error: When updating the certs in LBI websphere, when we imported and replaced, it complained about a security.xml file.
Potential solution:
Update the IIS certs and iisreset /restart after completing via CMD
Attempt to replace cert again, and just save to master even with error. Check the personal cert again to see if it saved configuration changes (or log back into websphere).
If you found this article helpful, Nogalis offers expert managed services to resolve similar Lawson related cert errors like this. Our offerings include troubleshooting technical issues, streamlining processes, and providing functional resource assistance (HR, Finance etc.). Whether it’s addressing security settings, resolving errors, or enhancing workflows, our managed services ensure your finance operations run smoothly without the need for a full-time, in-house team. Contact us to learn how we can simplify and optimize your Lawson experience.
https://www.nogalis.com/wp-content/uploads/2025/12/Websphere-Personal-Cert-Errors-and-potential-solution-Updated-2025.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2025-12-26 08:46:202025-12-18 11:57:09Websphere Personal Cert Errors and potential solution – Updated 2025