How to resolve Lawson Error Unable to remove object delete failed

, ,

Follow these simple steps to know how to resolve the Lawson Error, “Unable to remove object delete failed”

 

You may come across the following: Unable to remove object (RQRequester), delete failed. Original Exception: Role RQRequester is in use on a resource or group and cannot be deleted. (Note: there are 3 screenshots below)

 

To resolve, you need to remove role from the user and try again. follow these visual guides for the role removal process: (Note: there are 2 screenshots below)

That should be it!

Mass remove candidates or suppliers and their identities from LSF

, ,

Candidates and suppliers from Landmark applications should not be synced to LSF. Services which allow users to register externally are services that should NOT be synced. If they were synced to LSF, follow the steps below to remove user and identity records from LSF.

Configure sync service lists to exclude candidates from sync – This process should be used if possible
Use Configure Services for Synchronization menu in ISS

Manual Sync service list configuration – This process may be used if not all services are shown in ISS
Export list of all services from LMK
 secadm -p <secadmpassword> service list
 The list outputs to the screen –copy the list from the screen into a text document
Determine which services from each system you DO want synced

Configure sync service lists for LSF and LMK in the LSF by adding the following lines to LAWDIR/system/lsservice.properties file:

 fed.LSFSERVERNAME.DOMAIN.COM;40000;40001;LSF. syncServiceList=YourListofLSFServicesToSync,SeparatedByCommas,NoSpaces fed.LMKSERVERNAME.DOMAIN.COM;10888;11888;LANDMARK. syncServiceList=YourListofLMKServicesToSync,SeparatedByCommas,NoSpaces

 Save changes and close lsservice.properties
Restart LSF and WAS

Configure tuning for sync*

  1. Add the following line to the LAWDIR/system/lsservice.properties

file: Nthread=5

This value can be any number between 2 and 10. You can tweak the Nthread parameter until you find the optimized setting for your system. Do not go above 10 unless directed by Infor.

  1. Adjust lase GRID node max heap to at least 3096

From the Grid Management main page go to Configuration Manager->Applications->Application->Landmark and the select the environment.
Select “Edit Properties.”
Under Grid Defined Properties -> Node Memory, select “Max Heap.”
Adjust the lase node memory to 3096 and then click Save
It may be set higher if number of users/identities indicates
-Restart the node for this environment or restart Landmark.

 

Change the Passwords in install.cfg

, ,

The passwords in install.cfg are encrypted in later versions of lawson.  If these passwords change, it would be ideal to also change them in install.cfg so the next update doesn’t run into any issue. To do this, follow the instructions below:

First, Open a command line utility with Lawosn env variables set.

Then type in the command java -cp %GENDIR%/java/thirdParty/installer.jar com.lawson.delivery.secure.PasswordAdministrator -s %LAWDIR%/system/install.cfg

Enter the Lawson configuration password

Next, View or edit passwords.  You can show them in clear text by clicking the “Yes” radio button.

Click finish when done

Restart Lawson services, or reboot the server. This should make the necessary changes and prevent any issues.

How to include Report ID in LBI Maintain Reports

, ,

Follow these simple steps to learn how to include Report ID in LBI Maintain Reports

  1. First, go into Tools when logged in as an admin and select “Reporting Services My Reports”.
  2. Under the “All” section in the Report Lists on the left side dash, click “Edit List” on the top right of the screen.

  3. Next, under “List Options” select “Columns”.
  4. Then select “Report Id” and click the right arrow in the middle of the screen:
  5. Click “Save and Exit” and then go to “Maintain Reports” in the Reporting Services Administration Report Management Menu.
  6. Now you’ll see all the Report ID’s on the right hand column:

 

That’s all there is to it!

GL256 No report in Print Manager

, ,

Problem:
If a GL256 was run but did not create a report in the Print Manager, but, there is a csv file, follow these simple and quick steps to change the csv output to a prt file.

 

Resolution:
First, you will need to create a GL55.1 for this report.

Navigate to the Basic Tab, then change the CSV Output parameter from Y (Yes) to N (No).

Next, Re-run the GL256 and it will produce a regular report in the Print Manager.

This should create a report in print manager with the proper output format.

That’s all there is to it!

Process Server Administrator – How to access Channel Administrator

, ,

File channels in Lawson Infor Process Automation (IPA) are very useful for picking up flat files and processing them.

 

In Infor’s older Rich Client tool, this can be easily found under the Start button drop down.

However, based on user permissions, this might not appear properly so I will tell you two ways to access the Channel Administrator.

 

