The option to “Create CSV File” in print manager in Portal or attempt to export a report to CSV using Lawson Addins, the CSV file is not generated and the following error message is displayed in Excel or the browser after it opens:

Error generating CSV report file. Check IOS logs for details.

ERROR [ key=ERROR_GENERATING_CSV level=1 ]

<![CDATA[ Error generating CSV report file. ]]>

<![CDATA[ Check IOS logs for details. ]]>

The ios.log shows the following type of detail:

 

2024-01-05 13:40:32,088 ERROR [WebContainer : 8] [user1      ] [REPORT      ] [BldxffilesRunner] ********************** bldxffiles **********************

2024-01-05 13:40:32,088 ERROR [WebContainer : 8] [user1      ] [REPORT      ] [BldxffilesRunner] Security Violation

/GENDIR/bin/rptgen: Error Encountered In Execution

2024-01-05 13:40:32,088 ERROR [WebContainer : 8] [user1      ] [REPORT      ] [BldxffilesRunner] ********************************************************

2024-01-05 13:40:32,088 ERROR [WebContainer : 8] [user1      ] [REPORT      ] [ReportEngine] IOException generated while streaming / LAWDIR/print/user1/ap201/1/AP201.csv/

2024-01-05 13:40:32,088 ERROR [WebContainer : 8] [user1      ] [REPORT      ] [ReportEngine] File not found  /LAWDIR/print/user1/ap201/1/AP201.csv

2024-01-05 13:40:32,089 ERROR [WebContainer : 8] [user1      ] [REPORT      ] [Report] com.lawson.ios.core.Report.ReportException: ERROR_GENERATING_CSV

2024-01-05 13:40:32,096 INFO  [WebContainer : 8] [            ] [            ] [IOSSecurityContext] Destroying security context for user1

 

Resolution:

To troubleshoot this issue, follow the steps below:

Check the LAWDIR/system/ios.logs for the actual error message and problem. When reviewing the IOS logs, start with a search for “ERROR_GENERATING_CSV” and then review the messages that occur before that.

For the error message used in the example above, make sure the user has been granted access to the “rptgen” token under the ENV profile in Lawson Security. The user should be assigned a batch role which grants access to ‘rptgen’.

  1. Log into the Lawson Security Administrator.
  2. Go to the ENV profile.
  3. Select your batch security class.
  4. Click Add Rule.
  5. Choose the box for development tools.
  6. Select Grant all access.
  7. Expand the development tools.
  8. Select rptgen – Grant all access.
  9. Apply the rule.

 

Lawson Portal 10.1 Series –  Personalizing the Form Elements of Lawson Portal 10.1

In the first article of the series we went over how to personalize the theme of your Lawson Portal. The next article in the Lawson Portal 10.1 Series overview will cover how to personalize the form elements on the page.

 

To update the form elements, such as label colors and sizes, of Lawson Portal 10.1, from the left-hand menu, go to General > User Options.

 

Next, click the Personalization Tab.

 

Under Form Customizations settings you have the options to select a label size, label style, label color, and detail area headers color. Feel free to customize to your likings or match your company’s colors.

 

Lawson Portal 10.1 Series – Personalizing the Theme of Lawson Portal 10.1

Welcome to the first article of the Lawson Portal 10.1 Series. Along with this one, future posts will cover other personalizations, how to set up your bookmarks, and adding main content to your Lawson Portal screens. Let’s get started with the first topic – personalizing the theme of your Lawson Portal 10.1.

 

To change the theme (background/foreground colors) of Lawson Portal 10.1, from the left-hand menu, go to General > User Options.

 

Next, click the Personalization Tab.

 

Under Global Customizations you have the options to select a new theme (light, dark or high contrast), and a different Accent Color if desired (usually to match your company’s colors).

 

Welcome to Nogalis’s LSFIQ security reporting tool overview.

 

What is LSFIQ?

  • LSFIQ is a cloud-based Lawson security reporting tool
  • Designed with a user-friendly interface for non-technical and technical users
  • Faster and more accessible reporting without the need of VPNs or Lawson server access
  • Provides enhanced Lawson security reports that are not included in the traditional tool

 

The Dashboard is a quick overview of batch information personal to your LSFIQ account

  • A batch is generated on the Lawson LSF server via Lawson Interface Desktop tool
  • This batch is then uploaded to LSFIQ and ready for reporting

The Upload tool is where you name and select the batch files to be uploaded:

The Analyze tool is where all the reporting happens:

First you select your batch (DEMO is this example), then you can select a wide array of reports:

