• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

PR198 with CheckLS=YES goes into needs recovery

 3 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
B Crace
New Member Send Private Message
Posts: 2
New Member
2/17/2010 2:12 AM
We are currently implementing Lawson Security for HR/Payroll, and we are running into a very perplexing problem.

When we run PR195, the job goes into needs recovery with the following error:
Execution error : file 'E:\test90\law\test90\obj\IFJR.gnt'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)

However, we can then recover the job, and it runs to completion. We can then run PR197 with no errors. But, when we run PR198, the job goes into recovery with the same error. The difference is that PR198 cannot be recovered, unless we change the user's CheckLS flag to NO.

Thinking that this was related to missing access, we created a security role that contains full access to all objects in all profiles (GEN, ENV, LGN, RM, ADM, and our productline). With CheckLS=YES, the same problem occurs - PR198 goes into needs recovery and can only be recovered if we turn the CheckLS flag to NO.

Has anyone every seen anything like this? And if so, how did you resolve it? Our go-live is being delayed because of this one form, and I'd really like to get it working...
B Crace
New Member Send Private Message
Posts: 2
New Member
2/17/2010 12:38 PM
One additional piece of information - we even turned Lawson Security checking to Off, Allow All Access for the productline, and the problem still happens. As long as the user's CheckLS flag is set to YES, the job goes into needs recovery.
SanfordMatt
New Member Send Private Message
Posts: 1
New Member
6/7/2011 7:22 PM
We are having the same strange occurrance. Except ours is with PO220. If we run it with any user account and CheckLS = YES then it goes into recovery with the same error message that you received. If we switch that user to CheckLS = NO, then it works like a charm.

I've had a GSC case open for over a month now, and we still haven't figured out the problem.
krisB
New Member Send Private Message
Posts: 1
New Member
1/31/2012 12:13 PM
Did you ever find out why this was happening?