How to load email devices into LBI

,
  1. In LBI, open Reporting Services Report Administration
  2. Under Server Administration click on Email and Printer Settings:
  3. Select All Devices to see current list of devices and note the device type (important for loadfile):
  4. Now lets build the loadfile in CSV format:From left to right, the columns are <ownername>, <username>, <user email>, <Device Type>If it’s a printer, replace username and user email with <printername> and <\\networkprinter>
  5. Now lets import the file with Import Devices:

If there are any errors, it will let you know, if not, you can check All Devices section to see if your device loaded in.

Many organizations opt to engage Lawson consultant teams for managing their Lawson Security and LBI systems. These consultant teams offer managed services at a fixed monthly rate and possess extensive knowledge and expertise. This service is particularly suitable for larger organizations, but smaller organizations that do not require a full-time Lawson employee on-site may also find it beneficial. Nogalis provides this service, and you can contact us via our contact page for further information.

Compile Error Key Number Does Not Exist

, ,

There are times when you may encounter the following error message, “Fld Error: Key Number Does Not Exist”. This can appear when attempting to compile a 4GL program in Lawson, it is possible that the key needs to be added to kndef.

Note that this error message will likely present itself in the XXXX.scr.err file.

To resolve this error, simply follow the steps outlined below:

  1. Login to LID
  2. Run command kndef to define the missing key
  3. cd LAWDIR/(productline)/sdlib
  4. rm *
  5. srgen (productline) (source)
  6. qcompile (productline) (source) (program)
  7. recompile any other invoked programs

Your error message should now disappear and the program should run normal.

EX542 error – Invoice Already Exists

, ,

Lawson Expense Management can occasionally lead to a duplicate invoice or another issue. If you’re running the EX542 and it goes into status 1 or 2 (in process or error) in EX20.1 and EX20.2 for your expense report.  Then you’ll likely see an error saying “Invoice Already Exists”.

 

To resolve this, you may need elevated privileges. If you believe you have the access, follow the steps below.

  1. Go to EX20.1, inquire on your ER number.
  2. Change the status to 9 and click Change.
  3. Go to EX20.2, inquire on your ER number (locate the ER with the error field “Invoice Already Exists”
  4. Change the status to 9 and then remove the error field. Click Change.
  5. Re-run EX542 and see if it completes properly.

That it! If you’re still having issues and Infor is not able to assist, it might be worth looking into Lawson Managed Services (MSP). Reach out to a Nogalis representative to see if they can assist and or to provide your organization 24/7 Lawson support from an entire team of consultants at a fixed rate instead of having to hire a full-time position.

Using tokendef to add a user menu

, ,

tokendef: Using tokendef to add a user menu with a couple of different forms as menu options in Portal.

 

Trying to use ‘tokendef’ to add a user menu with a couple different forms as menu options, specifically for AP90.1 and AP90.2.  In Portal the menu launches (the menu name appears at the top), but the menu options do not display.  An XML error may also be encountered in Portal when trying this.

Resolution:

To setup this up correctly, menu names that are going to be used in Portal, must be in a XXXX.01 format, where ‘X’ is a letter or number.

 

After creating a new menu using tokendef you will need to run an IOSCacheRefresh otherwise, you will get an error stating bookmark not found in Portal when trying to access the new menu.

Restoring existing Lawson Cloud Security Users – Unable to Authenticate Error

, ,

When restoring an existing cloud user in Lawson security (that was previously disabled), you have to match the mingle IFS ID with the SSOP identity.

 

  1. Go to mingle >> User Management

  1. View a user and under details look for the IFS User GUID
  2. Go to your orgs Infor Security Service webpage and edit the users identity
  3. Under SSOP Identity, (delete existing one) and copy the IFS User GUID in step 2 in the user field.
  4. Type in any password in both fields and click Save

 

 

This should resolve the authentication error.

 

Here is a screenshot of the whole process (ISS on left, Mingle User Management on right):

Good luck!

Lawson Portal: Requestor does not exist error when logging in to Portal and selecting the shopping link for RQC

, ,

At times your user may get the error “Requestor does not exist” when logging into Lawson Portal and selects the Shopping link for Requisition Center.

 

This is because a valid Requestor must exist in Manage Identities in the Lawson Security Administrator (LSA) application.  To verify this, follow these steps:

1)  Login to the LSA Application

