Prior to Landmark version 11.0.29, IPA had trouble recovering gracefully from a loss in data connection. When IPA loses connection with the database, it can sometimes throw this exception in the Work Unit logs:
To recover from this issue, you will need to restart the LPA node in Landmark grid, or restart the Landmark server. After that, upgrade Landmark to a more stable version at the earliest convenience.
The error “security.authen.os_account_not_configured” in Landmark will present itself when attempting to open Landmark web pages. There will be a 500 service error, and the security_authen.log will throw an exception similar to “: SecurityEventHandler #34 got exception.
1617884962 – L(2) : security.authen.os_account_not_configured”.
In this case, the resolution is to open the Landmark command line utility as the install user, and run the command secadm provision os -C -o -a.
Security_authen.log
Sat Sep 25 12:29:59.250 PDT 2021 – default-1617884962 – L(2) : security.authen.os_account_not_configured
Sat Sep 25 12:29:59.250 PDT 2021 – default-1617884962 – L(2) : SecurityEventHandler #34 got exception.
1617884962 – L(2) : security.authen.os_account_not_configured
Stack Trace :
com.lawson.security.authen.SecurityAuthenException: 1617884962 – L(2) : security.authen.os_account_not_configured
at com.lawson.security.authen.LawsonOSAuthenticatorImpl.getPrimordialContext(LawsonOSAuthenticatorImpl.java:206)
at com.lawson.security.authen.LawsonOSAuthenticatorImpl.getPrimordialContext(LawsonOSAuthenticatorImpl.java:58)
at com.lawson.security.server.SecurityEventHandler.getSecurityContextForEvent(SecurityEventHandler.java:376)
at com.lawson.security.server.SecurityEventHandler.processEvent(SecurityEventHandler.java:350)
at com.lawson.security.server.SecurityEventHandler.run(SecurityEventHandler.java:228)
secadm provision os -C -o -a
In Lawson you may be creating a custom ESS form that you don’t want users to be able to get to (assuming you removed the search button).
Example of this below:
Open design studio by going to https://yourcompany.domain/lawson/studio
To remove these related forms, edit the custom form in design studio and remove transfers id in source:
Save the now custom form, make sure it is set to default in logan or is accessible via a bookmark direct URL.
Clear your IOS Cache and test to make sure the related button is now gone.
Good luck!
LBI Smart Notes not working (even intermittently) and the SystemOut log is spamming the error below?
Failed to obtain DB connection from data source ‘SNDB’: java.sql.SQLException: Could not retrieve datasource via JNDI url ‘java:comp/env/jdbc/LawsonSN’
Below is an easy fix for this as this is typically caused by differing versions of java.
First login to your LBI server and locate the InforLawsonBI Install directory typically found on the secondary drive (D drive in our case)
Go to file path:
..\InforLawsonBI\SmartNotification\Smart Notification.ear\lsnwar<Insert version>.war\WEB-INF\classes
Locate and open the quartz.properties file with Notepad or a text editor of your choice.
Edit the line shown below:
Change it to the following:
Save and reboot the LBI server or restart the IBM Webservices.
That’s it!
If one of your users in Lawson Portal or Mingle is receiving this error (or similar), a Lawson Security administrator will have to follow the steps below.
- Login to Lawson Administrator Tool
- Go to Use Management > User Maintenance
- Query the user who is having the issue.
- Right-click on their record and choose ‘Edit Lawson Environment Information’.
- Make sure the user has a data area set. Edit >> Change after changing.
- Alternatively, if the data area is already set, select Edit >> Change. Reminder, if you are using ISS, hit the save icon. (You do not need to actually add or change anything on this form/screen.) This creates the R_USER record in the GEN database.
- In Lawson portal (or mingle, selecting the globe icon), if you’re a portal admin, you should see an option to Clear IOS Cache.
- Have the user that was encountering the error close all of their web browsers Internet Explorer (IE), Chrome, Edge, etc and then open a new web browser session and log in again.
Note: LSF 9 ONLY – LAUA users: If the user has the attribute CheckLS=No, the user may also need an LAUA Security Class assigned to their Operating System account via LAUA.
Good luck!
This error occurs in Lawson portal version 9.0.1 right when the user logs into Lawson Portal.
This is a web server issue when users and group are not allowed access to the directory.
To resolve this error, verify that the <document root>\lawson\portal\admin\usersandgroup\usersandgroups.js file has the correct file permissions.
Note: This same issue should no longer occur in v10+
