Changing a Lawson system user password and checking if LDAP rebind is needed

, ,

When updating a Lawson system user, we need to make sure that the user is not LDAP bound and check if it needs a ldap rebind.

 

The first thing you need to do is login to Lawson Security Administrator then navigate over to Managed Privileged Identities.

 

From here, you need to select SSOP_BIND.

Next, select the DEFAULT key as shown below. Make note if the DN Attribute name is the same as the system user. If so, you will need to do a full LDAP rebind. If not, you’re okay to change the password.

And you’re all done. Good luck!

Cannot Delete Non-Journal Entries

, ,

PROBLEM

When I run CB187 job, I found an error message at CB N-68 as per below:

I am not able to delete CB entry with error message “cannot delete non-GL journal entries”. Should I go ahead and post the CB or is there any way I can delete the entry?

 

RESOLUTION

The message that you cannot delete a non-GL journal is a system enforced error. If the issue results in GL substituting error suspense, a sequenced journal will be created.

Otherwise after it is posted, you could copy with reversing entries to create a new journal with exact opposite data so the two ultimately net to zero.

Or if you simply need to reallocate an entry, a manual entry could be created to “fix” the data.

WFWK.1 error CCS product line has not been opened

, ,

When running a service in WFWK.1, it may produce the error message: “CCS product line has not been opened: Return Code 9”.

If this happens to you, follow these simple steps below to resolve it.

 

First, you need to start at the application product line, then go to screen WF01.1. Next, “Add” the Process Automation Productline “Logan”.

 

Next you will need to restart the Lawson services, or restart the Lawson server. Try to run the service in WFWK.1 again.

 

This should resolve everything and  you should not get the error message again.

 

 

***Also, the length of the flow name is limited

Bookmark Error

, ,

Problem:

No matter what browser I use, when I go back to a bookmarked link I get the following error when I sign in:

 

“Error encountered while processing the request. Additional information: Bad request cache id. This URL request may already have been processed…”

 

Resolution:

There is a simple solution to this common error. This is not security-related, but rather a bad link that you may have bookmarked. It’s important to make sure you bookmark the correct link: https://hostname/lawson/portal,so you won’t get this consistent error. Note that if you try to copy the URL before you have fully logged in, the bookmarked link will not work again.

How to Efficiently Analyze and Clean Up Lawson Directory Space

, ,

Overtime the LSF Lawson directory builds up and may even cause performance issues given the amount of data that may need to be backed up every night. Below are some steps you can take to help analyze and clean up your LSF Lawson directory.

 

  1. Download and Install the free WinDirStat tool found at https://windirstat.net/
  2. Once you open the tool, select and run it for your local LSF directory:
  3. You may notice right away that 3 directories stand out:
    1. %LAWDIR%\print
    2. %LAWDIR%\work
    3. %LAWDIR%\system\joblog


These directories will fill up overtime as users run batch jobs/reports.

  1. To clean up the work directory, you can expand the directory in Windirstat and manually get rid of large files, outdated reports and files.
  2. For cleaning up the print and joblog directory, Lawson has a utility called deljobhst
    1. To get a more in-depth look at the deljobhst utility see here
    2. NOTE: It is recommended to backup these directories especially if your organization has a retention policy.
  4. Open LID and connect to the environment you want to clean up.
  5. We personally are going to delete all printed reports and joblogs that are over 400 days old.
  6. convertunits.com can help determine what the date is 400 days from today is.
    2. In our case, it is November 26, 2019
  7. In LID, we would run: deljobhst -crj 112619
    1. This would remove all completed jobs (c)
    2. All generated print files associated with batch jobs (r)
    3. All recurring job entries (j)
  8. After this completes, if Windirstat is still open, click the refresh all button:

This type of work is typically done by a Lawson technical resource. Organizations often hire a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site. Nogalis does offer this as a service so feel free to reach out to us via our contact page. We typically provide the work above in a monthly or bi-monthly healthcheck that also captures several other key data points to stay proactive with your system before a problem occurs. Hopefully this was helpful!

