We've been having mutiple users' screens freeze up in both AR and PO. They have to log off and back in to continue. I've reproduced the problem myself. For example PO20, PO30, RQ10, AR20, AR30...

hangs up in po30.1 while receiving; hangs up whenever changing screens; when trying to release receiver#; also happens when paging up & down.
hangs up at different stages, not always the same places.

Please help - the users have been having a terrible time.

John

John - Have you had any luck finding a solution? I'm running into the same problem, primarily with PO30, ever since we upgraded to Apps 9.0.1.3 about a month ago.

No, not as of yet. This is very interesting that you have the problem, since we are on a frozen/unsupported version of Lawson Insight 7.3.3, BUT we DO NOT have this problem in our Lawson Development system where the Application and Database are on the same box. We've tried many many things and now have built a new App server for Prod and will be trying to point it to the database server.
For a workaround (which the users do not like), we are using the client in character mode pt-80e, where it does not hang up. We don't have the issue for the web users.

I have encountered this problem with occasional freezes. It turned out to be diskeeper software installed on the application server by the other team without my knowledge.

I've asked our people to look into it now. Sure would be great if this is the cause. I've got my finders crossed waiting to hear back from them!

Are you on aix using LID? We had this happen a few years ago and it was a flag for telnet. I think it was in the inetd.conf file and we had to remove the "-a" on the telnet line.

HPUX/Oracle with LID.

They told me that we don't run anything like Diskeeper, which they say is for Windows (we are on HPUX/Oracle).

This is from the knowledge base

PO20 and AP20 Will Not Launch in LID GUI mode
Article ID:5405908

Description:
I am unable to launch Purchase Order Entry (PO20) and Invoice Entry (AP20) in LID GUI Mode. The forms display in LID character mode and in Portal. How do I resolve this issue?
Resolution:
The TELNET Performance Mode "-a" option is enabled. This is known to cause problems in GUI and should not be enabled. You will need to go to /etc/inetd.conf file and at the end of the telnet line you need to remove the -a and then reboot the server.


You are describing the same symptoms we had only difference was we were on AIX. If you do"export TERM=pt80" and then try it, are you able to pull up data? It's hard to work with this terminal type but those screens worked for us with our terminal set to that but not set to univwin until we changed the telnet flag.

I sent the information you provided to our people and am waiting to hear back. Yes we have used pt80-e successfully as a temporary fix, but the users hate it.

Here's what they tell me:
Thanks for the info. I checked our /etc/inetd.conf file and we don't appear to have the -a option in use. Here is our setting:
telnet stream tcp nowait root /usr/lbin/telnetd telnetd -b /etc/issue