Archive for category: Frontpage Article

You are here: / / Frontpage Article

Websphere Personal Cert Errors and potential solution – Updated 2025

, ,

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:

  1. Go to the specified directory and delete the root-key.p12 file.
  2. Press okay again and it will complain about the default-signers.p12 file, then go into that directory and delete it as well.
  3. Press okay again and it may re-generate the default-signers.p12 file, delete it once more and try again.
  4. 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:

  1. Update the IIS certs and iisreset /restart after completing via CMD
  2. 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.

SAML for troubleshooting and diagnosis

, ,

Infor Support may ask you to Grab a SAML trace, which is a plugin for chrome. A SAML trace is used for troubleshooting and diagnosing issues related to Security Assertion Markup Language transactions. It allows you to view the complete exchange of SAML transactions and verify the accuracy and completeness of the data in the SAML exchange.

The download can be found here:

https://chromewebstore.google.com/detail/saml-tracer/mpdajninpobndbfcldcmbpnnbhibjmch?hl=en

Once you download and install it to your machine, you will need to pin it to the Chrome bar (see the screenshot below)

 

You may need to refresh your page after installing and pinning the plugin. Let it run in the background and duplicate the issue that you need to have diagnosed.

 

AP520 Error Job Already Exists

, ,

If your AP520 job goes into recovery with invalid parameters, and the examine log contains the error message “AP520 conflict, job already exists”, that means either an AP520 is already in recovery, or you will need to delete the conflicting record from APMONITOR.  First, check to see if any user has an AP520 job in recovery.  If they do, then resolve the issue and recover the job.  If there is no AP520 in recovery, you will need to delete the conflict from APMONITOR.  Either create a paint screen for the APMONITOR file, or connect to your database directly using a database utility.  Look for a duplicate AP520 job to the one that you are trying to run.  Remove that record from APMONITOR and recover your job.

 

How to Fix users not seeing bookmarks even though they have access Lawson v10

, ,

Follow the quick guide below to learn how to fix users not seeing bookmarks even though they have access Lawson v10.

 

Problem:

When logged in to the Lawson v10 dashboard, you notice that the user is missing a Manager Self-Service bookmark (see screenshot):

 

Resolution:

As an admin, navigate to “Manage Roles” on your Lawson Homepage:

 

Select the portal role assigned to user (if default.xml, then create a new one):

 

Next, enable “Allow use of menus and user defined bookmarks”:

 

This should now show the additional bookmarks the user has access to:

They may have to log out then log back in to see the changes made. That’s it!

How to debug Lawson Business Intelligence (LBI) Report prompting Database Login

, ,

Learn how to debug Lawson Business Intelligence (LBI) Report prompting Database Login.

 

Here is an example issue when opening a report via LBI dashboard:

It prompts to a login screen and no credentials work:

To solve this, first validate the datasource of the report and validate its correct (it may resolve after you click save and test the report again)

If not, see if you can view the report with Data Refresh

If it generates data, you can grab this URL:

Edit your report from the dashboard, in this example we edit the “LP Exception Report”:

You can copy this URL:

You can either replace it complete with the top URL shown below with the HTTPS://yourorg.domain.com…. Etc.

OR

You can modify the link with just the tail end of it as shown below:

Then copy and paste this URL back in and save:

That’s it! Test it and the database login prompt should no longer show if you followed everything correctly.

If this is too complex for you and you need Lawson specialists to help manage your Lawson ERP system, Nogalis offers a team of consultants to help manage this for you under one MSP contract. Feel free to reach out to us to get a free consultation today.

IPA Process Notifications

, ,

There may be some cases where you want to notify your IT or other staff that an Infor Process Automation (IPA) flow has run successfully, or has run with errors overall, in addition to internal notifications for specific events.  Follow these steps to set up notifications on an IPA process.

  1. First, log into Process Administrator.
  2. Next, navigate to Configuration > Process Definitions > User Defined Process
  3. Open your Process.
  4. On the “Notify by Email” option, select your preferred option.
  5. Once you select an email notification type, the email notification tab will open up.
  6. You can use global parameters in the email details.

You are now set up to receive notifications!

Active or Disabled Users Reporting

, ,

What is the best way for me to get a list of active or disabled users within the Lawson environment?

 

Resolution:

To see all users who are “Active” or “Disabled”, run the “RM User Attribute report” within the LSA tool. Follow these steps below.

  1. Reports
  2. Report Maintenance
  3. Click New Report
  4. Choose the “RM User Attribute Report”
  5. Add a report a name
  6. OPTIONS:
    ACTIVE USER LISTING: Create a query for the Filter Criteria  where  IsDisabled isNot YES
    or
    DISABLED USER LISTING: Create a query with the filter criteria set to  IsDisabled is YES
  7. Hit next
  8. Choose the attributes about the user you want to see, such as First Name, Last name, etc… By default isDisabled is already checked and ID will automatically show up on the report as well. Click Ok to save the report.
  9. Run the report by highlighting the report and clicking the “Run Report” button at the top of the screen, choose your report format, html, pdf or csv.
  10. Use the Refresh button at the top of the screen and wait for the status of the report to show as “completed”. Once it’s complete, make sure the report name is highlighted then choose View Report. Put a check next to the report format and click View File.

 

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.