When testing the FTP connection on a Lawson Back-office data source in LBI, you may receive the error message “System Directory Not Available”.  You may also see this message in the SystemOut.log on the LBI server when the system is testing the connection.

Here are some troubleshooting steps when you encounter this issue:

  1. Open a Windows command prompt on LBI server
  2. ftp <lawson application hostname>
  3. log in as <ftp user>
  4. cd <application home path>
  5. ls (You should see the ‘system’ directory listed here.  If not, that is the source of the “system directory not available” error). If you see the system directory, continue:
  6. cd /system/ers/backoffice/<pdl>
  7. get published.csv
  8. del published.csv
  9. put published.csv
  10. cd <application home path>/print/username/jobname/1 (use a username and job name for a published report, or any job if you have nothing published yet.)
  11. get <JOBNAME>.prt
  12. del <JOBNAME>.prt
  13. put <JOBNAME>.prt

NOTE you can also use an ftp client such as Filezilla to check for the file

Once you have ensured access to all of the above directories over ftp, you should find the following message when you test the FTP connection.

Intuitively you may assume that you can access scheduled processes in the Lawson Process Server Administrator main toolbar:

This becomes more frustrating because you would assume it would be under “Scheduling”. After all, this is supposed to be Infor’s convenient move away from the clunky Rich Client app.

 

To access your existing scheduled processes, you need to go to the top right where your user is and click there and select “My Actions”, NOTE: you’ll need to be logged in as the system user

This will take you to your Scheduled Actions as show below. Double click the Name to modify the schedule and you’re set after saving!

Here’s how to update IPA to add emails on the following error:

 

WU_Name.ipd

 

First, load the IPA and go to create process that checks for file, click on Error tab, copy TO, paste in CC but change to ManagerNoticiation.

What should happen on Error? STOP Process. (it is already on Stop Process so it will notify)

 

Next, click on the File tab then SAVE the changes.

 

Then Upload it

 

Next, go back to the Configuration Manager

 

Then go to Main and create or update ManagerNotification to include the email address(s)

Finally, look at process version

 

 

Follow these steps below to learn how to Access and elect an older IPA Process Version History:

  1. You can access via Rich client or web based Process Server Administrator:
    • Process Server Administrator – configuration >> Process Definitions >> User Defined Processes
    • Rich Client – Process Server Administrator >> Configuration >> Process Definitions >> User Defined Processes

 

  1. Double click the process:
  2. Under Process Versions >> Right Click the version you want >> Make Current Version

 

You’ll also see new versions here once uploaded from IPD.

 

If you upload the ACH file generated by PR160 to your bank, chances are you will need to fix the formatting after your upgrade to version 10.  Some banks require the 94-character fixed width format, rather than the sequential format that is the Lawson default.  Here are the steps to update your ACH file format.

  1. In LID, type in the command workdef
  2. Search for your product line and the File name TAPE

  1. File Media should be “Tape”
  2. The default “Value” for file name is PR160-ACHTAPE. If you need to drop the file under a custom name, you will enter it in the “Value”.  If you want to keep the default, leave that field blank.
  3. Click enter twice to save your changes
  4. The PR160-ACHTAPE file is defaulted to save in the user’s print directory. If you want it saved somewhere else, you can supply the filename on the PR160 job.  If you supply a file path on PR160, make sure the file name matches the “Value” field in workdef.

  5. In Lawson Security, make sure that your Batch role has access to the cnvexp development token

 

Sync has seven phases.

When it fails, it will create a locked process and it can be resumed from the last completed phase.

All errors are written to lawdir/system/security_provisioning.log. Sync can be cancelled altogether with ssoconfig.

Sync will always identify some conflicts. Follow the instructions in the ISS Configuration guide to know which conflicts can safely be ignored.

For example, it might fail to sync an environment identity for a user. Try creating or deleting that environment identity in Landmark under the Gen profile manually using Rich Client, then rerun the sync identities phase.

Once federation is complete use the ISS website for all user maintenance tasks instead of LSA. Grant the actor role SecurityAdministrator_ST to anyone who needs the ability to maintain Lawson user accounts.

Update or rewrite user provisioning scripts to work with the newly federated environment. Use ISS list-based sync functionality.

Here is a simple step-by-step guide on how to setup a distribution group in Lawson for a jobdef.

  1. Login into Lawson Interface Desktop (LID) and type in: grpdef
  2. Create a group name and add users to group
  3. Create a distribution list using command: dstlstgrpdef
    1. Add your group from step 2 to this new Distribution list
  4. Open jobdef select job you want >> Select step and press F6 >> B. Report Distribution
  5. Now arrow down to Destination and set as Dist Group, under Group/* Print, type your group name or Distribution List. This should populate a list of users on the right side.
  6. So when this job runs, the PRT and Error file will be placed in these users print directories. Press Enter twice to save changes.

If you found this article helpful, Nogalis offers managed services and expert technical resources to assist with Lawson system configurations like setting up distribution groups. Whether you need help managing user groups, optimizing workflows, or maintaining your Lawson environment, our managed services provide the support you need to ensure smooth operations. Contact us to learn more about how we can assist with your Lawson system.

Problem:

When I click on the LBI bookmark in my Lawson screen, I get an error message stating the URL redirected you too many times. This only happens when using the EDGE browser. It did not happen in Chrome.

 

Resolution:

Open settings in EDGE and go to Cookies and site permissions>>Cookies and data stored>>Cookies and site data and make sure the Block Third-party cookies is not off.

Turn on the following:

Now refresh cache and clear your cookies.

Note: adding any exceptions may cause the same issue, so make sure to remove any exceptions under Allow or Clear on Exit.