Posts

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.

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.

How to resolve the Lawson Fax Integrator error

, ,

Follow these simple steps on how to resolve the Lawson Fax Integrator error(s):

“There was an error connecting to the server” or “The remote server returned an error: (530) Not logged in” (see screenshot below)

To resolve either of these, first navigate to the Servers >> Lawson tab, then make sure you use valid credentials for the FTP user.

Next, Under the Servers >> Portal tab, make sure that you have valid Lawson user credentials. If not, then enter the correct information.

Finally, click Update after entering your credentials. This will resolve the 530 FTP invalid credentials error. That’s all there is to it!

MHC An error occurred while viewing – Printer Issue

, ,

You may come across this error at some point – “MHC An error occurred while viewing – Printer Issue” (see screenshot)

 

This means that the printer below for this account is no longer valid.

 

See Print routine data here:

 

To update this, first add the network printer to server where Document Express is installed via windows Add New Device.

Once located, then double click within the box where the existing printer is and select the new one:

 

Save the changes and click view to see if the document shows up. You should now be able to print in Document Express and the error will disappear.

Lawson Error – loadResource returned identity already exists

, ,

This article shows you a step by step guide on how to resolve the following Lawson error:

“loadResource(): returned identity [User:] already exists“

We need to run a list-based sync but first let’s explain what it is.

 

How list-based sync works:
Initially, an XML file containing all the records to be synchronized is required for executing the procedure. Later, the ssoconfig utility is employed to import the file. As a result of the sync command, all the relevant data related to actors/users, identities, and their associated roles (and services if required) is transferred from the “original system” (the one with updated data) to the “target system” (the one in need of an update).

 

Note: Please keep in mind that when synchronizing, if a service is present on the original system but not on the target system, it will be generated on the target system. It is important to note that syncing of services is a one-time process.

By default, during synchronization, Actor Roles are included with other user information and combined. For instance, if an Actor record in the LSF has one role “NormalUser,” and the same Actor is present in Landmark with two roles “NormalUser” and “BenefitsClerk,” then after synchronization, both systems would display “NormalUser” and “BenefitsClerk” for that actor. However, if you prefer to prevent the merging of Actor Role attributes, you can override the default setting in the input file. In this case, you will be asked to decide between Update Local or Update Remote action for each difference, similar to other attributes.

 

Create the XML input file (default behavior for Actor Roles)

Prepare an XML file in the suitable format for importing. The following example depicts the standard approach, where Actor Roles are combined during synchronization.

 

Example File:

XML input file in which you specify behavior of Actor Roles

This instance contains the “mergeActorRoles” attribute, which is present in the file and set to “false.” Consequently, the roles will not be merged, and the specified action in the XML file will be followed instead.

NOTE:  If you require the merging of roles for some Actor records, you should adjust the “mergeActorRoles” attribute to “true.”

 

Example file:

Run the import command using the ssoconfig utility

  1. Execute the import command using the ssoconfig utility. Open a command window and enter the following command:

ssoconfig -S PWD <full_path_and>InputFileName

 

In this command, replace PWD with the security administrative password and <full_path_and>InputFileName with the name of the input file that you created in the previous step.

Once entered, a notification will confirm that the synchronization process has begun.

  1. To monitor the synchronization progress, navigate to the Check Background Sync Status option within the Manage Federation sub-menu.

Validate results.

How to resolve error: actor_does_not_support_run_as

, ,

After an install or an update, you may experience an error “actor_does_not_support_run_as” on certain node types.

Caused by: com.lawson.security.authen.SecurityAuthenException: com.lawson.security.authen.LawsonUserContextImpl.security.authen.actor_does_not_support_run_as
at com.lawson.security.authen.LawsonUserContextImpl.setRunAsUserOnContext(LawsonUserContextImpl.java:1498)
at com.lawson.security.authen.LawsonUserContextImpl.setRunAsUserOnContext(LawsonUserContextImpl.java:1461)
at com.lawson.security.authen.LawsonUserContextImpl.setRunAsUserOnContext(LawsonUserContextImpl.java:1452)
at com.lawson.security.authen.LawsonUserContextImpl.setRunAsUserOnDuplicateContext(LawsonUserContextImpl.java:1593)
at com.lawson.security.authen.DataCtxUserCtxWrapper.setRunAsUserOnDuplicateContext(DataCtxUserCtxWrapper .java:432)
… 15 more

To mitigate this issue, log into ISS, and go to Manage Users.  Search for the lawson user and click the Edit button.  On the Basic tab, set “RunAs Enabled” to “YES” and click save.  Wait for the configuration to take effect, or run a stoplaw/adminlaw/startlaw.

 

 

If you are not using ISS, the Landmark command to set the RunAs is:

secadm actor enablerunas lawson

After running this command, run the stoplaw/adminlaw/startlaw.

 

How to resolve Lawson XM Error – No XM User exists with User Principal Name

, ,

Lawson XM errors are never good, but can easily be resolved. For example, you make come across this Lawson XM error: “No  XM User exists with User Principal Name (UPN)” (see screen shot below)

This error can easily be resolved by checking the settings for specific permissions.

In LSF ISS you must make sure that the SSOP identity user matches the Second user Identity (IFS) in XM SAT. These parameters allow users to log in to Mingle XM via SSOP and allows users to log in to SAT. Once you confirm these permission settings, you shouldn’t have the error again.

 

Bookmark Error

, ,

Problem:

No matter what browser I use, when I go back to a bookmarked link I get the following error when I sign in:

 

“Error encountered while processing the request. Additional information: Bad request cache id. This URL request may already have been processed…”

 

Resolution:

There is a simple solution to this common error. This is not security-related, but rather a bad link that you may have bookmarked. It’s important to make sure you bookmark the correct link: https://hostname/lawson/portal,so you won’t get this consistent error. Note that if you try to copy the URL before you have fully logged in, the bookmarked link will not work again.

Resolving “Cannot run this program while GL190 is running” error when trying to release journal entries in GL40.1

, ,

You may run into this error at some point in GL40.1:

Fortunately, there’s an easy fix to this. First login to Lawson portal and search GLMONITOR:

In GLMONITOR, type in GL190 and hit Inquire, if you get results and notice the run time, the process is in fact still running and causing the issue with GL40:

Go to job scheduler by opening LID and typing in jobschd >> F7 + A to select all users >> Then W to go to waiting screen.

Look for any GL190 jobs running and verify the User Name is the same one in GLMONITOR when inquiring on GL190 program. Check the error and if its safe to recover, recover it and let the job complete.

 

Go back to GLMonitor and inquire on GL190 to verify the job is no longer running:

 

Go to GL40.1 and release your Journal Entries.  Good luck!

 

This type of work is typically done by a Lawson functional resource. Organizations often hire a Lawson consultant team who offer managed services at a fixed monthly rate. These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site. Nogalis does offer this as a service so feel free to reach out to us via our contact page.