Update Infor OS Certificate

, ,

Follow these steps to update the server certificate in Infor OS.

  1. Log into the Infor OS server as an admin
  2. Mount the InforOS iso installer file. You’ll need the iso for the version that you are currently on.  If you don’t have it already, download it from the Infor Concierge archives.
  3. Open command line as admin
  4. Navigate to the drive that was created when you mounted the ios
  5. Run command exe -v”CERTIFICATEUPDATE=true”

  6. Wait for installer to load
  7. Select “Modify”
  8. Enter the location of the new certificate, and the password. This should be a pfx file with a password.
  9. Click install, and wait for a successful completion.

 

Troubleshooting IPA Schedules

, ,

Sometimes you may find that your scheduled flows have not run, seemingly with no explanation.  When this happens, there is a good possibility that there was an error in the scheduler that needs to be resolved.  To check the scheduler, log into Rich Client or your IPA Web Administrator as the user who owns the schedule.  Search for “My Scheduled Actions”.

 

Find the schedule of the flow that didn’t run, and verify if there is an error.  Double-click on the failed instance at the bottom of the screen to get more detail on the error.

Once you have resolved the issue that caused the error, right-click on the instance and select “Requeue”.  Note that this will cause your schedule to run immediately.

After the schedule has run successfully, there will not be any more items in the “Action Instances” tab.

 

Accessing Rich Client directly with the local Lawson user

, ,

If you’re an On-Premise Lawson client and your Windows user profiles were wiped and you you’re your shortcuts to Rich Client. You can still access Rich Client directly with the local Lawson user account.

 

First, find out the local lawson account in services on the Landmark server:

 

Use Windows Remote Desktop Protocol (RDP) to login into the Landmark server with the .\lawson local account which should show the domain as the Virtual or Physical machine name:

 

 

Find and run the the Command Window for Lawson Landmark as Administrator.

Type canvas64 gen and press enter

 

This brings up Rich Client with full access

 

PO140 – Program Information

, ,

Purchase order PO140 – program information has some useful functions. For instance, you can run Receiving Release and Delivery (PO140) to release receivers and are able to print a list of all released receivers as well as a list of unreleased receivers with errors. PO140 is also able to create and print Delivery and Putaway tickets. Additionally, it can also update the ARRIVAL file for Mobile Supply Chain Management) tracking. Once the delivery ticket is printed then it will update the delivered quantity in the POLINESRC table. This is what Mobile Supply Chain Management, or MSCM, uses to update the Quantity On Order.

How to restrict or grant access to a function code in Lawson Security

, ,

For this example, we will be granting access on a restricted function code on GL45.1. The function code is the Q – Quick Post.

 

On the Lawson form to get more information, select the function code field and press CTRL + SHIFT + O

 

We care about LINE-FC and parent column DT0.

  1. In LSA create your security class and click add rule.
  2. Grant all access to GL45 system code:
  3. Now expand GL45.1 and search for column DT0, then expand it.
  4. Find LINE-FC and select it
  5. On the right, select the Unconditional Access for Action and click in the blank white box, you’ll see a list of codes you can grant access to. For this example select Q for Quick post.
  6. Now click Apply and you’re done.

You can also restrict this by creating a Conditional Rule Access.

Good luck!

ISS: IDENTITY record failures in the sync

, ,

Problem:

After running an Infor Security Services (ISS) sync, I have found the errors related to the failed IDENTITY records.

 

Resolution:

Determine which system, Lawson System Foundation (LSF) or Landmark (LMK), the identity record failed in by reviewing the following:

security_provisioning.log(s). All transactions completed in ISS related to user maintenance, federation, and synchronization, are logged in the LAWDIR/system/security_provisioning.log(s). Please note there may be several security_provisioning.logs with different naming conventions that contain the information that rolled out of the main security_provisioning.log and you may need to review all the updated logs to find the information you need.

Open the most recent provisioning log and go to the bottom of the log. If nothing has been done in ISS since the sync completed you should see a message similar to the one below followed by a list of records that failed:

Thu Apr 26 16:56:01.282 CDT 2023 – default-457261151: Sync Analysis for object type IDENTITY completed with status=true

Thu Apr 26 16:56:01.282 CDT 2023 – default-457261151: Sync Analysis successfully completed for object type IDENTITY

Thu Apr 26 16:58:52.073 CDT 2023 – 1360326122: Sync Execution successfully completed for Task ID[4,963] with failed transactions for Sync Records:

The list of records that failed is limited to one section of the sync. You will see a list of either roles, actors, services, domains, endpoints endpoint groups or identities, depending on which section of the sync had failed records. This is because once the sync completes the analysis or execution of the section with the failed records the sync process will not continue. You must address the failed records to continue the sync.

Alternately you can search the log for the word “completed” to find the most recent section of the sync process that completed. There will be a completed message for each section of the sync.

To find the exceptions for the failed records you will need to search within the log(s) each failed record. For each failed record you will search for the value from the list without the semicolon at the end of the line:

For failed record ACTOR=user1; you would search for “ACTOR=user1”

After finding the exception in the log, scroll up in the log until you see a message such as this:

Wed Dec  4 12:19:45.528 EDT 2023 – default-137596214: Getting resource from INFORBCLM01.INFORBC.COM;9906;9907;LANDMARK

or

Wed Dec  4 12:13:24.761 EDT 2023 – default-1973664225: Getting resource from INFORBCLS01.INFORBC.COM;6626;6627;LSS

or

Wed Dec  4 12:19:43.440 EDT 2023 – default-1973561960: 1973561960 Processing record #4,996 of LSF

or

Wed Dec  4 12:19:43.440 EDT 2023 – default-1973561960: 1973561960 Processing record #4,986 of LANDMARK

Messages that reference LSS or LSF indicate the issue is in LSF and the record should be reviewed in that system. Messages that reference LANDMARK indicate the issue is in LMK and the record should be reviewed in that system.

 

Lawson Can’t Find lacobrts

, ,

There can be many symptoms when Lawson can’t find lacobrts.  For example, Batch jobs will run and die without failing. When this happens Ladb.log will show the error below (insufficient netexpress licenses).  These all can be red herrings that point to an issue with the LAW_COBRTS_PATH setting in laconfig.  This is either due to the permissions on the directory can be incorrect, or the path itself can be incorrect.

To check the path, open a command line window and set the environment variables.  Then type command “laconfig”.  Choose your environemtn.  Make sure LAW_COBRTS_PATH points to the Micro Focus install directory, subdirectory bin64.