5 Patching Tips in Lawson v10

, ,

These 5 tips could make applying patches that much less stressful and are also good practice in general.

 

Tip 1: Check existing patch logs to see if a patch has already been applied previously and current versioning. This is good to check after a patch has been applied as well.

These logs can be found and generated here in LID:

perl %GENDIR%\bin\patches_installed_report <productline>

perl %GENDIR%\bin\source_versions_report <productline>

 

Tip 2: Restart the LSF server (or services) to ensure no processes are being held up and when it boots up, turn off Websphere LSF Appserver service before applying a patch to ensure users cannot log on, especially if patch needs to be applied during or close to work hours.

 

Tip 3: Run dbdef command to make sure there is a connection to the database before patching

 

Tip 4: When activating or staging multiple patches, run this command to speed up the post compile process:

qcontrol -jlocal,4  – This will set the servers cores to 4 when processing form compiles. Set it back to 2 when done. You can also check the status of the compiled jobs with command: qstatus | head -5

 

Tip 5: If a Plus dictionary is created after patching, its typically good practice to compile the entire product line with the command: cobcmp (be aware this can take up to 20-30 minutes to complete, tip 4 helps with this). This ensures that all programs are functioning correctly before passed to testers.

 

Bonus Tip: Verify security is on before sent to the testers!  Hope these were helpful.

 

If you found this article helpful, Nogalis provides managed services and expert technical resources to assist with Lawson patching and system maintenance. If applying patches feels overwhelming or time-consuming, our team can simplify the process by managing everything from version checks to database connectivity and post-compile optimizations. Let us help ensure your patches are applied efficiently and your system is running smoothly. Contact us to learn more about how we can support your Lawson environment.

Lase_server indicates a message is too large

, ,

The message “lase_server logging issue – Invalid message is received and size” indicates that an error message that is too large has been sent from the security server.

Example full message text

default.SEVERE server.SecurityEventHandler.run(): SecurityEventHandler #816 got exception. com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=64706,localport=450000].

Stack Trace : com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=6406,localport=50000].

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:339)

at com.lawson.lawsec.server.SecurityEventHandler.run(SecurityEventHandler.java:151)

Caused by: java.io.IOException: Invalid message is received and size:300095616

at com.lawson.security.server.AbstractDefaultEventSource.readMsg(AbstractDefaultEventSource.java:351)

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:352)

 

Resolution

The parameter server.readMsgMaxSize must be added to lsservice.properties.

The MsgMaxSize parameter ensures that a logging message that occurs when a vulnerability scan is run does not become so large that it causes the system to hang. The parameter catches very large messages and replaces them with shorter sample messages.

Perform these steps to add the parameter.

  1. Stop the Infor environment and the application server.
  2. Open the lsservice.properties file for editing.
    On Landmark, the location is: LASYSDIR/lsservice.properties
    On LSF, the location is: LAWDIR/system/lsservice.properties
  3. Add the parameter server.readMsgMaxSize=[size number in Bytes] to the end of the file. The default size is 20MB. Infor recommends not setting the size larger than 40MB.
    Example: server.readMsgMaxSize=20
  4. Restart the Infor environment and the application server.

 

Lawson Security Administrator Stuck on Authenticating after two-factor sign-in

, ,

Note that the below information is reproducible on a cloud client via jumpbox or local PC connected to VPN.

 

If your Lawson Security Administrator is stuck on authenticating after two-factor sign-in, follow these steps to reproduce and get a solution (this is to make sure you’re experiencing the same issue):

Run LSA as Admin and login.

Ping ID or Two-factor equivalent Authenticates

Script Error will pop up. Clicking yes, no or closing the window leads to the same result:

Doesn’t connect after, stuck on Authenticating.

This occurred on LSA Version 10.0.3.01065 in a Infor Cloud Environment.

 

Resolution:

Installing LSA Version 10.0.3.01069 Resolves issue and LSA is able to authenticate after the two-factor.

 

Adding Context Apps in Infor OS Portal

, ,

Follow the steps below to add a new context app in Infor OS Portal.  In this example, we will enable the app for Infor Lawson S3.

Log into Infor Portal and Click on User Settings > Admin Settings

Go to the Manage Context / Utility Apps tab and select “ADD CONTEXT/UTILITY APP”

Enter a Type, Name, Description, and URL.  Click Save.

 

Now, add the application(s) that will be using this context app.  At the bottom of the screen, select the Applications tab and select “Add/Remove Applications”.

Select the application(s) and click Done

Be sure to Enable to application and then click “Save”

Your context app now shows up in the right side menu

 

How to preserve linked Lawson tables in Access when copying to different machines

, ,

Need an Access Lawson database to reside on the desktop of select users without having to relink all the tables each time?

If so, see the below query for the DSN-less connection with a function to relink all the tables and pass-through queries. This also just works for databases in general. Good luck!

 



 

If this process seems too complex or time-consuming, Nogalis offers expert managed services to help you manage and optimize your Lawson databases, including handling table linking and other database configurations. Whether you’re looking to simplify data management across multiple machines or improve overall system performance, our team can provide the support you need—without the overhead of a full-time, in-house staff. Contact us to learn more about how we can assist with your Lawson environment.

Upgrading to Infor LTR

, ,

This article will give you all the information you need to know about the Infor OS decommission, as well as what you will need to migrate from Infor OS on-prem to Infor LTR on-prem.

What is happening?

Infor OS and Infor OS Lite on-premises are moving to sustaining maintenance on March 31, 2025.  Sustaining maintenance means that there will be no new patches, updates, or fixes for Infor OS.  The pre-existing patches and documentation will remain available.

