Flexform Broke after adding Memory to Lawson Server
After updating the memory on the application server the flexform application started having issues with printing. The Memory increase was reverted and decreased it to what it was(16g).
At that point, admin was not able to get the Lawson service to run. The lawson.insight Environment “lawprod” service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
Resolved by rebooting all three servers (DB, LMK, APP).
To add memory to the application server and not impact Flexform, you must work in tandem with Flexform so that they can get a new license implementation based on the new memory added.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
