ADFS Timeout

, ,

To check and/or change the Web SSO lifetime within AD FS, follow these simple steps below.

On the server with AD FS (Active Directory Federation Services) access the AD FS Management Console.

  • First, select ADFS on the left
  • Next, select the “Edit Federation Service Properties” on the right-hand side
  • Locate the Web SSO lifetime is at the bottom of the dialog box presented
  • If needed, change the value; the number displayed is in minutes
  • No restart is needed to enable the change

See screen shot below for a visual guide.

 

Login to User for Infor Landmark Updates

, ,

When running cumulative updates in your Landmark environment, it is important to be logged into the server with the correct account.  If you aren’t on the right account, then the updates will fail with little to no explanation for why.

To determine which user needs to log into the server to run update scripts, open Windows Services and look for the Infor ION Grid service.  The account that is running the Grid service is the account that should be logged in.  It is often the local Lawson account, but could also be a domain account. See the screenshot below for reference.

 

 

 

 

Troubleshooting steps for problems with batch jobs

, ,

When batch jobs are not running and are in a waiting status. Our users are unable to add or submit batch jobs.

Resolution:

Here are some steps to troubleshoot problems with batch jobs

  1. If users are not able to add a batch job:
    • create the NOPARAMVAL file in the LAWDIR/system directory. The NOPARAMVAL touch file allows the system to skip the parameter validation when a new batch job is added.

From a LID command line, type the following:

cd $LAWDIR/system

touch NOPARAMVAL

  1. If jobs are not submitting, failing, or hanging, follow the steps below:
    • fix corrupt jobstep records

 From a LID command line, type the following:

 jobinteg -d

Increase the Max Number of Jobs and Max Number of Update Jobs values in jqdef

Ensure the RUNJOBS setting is set high enough in the LAWDIR/system/lajs.cfg. If the total Max Number of Jobs from jqdef is set at 10, RUNJOBS must be set to at least 10.

Restart the Job Scheduler by using the startjobqueue command

Recover and resubmit any jobs that are in Needs Recovery.

Lawson Add-ins is producing “Script error” message

, ,

So you’re getting another Lawson Add-ins Script error but disabling third-party plugins in excel didn’t resolve the issue?

 

This may be due to the fact that Add-ins still uses the old internet explorer settings (this is likely only if you’re using Windows 10).

 

Workaround:

  1. Let’s disable usage of scripts in Internet Explorer when you go to: Settings > Internet Options > Advanced > go to Browsing section > check both the:
    1. Disable script debugging (Internet Explorer)
    2. Disable script debugging (Other)
  2. Hit the Ok button

Now in Microsoft Edge Browser:

  1. Go to Settings > click on Privacy, search and services > go to Clear browsing data for Internet Explorer > and click on the Choose what to clear button.
  2. On the Delete Browsing History dialog box, clear the check box for Preserve Favorites website
  3. Select the check box for Temporary Internet files and website files
  4. Select the check box for Cookies and website data
  5. Click Delete

That’s It! Try rebooting your PC if the issue still occurs after changing these settings.

 

Lawson Add-ins Script error – An error has occurred in the script on this page

, ,

Lawson Add-ins Script error “An error has occurred in the script on this page”. This used to be caused by an outdated internet explorer browser before Microsoft migrated fully to Edge. Now this can occur when Excel extension apps get added via an app update or feature update.

 

When logging into Lawson Excel addins, you may get this script error, locking up your session and not being able to login.

 

To resolve this, in Excel, go to File >> Options >> Add-ins >> Com Add-ins >> Go

 

In this case, it was an Acrobat PDFMaker office com addin extension that was added after an update, simply uncheck this extension and click OK.

 

Now close excel and open again, you should be able to login to Lawson Add-ins now.

Resolving “Metadata not available” error in Infor Reporting with Chrome browser

, ,

Problem:

A user is encountering a problem while utilizing the XM reporting tool in conjunction with the Chrome browser.

 

Solution:

When launching the Ad-hoc reporting tool using Chrome and selecting the ER Model option, the “list” option is chosen from the provided pre-defined report layouts. Normally, users would be presented with the report building functions, and the right-side source panel would display all available fields that can be dragged into the report area. However, as observed in the attached document, both the source field and report area are completely empty, rendering it impossible to construct any form of report.

 

This issue persists when creating new reports and running existing ones through both Ad Hoc and Professional Reporting, specifically when utilizing Chrome or Incognito mode.

 

Note: Please be aware that IR only supports IE11 or Edge (in IE mode).

 

Another workaround may be to use another Browser:  IE, Firefox, Edge, etc.

 

And that’s all there is to it. Good luck!

Where does Lawson Process Flow (IPA) get the SMTP server for emailing?

, ,

If you’re creating a new IPA (Infor Process Automation) Process Flow or editing a new one, you’ll want to know where the SMTP configuration information is to send out email notifications within the flow itself.

 

For 901 and v10 systems:

  1. Go to your LSF application server
  2. Go to the $LAWDIR\system directory.
  3. Search for the bpm.properties file and find the mailserver= line that contains the SMTP server info.
  4. Update it if needed, restart the server and test.

 

For cloud customers, this can be found in the Web based Process Server Administration portal for your organization.

  1. Login into your organizations Process Server Administration portal
  2. Go to Configuration >> System Configuration
  3. Locate the “system” configuration name and double click it to open
  4. Under property name, find mailServer, edit the value if needed

That’s it!

Install and configure IPA Services for Lawson Applications

, ,

The IPA Services for Infor Lawson product (lpaservice.jar) contains the definition for each service.

These steps describe how to download, install and configure the services.

Download and install the services

  1. Download IPA Services for S3 from the Infor Product Download Center.
  2. Transfer the .jar file to your IPA server.
  3. Extract the contents of the .jar file to a new temporary directory.

jar –xvf lpaservice.jar

  1. Run the installation program from the temporary directory. Use the data area created in Landmark for IPA.

perl install-lpaservice.pl dataarea

  1. In order for Lawson applications to create workunits in IPA, standard workflow service data must be loaded onto the System Foundation (LSF) server.

In the temporary directory that you created, you will see the following directory structure and file:

YourTempDir/lsf/ wf-data-10.exp

Copy this file to your LSF environment in your normal install directory.

  1. Run the following command:

perl GENDIR/bin/pflowimpexp.pl imp wf-data-10.exp

NoteIf the installation provides feedback that some data was duplicated, you can ignore the message. This means that some or all of the workflow data already existed on the server which is not a problem.

  1. Verify that the services imported. View them on the IPA server. Navigate to: Start > Applications > Process Server Administrator > Configuration > Service Definitions

 

Configure email properties for IPA services

  1. From the IPA administration console on the IPA server, navigate to Configuration > System Configuration.
  2. Locate a configuration set named “ProcessFlowSolutions”.
  3. Verify that the configuration set should contains the following properties:
    • FromEmailAddress
    • ToEmailAddress

If the configuration set and/or the two properties do not exist, either re-install the product OR manually create the configuration to add the properties. Be sure to name them as shown above.

  1. Set the values of the properties to be meaningful for your organization.
  2. When you are finished updating, save the configuration.