Archive for category: Articles

Common Problem: User XXXXXX does not have update authority for folder XXXXX

This is an error you may run into when a user doesn’t have report writer permissions to add to a folder.

To resolve this, follow the example below:

This will take you to RW03.1 (you can also go directly to RW03.1 if you know the user class name)

Once you have the user class selected, set FC to A, add your users ID, set flags and press change. If list is full, press Page Down key.

In Requisition Center, we are seeing an error next to the item we are ordering.  Hovering over the exclamation icon, we see the message:  “Error – 70500 is not included in account generation list”  How can we resolve this? 

In the item master, IC11.1, the account on the item is 6400.  If you go to GL20.1, you can inquire on the accounting unit 70500 and then click on the Accounts button for GL20.2.  Paging down will take you to account 6400.  There is an “Exists” column that shows No.  If you mark the line for add and change the accounting unit, the account will be changed to Exists Yes.  You should then be able to continue with the requisition without the error message. 

RQC

IC11.1

GL20.2

We traditionally think of managed service as a hosted solution. But what about all the applications that must stay in-house? Depending on the industry there are state or federal regulations and compliance matters to consider when deciding where and how to host your application. Your PCI data for example must stay confined to a very specific set of parameters well defined by Data Security Standards (PCI DSS). HIPAA (Health Insurance Portability and Accountability Act of 1996) provides data privacy and security provisions for safeguarding medical information and has specific requirements for how and where you can host your data and applications that can get access to that data. You can’t just hire any managed service provider to host all your applications. One option is to host the application and data On-Prem but partner with a managed service provider who can manage and maintain it for you.

Managing an enterprise application boils down to a few major areas of concern:

• Application Server Hardware or VM Hardware
• Networking Equipment (Routers, Switches, etc.)
• Operating System (Windows, UNIX, Linux)
• The application itself
• The Database
• File Storage
• The users

Typically, managed service providers would handle all of the above and send you a monthly bill for using the application which mainly boils down to owning a SaaS application. However in the On-Prem scenario the only part the MSP is responsible for is the application. That means that the organization is still in charge of everything but the application itself. This is the most common managed service scenario for most of our clients at Nogalis. The client manages the hardware and network, the OS patching, the Database Administration, and Nogalis takes care of the application and the users.

There are several factors that determine the success of an on-prem MSP engagement:

• Remote access setup from the provider to the application and related servers.
• A web-based ticket/issue tracking system that’s accessible by bother parties (i.e. ServiceNow)
• A single point of contact on the client side that can take ownership of the relationship with the MSP. This ensures direct and efficient communication between both parties.
• A client coordinator on the MSP side to facilitate projects and ongoing communication.
• Dedicated MSP resources that are assigned to the client. Avoid providers who cannot commit a specific resource as having dedicated resources can make the biggest difference in the quality of work delivered.
• Availability of a fast and reliable teleconferencing and screensharing service such as WebEx.
• Weekly status meetings to discuss upcoming change control items and upcoming client needs.
• Detailed breakdown of time spent on delivering services down to the 15-minute increment.

During an LSF outage, we checked the latest logs and saw security_authen.log was updated. It showed a number of errors that a certificate was not trusted. We checked the trusted certificates and saw that the certificate and related certificates were all trusted. So why was the error returned?

Scroll further down the log list to ladb.log. You may see that there is a GEN failed message. Verify that the GEN database really is available by connecting to it directly with a database utility like SQL Studio. Then verify that the gen database connection info is correct in LAWDIR\gen\MICROSOFT. If you are using SERVICENAME to lookup the password, you may want to test commenting out the service name and including the id/password in the file and secure the file. Restart the server and test the portal.

SECURITY_AUTHEN.LOG

Caused by: java.security.cert.CertPathValidatorException: The certificate issued by CN=PKIROOT-01-CA is not trusted; internal cause is:

java.security.cert.CertPathValidatorException: Certificate chaining error

at com.ibm.security.cert.BasicChecker.<init>(BasicChecker.java:111)

at com.ibm.security.cert.PKIXCertPathValidatorImpl.engineValidate(PKIXCertPathValidatorImpl.java:199)

at java.security.cert.CertPathValidator.validate(CertPathValidator.java:278)

at com.ibm.jsse2.util.f.a(f.java:14)

… 68 more

Caused by: java.security.cert.CertPathValidatorException: Certificate chaining error

at com.ibm.security.cert.CertPathUtil.findIssuer(CertPathUtil.java:316)

at com.ibm.security.cert.BasicChecker.<init>(BasicChecker.java:108)

… 71 more

LADB.LOG
DBDataAreaFactory_1 Create of kind “GEN” failed.
java.lang.UnsatisfiedLinkError: com/lawson/rdtec
h/db/api/DBJni.jniTsDBConnect(I)Ljava/lang/Integer;
DBDataAreaFactory_1 Create of kind “GEN” failed.java.lang.UnsatisfiedLinkError: com/lawson/rdtech/db/api/DBJni.jniTsDBConnect(I)Ljava/lang/Integer;

MICROSOFT
#LAWGATENAME=msfdb2000
DBSERVER=lawdbserver
DBNAME=LAWGEN
#SERVICENAME=DBGEN
LOGINNAME=lawson
PASSWORD=lkaj7fde#%&hdsw
SCHEMA=dbo
FILEGROUPS=FALSE
#DEBUG=TRUE

PORTAL

How to Fix Lawson Backoffice Publish Issue

This is a simple fix but sometimes hard to determine even if you’ve reviewed the Infor documentation.

So first lets make sure your FTP settings are setup correctly:

Lets assume you already published your report in LBI, for us we are doing CU201 for testing:

We run the job again so it will publish automatically via backoffice:

Problem:

The broadcast.csv and published.csv shows the CU201 report being transferred but the Instance is NOT being created.

Solution:

Give your Lawson Backoffice user write/read access to the LSF %LAWDIR% directory as well as FTP access to \Lawsonprod_Apps which most have setup already.

Results:

You should now see the instance created when you run the same CU201 job: