Lawson Patch Error – failed to uncompress patch.tar.Z file

, ,

Resolution 1:

One reason you could be receiving this error is because there is an additional patch.tar file from a previous or concurrent CTP install.

 

After running the tar command you should only have 3 files for this CTP in the <versionfiledir> that you uncompressed the CTP to.

Examine the extracted files to make sure you received the following three files:

– x.x.x_patch_CTPnumber.readme.html

– Versions

– patch.tar.Z

 

Remove any previous CTP files from this directory, especially any patch.tar files, and run the lawappinstall again.

 

Resolution 2:

If you are encountering this error on a Windows server it is possible that you have spaces in the folder names of the path to the versions dir.  You would receive the failed to uncompress message if this is true.

 

Use a “_” for the space, or use folders that do not contain a space in the name and run the lawappinstall again.

 

Resolution 3:

Make sure the user you are applying the patch with has the proper Windows file permissions to install the patch. This should be the entire LSF application directory.

ujobload fails in lawappinstall activate

, ,

Problem:           

Patch being installed if failing when running lawappinstall activate. It fails when running ujobload.

10/31/2023 5:44:25 Executing ujobdump.

10/31/2023 5:44:25 ujobdump execution successful.

10/31/2023 5:44:25 Executing ujobload.

10/31/2023 5:44:26 ERROR – ujobload failed.

