How to resolve dbreorg errors

, ,

Follow the quick steps below to learn how to resolve dbreorg errors.

 

Problem Description:

Executing lasetup with the preview option.

ERROR – failed to uncompress “patch.tar.Z” file.

 

Installation YEAREND126174.preview of YEAREND126174 terminated abnormally (start = 12/20/2023 13:27:01, stop = 12/20/2023 13:27:01).

ERROR – lasetup execution unsuccessful.

lawappinstall PREVIEW YEAREND126174.preview installation completed unsuccessfully at 12/20/2023 13:27:01.

 

Resolution:

To solve the errors, complete the following actions:

  1. First, backup current LUU directory
  2. Create a new blank folder for LUU
  3. Next, move pl program to LUU
  4. Run this command:

perl LUUsetup.pl -c E:\LUU

  1. Next, run dbreorg again
  2. Finally, run activate again and compile

 

This should resolve the dbreorg errors you have.

Running an IPA Workflow from ProcessFlowAdministrator

, ,

To manually run an IPA Workflow, first log into process administrator:

https://<landmark_server>:<web_port>/<product_line>/LpaAdmin/page/ProcessFlowAdministrator

If you get this page, just keep refreshing until the page loads

Go to Scheduling > By Process Definition

If the Process Name isn’t listed, you’ll need to add a trigger

Click the add icon

Select the Process

Work Title is required

Click the save button after selecting a workflow and entering the work title

To run the process, right-click on the Process Trigger, and select “Start”

To view the process update and log, go to Administration > Work Units > Work Units

Double-click the work unit to open the admin panel.  The “Log” tab is the most useful.  It’s best to click “Open” on the log and it will download to a text file.

Reboot Order – Lawson Application and Landmark and DB servers

, ,

Please note: This reboot sequencing requirement only applies IF the DB server is rebooted. If the DB server is not rebooted, you can reboot the other servers in any order

Follow this process to ensure the Lawson system comes up clean when a DB server is rebooted:

  1. Reboot the DB server BEFORE the other servers.
  2. Wait for the DB server to be completely up before rebooting any of the Application servers.
  3. Once DB server is up and running reboot Lawson application server and the Landmark Server

The main concern is that the DB server must be up and running for all other Lawson applications to connect to the DB. 

 

How to debug login issues in Lawson with SAML Tracer Tool

, ,

When logging into Lawson via a federated system and SAML configuration, a SAML response is received from Azure and that is all Lawson cares about when authenticating.

 

Users may see an error like this if the ID differs from the SAML configuration:

Authentication Failure

Unable to create a session. Contact your system administrator and provide this information along with the tracking id:
<long hash code ID for Infor to debug>

 

How to debug:

Once you’re in Lawson, any app issues are related to Lawson internally.

 

  1. Add SAML Tracer: Browser extension to chrome
    1. https://chromewebstore.google.com/detail/saml-tracer/mpdajninpobndbfcldcmbpnnbhibjmch?hl=en

 

  1. Open the SAML Tracer
  1. Login to Lawson and export the SAML Trace:
  2. Open the json or XML file in Notepad++ and search for <NameID Format=
  3. Search for your known user name:

That’s it! This is what is being returned from SAML response on the Azure side. You’ll have to work with the network team to coordinate on the proper ID for the user to use in Lawson.

How to find logs for Users getting error logging into Lawson

, ,

Follow the steps below to learn how to find logs for users that are getting an error when logging into Lawson.

First, look for errors on the LTR Grid (Local Technology Runtime) by going to applications/STSRuntimeService and click on the lower left hand corner number as shown below:

Next, search for code in the error message to determine why it is erroring out. (suggestion: use the Find function to detect the errors in the logs faster)

You IT should be notified of these errors in the logs and be able to resolve it quickly to allow user access the next time they log in.

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!