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.

LBI does not use a web server, so replacing those certificates differs slightly from Lawson & Landmark.  Replacing the LBI certificates is done exclusively in WebSphere console manager.

First make sure that you have a pfx file stored locally on the server, and that you have the private key for that file.  Open the console manager and navigate to Security > SSL certificate and key management > Key stores and certificates.

Select the CellDefaultKeyStore

Select Personal Certificates

Import the new certificate first.

Set the path to where you have saved the file locally, and enter the password.  Click “Get Key File Aliases” to get the certificate information.  Enter a meaningful alias for the certificate.

Select the old certificate and click “Replace…”.

Select the new certificate as the replacement.  Check the boxes to Delete the old certificate and signers.

Validate that the Trust Store certs were updated by going into CellDefaultTrustStore > Signer certificates.  You can add the intermediate and root certificates (base64 cer files) if they aren’t there.

Bounce the application server, and your certificates will be updated!

Problem: Submitted requisitions aren’t triggering on IPA server via reqapproval process and are not showing in Rich Client.

1. Go to LSF application server, start LID and type: pfserv ping all
   
   Make sure Event Manager is running.
2. When Event Manager is NOT running:
   Let’s restart it but make sure we can see the java process with –classpath in their command line close.

Now in LID on LSF server, run these stop commands IN THIS ORDER:

Verify the java.exe –classpath processes closed, else manually end them.

Now start them up IN THIS ORDER:

Now run a pfserv ping all to see if Event Manager is running.

Go to Rich Client and check Live Workunits to verify that hung processes are being picked up:

This issue can often be prevented with regular Lawson maintenance and monitoring via monthly health checks. Organizations with a single Lawson professional are sometimes spread thin and overwhelmed.

To combat this, 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.

You may have come across this message on Lawson MHC – An error occurred while printing. This problem happens when printing Lawson forms or checks from MHC Image Express, and users may receive the error on their screens while printing.

In MHC, users often print 1099 forms, checks, etc. and may need to re-print a form.

When re-printing they sometimes run into this error and are unable to resolve on their own:

1. First, you’ll need an MHC or Lawson trained individual who understands the application.
2. Locate the output files via the print routines in the same account the user previously printed from.
3. Below is an example of where our print routines point to. Delete or move these files to a backup directory to resolve this error:

MHC Image Express integrates with Lawson and it’s a lot to ask of an individual Lawson employee to maintain when they may be tied up with other daily issues.

To combat this, organizations often bring on Lawson consultants who offer managed service and typically have expertise in maintaining and updating MHC related products (especially around year-end).

Good luck!