Reason for the Change

On-premises Infor OS installations are currently running on outdated software components, including outdated versions of Windows, Java, SQL Server, and .Net Framework.  The new product, Infor LTR, will allow all for all of these components to be upgrade to newer and more secure versions.

What are my Options?

On-premises customers have three options for handling this change:

  • Purchase a new MT Infor OS license tier (SaaS)
    • This is a cloud offering from Infor that would create a hybrid environment for clients. Infor OS would run in the cloud, and can still be used for SSO authentication, and your remaining Infor applications could stay on-prem.
  • Upgrade to Infor LTR
  • Take no action and continue to use Infor OS (this contains risks)

What are the Risks of Staying on Infor OS?

Keeping Infor OS can cause your organization to miss out on important security updates.  It also would require your organization to maintain an application on outdated technology, which can be a security risk.

What is Infor LTR?

Infor LTR is a core technology runtime service, that is a “wrapper” for Infor applications.  It serves as a single hub where users can log into one URL and then access all their Infor applications from a menu.  Infor LTR will be supported until at least 2029.

How to Upgrade

To upgrade from Infor OS to Infor LTR, it is possible to do an in-place upgrade procedure.  For a one-step upgrade, you must currently be on Infor OS 2021.12 or higher.  If you’re not on a compatible version of Infor OS, you’ll need to first upgrade Infor OS to one of those versions, and then you can upgrade to Infor LTR.

The upgrade process has the exact same look & feel, and the same installer as Infor OS, so if you have previously done an Infor OS upgrade, you will not have any learning curve.

Server & Compatibility Specifications

Before starting any kind of Infor upgrade, please first read the installer document for the exact specifications.  As of the writing of this article, these are the specifications for Infor LTR:

  • Microsoft SQL Server 2022, 2019, or 2017
  • Windows 2022 or 2019
  • .NET Framework 4.8
  • AWS Corretto JDK 17 (Infor LTR requires a very specific minor version, so be sure to check your documentation before downloading)
  • Minimum Hardware
    • 4 CPU Cores*
    • 32 GB of RAM*
    • Install drive of 50GB+
    • Data/content drive of 300GB+

*NOTE: These are minimum hardware recommendations.  If you are going to use Infor LTR for SSO authentication, it is recommended that you increase the CPU cores and RAM.

Using Infor LTR with Web Applications

Infor LTR offers the same Infor web application utilities as Infor OS.  You can set up menu widgets for applications such as Lawson, LBI, and MSCM.  You can still use the direct URL to access these applications.  Infor LTR is not required the access your Infor web apps, but it is required for compliance with your Infor licensing.  Infor LTR is required if you want your Infor applications to authenticate using an identity provider other than ADFS.

Here are some basic screenshots of setting up and application in Infor LTR:

Infor LTR as STS

Infor LTR can be used as the SSO authentication application for all your Infor web applications.  You can authenticate using multiple different identity providers (IdP).  For instance, you can configure Infor LTR to authenticate with Azure AD, MS Entra, AD FS, or Okta.

Where do I get Infor LTR?

Check your product downloads under Technology > Infor Local Technology Runtime (LTR).  If you do not see LTR in your product downloads, reach out to your Infor account rep

How to find and run the Landmark Validation URLs

, ,

There are occasions when Infor Support will request you to report if you are able to access all validation links. To find the links for validation, follow the steps below:

First, in file explorer, go to the InforLandmark folder

In the folder, you should have an htm file for the validation URLs (see screenshot)

 

Next, double click on the file to open it.

Click on each of these links to validate you can access each link.

Finally, send Infor the screen shots of any links that have errors so they can review.

Strengthen Your ERP Security with Smarter SoD and User Access Management

, ,

Enterprise Resource Planning (ERP) systems are essential for managing core business functions but their central role also introduces significant risks if not properly secured. To prevent costly fraud and compliance issues, IT and business leaders must prioritize effective Segregation of Duties (SoD) and user access management. In an article on ERP Today, written by tech expert Jennifer Lawinski, she emphasizes the importance of enhancing ERP security through smarter Segregation of Duties (SoD) and user access management. The article highlights that ineffective access controls can lead to fraud, errors, and compliance issues, making it crucial to implement robust policies. Automation tools can help identify and mitigate risks by continuously monitoring user activities and access rights. Regular audits and reviews ensure that access privileges remain appropriate over time. Role-based access control (RBAC) simplifies management by assigning permissions based on job roles, reducing errors. Dynamic access management adapts to changing organizational needs, improving security and efficiency. The article advocates for integrating security solutions with existing ERP systems to streamline oversight. It stresses the importance of strong authentication methods, such as multi-factor authentication, to prevent unauthorized access. User provisioning and de-provisioning should be automated to minimize human error. Implementing real-time alerts for suspicious activities can help detect potential breaches early. Establishing clear policies and training staff enhances adherence to security protocols. Regular risk assessments identify vulnerabilities proactively. Combining technology with governance ensures comprehensive security coverage. The article notes that organizations often overlook the complexity of SoD conflicts, which can be mitigated with smarter tools. It advocates for a risk-based approach to access management, prioritizing high-risk areas. Proper documentation and audit trails support compliance with regulations like SOX or GDPR. Continuous improvement of access controls aligns security with evolving threats. The article concludes that smarter SoD and user access management are vital for safeguarding ERP systems effectively. Investing in these practices reduces the likelihood of security breaches and financial losses.

 

For Full Article, Click Here