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.
If you are unable to log into Infor Federation Services (IFS) with a very vague error message, check the event viewer on the AD FS server to see if there are any more descriptive messages there. A database login issue could indicate that the install user for IFS doesn’t have the proper permissions on the database. Make sure the Lawson and spinstall accounts both have full access on the two databases that are created by the IFS install.
Occasionally when installing patches, you may get a message during the dbreorg phase of the activation. This usually means that some process has a lock on your files. Bounce your Lawson services, then run the dbreorg manually. If you get the same message, you may need to delete the + dictionary file.
Now, activate your patch.
When AD FS is configured for Lawson, there is also a “Thick Client” installed, which allows users to connect to client tools such as Microsoft Add-ins or Lawson Security Administrator. For users to be able to log into these tools, they must have a thick client identity set up in Lawson Security. The thick client value will be the same as the ssop value. Password isn’t used, so it can be set to anything.
Can’t assign a printer in a RECDEF job? Make sure you have a Printer assigned to you. Although the rest of the job can be setup, if you do not have a printer assigned to you, then you won’t be able to assign a printer to a step in RECDEF. For more information see KB 1206370.
There may be multiple applications for PGP encryption keys at your organization. It is very simple to create and use the keys using the secadm tool on your Landmark server.
IPA is a useful tool for dynamically updating the parameters of batch jobs in Lawson. At some point you may find the need to update a multi-step job. In that case, you will need to supply values for some of the hidden fields on your batch job. You will need to provide a value for _STEPNBR (a 0-based array). _f13 is used to name the print file, _f14 is used in the Reports section to set the distribution (“None” for default, “Dist Group” for a distribution group, “Printer” for a printer. _f15 provides the value of the item in the _f14 selection. So, if you set a “Dist Group”, you would provide the distribution group name in _f15. Field _f18 sets the directory of the print file, if you want it to be different from the default. Here is an example of a multi-step update:
There are two places where GL distribution information resides. One is in MMDIST. If the item is a special item or not setup on IC12, then MMDIST is where you will find the GL distribution information.
Keep in mind that a PO line might have started as a requisition and the GL Distributions were added then. When you are looking for PO line distributions, make sure you look for the document type of PO and specify the company and the document number that matches the PO you are looking for.
If the item is on IC12 it is either an inventory item or a non-stock item that is found at an IC location. All items that are setup on IC12 will have a GL Category assigned to them and that is where the GL distribution information can be found for these items. The key fields here are the Company – IC Location – Item. You will be able to find the GL distribution information for these items using these key fields on the GL Category table.
If you are configuring AD FS, it is important to remember that you must have at least one domain controller hosted on Windows Server 2012 (at a minimum). If your infrastructure does not meet these requirements, you will receive the below errors during the AD FS configuration. Update those domain controllers!
When it is time to renew the certificate on your AD FS server, you will need to import the new certificate. To do this, you will first need to get the thumbprint of your newly installed certificate. Then, run the Set-AdfsSslCertificate command and provide the thumbprint value you retrieved.
