Bad File Status After a Refresh

, ,

Problem:

We noticed our jobs are failing after refreshing our productline. The job log is showing a bad file status error.

This particular error was caused by windows permissions not being inherited.  Even though the owner of the applications directory was correct, it was not the owner of the files and folders underneath it.

 

Resolution:

This was resolved by setting the owner in the advanced security settings of the folder properties and running icacls to reset permissions on the files.

——————————————————————————–

User: domain\lawson                     Job: PR140           Queue: **********

——————————————————————————–

BEGIN:  Job Submitted:  Wed Feb 14 09:22:06 2018

Step  1:  PR140 Started. . . . . .:  Wed Feb 14 09:22:06 2018

Token Command. . . . . .:  C:\LSFDEV\law\dev\obj\PR140.gnt

Executable Command . . .:  C:\COBOL\bin64\run.exe C:\LSFDEV\law\dev\obj\PR140.gnt dev NT00000004 PR140 1

Process ID . . . . . . .:  4008

Running as Account . . .:  domain\lawson

Program Messages:

** Creating .prt and .dtl files

Bad File Status 3 7 On File PRPAYRPTEN-FILE

Elapsed Time . . . . . .:  00:00:00

ERROR:    Stopped On Exit 1.

Elapsed Time:  00:00:01

END:    Job Ended:  Wed Feb 14 09:22:07 2018

Cash Ledger (CB) job submission error: “User XXXX does not have access rights”

, ,

Problem

When I try to add a record in Cash Ledger (CB), I get the error message User XXXX does not have access rights, even though I have security to run CB jobs. How do I resolve this error?

Solution

To resolve this error, follow the steps outlined below.

  1. Inquire on your cash code in CB00.2 (Cash Code).
  2. Click on the Security button on CB00.2. You will automatically be transferred to CB01.3

(Cash Code Security).

  1. Make sure your user ID has been added to the User Class associated with your cash code
  2. Inquire on CB04.2 and add your id to the security group.

Removing a Server Definition from LID

, ,

Sometimes you might inadvertently add a server definition in LID, or you may have some old server definitions hanging around that you would like to remove from the list to clean up space and keep up with some basic housekeeping/organization.

The good news is this is an easy task to perform. In order to do this, you will first need to go to %AppData%/Local/Lawson Software/ univwin64.  Next, find and open the univcomm.ini file. Look for the server definition(s) that are no longer valid for you and from here you are able to remove them. You can refer to the example screenshots below as a guide.

 

Changing a Lawson system user password and checking if LDAP rebind is needed

, ,

When updating a Lawson system user, we need to make sure that the user is not LDAP bound and check if it needs a ldap rebind.

 

The first thing you need to do is login to Lawson Security Administrator then navigate over to Managed Privileged Identities.

 

From here, you need to select SSOP_BIND.

Next, select the DEFAULT key as shown below. Make note if the DN Attribute name is the same as the system user. If so, you will need to do a full LDAP rebind. If not, you’re okay to change the password.

And you’re all done. Good luck!

Cannot Delete Non-Journal Entries

, ,

PROBLEM

When I run CB187 job, I found an error message at CB N-68 as per below:

I am not able to delete CB entry with error message “cannot delete non-GL journal entries”. Should I go ahead and post the CB or is there any way I can delete the entry?

 

RESOLUTION

The message that you cannot delete a non-GL journal is a system enforced error. If the issue results in GL substituting error suspense, a sequenced journal will be created.

Otherwise after it is posted, you could copy with reversing entries to create a new journal with exact opposite data so the two ultimately net to zero.

Or if you simply need to reallocate an entry, a manual entry could be created to “fix” the data.

WFWK.1 error CCS product line has not been opened

, ,

When running a service in WFWK.1, it may produce the error message: “CCS product line has not been opened: Return Code 9”.

If this happens to you, follow these simple steps below to resolve it.

 

First, you need to start at the application product line, then go to screen WF01.1. Next, “Add” the Process Automation Productline “Logan”.

 

Next you will need to restart the Lawson services, or restart the Lawson server. Try to run the service in WFWK.1 again.

 

This should resolve everything and  you should not get the error message again.

 

 

***Also, the length of the flow name is limited

Bookmark Error

, ,

Problem:

No matter what browser I use, when I go back to a bookmarked link I get the following error when I sign in:

 

“Error encountered while processing the request. Additional information: Bad request cache id. This URL request may already have been processed…”

 

Resolution:

There is a simple solution to this common error. This is not security-related, but rather a bad link that you may have bookmarked. It’s important to make sure you bookmark the correct link: https://hostname/lawson/portal,so you won’t get this consistent error. Note that if you try to copy the URL before you have fully logged in, the bookmarked link will not work again.