You may be running Document Express with Lawson and Citrix Storefront and encountering this error. Before you jump to conclusions that this issue is related to Lawson or Citrix security, check these steps below.
The user is likely experiencing this error when trying to import invoices into Document express.
Make sure that all application related access is set in MHC.
Verify the user has Active Directory access to the import routine folder on the server where the invoices are loaded in from Lawson.
Lastly, verify the user has access to the import routine directly from Windows folder explorer. This path can be found in the import routine itself in document express.
Copy the import routine path, paste it into Windows folder explorer to verify access.
Conclusion: When the user imports the invoice in doc express, it downloads the file locally and opens it. Verify both channels are open for the user.
https://www.nogalis.com/wp-content/uploads/2020/10/Document-Express-error-52-Bad-file-name-or-number.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-10-06 08:09:092021-01-06 17:58:06Document Express error 52 – Bad file name or number
If you launch Rich Client and get a certificate error (particularly after a new Landmark install or update), here are the steps to update your IRC certificate.
Here is a sample error message that you might receive before you are even presented with a login screen:
You can resolve this issue either in the LPA web administration tool, or you can log into your IPA server as the lawson user, open a Landmark command window, and type the command “canvas64 gen”. These tasks are performed in the GEN data area.
In the search box, type “IRC” and select “IRC Trusted Certificates”
Go to Actions > Create
Add the certificate by file. Browse to a previously exported certificate (Base 64 cer format) and click the save button. The certificate details will be displayed if the certificate is valid.
https://www.nogalis.com/wp-content/uploads/2020/09/Certificate-Error-When-Loading-Rich-Client.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-10-01 08:32:572021-01-06 17:59:03Certificate Error When Loading Rich Client
We recently noticed some strange behavior in IPA. All of our work units were stuck in “Ready” status, and the few Work Units that actually had errors indicated a java heap space issue. Some of the work units weren’t showing that a log was being created. We were also getting a generic error when uploading IPA processes.
It did seem like there was some kind of space or memory error. A reboot of the server didn’t address the issue. We were investigating and just happened to look at the command line window that opens up with IP Designer. That was the only place where saw a useful error message. It indicated that the database file had run out of space.
The resolution was to increase the “Maxsize” property on the IPA database file. In SQL Server, this is in the Database properties, Files tab.
https://www.nogalis.com/wp-content/uploads/2020/09/Database-File-Space-Issues-That-Manifest-in-IPA-Errors.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-09-28 08:33:232021-01-06 18:02:44Database File Space Issues That Manifest in IPA Errors
As of October 31, 2020, Infor is no longer going to support Internet Explorer as a browser for accessing Lawson applications. According to Microsoft, the end of life for IE will coincide with the end of life for Windows 10, so this is not a notice for the end of life for IE. This just means that any future Infor patches will not be developed to function with Internet Explorer.
Lawson has been stable in Chrome since the later releases of version 9. It is also supported on Microsoft Edge Chromium and Firefox. There are some things you will want to consider before moving to a different browser:
Impacted Applications
Infor Lawson System Foundation (LSF) 10.0.X.0 release
Infor Landmark Technology Runtime 10.1.1.X and 11 releases
Lawson for Infor Ming.le 10.0.X.0 and 10.1.X releases
Infor Lawson for Ming.le Content Lawson applications 10.0.X release
Infor Lawson Mobile Supply Chain Management (MSCM) 11.X release
Infor Lawson Point of Use (POU) 11.X release
Infor Lawson Business Intelligence (LBI) 10.X.0.0 release
Infor Business Intelligence for Lawson (IBI) 10.X.0.0 release
All Infor Human Capital Management (HCM) products, including Infor Global Human Resources (GHR) and Infor Talent Management 10.1, 10.2 and 11 releases.
Design Studio 10 (the application) is going to continue to be supported in Internet Explorer
Design Studio forms might need some updates to make them compatible with a different browser. Design Studio relies heavily on JavaScript, and some of the syntax is browser-dependent. Make sure you test all of your design studio forms before having users switch browsers.
MSCM
MSCM 10 is not compatible with Chrome. Infor will continue to support Internet Explorer with MSCM 10 installations until the end-of-life for MSCM 10.X.
MSCM 11.X (base, POU, and SIM) is compatible with Chrome, and it is recommended that you get to v11 as soon as possible! Contact us if you need help upgrading.
Recommendations
Switching browsers should be pretty seamless. Just have your users spend a week performing their daily tasks in your organization’s chosen browser, and log any issues that arise. If they hit a wall, they can always move to IE until a workaround is provided.
Upgrade MSCM! If you own licensing for MSCM, the update should already be available to you.
As always, check the Infor Lawson compatibility matrix to get the latest information in application compatibility.
https://www.nogalis.com/wp-content/uploads/2020/09/Infor-Support-Ending-for-Internet-Explorer.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-09-17 09:37:282021-01-06 18:05:06Infor Support Ending for Internet Explorer
If your organization has custom websites that need to be secured quickly and easily, you can use the IIS internal authentication and authorization rules.
First make sure that your host server is set up to utilize Windows Authentication. In Roles and Features > Server Roles > Web Server (IIS) > Security, install “Windows Authentication”.
Once Windows Authentication is installed, select your site in IIS and select “Authentication”
Set Windows Authentication to enabled
Go back to your website, and select “Authorization Rules”
From here, you can give access to individual users or Active Directory groups. The users will be presented with a Microsoft credentials dialog, and they will log in with their Windows credentials.
https://www.nogalis.com/wp-content/uploads/2020/09/Securing-a-website-using-IIS.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-09-14 09:01:052021-01-14 15:39:42Securing a website using IIS
If AD FS is configured to use the Windows Internal Database (WID) server, there are a couple of ways to maintain the databases created in the install. They can be maintained using command-line sql or SQL Server Management Studio. The AD FS configuration databases are called AdfsArtifactStore and AdfsConfiguration.
Not that both of these methods need to be performed on the server where AD FS is configured.
Command-line SQL
Log into the AD FS server using the service account under which AD FS was configured.
To prepare the server to run SQLCMD.exe, you will need to install the Native Client, ODBC Driver 11 for SQL Server, and the Command Line Utilities for SQL Server 2012. These can be downloaded from Microsoft’s website.
Once these utilities are installed, create two “.sql” files using a text editor, one for the artifact database and one for the configuration database. The following text should be placed in the sql file (update with the appropriate names and file paths). The database names are AdfsArtifactStore and AdfsConfiguration.
BACKUP DATABASE [database name] TO DISK = “backup-path/backup-file.BAK” WITH NOFORMAT, INIT, NAME = “Artifact – Full Database Backup”, SKIP, NOREWIND, NOUNLOAD,STATS = 10
GO
Next, run the sqlcmd to execute a SQL script (provide the name of the script you created in the step above).
The WID server can also be accessed using SQL Server Management Studio (SSMS). Note that SSMS must be installed on the server where AD FS is configured in order to be able to connect.
Log into the AD FS server using the service account under which AD FS was configured. Run SSMS as administrator. Connect to the server \\.\pipe\MICROSOFT##WID\tsql\query, and use Windows Authentication to connect.
The AD FS configuration databases are AdfsArtifactStore and AdfsConfiguration. As long as you logged into SSMS as administrator, you should have admin rights on these databases to perform backups, run queries, etc.
https://www.nogalis.com/wp-content/uploads/2020/09/Backing-up-the-AD-FS-internal-databases-on-Microsoft-Server-2012.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-09-09 08:16:362021-01-14 15:40:37Backing up the AD FS internal databases on Microsoft Server 2012
A user in Lawson is unable to login to their account. Username or password is incorrect. Assuming your organization is using single sign-on through Active Directory, you can verify the user’s username via Windows powershell.
Login into Lawson Security Administrator (or SCWeb Admin App). Locate the user and copy the username.
Open powershell and check the user via this command: Get-ADuser -identity <username>
If you receive this error: “Cannot find an object with identity”, the user is not setup in AD under that username.
Check with the organizations IT team to verify the correct AD user (assuming you don’t have direct access).
Once they send you that ID, check via powershell again and it should return this result:
https://www.nogalis.com/wp-content/uploads/2020/09/How-to-verify-Lawson-user-AD-identity-through-Windows-powershell.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-09-03 10:01:412021-01-14 15:42:21How to verify Lawson user AD identity through Windows powershell
Though this is a fairly simple task, it typically requires higher access (sometimes temporary access as some organizations only want users deleting journal entries once or twice a month).
Login to Lawson portal and go to GL70.1
Enter the company and journal entry number, hit Inquire.
Click the “New Entry” button
This will take you to GL70.2 and contain the same company/entry number (if not, enter again and hit inquire).
After inquiring again, hit Delete and confirm the journal entry has been deleted.
And you’re done!
https://www.nogalis.com/wp-content/uploads/2020/08/How-to-delete-a-recurring-Journal-Entry-in-Lawson.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-08-26 07:17:182021-01-14 15:45:07How to delete a recurring Journal Entry in Lawson
You may need to access APMONITOR for a failed job etc. Its usually as simple as searching APMONITOR in Lawson Portal. Often times its not setup in Lawson security and needs to be added.
In Lawson security, go to the class you want to add APMONITOR to.
Add a new rule and go under Online system code AP and search for token QAPM, grant all access.
Clear server cache and log back into Lawson, search APMONITOR and your user should now be able to access it.
NOTE: As of March 2016, patch (CTP104021, JT-751224) has changed the token for APMONITOR to AP94.
https://www.nogalis.com/wp-content/uploads/2020/08/APMONITOR-not-found-or-accessible.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-08-20 08:14:272021-01-14 15:46:52APMONITOR not found or accessible