Client Access V6r1 keyboard locking
Home > IT Answers > AS/400 > Client Access V6r1 keyboard locking
Slhamilton
35 pts.
0
Q:
Client Access V6r1 keyboard locking
iSeries Access for Windows, Client Access 6.1, Client Access, V6R1, Windows Terminal Server, Windows Server 2008
I have upgraded my clients to V6r1, 64 bit, running on a Windows 2008 terminal server. AS/400 is on V5R4. My clients will get the message "The host system has locked the keyboard, See if message appears, wait, or press rest" this doesn't happen all of the time nor is it consistant to certain keys. Pressing System Attn releases it. IBM has no ideas other than to run a trace until the problem happens.
ASKED: Jun 22 2009  1:38 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Slhamilton
35 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
Last Answered: Jun 22 2009  1:38 PM GMT by Slhamilton   35 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Steveoasdfasdf   625 pts.  |   Jun 25 2009  4:07PM GMT

We use Citrix and I find that sometimes you have odd key mappings on the client end that would cause this issue.

 

Slhamilton   35 pts.  |   Jun 26 2009  1:07PM GMT

We are using BosAnova thin clients. I just learned that the RDP session is Unix although Box has not heard of anyone having the same problem nor is there any new version updates for the firmware. The map we use is the same as the old version. I created it in a common area then I copy it when I install a new user. I thought I would try deleting the new map and letting client access create it again and then change it. We don’t change much on it so I would not think that is the problem, but you never know.

Thanks for the info.

 

Slhamilton   35 pts.  |   Jul 8 2009  4:56PM GMT

IBM sent me a dll to fix the problem. So far it is working. The dll is pcslt52.dll.

 
0