Lawson job stuck in submitting status

, ,

Is your Lawson job stuck in a submitting status after clicking submit multiple times as shown below?

This commonly happens when a user returns to an organization and their access is restored or another users lawson jobs are copied over to this user. These jobs have been updated from CTPs or patches and may have old or corrupt parameters.

 

Resolution 1:

Try and simply create a new job in Lawson (deleting the old) and try submitting again. This is assuming the user’s security and identity are already setup correctly.

 

Resolution 2:

If the above doesn’t resolve the issue, the cause of the issue can occur when the users DOMAIN Identity is corrupt or out of sync in LDAP. This is the domain identity that controls the print directory found in “Managed Identities” when viewing a user in Lawson Security.

 

First backup the users print directory and do a jobdump command in LID to copy their jobs. The delete and re-add this DOMAIN identity to see if it resolves the issue.

 

If it doesn’t, you’ll need to delete the user completely and re-add them into Lawson. This can be done with the Lawson Security Admin tool. You can also download Jxplorer and see if LDAP is holding onto the identity (backup LDAP before editing/deleting any identities in Jxplorer).

 

Good luck!

Set debug logging on Lawson Security Rules

, ,

Follow the steps below to set debug logging on Lawson Security Rules.

 

Launch Lawson Security Administrator (LSA).

Select Server Management.

Select Server.

Select the Auditing + Logging tab.

Under Logging Levels on the right, click Debug.

Under the Select User to Log section type in the RMId of a user who should be logged.

Additionally, under the Select User to Log section type ALL in upper case*.

Click Apply.

After the security Caching Interval time is reached then perform the same action you need to troubleshoot.  Note the date/time you perform the action.

Collect the logs: On the Lawson server, the name and location of the log files are: LAWDIR/system/lase_server_*_*.log  and ios.log and ios.log(x).

To disable the debug logging in LSA, go back to the Auditing + Logging tab. Change the Logging Levels to Critical and highlight the RMId you added and click Remove, then highlight ALL and click Remove.

Lawson Error – Ask your administrator for access to other applications

, ,

A user logs into Infor OS or Lawson Mingle, clicks the waffle icon in the top left and encounters the below error:

“If you’re seeing this, ask your administrator to give you access to other applications”

 

Resolution 1 (Requires a Lawson Administrator):

Verify if the IFSSecurityRole has been assigned to the Application:

  1. In Infor OS, click on the User Menu and go to Admin Settings
  2. Within the “Manage Applications” section, double-click on the Application that the user is attempting to use (e.g., Infor Lawson).
  3. In the Application Details screen, choose the Permissions tab

On the Permission screen, you should see the IFSSecurityRoles configured for the application.

To grant permission to the user for the application, ensure that at least one of the listed IFSSecurityRoles is assigned to them.

 

Resolution 2 (Requires a Lawson Administrator):

Provide User Permission:

  1. Access the User Menu and navigate to User Management.
  2. In the Search field, search for the user
  3. After the user’s details appear in the search results, click on the User Details icon.
  4. On the user screen, proceed to the Security Roles tab.
  5. Click the plus sign in the upper left corner, choose the appropriate IFSSecurityRole, and click on ADD & CLOSE to grant permission.

Have the user sign out and sign back in to Infor OS after the change.

 

Updating Infor RQC Configuration

, ,

If you make changes to the rqc_config.xml file, you will need to deploy the changes to RQC. Luckily, this is a simple change.

To update or make changes to RQC, follow these steps:

Either go to http(s):/<lawson server>:<port>/rqc/html/utility.htm

OR

Open Lawson portal and navigate to Bookmarks > Requisition Center > Utilities. They both will lead you to the next screen where you will have a couple options.

By clicking “Reload Configuration File”, this will deploy your changes to rqc_config.xml. And by clicking “RQC IOS Cache Refresh”, this will refresh the RQC cache. See the screenshots below for reference. Your rqc_config.xml file is now successfully updated.

 

 

 

How to run Lawson Infor Reporting “Report Studio” and “Workspace Advanced” in Microsoft Edge using “Internet Explorer Mode”

, ,

