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!

How to clear up Lawson Interface Desktop (LID) processes and free up licenses error

, ,

Follow this simple guide below to learn how to free up Lawson Interface Desktop (LID) error about max license usage.

When too many users are using LID (or don’t exit out properly), you can max out license usage.

To resolve this error, on the LSF App server (or server users are connecting to via LID), open task manager and end any LAPM.exe tasks as shown below (the users login name should show below so if this request is for a specific user, you can surgically end these lapm.exe processes):

Once those lapm.exe processes are killed, tell the user to try and login again and it should allow them to do so.

 

GL190 message: “Another job currently processing for company (0)”

, ,

The Journal Posting (GL190) program output states the message “Another job currently processing for company (0).”

This error indicates that another updating job is currently processing, in needs recovery, or was deleted from recovery.

Go to Job Scheduler and choose all users and verify that an update job is currently running for this company. If so, you will need to allow this job to complete before you can run GL190.  If no active jobs, check waiting and resolve any jobs in needs recovery.

If there is not another job being processed or needing recovery, you will need to update the record that will allow GL190 to run.  Create a paint a screen to update the GLSYSTEM file in the IF System Code and change the Updating field to 00 or blank out the field entirely.

GL190 may also create a GLMONITOR record that needs to be cleared. To clear this record, go to GL15.1, GLMONITOR Maintenance, and Inquire on the program that is running (in this case, you would Inquire on GL190). If a record appears, but the job is not actually running, delete the record.

Check the WAS Server status

, ,

There is a simple way to check the WAS Server status. First, open the command (cmd) prompt. The command to check which servers are running in WAS is in WAS_HOME/profiles/<profile>/bin.  To check all the servers, supply the switch “-all”.  Otherwise, provide a server name. See the screenshot below for a visual reference for checking the status of your WAS Server.

 

 

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.