Archive for category: Frontpage Article

You are here: / / Frontpage Article

V10 Portal Bookmarks

, ,

Follow this quick guide to re-label portal bookmarks in Lawson:

To change the Lawson v10 bookmark button label, locate and edit the file at %LAWDIR%\persistdata\lawson\portal\data\msgs\en-us\portal.xml, which controls how the label is displayed in the portal. Open the file in a text editor and search for “lbl_BOOKMARKS.”

Update the associated value to reflect your preferred naming convention, then save your changes. After updating, refresh the portal to confirm the new label appears correctly.

Keep in mind that this file may be overwritten during Portal or S3 Workspace patches and upgrades, so you will need to reapply your changes after each update to maintain the custom label.

How to resolve Lawson ‘Distribution List Has Not Been Defined’ Error in jobdef

, ,

Summary: When setting up a Distribution group so other users can view the print manager of another user, typically a system user like lawson. You need to complete a very important step before being able to add it.

 

  1. In Jobdef when you try and set the distribution group you get the “Distribution List Has Not Been Defined” error (not displayed below, but it’s an example of it being set)
  2. To resolve, go to users environment info shown below in ISS (This can be done in LSA or ISS)
  3. M sure to add the distribution group to the environment info of the Lawson user (assuming you’re distributing a lawson job to other users).
  4. Open jobdef and add it now. NOTE: After adding to Jobdef, you can clear this field and it should still work.

 

Configuring LSA logging for the passive client

, ,

Follow the steps below to configure LSA logging for the passive client:

  1. Right mouse Click on the Lawson Security Administrator icon and run as Administrator
  2. On the upper right corner of the Server Connection form, click Settings.
  3. On the Settings form, select the Logging tab then configure the following:

    Configuration Directory

    Specify where LawsonNlog.Config is located. LawsonNlog.Config is the configuration setting for LawsonHttpClient that takes care of logging.

    Enable Logging- toggle logging.

    Log level

    Debug – Log the detailed trace

    Error – Log the exception errors

    Log Directory

    Provide the location where the generated logs will be saved on the same computer where LSA is installed.

  4. Select Apply, and Yes – to apply the settings before re-launching LSA.

 

AWS Schema Conversion Tool Error 602

, ,

When migrating schemas to MySQL using the AWS Schema Conversion Tool (SCT), you may encounter the error:

“602: Converted tables might exceed the row-size limit in MySQL.”

This warning means that one or more tables being converted could exceed MySQL’s row-size limit. For the InnoDB storage engine (default in MySQL and Amazon Aurora MySQL), the maximum row length is 65,535 bytes. If your converted table design goes beyond this, MySQL will reject it.

Why This Happens

  • Large VARCHAR or TEXT columns
  • Too many columns in a single table
  • Wide columns that, when combined, exceed the 64KB limit
  • Non-optimized data types during schema conversion

Fixing the Issue

  1. Review and Optimize Column Data Types
  • Reduce overly large VARCHAR lengths. For example:
    • VARCHAR(1000) → VARCHAR(255) if values never exceed that length.
  • Replace TEXT with smaller types (TINYTEXT, MEDIUMTEXT) where possible.
  • Use integers (INT, SMALLINT, TINYINT) instead of BIGINT if values fit.
  1. Normalize the Table

If your schema has too many wide columns:

  • Split them into multiple related tables
  • Use foreign keys to maintain relationships
  • Store large blobs of data separately
  1. Drop Unnecessary Columns

Remove unused or redundant columns before migration to shrink the row size.

  1. Consider Storage Engine Options
  • InnoDB enforces the row-size limit but stores large TEXT/BLOB columns off-page (only a 20-byte pointer remains in the row).
  • If you only need full-text lookups, splitting those into reference tables may help.
  1. Change InnoDB Page Size (Advanced)

By default, InnoDB uses a 16KB page size. MySQL allows compilation with different page sizes (4KB, 8KB, 16KB, 32KB, 64KB).
⚠️ Important: This cannot be changed dynamically. You must recompile MySQL from source with a custom setting.

  • Download MySQL source
  • Modify the UNIV_PAGE_SIZE definition
  • Rebuild and reinstall MySQL
  • Re-import your schema and data

This approach is rarely used in practice because it complicates upgrades and maintenance, and is not supported on managed services like Amazon RDS or Aurora MySQL.

Best Practice in AWS Context

Since you’re working with AWS SCT and likely using Aurora MySQL or RDS, you cannot change InnoDB page size. Instead, the best fix is to:

  • Normalize your schema
  • Adjust column definitions
  • Split oversized tables

Takeaway

The 602 error in AWS SCT isn’t a hard failure—it’s a warning that your schema design may hit MySQL’s row-size limits. While increasing InnoDB page size is technically possible in self-managed MySQL builds, on AWS-managed databases the right solution is schema redesign and column optimization.

✅ Rule of thumb: If you’re migrating from Oracle, SQL Server, or DB2 into MySQL, review the largest tables carefully. Wide schemas that were fine in those engines may not fit in MySQL’s stricter row limits.

 

Lawson GL40.1 Error when trying to release journal entry – Workflow is not enabled

, ,

Problem:

You’re trying to release a Journal Entry on GL40.1 but getting a “Workflow is not enabled” error (see example screenshot below):

 

Solution:

This is a simple resolve. First, on GL10.1, inquire on the company and under the Journals tab, set workflow to No >> Click Change

Go back to GL40.1 and release journal entry. This should remove the error and fix things. You’re done!

 

NOTE: This issue may happen when your GL10.1 form is a custom form and has customizations for the Workflow field.

Error: LSA is not compatible with the version of Windows

, ,

If you receive this message when working with Lawson Security Administrator:

“The version of this file is not compatible with the version of Windows you’re running. Check your computer’s system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program.”        

Corrective action

The LSA tool should be able to run on both 32-bit and 64-bit systems. Take these steps to check to see if this message is related to a different operating system issue.

  1. Restart your Operating system.
  2. Log in to computer as an Administrator> Run LSA installer as an Administrator > Proceed with LSA installation.
  3. If the error message occurs again, the LSA download file might be corrupted. Download the latest version of the security administration tool and repeat step 2.
  4. If you continue to get the same error, right-click the LSA installation program > Select Troubleshoot Compatibility > Click Try Recommended Setting > Click Start the Program > Proceed with the LSA installation.
  5. If the installation is still not successful, contact Infor Support.

 

How to update a user’s DB password via Infor Lawson Cloudsuite

, ,

Follow these steps to update a user’s DB password via Infor Lawson Cloudsuite

  1. Login to your concierge account and go to Cloudsuite app (this assumes you have access to this else open a ticket with Infor).
  2. Create a Service Request
  3. Select Deployment and Request Type: SQL Manage User
  4. Select Database Server and in the drop down select Change Password
  5. Enter username, the new password for the user, then click Submit

 

All done! Validate with the user. If this is something you’re need assistance managing, Nogalis offers a team of Lawson specialists within a single MSP services contract for customers. Let us know if we can assist you today.