Lawson MHC – An Error occurred while printing

Scenario: You have Lawson invoices or orders that get moved over to MHC.

When you print them from MHC, the print queue you have setup produces PDF.


An error occurred while printing


Make sure you go into the folder where the PDFs are produced and delete any old or existing ones.


This all depends on how you’ve setup your print queues. Good luck!

Lawson ISS – Using an ISS Sync to remove roles assigned to users

In Lawson ISS, you may come across one or both of the two scenarios below:

  1. I removed a role from a number of users in Lawson System Foundation (LSF) and want to use an Infor Security Services (ISS) sync to remove these same roles from Landmark (LMK).


  1. I removed a role from a number of users in Landmark (LMK) and want to use an Infor Security Services (ISS) sync to remove these same roles from Lawson System Foundation (LSF).


There is a resolution for both of these scenarios:

A full ISS sync does not have the ability to remove roles from users. However, you can run a list-based sync via an ssoconfig command to remove the roles in the other system.


There is a flag that can be included in the list-based sync file that allows for roles to be overwritten in the system that is being updated called the mergeActorRoles flag. When this flag is not included in the xml file to be used, or is set to true, the roles from the source system (the one you are NOT updating) that are not found in the other system will be appended to the roles currently assigned. When this flag is set to false, mergeActorRoles=false, the roles assigned in the system that is being updated will be overwritten to match those in the source system, hence removing roles if necessary.


A list-based file template is delivered with each upgrade to ISS, you will use this file as a base for your work. The location of the file is:



Create a copy of the file and edit the copy, ensure the following are set:


defAction is set to update the system where the roles have NOT already been removed options:  update_remote or update_local

mergeActorRoles is set to false

IMPORTANT: The local and remote sections shown in the example below MUST be included since the users already exist in bot LSF and Landmark. These areas would contain each user to be updated.

Example of a completed list-based sync file that will update roles in LMK for existing users test1 and test2 to match roles in LSF:

Once you have the file the way you need it, you need to run the ssoconfig command for the list based sync.

The syntax for that is as follows and there is no ssoconfig password required for this process/command syntax:


ssoconfig -S sync_file_with_fullDirectoryPath


Example command for Windows customers:  ssoconfig -S D:\LSFPROD\gen\system\provisioning\metadata\FileNameOfBackgroundSyncTemplate.xml

Example command for Unix or IBM i customers: ssoconfig -S /LSFPROD/gen/system/provisioning/metadata/FileNameOfBackgroundSyncTemplate.xml


NOTE: In the above examples, if you placed the xml file for this process in another directory, simply replace the full path to the location of your xml file.



Lawson Security – loadResource returned identity already exists

When we try to update some user records on the Infor Security Services (ISS) webpage, it gives an error stating: “loadResource(): returned identity [User:] already exists”

This error is due to missing extended attributes in LDAP. The extended attributes are what allow ISS to know that the user exists in LMK and are created when a user is added via ISS or the user is included in a sync.

To create the extended attributes for the user, you have two options (we recommend step 1):

  1. Run a list-based sync for the user who you are getting the error on.
  2. Run a full sync via the ISS webpage.


See LSSCG_11.0.0.0_UWA.pdf via Infor Concierge for example on list-based sync.


This is typically done by a Lawson technical resource. Organizations often hire 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. Nogalis does offer this as a service so feel free to reach out to us via our contact page.

Weekly Patch Notification: December 31, 2022

How to setup Lawson Security to give user different security access in 2 different productlines in same environment at the same time

You might be wondering if it is possible in LSF to a give a person access to 2 different data areas (productlines) with 2 different roles at the same time.


So let’s say if user1 is in data area 1 and has the security access associated with the role that has access to data area (1) and then again user1 also is in data area 2 they have the security access associated with the role that has access data area (2).

More discreet way of putting it:

User1 >> DataArea1 >> ReadOnlyRole access in DataArea1.

User1 >> DataArea2 >> ChangeAccessRole access in DataArea2.


The best way to set this up is to separate the two DataSources so they each have their own Productline and their own separate security profiles. That’s it!


User1 >> DataArea1 >> ReadOnlyRole is in SecurityProfile1 which is set to DataArea1.

User1 >> DataArea2 >> ChangeAccessRole is in SecurityProfile2 which is set to DataArea 2.


Good luck!

Weekly Patch Notification: December 24, 2022

Weekly Patch Notification: December 17, 2022

Lawson CSV Read Error – Bad Field Data Format for Fld: 5 on Record Nbr 1

Common error with conversion upload file: “CSV Read Error: Bad Field Data Format for Fld: 5 on Record Nbr 1”.


This could happen for example when running say PR530 in Lawson.


There are a couple ways to resolve this issue:


Resolution #1:

Fix the headers of the file by removing spaces or bad characters that the program doesn’t like in the file you’re using for upload.

Also keep in mind that if there are problems with the header records, you will be able to see the exact errors in the examine log after you run the job (Job Scheduler > Completed Queue > click on completed job and then select ACTIONS from the menu and highlight Examine Log). This gives more detail as to the exact CSV Header Read errors.


Resolution #2:

For the job that’s throwing this error, in LID, go to jobdef and enter the username and jobname

Move down to the form field >> F6 >> C. CSV File Attributes (PR530 is the example below):

Turn off File Header and Xlt Header Names and save.

When you run the job again, it will ignore the headers and process the data so make sure the columns are correct. This has to be done per user that runs the job.


Good luck!

Weekly Patch Notification: December 10, 2022

Weekly Patch Notification: December 3, 2022