Resolving LBI Error: There are not any Rights on File for the requested User

,

Lawson Business Intelligence has this common issue where users load up a report and get an error that they don’t have the proper rights to access a report setup with bursting. At first glance it appears they are all setup but are they?

 

Resolution:

  1. Login into LBI (must have admin rights) >> Tools >> Report Administration
  2. Go to Maintain Rights and filter down on the user that is having this issue:
  3. At this point it appears the user is setup correctly but there are two checks that need to be done.
    • Verify the report the user is accessing (assuming it’s a historical instance) was generated after the Start Date field, else change the Start Date to an earlier date to resolve.
    • Click on the blue green people icon to make sure the user’s bursting rights weren’t setup before the user synchronized into LBI from LSF.
  4. If you see the user is categorized as a (Custom Group), delete the users current rights.

Delete:

  1. LBI dashboard >> Tools >> Synchronize Users and Roles >> Click Synchronize
  2. Go back and create the users rights and verify the (Custom Group) is no longer displayed near their name.

Hope this was helpful, good luck!

Resolving Lawson IPA Error: Unable to lookup RMI object

, ,

If you’re reviewing an Infor Process Automation log and notice the “Error: Unable to lookup RMI object rmi://localhost:16003/dbSecurity” or something similar firing on a FileAccess node, this means your bpm.ear config file got updated (possibly from an environment update) and needs to be fixed.

To resolve this, you’ll need to update the dbrmihostname field from “localhost” to the LSF server domain name in the bmp.ear file. See steps below.

 

To update the bpm.ear and bpm.war files follow the steps below:

  1. You must run the command from the same directory as where the bpm.ear file and bpm.war file exist:

cd %GENDIR%/assembly/products/bpm/jar

  1. Execute the perl script to rebuild the files, providing the new RMI port and hostname of your LSF machine:
    • perl %GENDIR%/bin/updateArchive.pl <RMI_PORT> <HOSTNAME>
    • Example: perl %GENDIR%/bin/updateArchive.pl 16003 lsfserver.domain.com
  2. Redeploy bpm.ear in WebSphere from the %GENDIR%/assembly/products/bpm/jar directory.
  3. Generate and Propagate the Plugin in WebSphere.
  4. Restart Process Flow.
  5. Restart the LSF WebSphere Application Server(s).
  6. Restart the web server.

Lawson PA100 Job Goes into Recovery due to On-Prem BSI License Expiring

, ,

Problem – PA100 Job goes into recovery with similar error:

 “Error connecting to Taxfactory11 – THE PROVISIONAL LICENSE IS NOW EXPIRED.”

 

  1. To resolve this issue, login to your MyBSI account at https://mybsiconnect.force.com/login
  2. Go to your TaxFactory Tab on the Home Page
  3. Select Maintain Machine Key

  4. Click Add New Key >> Select Desired Version and enter Host Name where BSI is being hosted.
    1. Note: To verify current Host Name of license, open command prompt, change dir to where tf11lic.exe is located and type following command tf11lic -v

  5. One you enter the New Key Info, select the Request Server Key button
  6. You should now see your newly added Machine Key, click Save as File to download
  7. Copy the machinekey.lic file to the server where TF11 is installed and the tf11lic.exe is located
  8. In command prompt, cd to where tf11lic.exe is and type this command: tf11lic -i machinekey.lic

  9. Type tf11lic -v to validate if the license is valid.
  10. In Lawson portal, calculate a PR80 record to verify Lawson is connecting to BSI
  11. Connect to Lawson Interface Desktop >> jobschd >> recover PA100 job in recovery (or any other job that requires a valid BSI license that went into recovery)

 

That’s it! Good luck!

Microsoft Edge Browser redirects to Internet Explorer 11 instead of the Lawson Login Page

, ,

If you’re using Microsoft Edge and trying to access Lawson but it’s redirecting you to an IE11 browser page with the error: “The request contained illegal input and was cancelled”, there is an easy solution to resolve this.

 

  1. This issue is caused by using a deprecated Legacy version of Microsoft edge instead of a new Microsoft Edge Chromium version.
  2. The best way to verify you’re using the correct browser, is comparing the Edge browser icons (see below)

Using the New Edge version should resolve this annoying redirect and get you into Lawson faster since IE11 is no longer supported.

 

Good luck!

How to verify if Lawson Payroll is working with BSI

, ,

You may have installed a new BSI update/license or need to verify if it’s safe to run an update batch job.

 

An easy way to do this is to run a simple smoke test in PR80.

 

  1. Login to Lawson portal and go to PR80
  2. Start with a company, employee, bank code, and payment number
  3. Under the Time Records tab FC >> Add >> Pay Code 0001 >> Hours 80
  4. Go to Payment Tab >> Select a Payment Date >> Deduction Cycle 2
  5. Now click Calculate and wait for it to finish.
  6. You should be brough to a HR99.1 Messages form with warnings etc. This means everything ran and Payroll communicated with BSI.

