Resolving the “Operator Not Authorized to Change Unit Cost” error

This is one of those Lawson errors that could waste a morning of work looking through the Infor knowledge base, analyzing/changing security, and or reviewing logs.


So, you’re on PO20.1 and want to make a change to a PO entry and get this error:

To resolve this is actually incredibly simple and can be changed on PO04.1 at the bottom of the Buyer Information Tab (your settings may be different based on your needs):

If you happen to get a similar issue for a requisition cost change “Requester not authorized to change unit cost”, simply go to RQ04 and allow unit cost override for the specific requester (your settings may be different based on your needs):

Error Running Lawson Command Line Utilities

UnsupportedClassVersionError occurs when running Lawson command line utilities. This could mean that Lawson is using an incompatible version of Java. Make sure you have a compatible version of java installed and activated. If that is the case, then check your enter.cmd file and make sure it isn’t manually setting the JAVA_HOME variables to the incorrect version of java. If it is, update to point to the correct location.

IFS Installer Fails with No Error Message

During a recent IFS install we encountered an install failure and the error message/return code was blank. The setup_log.log file said “Error: IFS -DoInstall failed with a return code of”.  We noticed that the setup_log.log claimed that it had created the new database successfully, but the database was not there. After much troubleshooting, we finally realized that we needed some inbound/outbound firewall rules for our IFS database instance. The interesting thing is that the install wizard made it past the database connection screen, but once we added those firewall rules, we were good to go.

Resolving “Cannot run this program while GL 190 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 “GL190” and select 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. This should solve the error. Good luck!

5 ways to properly secure new technology

Database errors and security breaches have increased significantly in recent years. With data migration, vulnerability to error and hacking is a great risk. “We have seen a large number of breaches and failures due to human error,” says Robert Reeves, Co-founder and CTO of Datical. Often times, humans underestimate and rely too much on “technology” to believe there will be room for error, but you can still make mistakes. Reeves emphasizes the need to automate security and system standards to eliminate (or significantly decrease) human error. Below are five recommendations on how to ensure that new technologies and systems are properly automated and secured:

IP Designer Error

When trying to open IPDesigner, we ran into this error:


Opening the log reveals a java.lang.StackOverflowError:


This error was fixed by going to (C:\IPDesigner\ADTALEMPRD\workspace\.metadata\.plugins\org.eclipse.ui.workbench)
And removing workbench.xml. We opted to rename it to workbench_old.xml and when we restarted IPDesigner, it generated a new workbench.xml and started working correctly.

WebSphere Update Error

When updating a WebSphere fix pack, the following error can be seen from the IBM Installation Manager.

The update in this example is from WebSphere to Fix Pack 10 –

Looking at the error details shows that a dll file was unable to be deleted –

D:\IBM\WebSphere\AppServer\bin\WASServiceMsg.dll. This file can be locked by the Cell Manager when the server is started.

To resolve the issue, stop the WebSphere service in Computer Management and set it to manual start (not to start automatically).

Then find the file that was locked (WASServiceMsg.dll) and rename it to something like WASServiceMsg8550orig.dll.

Permissions may need to be added to the IBM directory to ensure Full Control is Allowed for your user id. Then restart the server and run the IBM Installation Manager again to apply the update.

Afterwards, you can see an updated version of the dll is available along with the original file that was renamed.

Be sure to change the service back to start automatically after the update is complete.