When performing an update of Lawson Core Technology, you may come across the error “LID port xxx already used”. If your services are stopped, and you know nothing is listening on the LID port, you may have to temporarily change the port to get the install to complete.
To change the port, open the command line as administrator and set the environment variables. Then, type the command “laconfig” to open the configuration screen. Change the “lalogin Port” to some other port that isn’t being used. Click “Apply” and “OK”. Continue with the technology update.
After the technology update, go back into laconfig. The port should have been set back automatically (based on the install.cfg file). If it isn’t, you can set it back manually.
https://www.nogalis.com/wp-content/uploads/2021/09/LSFCT-Update-LID-Port-Already-Used.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2021-09-24 07:58:132021-09-16 14:00:09LSFCT Update – LID Port Already Used
Often, when you are having an issue with Lawson and/or Landmark, one of the questions Infor will ask you is whether your systems are federated. If you are unsure, there are a couple of simple ways to tell.
First, you could log into the WebSphere instance for your LSF application. Go to Applications > Application Types > WebSphere enterprise applications. If you see the application “scwebadminapp”, it is very likely that your systems are federated.
Another way to tell is to review the lsservice.properties file on either of your service (at LADIR/system for Landmark or LAWDIR/system for Lawson). If you see references to the remote server in these two files, and you see that there is an entry for “server.authservicename”, then your system is federated.
https://www.nogalis.com/wp-content/uploads/2021/09/How-to-tell-if-Lawson-and-Landmark-are-Federated.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2021-09-21 07:53:522021-09-21 11:39:11How to tell if Lawson and Landmark are Federated
If you are running a Federation Sync in Landmark, and you get the below message “Socket timeout exception occurred”, you may need to increase the max heap on the lase node. This error message will also present itself in the security_authen.log on the Landmark server.
at com.lawson.security.server.events.BaseEvent.readMsg(BaseEvent.java:235)
at com.lawson.security.server.client.ClientActorEvent.getNextActorIds2(ClientActorEvent.java:239)
at com.lawson.lawsec.authen.SyncAnalysis.getRemoteActorList(SyncAnalysis.java:2962)
at com.lawson.lawsec.authen.SyncAnalysis.loadActorsToSync(SyncAnalysis.java:1299)
at com.lawson.lawsec.authen.SyncAnalysis.performActorSyncAnalysis(SyncAnalysis.java:513)
at com.lawson.lawsec.authen.SyncAnalysis.run(SyncAnalysis.java:269)
at java.lang.Thread.run(Thread.java:748)
To update the lase max heap, open the Grid Admin window. Go to Configuration Manager > Grid Configuration > Grid Properties > Node Memory > Max Heap. Update the max heap to an appropriate level.
Save the setting and restart the lase node, or restart Landmark.
While you are running the federation sync, you can monitor the lase node in the grid’s topology view to see if your setting is appropriate for future syncs.
https://www.nogalis.com/wp-content/uploads/2021/09/Federation-Sync-Times-Out.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2021-09-17 08:06:082021-09-10 15:09:14Federation Sync Times Out
When dissecting the Object field of the comment (which contains the actual verbiage of the comment and other information) the first value is TYPE. This type determines the type of the comment that is stored.
The comment types for those added to an AP Invoice are as follows:
Invoice Note/Report/Check Comments
Type=A
Invoice Notes
Type=N
Invoice Report Comments
Type=D
Invoice Check Comments
Type=C
Keep in mind that to have the comments print on a check, not only would you need to have an Invoice Note/Report/Check Comments or Invoice Check Comments the users need to make sure that when the payment processing jobs (AP155/AP160 or AP161) needs to be set to Print or Include Comments.
https://www.nogalis.com/wp-content/uploads/2021/09/Comments-can-be-a-little-tricky-in-Lawson.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2021-09-14 08:14:442021-09-13 14:30:15Comments can be a little tricky in Lawson
If you have to open an Infor ticket for any Lawson product, such as EDI or EMSS, one of the first questions is going to be which version of the application you are using. Here are some quick ways to find your versions.
EDI
Navigate to LAWDIR/<prodline>/edi/install/install.cfg and look for “COMPONENT.EDI.VERSION”
RQC
Open the shopping screen (or any RQC screen) and select the down arrow in the far right corner. Click “About”.
EMSS
Open any Infor-delivered EMSS screen and click the down arrow in the upper right corner. Click “About”.
Smart Recon
Open the System Configuration menu item and make note of the “application fileversion”.
https://www.nogalis.com/wp-content/uploads/2021/09/Getting-the-Versions-of-Infor-Lawson-Products-min.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2021-09-10 08:48:032021-09-09 11:05:46Getting the Versions of Infor Lawson Products
When installing a new IPA product line using the intall-lpa.pl command in Landmark, you may encounter the error “Security Class does not exist.” This will prevent the IPA environment from completing the install. To resolve this error, first run the command “scupdate <product line>”. This command will generate all the security classes needed for the new IPA product line. Then, rerun the install-lpa.pl command, and it should complete successfully.
Error messages (on the command line, and also found at LALOGDIR/managelpa_<pdl>.log)
Run the scupdate command and verify no errors
Complete the IPA product line install
https://www.nogalis.com/wp-content/uploads/2021/08/Security-class-does-not-exist-Error-During-IPA-Install.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2021-09-08 08:59:392021-09-02 10:32:47“Security class does not exist” Error During IPA Install
If you perform a Java update on your Landmark server, and your JAVA_HOME location is moving, you will need to update the java location in several places in Landmark.
InforIONGrid
For the Grid, first open an administrator command window and navigate to GRID_HOME/grids/<grid name> and run the “ChangeJDK.cmd” command with the NEW location of Java:
Next, open the Grid Management Pages. Go to Configuration > Grid Configuration > Grid Properties. Select Property “Java Executable (Path)”. Set the Java path to the new location under your grid host.
Landmark
For Landmark, set the JAVA_HOME and LAW_JAVA_HOME environment variables to the new location. It is also a good idea to update LAW_JAVA_HOME in the LASYSDIR/install.cfg file for future patches.
Finally, open an administrator command window and set the Landmark environment variables. Navigate to the NEW java location. Run the command java -jar %LAENVDIR%/java/jar/bcinstall.jar. Verify that this command adds the bouncycastle provider to the java.security file located at JAVA_HOME/jre/lib/security. Also, verify that the command copies the “bcprov” jar to JAVA_HOME/jdk/jre/lib/ext. If either of these tasks is not completed, you can handle them manually.
Run a stoplaw/startlaw and restart the grid. Or, better yet, reboot the server.
To verify that the new java location is being used by all the application systems, open task manager, and add the “Command line” header under the details screen. Verify that all “java.exe” processes are running from the correct location. You are now safe to uninstall your old java instance.