ujobload via lawappinstall activate *** No jobs found to load When run manually, it fails with Segmentation Fault(coredump:

 

Resolution:     

lawappinstall update will stage tokens potentially needing a ujobdump/ujobload in LAWDIR/productline/backup/ACTIVATEstage/JOBconversion.

If conditions are correct, lawappinstall activate will run ujobdump and ujobload, then clean up the staged area.

  1. ujobdump -d LAWDIR/productline/backup/ACTIVATEstage/JOBconversion productline $LAWDIR/productline/backup/ACTIVATEstage/JOBconversion.dmp -t <list of Tokens>

In the above <list of Tokens> would be a space-separated list of the tokens located in $LAWDIR/productline/backup/ACTIVATEstage/JOBconversion/??src directories.

  1. ujobload -ou productline LAWDIR/productline/backup/ACTIVATEstage/JOBconversion.dmp
  2. remove dump file, LAWDIR/productline/backup/ACTIVATEstage/JOBconversion.dmp
  3. remove stage dir, LAWDIR/productline/backup/ACTIVATEstage/JOBconversion

Run steps a through d manually, then rerun lawappinstall activate.   If the ujobload fails in step b with a Segmentation Fault(coredump) or other error, make sure the user running ujobload has write access to these files and their directories.

LAWDIR/UJobLoadDir/productline/Tokens

LAWDIR/productline/UJobLoadDir/LDLog

Make corrections if necessary, run steps b through d above, and rerun lawappinstall activate.

CTP Preview fails in lasetup

, ,

Problem:           

Sometimes when running a CTP patch install preview GENDIR/bin/lawappinstall preview <productline> , the program is executing lasetup with the preview option, and is displaying the following error:

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:     

Follow these simple steps to resolve the issue above.

  1. Backup the current LUU directory
  2. Create a new blank folder for LUU
  3. Update the pl program to LUU
  4. Run the following command:

perl LUUsetup.pl -c E:\LUU

  1. Finally, run the CTP preview again. There should be no more errors.

What do the Lawson Base Mingle Roles Control?

, ,

What do the Lawson Base Mingle Roles Control?

  • “Infor-SuiteUser” is the end-user role. This is the default role assigned to all the users. Users with this role have access to the portal only. The portal is one of the components of the Infor Ming.le application. The portal consists of a top level header, an app switcher panel, search, the user menu, share, bookmarks, and a right panel (context/utility applications panel). The users with this role only do not have access to the social space or ION-related features.

 

  • The “MingleEnterprise” role provides access to the social space component of the Infor Ming.le application. The social space component consists of activity feeds, connections, and groups.

 

Users who have this role can do these actions:

    • View the activity feed page
    • Post messages to colleagues and groups
    • Create new groups
    • Connect to users and groups

 

  • “MingleAdministrator” is the role assigned to users to have access to administration pages in Infor Ming.le.

 

By design, the “MingleAdministrator” role is added to all applications in the tenant. The user with this role can view all application icons on the App Switcher panel. The user’s ability to open the application and access functionality, however, is controlled by the application security.

 

Users who have this role can see the Admin Settings menu item under the profile menu.

 

Users who have this role can do these actions:

    • Manage applications
    • Manage context/utility applications
    • Manage drillbacks
    • Manage general settings
    • The user with the “MingleAdministrator” role also needs the “MingleEnterprise” role in order to administer some of the users’ related features in social space.

These users can also do these actions:

    • Manage users’ feeds and groups’ feeds
    • Delete any Infor Ming.le group
    • Deactivate the users and groups and also reactivate them

 

  • “MingleIONEnabled” is a role that allows users to access ION-related features within Infor Ming.le.

ION-related components consist of alerts, tasks, ION notifications, and workflows.

 

Users who have this role can do these actions:

    • View alerts and perform all the actions in the alerts
    • View tasks and ION notifications and perform all the actions in the tasks and ION notifications
    • Alerts and Tasks options are displayed in the user menu for the users who have this role.

Update the ADFS Token-Signing Certificate

, ,

When the ADFS Token-Signing certificate is updated on the ADFS server, it will have to be imported to Lawson and Infor OS.  The networking team should let the Lawson team know when the certificate is being updated in ADFS.

Someone with admin rights on the ADFS instance will need to export the certificate and provide you with the “.cer” file before these tasks can be completed.

Update the Certificate in Lawson

Log onto the Lawson Server

Start a ssoconfig -c session

Go to “Manage WS Federation Settings” > “Manage Certificates”

Select “Delete WS Federation Certificate”

Select “Create certificate for “WS Federation”

Select “Delete IdP certificate”

Enter the service name of your ADFS service (if you are unsure, export all the services and look for the one that redirects to  your ADFS server).

Select “Import IdP Certificate”

Enter the service name of your ADFS service

Provide the full path where you have the token-signing certificate saved

Reboot the server

Update the Certificate in Infor OS

Log into the Infor OS server as the LAWSON user

Log into the InforOSManager (should be an icon on the desktop)

Go to Identity providers on the left side

Double-click on your IdP

Select “From URL” to import the new certificate and metadata

Provide the URL: https://<your adfs server>/federationmetadata/2007-06/federationmetadata.xml

Click “Load”

Make sure the certificates load (there may only be one, but there should be at least one)

Reboot the server

 

 

Suppressing Receiving Delivery and Putaway Delivery Tickets

, ,

To suppress Receiving Delivery and Putaway (PO134) delivery tickets when MSCM Delivery Documents are all that is needed is to disable the Back-Office PO Receiving (PO30) Receiving Delivery and Putaway (PO134) delivery ticket by removing the printer from PO Receiving (PO30) or create a dummy printer to stop the back-office delivery ticket from printing.

Removing the printer from PO Receiving (PO30) only works if the user does not have a default printer assigned to them. After being removed, the default printer will simply populate back in the field upon clicking change.

Additionally, an enhancement to PO Company Setup (PO01) was added which provides a flag called “Delivery and Putaway Ticket Print” which allows disabling the delivery ticket printing at the company level.

How to resolve Lawson error – Cannot run AP520, entire Company run is in progress

, ,

In Lawson you may run into the following error when a user is trying to change or run a job:

“Cannot run AP520, entire Company run is in progress”

The error can be found at the bottom of your screen (see below screenshot in red box)

 

To resolve this, open and then log in to Lawson Interface Desktop (LID):

Type the following: lapm <enter_your_productline> qmon and press enter

 

Next. find the AP record and delete it. The error should be fixed and disappear. See if the user can now change/run the job. Refer to the screenshots below for a visual guide.

 

How do I request a new Lawson software license key?

, ,

Have you ever wondered how to request a new Lawson software license key?

You will need to request a new software license key from your Infor Representative. Here are the steps to do so:

  1. Log into Infor Concierge
  2. In the Application Switcher select the Infor Support Portal application.
  3. At the top click on the Resources menu
  4. Select Request a Software Key > Key Request
  5. Click the Browse button to search for and locate your company name
  6. Fill/Select required fields
  7. Select Next button
  8. Select the product you need a license key for. If what you need is not on the list, then note it in the ‘Notes’ section at the bottom of the page.
  9. Click the Submit button.

 

That’s all you need to do!