Given Microsoft’s discontinuation of support for Internet Explorer, which is required for report creation, editing, and saving in Infor Reporting, an alternative browser setup is essential. Here’s a step-by-step guide for configuring Microsoft Edge to operate in Internet Explorer mode for Infor Reporting. Ensure to follow these steps carefully:

  1. Launch the Microsoft Edge browser.
  2. Access the “Settings” menu.
  3. In the left panel, select “Default Browser.”
  4. Set the “Internet Explorer compatibility” option to “Incompatible sites only (Recommended).”
  5. Set the “Allow sites to be reloaded in Internet Explorer mode” option to “Allow.”
  6. In the “Internet Explorer mode pages” menu, click the “Add” button and input the URL used for Infor Reporting:

As of 7/7/2022

  1. Log in to Ming.le.
  2. From the app menu, select “Infor Reporting.”
  3. In the Edge browser, click the “…” settings icon located in the top right corner of the screen.
  4. Toward the bottom of the menu, choose “Reload in Internet Explorer mode.”
  5. Optionally, enable the option to “Reload Reload in Internet Explorer mode next time.”
  6. Click “OK.”
  7. You might be redirected to the Ming.le login page; if so, log in again.
  8. Access “Infor Reporting” (it should now indicate that you are running in Internet Explorer mode).
  9. Select a report and open it for editing.
    1. Example for EU1 MT Cloud:
      1. https://infor-reporting.eu1.inforcloudsuite.com/InforReporting/
    2. Example for on-premise Infor Reporting:
      1. https://myreportserver:800/InforReporting/

 

For MT Cloud Environments via Ming.le

To make Infor Reporting function properly through Ming.le, an additional step is needed:

  1. Log in to Ming.le using the Microsoft Edge browser.
  2. Once logged in to Ming.le, open a new “tab” by clicking the “+” (plus) icon (or pressing CTRL-T).
  3. In the new tab, enter the URL for Infor Reporting, e.g., for EU1 MT Cloud: https://infor-reporting.eu1.inforcloudsuite.com/InforReporting.
  4. Infor Reporting should start, and your Microsoft Edge browser should display a top bar indicating “You’re in Internet Explorer mode.”
  5. This top bar can be closed by clicking the “x” icon in the top right corner of the screen.
  6. You can now launch “Report Studio” or “Workspace Advanced.”

Example:

 

By default, URLs added in the “Internet Explorer mode pages” menu will expire after 30 days and must be re-added. You can change this behavior using Group Policy or a Windows registry adjustment, as explained here.

 

Note: If you encounter an authentication error when opening a new tab in Ming.le (as shown below)

  1. Access your MS Edge browser settings.
  2. In the left panel, select “Privacy, search, and services.”
  3. Click on “Choose what to clear” in the “Clear browsing data” section on the right panel.
  4. Select all options and set the “Time range” to “All time.”
  5. Close all browser windows.
  6. Try again; the authentication error should be resolved.

Infor Landmark Cannot handle action type 3

, ,

If you encounter the following 500 service error “Cannot handle action type 3” when opening Infor Process Administrator, follow these steps to resolve the issue.

 

First go to the <server name>:<port>/ssoconfig/ssoCfgInfoServlet site to see if you can get a more descriptive message.  If the message there reads “Domain has been disabled”, this means the Domain for your Process Server Administrator site is disabled and needs to be enabled.  In Rich Client > Gen (Or the Gen web admin), go to Security System Management > SSO Domain, and select the Domain for your site.  Click the check box to enable it, then flush the GEN configuration, or reboot the server. Refer to the screenshots below for guide.

 

Set Timeout Duration to Timeout After No Activity

, ,

Portal Timeout

To configure a timeout duration for users’ session to timeout after no activity

 

The Lawson delivered default value for session timeout is 60 minutes.  If you wish to change the timeout duration, you can use the ssoconfig utility to change it at any time.  The timeout value does not affect performance.

To change the SSO timeout parameter complete the following steps:

  • From a command type: ssoconfig -c
  • Enter the ssoconfig password.
  • Select “1” to Change Single Sign-on Server settings
  • At the prompt to “Choose the protocol for use to connect to the Lawson authentication service”, do NOT make any changes. Type the number that corresponds to your existing setting (either SSL or TCPIP).
  • At the prompt for “Enter the service to use to sign on (SSOP),” press Enter to bypass the prompt. You do not want to make any changes here.
  • At the next prompt, enter a timeout value in minutes.
  • Restart WebSphere Application Server (WAS).
  • To verify that your change worked, run http://hostname/ssoconfig/SSOCfgInfoServlet and look for the “sessionto” property, for example:
  • <PROPERTY name=”sessionto” value=”30″/>

 

Note:

The SAML Token Lifetime value is equal to the “sessionto” from SSOCfgInfoServlet.