iSeries Client access process pcscm.exe not ending
After starting a number of CA sessions, and then closing all the windows, the pcscm.exe and pcsws.exe processes in Windows XP does not end. Before I can start a new CA session, I must end these processes. How come these processes do not end after closing all CA sessions.
Software/Hardware used:
Windows XP
Software/Hardware used:
Windows XP
ASKED:
February 6, 2010 7:15 PM
UPDATED:
October 5, 2010 1:34 PM
Answer Wiki:
You need to signoff each session before closing out the windows. People make this mistake all the time.
I do sign off each session. Even if I did not those processes should have ended.
I applied service pack like TomLiotta suggested…. I have not had a problem since then. Thanks for pointing me to the service packs.
To see all answers submitted to the Answer Wiki: View Answer History.
What version of iSeries Access (or System iAccess) are you running? What is your service pack level? (See the Properties in the Start-> Programs menu.)
First guess is usually that you need the appropriate fix pack applied.
Tom
IBM iSeries Access for Windows
Version 5 Release 2 Mod 0 Service level S106631
Installed 3/2/2008
Your service level is pretty old. (Of course, V5R2 is old anyway.) The latest service pack for V5R2 is SI23978 which is from May 31, 2006. You should download/install it. It can be retrieved from the IBM i Access for Windows Service Packs page.
See if and how that changes behavior and post results back here. From that service level, maybe there is more that can be done.
Tom
I’ve also seen issues with older versions of Client Access putting profiles (*.ws files) in locations that are not later writable by non-administrative users. If you go into IBM Client Access Properties, you can change the default profile save location to each user’s My Documents folder, instead of the Program Files folder.
I always check this option from now on when I install iSeries Access, prior to setting up profiles…just in case.
I applied service pack like TomLiotta suggested…. I have not had a problem since then. Thanks for pointing me to the service packs.
I was able to correct this issue by punching a hole in my firewall for these programs to the iSeries. I think they run in the background and part of their job is to monitor connectivity to the iSeries. If they can’t get through the firewall completely, then they goof up and leave the currently active session in a state of limbo as if the cable was unplugged.