The Batch Overview feature is a great first step to analyze your current Lawson Security:

  • Batch Stats shows important information about your system like number of roles and groups
  • Batch Health represents potential issues with your system, including checking if the CHECK_LS flag is not set to YES (this means security is off for this user depending on the version of Lawson your organization is on).
  • All of the Batch health rows are clickable and will generate a report in a new tab.

The User Profile is also a nice feature that shows RMID info from Lawson Security:

 

You can also compare two user profiles with the compare tool:

This shows the different roles and other info each user contains that the other does not:

The All Roles query shows all your roles as you’d expect:

However, you can also click each one quickly to query down on them or simply download them all:

Tokens by Role AMINQROLE generated from above:

One of our most used reports is the All Users report:

 

All other reports show in a similar fashion and provide a wide array of versatility when reviewing user security.

If you have a user that changed security recently, but wanted to compare to an old batch, you can do that with the Compare Tool:

Since this example account only has one batch called DEMO, it can’t compare.

You can also Purge batches if needed under Manage Batches:

Need to mass change users in Security? That’s what the Export Loaduser tool is for:

This builds out XML files for the native Lawson loaduser command.

 

LSFIQ is ready to go in literally 5 minutes! Contact us today, go to our website at nogalis.com under products >> LSFIQ – Lawson Security Reporting

Linked is a recent webinar we did demoing this tool live. Thanks for visiting!

FAQ:

Q: Does LSFIQ include disabled users in it’s All User report?

A: Yes!

 

Q: Can you download reports and send to other users?

A: Yes, they download in CSV format and can easily be re-saved as excel format if needed.

 

If you’re experiencing Landmark Error:

“Email failed with error: 554 Access denied: Amazon SES no longer supports TLS 1.0 and TLS1.1 connections”

 

This is a known issue with TLS v 1.2 with the version of Landmark your current system is running. It’s resolved in the 11.0.49 release, reach out to your Infor representative or MSP consultant to get this updated. Here at Nogalis we also provide this MSP support if needed.

 

In the meantime, you can download the attached jar file or search KB 2221448 and then follow the steps below.

  1. Stop Landmark and Stop WAS to be thorough (LMK command window type stoplaw)
  2. Delete (or save off into a different directory) GRIDHOME\LAENVDIR\java\thirdParty\mailapi.jar
  3. Copy the javax.mail-api-1.6.2.jar you downloaded into GRIDHOME\LAENVDIR\java\thirdParty and rename it to mailapi.jar
  4. Start Landmark (LMK command window type startlaw) – Start WAS

 

Done! Hope this was helpful and resolved your TLS issues in Landmark.

 

When using a Web Service node in IPA that retrieves XML data, you may encounter the “innerElementCountThreshold” error if the XML returns too many records for IPA to handle it.  You can increase this threshold by updating the Grid properties.

Open the Landmark Grid and navigate to the Configuration Manager (gear symbol) > Grid Configuration > Grid Properties > Node Properties > Generic JVM Commands

Select the Landmark application property under “Any Host”.

Append the command -Dorg.apache.cxf.stax.maxChildElements=500000.  You can set it to more records than 500000, but be mindful of system performance.

Click Update Property, and then Save the configuration.  Reboot the server for the changes to take effect.

Problem:           

You need the command for an Infor Process Automation (IPA) to automatically recover or kill jobs waiting queue.

 

Resolution:     

There is a simple solution for this. You will need to first create a Process Flow that checks Jobs and Recovers and Kills them (Note that Invalid Parameters Status jobs aren’t going to recover).

Next, add the jqaction token to a security class, as it’s not defaulted.

Next, try SysCmd Nodes using the jqstatus -wr to get the Job List, and then jqaction -r to recover a job and jqaction -k to kill a Job.

Now you are able to recover or kill jobs waiting in the queue.

You need to update your license file if you exceed the maximum number of application users. All application users are also Infor Lawson Environment users.

The license and applications information is stored in the %LAWDIR%\system directory.

Note:  To update your license, you must first have received a new license file via e-mail from Infor.

Shut down the WebSphere application server. Use the instructions provided with your application server to stop the server you configured to run Infor Lawson. The person who shuts down the application server must be a member of the group for Infor.

Stop the Infor Lawson system.

At the command line, specify this information:

stoplaw

Optional. If you want to keep a copy of your existing license, make a backup copy.

Copy the license content you received in email to %LAWDIR%\system. At the prompt to overwrite the existing file, select yes.

Start the Infor Lawson system.

To start the Infor Lawson servers, at the command line, specify this information:

startlaw

Restart the application server. Use the instructions provided with your application server to start the server you configured to run Infor Lawson. The person who starts the application server must be a member of the group for Infor.

Note: The web server must be running in order for the Infor Lawson system to run, but you do not need to start it before you start the Infor Lawson system.