Weekly Patch Notification: September 24, 2022

Weekly Patch Notification: September 17, 2022

Weekly Patch Notification: September 10, 2022

Weekly Patch Notification: September 3, 2022

Weekly Patch Notification: August 27, 2022

Weekly Patch Notification: August 20, 2022

Run a network trace on a Lawson issue WITHOUT fiddler

Lawson issue not showing in the logs? This is how you would run a network trace WITHOUT fiddler.


Using Google Chrome.

  1. Open Chrome, open a new tab and press CTRL-SHIFT-I.
  2. On the Network tab, ensure the circle in top-left corner is red. CTRL-E toggles tracing on/off.
  3. Duplicate the issue.
  4. Right-click on any of the http sessions, and select “Save as HAR with content”.
  5. Save the file to your desktop, and upload the file to the support incident.
  6. Send file to your Lawson support consultant.

Chrome Example screenshot below:

Using Microsoft Edge Chromium

  1. Open Edge and Press “F12” to open IE Developer Tools.
  2. On the Network tab, ensure there is a red circle in the top-left corner. If you see the green “play” button, click it to start recording.
  3. Duplicate the Issue.
  4. Click on the “Export HAR” icon to save traffic to a .har file.
  5. Send file to your Lawson support consultant.


Edge Example Screenshot:

This is sometimes daunting for users to perform on their own so a trained Lawson professional is ideal to assist via a remote meeting like Zoom or Teams.

Organizations often have trouble staffing Lawson professionals (or they’re spread thin) and alternatively go with teams of Lawson consultants who offer managed services at a fixed rate. This can help larger organizations who have daily user issues and need a team of trained Lawson professionals to assist.

Compiling an entire product line in Lawson Interface Desktop and speeding up the process

Often when you install a patch into Lawson, you want to ensure all forms run the next day without issues. This is especially important with larger patches that affect dozens of Lawson forms and or when a new db dictionary is created.


This is easily done through the cobcmp command.


When you run the cobcmp command, it will run through a list of all Lawson forms.


Once this is done, you can check its process by using this command: qstatus | head -5

This command will show you the amount of forms left to compile.


If you want to speed up this process, you can increase the amount of compile jobs running.

In LID this is done with this command: qcontrol -jlocal,4


This increases your job count to 4 (default is 2)

If your server only has 2 cores, it is recommended to keep it at the default 2.


I’d only increase the compile job count to one less than the maximum amount of cores your server has so you don’t overload other processes.


Once done compiling, it is recommended to change the job count back to 2, or: qcontrol -jlocal,2


Infor is moving away from their traditional CTP method of apply patches (as of 2022) and moving towards the new DSP standard. It is still recommended to recompile programs when they act up or after patches.

We recommend organizations look into hiring a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site.

Weekly Patch Notification: August 13, 2022

Lawson Mingle Sign-On Error

Problem: A user in your organization is getting this error when selecting a Lawson chiclet through Okta or a Mingle URL but their Lawson and Mingle security is setup correctly along with their identity information. See below for the fix.


Example of the error below:

  1. Verify the user is setup correctly in Lawson with the correct identities and Mingle security roles required.
  2. Make sure your organizations Windows team filled in the correct Active Directory email address for the user.
  3. Have the user clear their browser cache and attempt to access the Mingle via URL or Lawson chiclet app (if using Okta etc.)

That’s it! This is a common issue when ticketing system workflows (like Service Now) are processed out of order and the user’s Lawson account gets created before the Windows team fully sets up their AD account.