2)  Select User Management

3)  Select Manage Identities and verify the correct Requestor is populated

4)  Upon entering RQC/Shopping and the User’s Profile in Shopping where you see the user’s Requester, if it’s not showing the correct Requester, have the user click on the “New” button in the bottom-right-hand corner of the screen.

 

Note:  After any changes are made in LSA, upon re-entering RQC XML, you need to go into the Utilities link (rqc/html/utility.htm) and click on the RQC IOS Cache Refresh button before accessing the Shopping link again in RQC.

Error: ‘Access/Excel connection is no longer supported

, ,

Description:

Error: ‘Access/Excel(DAO) connection is no longer supported…’

Report based on Excel, Access, or a Text file fail to refresh in Crystal Reports.

Could successfully refresh the report in previous version of Crystal Reports.

When refreshing a report connecting to MS Excel, or MS Access, or a Text file in Crystal Reports, it fails with the error:

 

“Failed to load database information.

“Details: Access/Excel(DAO) connection no longer supported,

use another alternative if possible, e.g. ODBC/JDBC.”

 

Followed by:  “Failed to load database information.”

 

 

Steps To Reproduce:

  1. In Crystal Reports 2016 or below, create a new report.
  2. In the Database Expert, under “Create New Connection” double click on “Access/Excel (DAO)”
  3. Select the MS Excel, or MS Access file to report from.
  4. Refresh the report, and it successfully display data.
  5. Save the report.
  6. In Crystal Reports 2020, open the same report, and refresh it.

It generates the error: “Failed to load database information. Details: Access/Excel(DAO) connection no longer supported,…”

 

Cause

  • The report connect to Excel, Access, or a Text file using Microsoft Data Access Objects (DAO), which used Microsoft JET Engine.
  • This 32bit only connectivity technology have been deprecated by Microsoft.
  • Previous versions of Crystal Reports were 32bit applications, and could still use the deprecated Microsoft DAO technology to connect to Excel, Access or a Text file, as a legacy connection type.
  • Crystal Reports 2020 is a 64bit application, and therefore it is no longer possible to connect to Excel, Access, or a Text file using DAO, since there is no 64bit version of this deprecated Microsoft Technology.

 

Resolution:

  • Use an ODBC connection to connect to one of the following data sources in Crystal Reports:
    • MS Excel
    • MS Access
    • Text file
  • For MS Excel, and MS Access, you can also use an OLEDB Connection.

 

To use an ODBC Connection:

  1. Launch the 64bit Microsoft ODBC Data Source Administrator. (C:\Windows\System32\odbcad32.exe)
  2. In the 64bit Microsoft ODBC Data Source Administrator, under the tab “System DSN”, click “Add…”
  3. Select the ODBC Driver corresponding to the type of document you want to report from:

– For MS Excel, select   : Microsoft Excel Driver (*.xls,*.xlsx,*.xlsm,*.xlsb)

– For MS Access, select : Microsoft Access Driver (*.mdb, *.accdb)

– For a Text file, select  : Microsoft Access Text Driver (*.txt, *.csv)

 

Note

