F42UI11 error

sshepard

Active Member
B733.2
SP 11.3
HP9000

Getting an error, "Add to Cache F42UI11 Failed" when modifying a sales order
detail line.

Does anyone have any experience regarding this ?

We did not see this until ESU 4116422 was deployed. It appears on both our
server set up as well as fat client set up.

Pursuant to an earlier message regarding a F04UI002 cache error, I examined
Processing Options to make sure Interoperability was not turned on.

Any thoughts ?
 

hedgiehoghill

Active Member
Look into SAR #4786813
We had this and originally applied ESU JD8848 but it looks like they have re-built this since and changed the ESU number.
Good Luck,


B73.3.2 SP 11.1_UPKG, NT, MS-SQL 7.0, WIN2K/Metaframe 1.8a & Fat

Jeff Hill
IS Division Manager
Yamazen Inc.
 

DaKAA

Member
We are also seeing this error alot. Haven't heard of a fix for it.

Keith Anderson
BIC-USA
B7332 SP15 AS400-V4R5 CO-NT/SQL WTS
 

devimisra

Active Member
I have seen these problem appear and disappear at the same time in our
development environment. Which make me think it is the data which causes
the problem. I blame the line numbers(lnid) or the action code.

just a thought
 

sshepard

Active Member
Hedgiehoghill - SAR 4786813 is for F04UI002 Failed - Match Voucher to Open
Receipt - P4314 ... but thanks for the note.

None of SARs listed on KG seem to match the problem. It is not a configured
item.

Any other thoughts ?

SS
 

Dawn_Detz

Member
Yes ESU JD9895 - we have put it into DEV but not tested yet.... we just
refreshed our data... will try today, will keep informed of results.

B73.3.2 SP 11.1; NT; Oralce 5.1
 

hedgiehoghill

Active Member
Re: RE: F42UI11 error

The voucher matching was our visible problem. However the underlying problem was they were not closing the database cursor correctly in the p4310 application and the underlying business functions. After it racked up over 100 open cursors if I remember correctly the applications would crash.
Do a debug log and when you get the error check the log to see if you have errors relating to the cursors.
Ours didn't appear until we applied the ESU 4116422 either so it really sounds like the same problem we had and your error message is exactly what we got.
I hope this helps.

p.s. after this working for about 2 months for some reason (i'm guessing an undocumented esu object change) it was broken again. we are in the process of reapplying the esu and it appears to be working once more.

B73.3.2 SP 11.1_UPKG, NT, MS-SQL 7.0, WIN2K/Metaframe 1.8a & Fat

Jeff Hill
IS Division Manager
Yamazen Inc.
 
Top