NOTE: Remember that the parameters above may be different for your organization and most can be anything since we are simply testing to see if Payroll is communicating with BSI by doing a calculation. As long as we are selecting Calculate, nothing is being changed with the record.

 

Good luck!

How to Decommission Lawson

, ,

When William Lawson, Richard Lawson, and John Cerullo founded Lawson Software in Minneapolis in 1975 they probably had no idea it would serve customers for nearly 1/2 a century. It has been a very impressive run that has created entire communities along the way. Whether you have been a user, an implementer, or somehow otherwise involved in the ecosystem, you have no doubt felt like you have been part of a community. As a consultant who started out with the Summit Group back in 1999 and later worked directly for Lawson software I have spent nearly every workday of the past 22 years working with Lawson. It is bittersweet therefore to be talking about this subject of decommissioning this brilliant application. With more and more customers migrating to CloudSuite applications and other ERP systems over the next few years, it makes sense now more than ever to begin planning the proper way to decommission the Lawson application.

The easy part of decommissioning is unplugging the servers. The hard part is to figure out a plan that ensures continuity with minimal disruption to the business. Therefore any discussion of decommissioning and archiving of an ERP application has to include the following three components:
  • Data Retention
  • Accessibility and Auditability
  • Security
Data Retention
Most organizations have data retention policies that are derived from industry or regulatory requirements. This is a good starting point. Working with subject matter experts within HR, Payroll, Finance, and Procurement, will flush out additional requirements around specific items like pay stubs, open invoices, or personnel action history to name a few. The important thing is to ensure whatever plan you have for decommissioning satisfies these requirements.

 

Accessibility and Auditability
Retaining data is fine and good, but you will need access to it if it’s going to serve its purpose. There is a lot to unpack here but the main requirements with accessibility are:
  • Intuitive User Interface – Given that this data is historical it doesn’t make sense that any interface to it should need extensive training.
  • Integration with AD – Future proofing your archived data means user accessibility must be supported for the duration of the data retention period and remain compliant with your IT standards for years to come.
  • Auditability – One of the main utilities of archived data is to serve the needs of auditors. In this capacity, your archival solution must provide reporting capabilities that can satisfy all audit requirements without the need for further skills or professional services.
Security
Under normal circumstances, your Lawson data is heavily secured with specific access rules in place to ensure prevention of improper access, segregation of duties, and malicious intrusion. The fact is that the security of this data is just as important in archive status as it was when it was in production. Any viable solution must have the ability to secure the data in such a way that satisfies all your data security requirements.
We built the APIX platform from the ground up with these specific requirements in mind. Our clients have been able to completely decommission Lawson in as little as six week and still get full access to their data through the APIX lightweight interface. Contact us to schedule a demo of the APIX Lawson Data Archive solution today!

How to setup a Lawson deljobhst recurring job to keep your Lawson print/job directories clean

, ,

Follow this step-by-step guide to set up a Lawson deljobhst recurring job. This will keep your Lawson print/job directories clean.

  1. Login to LID (elevated admin rights required)
  2. Go to jobdef and create a new deljobhst job
  3. Down arrow to Form ID >> F4
  4. Type >> F4 >> Universe >> Enter
  5. Data Area/ID >> F4 >> JOBSCHED >> Enter
  6. Down arrow to deljobhst >> Enter
  7. F6 >> A. Step Parameter
  8. Type the parameter letters you want without a dash, for this example we are just deleting old %LAWDIR%\print directory files using the r parameter and for any files > 400 days old
  9. To Date must be in the above format of: ‘curdate’ – NumberOfDays
    1. When the job runs on schedule, files greater than and equal to the date 400 days ago from current date will be deleted.
    2. 400 day example: Todays date is 6/7/2021 so print files as created on 5/3/2021 and older will be deleted.
  10. Press Enter to save jobdef and go to recdef in LID
  11. Create a new recdef entry and select the job you just created under Job Name. Select all other parameters as you normally would.
  12. Example below: This job will run daily at 1:33pm starting 6/7/2021

 

That’s it and good luck.

How to mass delete Lawson waiting jobs in the job scheduler in LID

, ,

It is pretty common for a Lawson recurring job to error out and continually run for hours and days. This can build up in the waiting screen of the job scheduler (jobschd). To clean it up can be repetitive when it doesn’t have to be.

  1. Login to LID
  2. Go to the job scheduler by typing the jobschd command
  3. F7 >> A. to show all user jobs
    • In our example we have 7 jobs, but this method works for hundreds of jobs.
  4. On the top most job that you want to delete press the HOME key to “mark” the job. Notice the black arrow on the very left
  5. Now scroll down or even page down to the bottom most record >> Press the END key. Notice all jobs from the top to bottom have the black arrow on the left, indicating these are selected.
  6. Now press F9 (Delete) to remove these jobs. Press enter to confirm.
    • NOTE: if there are dozens or hundreds of jobs, you may need to hold Enter to continuosly delete them.

Hope this was helpful!