First should be the obvious way which is Administrator >> Channel Administrator

 

However, based on your _ST roles, this might’ve not been granted properly. So, the second way to access it is in the top right search box. You can search Channel Administrator and access it there.

Empty AP160ACHTAPE File

, ,

Description:
When running the AP160 the job did not create an AP160ACHTAPE to be sent to the bank, this file is empty.

Resolution:
AP160 runs the Lawson utility cnvtape to read the AP160ACHTAPE_SEQ file and to write out the AP160ACHTAPE file. To resolve this issue, you need to perform the following:

A. When using Lawson Security:

  1. Open Lawson Security Administrator
  2. Double Click on Profile Id “ENV”
  3. Double Click Security Class “DBAccess”
  4. Click “Add Rule” Button
  5. Select Securable Types “Executables”
  6. Expand Delivery Tokens
  7. Check box by cnvexp
  8. Click “Grant All Access” radio button
  9. Click Apply Button.
  10. Click on Profiles
  11. Double Click on Profile Id “ENV”
  12. Double Click Security Class “TranslTools”
  13. Double click on Rule Object “TRANSLATE”
  14. Right click Translation Tools and choose Select Next Level
  15. If cnvtape doesn’t exist under TRANSLATE then you must add it through Tokendef – Environment Form IDs – Category: TRANSLATE – Title: Convert Tape File
  16. Make sure radio button next to Grant All Access is checked
  17. Click Apply Button
  18. Double Click on Class Assignment>select the Role you want to assign the TranslTools Security Class to>Click Assign Security Classes Button>highlight TranslTools>click “>” Button>Click Close Button>Make sure that Role is assigned to user.

Once you have change users access, have the user run AP160 for Rerun Options – Recreate Tape=Y and the serial number of your tape to create the AP160ACHTAPE file which will be sent to the bank.

File Not Found error in LID when adding a job

, ,

After a fresh install of Lawson, you may receive a “file not found” error in LID when adding a batch job.  Or, inquiring on certain forms might time out.  The batch job itself may show an error message alluding to the LUU utilities (such as invalid fstab option).  The issue is potentially an incorrect LAW_COBRTS_PATH.

To resolve, open a command line utility with the Lawson environment variables set.  Type command “laconfig”.  The configuration window pops open.

Select your environment.

On the environment tab, check the LAW_COBRTS_PATH.  If it is incorrect, fix it.

 

Reboot the server, or restart the services, and try your batch job again.

 

How to find users that report directly under a manager in XM

, ,

Follow the steps below to learn how to find users that report directly under a manager in XM

 

First, in Mingle, go to Infor XM

 

Next, select Admin >> Users

 

Then locate the manager you want to search for users under:

 

Search fore your manager by name, then pick a result:

Now that we have the manager we want, click Find at the bottom and on the right hand side you’ll see all the users that are under this manager.

And that’s all there is to it! Just repeat the steps to view all users under different managers.

APIX Achieves SOC 2 Type 2 Compliance: Strengthening Trust and Security for Our Customers

, ,

At Nogalis, security and trust have always been at the heart of everything we do. Today, we’re proud to announce that our APIX ERP Archive Solution is officially SOC 2 Type 2 compliant — a major milestone that reinforces our commitment to safeguarding your data.

After earning SOC 2 Type 1 compliance earlier this year — confirming the strength of our security design — we set our sights on the next milestone: SOC 2 Type 2. This certification demonstrates that our controls don’t just look strong on paper; they perform reliably in practice, ensuring your data remains protected with the highest standards of security and trust.

Developed by the AICPA, the SOC 2 framework is an independent standard for managing customer data based on five key trust principles: security, availability, processing integrity, confidentiality, and privacy. Meeting these standards confirms that our internal controls and processes align with the most rigorous data protection requirements.

Our SOC 2 Type 2 assessment was conducted by independent auditing firm Sensiba LLP, who worked closely with our team throughout the process. Their expertise, professionalism, and partnership were instrumental in helping us reach this milestone.

What this means for you:

  • Your archived ERP data is protected under industry-leading security practices.
  • Our systems are continuously monitored and improved for data integrity and availability.
  • We remain transparent and accountable in every step of our data handling.

We’re proud to share this achievement with our customers and partners, and we’ll continue to invest in security and compliance as part of our promise to deliver the safest, most reliable ERP archiving experience possible.

Thank you for trusting Nogalis and the APIX ERP Archive Solution with your data.

— The Nogalis Team