LSA Security User Search Error

, ,

Description:

When I try to access user information in LSA security administrator, I am not able to see any users.

The error edit shows:

Stack Trace : org.mozilla.javascript.EcmaError: ReferenceError: “MISSING” is not defined. (<RuleAttribute>#1)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3226)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3216)
at org.mozilla.javascript.ScriptRuntime.notFoundError(ScriptRuntime.java:3289)
at org.mozilla.javascript.ScriptRuntime.nameOrFunction(ScriptRuntime.java:1633)
at org.mozilla.javascript.ScriptRuntime.name(ScriptRuntime.java:1572)
at org.mozilla.javascript.gen.c221._c0(<RuleAttribute>:1)
at org.mozilla.javascript.gen.c221.call(<RuleAttribute>)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:337)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2755)
at org.mozilla.javascript.gen.c221.call(<RuleAttribute>)
at org.mozilla.javascript.gen.c221.exec(<RuleAttribute>)
at com.lawson.lawsec.author.mgr.Rule.exec(Rule.java:168)

Resolution:

This message tells us that for some reason the security server (LASE process that runs) lost its connection to the ldap instance where the rules are stored for Lawson Security.

To work toward resolving the issue, you can follow KB Article ID: 1580306 – “Lawson Security: How to run a User Security Report when requested by Support”, for the application profile in question. Within that report, look for the word MISSING on the right hand side of the report where the ruleText is listed.
Most of the time, when this error is presented, you can use the Lawson Security Administrator (LSA) tool to fix the issue without doing a full restart of the Lawson related services.

If you do see the word MISSING, do the following from within the LSA tool:

  1. Click on “Server Management”
  2. Click on “Clear Cache”
  3. Go open a brand new IE browser session.. do not use a new TAB in an existing browser, it has to be a “new IE session”
  4. Log into Infor Lawson for Portal for Ming.leas someone that is a “Portal Administrator” that can run the “Clear IOS Cache” option.
  5. Ask one of the users to open a new IE session, not a new TAB within an existing browser, then try their same action that they were having an issue with.

ADDITIONAL INFORMATION:  In regard to the difference between the function of the “caching interval” setting and using/clicking the “Clear Cache” option under Server management. When you make security changes to users, you should not need to hit clear cache after making a change.  When the caching interval time is hit, the change will be placed into the security cache for use. The difference here is that when you hit the “Clear Cache” option, it drops the full security cache and re-reads the entire cache instead of reflecting just the changes. So, in order to clear up the issue where the security process could not find the rule Id tied to the securable objects, you needed to click on “Clear Cache”.

In some severe instances we may need to have the some of the rules deleted and rewritten but that is not a common occurrence and there are other steps we’d need to do prior to having you delete and rewrite rules so please open a new support incident if the steps above do not fix the issue.

 

Resolving “Cannot run this program while GL190 is running” error when trying to release journal entries in GL40.1

, ,

You may run into this error at some point in GL40.1:

Fortunately, there’s an easy fix to this. First login to Lawson portal and search GLMONITOR:

In GLMONITOR, type in GL190 and hit Inquire, if you get results and notice the run time, the process is in fact still running and causing the issue with GL40:

Go to job scheduler by opening LID and typing in jobschd >> F7 + A to select all users >> Then W to go to waiting screen.

Look for any GL190 jobs running and verify the User Name is the same one in GLMONITOR when inquiring on GL190 program. Check the error and if its safe to recover, recover it and let the job complete.

 

Go back to GLMonitor and inquire on GL190 to verify the job is no longer running:

 

Go to GL40.1 and release your Journal Entries.  Good luck!

 

This type of work is typically done by a Lawson functional resource. Organizations often hire a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site. Nogalis does offer this as a service so feel free to reach out to us via our contact page.