ujobload fails in lawappinstall activate

, ,

During patch install, if customizations exist, the activate will fail on ujobload

lawappinstall ACTIVATE installation started at 11/14/2024 15:48:00 for the following deliverables: PATCH121887.57 PATCH121211.58 PATCH126341.59.
command line = ‘E:\lawson\gen/bin/lawappinstall activate test10’.
11/14/2024 15:48:03 Bypassing Database preparation. Already successful.
11/14/2024 15:48:03 Bypassing blddbdict. Already successful.
11/14/2024 15:48:03 Executing dbreorg listing.
11/14/2024 15:48:03 dbreorg listing execution successful.
11/14/2024 15:48:03 Database change confirmation.
11/14/2024 15:48:07 Database change confirmation successful.
11/14/2024 15:48:07 Database reorganization confirmation.
11/14/2024 15:48:09 Database reorganization confirmation successful.
11/14/2024 15:48:09 Executing dbreorg.
11/14/2024 15:48:09 dbreorg execution successful.
11/14/2024 15:48:10 Executing ujobdump for TEST10.
11/14/2024 15:48:10 ujobdump execution successful.
11/14/2024 15:48:10 Executing ujobload for TEST10.
11/14/2024 15:48:10 ERROR – ujobload failed.

 

Resolution:
Review the lawdir/prodline/backup/ACTIVATEstage/JOBconversion.dmp file for user jobs that need to be deleted from jobdef.

  1. open up that dmp file and see what the actual job names are.
    Look for #> NTID JobName
  2. Look up the username for each of the NTID
    In portal, under LSF Administrator Tools, username lookup
  3. Go into jobdef and delete the job that it is failing on for each user.
  4. Once jobs have been deleted, run lawappinstall activate again and it should now complete successfully.

 

How to Analyze a Cloud-based Log Quickly in Lawson

, ,

In a Lawson Cloud environment, its difficult to get logs off the server since now you’re likely restricted to FTP access and the latest logs are currently being written to by the server itself, thus throwing a deny exception when trying to download the latest logs from FTP.

I previously made another article on this explaining a work around for this but that takes a few extra steps and time. This is a quicker command line method if you need to test something immediately.

 

  1. First login to Lawson Interface Desktop
  2. Go to the directory in which the logs exist
  3. Type this command: tail -500 <name of log file being written to> | lashow
  4. Example: tail -500 ios.log | lashow

As you see above, this uses the tail command combined with -500 parameter which returns the last 500 lines written to the log. You can change -500 to whatever amount of lines you want to return (the more the longer it takes to load)

The optional piped LASHOW command is to open this in a separate scrollable and searchable window within LID.

This becomes especially useful when testing live forms or code in Lawson.

If you found this article helpful, Nogalis offers expert managed services to optimize your Infor Cloudsuite or Lawson environment. From troubleshooting log issues to streamlining processes, we provide tailored support to keep your system running efficiently. Contact us to learn how we can enhance your Lawson Cloud experience without the overhead of full-time staff.

Error – NO_ACCESS_ALLOWED  for Lawson Enterprise Financial Management Application

, ,

Issue: You may come across an issue where a user is getting a NO_ACCESS_ALLOWED error when trying to access Infor Lawson Enterprise Financial Management (See Screenshots Below)

 

 

Solution: To resolve this issue, in Mingle, go to OS >> Security. Please note that admin rights are needed to access and make changes to the security screen for your user(s).

Next, search for the user and select their profile:

Under “Security Roles”, click the plus sign to add, then search LAWSONLMFIN-USER. Make sure it’s added to their security settings.

Finally, click “Save” to keep the changes made. The user should now have access!

Using Event View to Troubleshoot Lawson Errors

, ,

Sometimes Lawson errors can be very cryptic and difficult to troubleshoot.  Sometimes you will have a very specific error in the ios.log or other system logs, and a search on Concierge produces ZERO results.  It can be quite frustrating!  Don’t forget that you have another place to check for errors.

 

Use Event View

Always remember to check your Windows Event Viewer for another “perspective” on the error.  Sometimes a Google search or even Concierge search on the error text in Event Viewer will actually produce results where the log search didn’t.  Some examples I have found are an error in the importdb script, which provided more information for an Infor ticket I had open, and a MicroFocus license manager error that led me to a KB and a download that solved some performance issues for us.  So, the bottom line is, don’t forget to check server logs in addition to Lawson and WebSphere logs!

Users can’t submit batch jobs

, ,

Problem:
After user provisioning, your user cannot run batch jobs. When they click on submit and then submit in the pop-up box they get a security violation error. If the batch role is assigned to them that is not the problem. The error message is likely due to the job queue’s status is secure.

 

Resolution:
The “batchrole” should be assigned to the users. This role only works if only one queue is defined which is usually the ******* job queue. If multiple job queues are defined then go into the “batch” security class under the ENV profile and add each job queue to the class.

Copying User Jobs Between Environments

, ,

These are instructions for copying user jobs (by user) between environments.  This will NOT allow you to copy jobs between environments on different versions of LSF of Lawson applications if the job parameters have changed between versions.

  1. Run listusermap in both environments and make note of the NTID for the user in each environment
  2. In the source environment, run the command
jobdump –d –o job –v UserName “DOMAIN\UserName” outputfile
  1. Open the output file created by the command in a text editor
    1. Update any references to the NTID from the source system with the NTID of the destination system
    2. Make any directory structure changes as needed (i.e. change “D:\lsfprod to D:\lsftest”)
  2. Copy the output file to the destination system
  3. In the destination environment, run the command
jobload –c –o job inputfile

 

More on jobdump/jobload

 

ERROR – Reorg control file reorg.cntl exists when trying to Activate a CTP

, ,

Problem:

You are having this issue: I’m getting a reorg error when trying to Activate a CTP

“ERROR – Reorg control file ‘D:/lawson/db/APPS10/reorg.cntl’ exists.  It appears the database is in the midst of a reorganization.  Please complete before Activating.”

 

Resolution:

Follow these steps to resolve the error.

  1. In LID, run this command: dbreorg -d <Enter_Your_Productline_Here>
  2. Once it completes, run the lawappinstall again:
    1. perl %GENDIR%/bin/lawappinstall activate <productline>
  3. After this, run the verifymsf2000 to validate the dbdict and database are in sync:
    1. %gendir%/bin/Verifymsf2000 -u <your_lawson_user> -p <your_lawson_password> <your_productline>

This usually occurs when a reorg wasn’t completed previously on another CTP. Good luck!

Using the Field Prefix to Find a Column in SQL

, ,

Below is a useful tip for using the field prefix to search for a column in SQL

Clicking Ctrl+Shift+O in a field on a screen in Lawson is a useful tool to determine what database file that field is populated by.  This can be used in Lawson DME Queries, but it also can be used in SQL queries.  The prefix of the field name (such as VEN) maps to the table name where the value comes from.  If you don’t know how the prefix maps to a table, you can easily find this information in the GEN database.  The table you want to search is FILEDEF on the PREFIX column.  So, your query might look something like this:

SELECT * FROM FILEDEF WHERE PREFIX = ‘VEN’

This will return the record that contains table name and other information about the database file that populates this screen.