In Lawson, your users may be experiencing a GL190 job in recovery.

 

You may be getting this error:

This is due to the GL190 job being ran when another GL190 job is running in the same jobqueue.

 

Locate the job in recovery (notice the Job Queue below *********):

Go to GLMONITOR, inquire on GL190 program. This will bring back all jobs in recovery here, only delete the one you plan on recovering, then do so for the remaining.

Once the GLMONITOR is cleared of that specific job, lets recover it and see if it completes (make sure no other GL190 jobs are active).

 

That’s it, hopefully this helped resolve your issue!

We recently had an issue with a new install where all batch jobs were going into recovery with the error “Unable to log in <username>”.  The can often be attributed to an incorrect password in the BATCH privileged identity, but in this case it was due to a typo in lajs.cfg.  The “RUNUSERKEY” field was misspelled.  So, if you ever encounter this issue, you can save yourself some time and get a couple of sets of eyes on the lajs.cfg file!  After making the change, reboot the Lawson server or stop/start services. You should now be able to log in.

 

 

When it comes to IPA security access, you can assign the following Lawson delivered roles to IPA users:

 

Delivered role Intended for use by Contains these security classes
InbasketUser_ST Normal end-users who receive work items in the Inbasket BasicProductLineAccess_ST

ProductLineAccess_ST

InbasketUser_ST

Lpa_ST

ProcessSchedulingAllAccess_ST

JobQueueServer_ST Users who must perform actions on the Landmark job queue. BasicProductLineAccess_ST

ProductLineAccess_ST

JobQueueAccess_ST

ProcessDesigner_ST Process developers BasicProductLineAccess_ST

ProductLineAccess_ST

Lpa_ST

ProcessDesigner_ST

ProcessSchedulingAllAccess_ST

ProcessServerAllAccess_ST IPA system administrators BasicProductLineAccess_ST

ProductLineAccess_ST

Lpa_ST

LpaAdmin_ST

ProcessServerAllAccess_ST

ProcessSchedulingAllAccess_ST

ScheduledActionsAccess_ST

ProcessServerReadAccess_ST IPA assistant administrators, power users, developers ProductLineAccess_ST

ProcessServerReadAccess_ST

 

Searching JXplorer can be cumbersome when you have thousands of Lawson users and possible issues with “rogue” or “orphaned” identities being stored when trying to update identity information.

Below we are going to show how you can easily search for this information vs manually scanning thousands of users.

 

First Select the part of the LDAP tree to search from:

CTRL + F

 

Notice the “Starting Searching From” field, this search will search all trees below this.

Now go into your Text Filter tab and type in parenthesis the field and value you want, click search

 

It will automatically switch to the Results field and show your results:

You can then do another search within these results or go back to Explorer tab and CTRL+F again and it will bring your previous search up.

You can also get creative and search multiple fields and values with an “OR” search:

(|(cn=*jon.doe*)(mail=*jon.doe*)(uid=*jon.doe*)(lwsnssoListOfIDs=*jon.doe*))

This is an AND search:

(&(cn=*jon.doe*)(mail=*jon.doe*)(uid=*jon.doe*)(lwsnssoListOfIDs=*jon.doe*))

 

The | means OR, & means AND. So each field cn, mail, uid etc. have to all bring back a result for it to work. It’s best to use an OR search on average.

Remember, you can also save your searches:

As mentioned above, this is especially useful when finding users in JXplorer to remove any duplicate or “orphaned” RMIDs and Identities not showing up in Lawson Security.

 

Good luck!

To do a full manual recompile of a Lawson Program, follow these simple steps:

  1. Open a LID session
  2. Navigate to <LAWDIR>/<prodline>/map/default
  3. Run the command scrgen <prodline> <system code> <program code>
    1. for example: scrgen prod PO PO54
  4. Run the command xscrgen <productline> <program code>
    1. For example: xscrgen prod PO PO54
  5. Run the command lstinvk -q <prodline> <program code>
    1. For example: lstinvk -q prod PO54
  6. Run the command qcompile <prodline> <system code> <program code>
    1. For example: qcompile prod PO PO54
  7. Use the command qstatus to check the status of the compile

 

Once the compile is complete, check your program again. That’s all there is to it!

 

IPA Service definitions can be used to cause or trigger a process to run.

If your site has an event for which work units are delayed or not running for any reason, you can trigger a process to run using the Service Definition in Process Server Administrator.

A process, which is created using Infor Process Designer, routes and tracks the sign-offs that need to occur. In this case, a service, which is delivered with Lawson applications, triggers the launching of the process. It is also possible to create your own service.

  1. Access the Process Server Administrator and select Scheduling > By Service Definition.
  2. From the displayed list of services, double-click the name of the service that you want to trigger the process.
  3. Specify this information:

Work Title

Specify a name for the work item.

Filter Key

If filters have been enabled for users and tasks associated with this service, select an option.

Filter Value

If you are using a filter key, specify a filter value.

For example, if you selected City for a Filter Key, then Chicago might be a valid value.

Apps Key

Specify an application key.

Apps Value

Specify a value for the selected apps key.

  1. Optionally, on the Criteria tab, specify up to three levels of criteria.
  2. If variables are enabled for the service, the Variables tab is active.
  3. If links to documents or other information is available for use with this service, the Related Links tab is active.
  4. When you are finished defining the circumstances, click Actions > Save.

To trigger a work unit to process, follow these simple steps below:

 

First, you will need to access the Process Server Administrator screen and then select Scheduling > By Process Definition.

 

Next, select the process name and double click on it.

 

Then Select Actions > Start. You should now be able to trigger a work unit to process!

 

 

End of mainstream maintenance for SAP Crystal Server 2016 and support plan for SAP Crystal Server 2020

We are on Crystal Server/Reports 2016. Do we need to upgrade to Crystal 2020? I only see the 2016 version on the download site.

 

Infor BI 10.6.30 for Lawson S3/M3 now supports SAP Crystal Reports Server 2020 as a report’s server. As such, this should be reflected accordingly on the LBI installer. Changes were made on the installer to include CRAS 2020.

 

CRAS 2020 is backwards compatible with reports created in 32-bit. Users just needs to recreate the data source connections in ODBC to ODBC 64-bit using the same Datasource Name. This also means that users will need to install the 64-bit drivers and configure the settings from 32-bit to 64-bit. For MSSQL, the 64-bit drivers are already available once you already have it installed. For other data source type, download the respective 64-bit driver. Same with Lawson OLEDB, Infor has released a 64-bit version, uninstall OLE DB 32-bit and install the 64-bit version.

 

Since CRAS2020 is a 64-bit application, the JVMMaxHeap value can now be set more than the 3GB limit in D:\BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\CRConfig.xml

Open the CRConfig.xml file. Look for the following lines:

 

<JVMMaxHeap>64000000</JVMMaxHeap>

<JVMMinHeap>32000000</JVMMinHeap>

 

Change the JVMMaxHeap value more than the 3GB limit. Save and Restart RAS.

 

Please note that Crystal Designer 2020 will no longer work when installed in the same server as CRAS 2020. In CRAS 4.3 (CR server 2020), it is not supported to install both server side and client side in the same machine. Registry keys may get corrupted.

 

If you’re interested in moving forward updating your Crystal software, Nogalis offers MSP support to assist with upgrades and migrations.