You may have saw our article “How to load bursting rights into Lawson Business Intelligence” and encountered an error that your CSV file “exceeds the limit”.
To resolve this:
- Go to the Reporting Services server and open <application server directory>\ReportingServices\erswar-XXXX\
- Find and open the ersImportRights.jsp file in a text editor (backup before editing)
- Edit the following line:
- ERSFileUploadRequest multi=new ERSFileUploadRequest(request,”.”, 1024*1024);
- ERSFileUploadRequest multi=new ERSFileUploadRequest(request,”.”, 1024*1024);
- Multiply the 1024*1024 to the number of bytes you want to increase limit to. If you want it to be 10 MB max, the line would look like the below:
- Save the .jsp file
- Restart your app server, Websphere etc.
- Try importing the file again.
Good luck!
We provide several customers with our MSP services in Lawson and often are switching between several VPNs throughout the day. Our VPNs are fairly reliable but every once in a while, they fail to connect and only a reboot seems to resolve. Unfortunately, this means closing all of our current tasks and documents that are open and essentially stepping out of our work flow.
Follow these steps below to resolve your CISCO VPN connection issue:
- Close CISCO VPN by right clicking it in the bottom right Windows tray bar
- Open windows task manager with CTRL + SHIFT + ESCAPE
- Go to services and find vpnagent
- Right click it and select STOP, wait for it to stop completely.
- Right click it again and select START
- Open Cisco VPN again and try to connect once more. That’s it!
If you’re still having issues, it may be the VPN server you’re connecting to in which you’ll have to reach out to a dedicated Windows team for that client. Good luck!
You have ADFS setup on your server but addins is not working though the user is setup in Lawson with the proper security and addins flag enabled.
Steps to resolve:
- First make sure you have the proper URL in Addins
- ADFS is more strict so in most cases a secured port is required
- If your login is failing with this login box below, ADFS may not be authenticating correctly.
- Include port as seen in this example URL https://servername.organization-domain.com:1447
- The login box will appear differently as seen below:
- If your still having issue and the login page does nothing once the proper credentials are entered. Verify the user has a Thick Client identity assigned in Lawson Security Administrator.
TIP: The password for the thick client identity can be anything. As long as it is filled, it should allow ADFS to authenticate with addins. Good luck!
When Running PR160 or PR180 you may run into the error Ern2 Record exceeded limit size:
This is known to occur when the Earnings Record is blank on the Laser Print tab
- Update the Earnings Record parameter in PR160 or PR180.
- Rerun PR140.
- If PR160/PR180 gives an error of still running, restart PR00 by hitting delete function twice in PR00 to clear out * and R flags.
- Run PR160 or PR180 again and verify Earnings Record field is filled with a value.
Disabling a user in ISS vs LSA is pretty straight forward, however there are differences explained below.
When disabling a user in Lawson ISS, there is no “IsDisabled” field under the LSF tab as seen below:
So when disabling a user in ISS, you simply go to the top left and click on “Disable Actor”:
Once the page loads, search for the user again and you’ll notice the Disable Actor button is now called “Enabled Resource” (this is how you re-enable a user in ISS):
In LSA, you simply query the user >> Edit RM Information and set the “is disabled?” field to YES or NO:
The one advantage of disabling a user in LSA over ISS is that when you run certain user reports (custom or native), the disabled field actually shows YES or NO. This can be helpful to know when reviewing user security or running audits. (This can change in the future so please note this may not be the case anymore after this articles date).