If you do not see the ODBC Drivers, then it is either because you have a 32bit version of MS Office installed, or do not have a 64bit MS Office installed. To download and install the 64bit version of the Microsoft Office ODBC drivers, go to the Microsoft website, and search for: “Microsoft Access Database Engine”, then download and install the 64bit Microsoft Access Database Engine.

  1. Then click “Finish”
  2. Add an ODBC DSN Name and select the MS Excel, MS Access, or Text file you want to report from, and click “OK”
  3. In Crystal Reports, open your report based on MS Excel, MS Access or a Text file.
  4. Under the menu “Database”, select “Set Datasource Location”
  5. In the “Replace with” section, expand “Create New Connection”, and double click on “ODBC (RDO)”
  6. Select the ODBC DSN created in the previous steps to report from MS Excel, MS Access, or aText file.

Note: For MS Excel, if the Excel sheets are not visible, then:

  1. Right click on the “Connection”, and in the contextual menu, select “Options”
  2. In the “Options” window, check the option “System Tables”, and click “OK”
  3. Back to the “Database Expert” window, right click on the connection, and select “Refresh”
  4. The MS Excel sheets will now display. Select the desired MS Excel sheet.

 

  1. Once connected, in the section “Replace with”, select the new ODBC connection, and in the section “Current Data Source”, select the current connection, and click the button “Update”
  2. Once the connection is updated, click “Close”
  3. Back to the report, save the report.

 

To use an OLEDB connection

  1. In Crystal Reports, open your report based on MS Excel or MS Access.
  2. Under the menu “Database”, select “Set Datasource Location”
  3. In the “Replace with” section, expand “Create New Connection”, and double click on “OLE DB (ADO)”
  4. Select the Microsoft Office Access Database Engine Provider.

 

Note

If you do not see the OLEDB Provider, then it is either because you have a 32bit version of MS Office installed, or do not have MS Office installed. To download and install the 64bit version of the Microsoft Office ODBC driver and OLEDB Provider, go to the Microsoft website, and search for: “Microsoft Access Database Engine”

  1. Change the Office Database type to: Excel, or Access
  2. Select the MS Excel, or MS Access file.
  3. Leave the User ID and Password blank.
  4. Once connected, in the section “Replace with”, select the new OLEDB connection, and in the section “Current Data Source”, select the current connection, and click the button “Update”
  5. Once the connection is updated, click “Close”
  6. Back to the report, save the report.

Refresh user list in LID

, ,

If you have added environment users in Lawson, and you are not seeing the new users in listusermap, there’s an easy fix for that.

You will need to run it with the command -a.  This will refresh the cache and show all users in NT order.

listusermap -a

 

If you would like to run other commands, here are some other tips for the listusermap usage:

-a – list all users,

-c – list from cache (Default),

-n – clean up cache,

-u – find user,

-p – find account,

-h – find historical user (NTxxxxxxxx),

-o – show historical user names in list,

-k – list archived user cache

How to Gain access to Infor Reporting Tools

, ,

To gain access to Infor Reporting to create and edit reports, you’ll need to make sure your organization first has the license for the software. Consult with Infor before moving forward.

 

Example of Infor Reporting Icon:

The above screenshot shows how a user may gain access to view Infor Reporting Reports. These can be reports that show Expense Reports, User Proxies, etc.

 

To gain access to the administration tools, you’ll need to assign these two roles:

XM-AdvancedBusinessAuthor – Allows access to canned templates (example reports to build off of)

XM-ProfessionalAuthor – Allows freeform access to create new and edit existing reports.

 

These roles must be assigned in Mingle under user management tab

 

Good luck!

Lawson Portal 404 Error

, ,

If you receive the error message in Lawson Portal “The Server has not found anything matching the requested URI”, check the WebSphere SystemOut.log for the message “Failed to load webapp: context root /* is already bound.”  This means that one of your WAS applications (most likely the default app) is configured to start before the Lawson IOS application.  To fix this, either delete the Default Application, or configure its startup behavior.  Go to WAS Console > Applications > Enterprise Applications.  Click on the Default Application then “Startup behavior.”  Change the startup order to some larger number so the Default Application will attempt to start last in the order.  Save the changes and synchronize the nodes.  Then, start your IOS application.