iSeries Access session won’t connect or even give a status, just remains blank

15 pts.
Tags:
AS/400
Client Access
iSeries
We're running V6R1 on our iSeries (AS/400, IBM System i) and using IBM i Access 7.1 (Client Access, iSeries Access) with it. All of our PCs are on Windows 7. Every user has a .ws file that they use for starting sessions with their preferences, and it opens via PCSWS.exe. Today, one user cannot connect properly, even after restarting her PC. Nothing is wrong with her internet, email, or shared drives. I did a successful system save last night, so I thought that might have something to do with it, but no other user is having problems. We haven't bumped into our session limit, although to be safe, I've deleted some that had been varied off. When she runs her .ws file, a session window opens, but it remains blank and so does its status bar. Nothing happens when she chooses "Connect" from the Communication menu. Even the status bar does nothing. This problem also occurs when she tries to start a generic session using the PCSWS.exe icon. I was able to get her connected and signed on by going to "Start or configure session" and clicking "New session," so at least she can get some work done today, but this is a problem. Can anyone help?

Answer Wiki

Thanks. We'll let you know when a new response is added.

I am having similar incidences where 2 to 3 users opens a session & is completely blank screen but at the bottom of the status is “session connected” but no sign on screen appears there is an “M” at bottom on the status indicator bar. they can open additional sessions and they work just fine. I can even delete the session that does not work create a new one save it works fine then I close it and reopen no sign on screen will appear. Their configurations are set up just like all other users have even compared other user screens and my own just to verify cannot seem to find any differences or why it would cause a blank screen or no sign on screen to appear.
One peculiar thing I have found if you change the type of emulation for the display size from 27 x 132 to 24 x 80 it will work. but if you change it back to the 27 x 1 32 and save it it will not work .

Discuss This Question: 13  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • pdraebel
    On the Communication Menu you can also select "CONFIGURE". Try that and see if it works. My guess is that something is wrong with the session naming. Either there are no entries for the device in any subsystem available or the name is a duplicate and is in use.
    7,545 pointsBadges:
    report
  • ToddN2000
    I'd check to see if there is a phantom session preventing a new sign on. Open operations navigator and look under active jobs. If you find it, you can end it bight right clicking and end the job.
    113,720 pointsBadges:
    report
  • ukcazo53
    Thanks for your answers.  For every user here, the "Specify workstation ID" option in the Configure menu is always selected but blank.  It didn't occur to me to check for phantom sessions, so if I run into this again, I'll try that.

    The same problem occurred today, even after she had shut down her PC over the weekend.  I was again able to use "Start or configure session" to begin a generic session, so I saved that session as her .ws file (overwriting the old one), and the problem has gone away.  I guess the .ws file must have just gotten corrupted somehow.  Thanks again.
    15 pointsBadges:
    report
  • Splat
    If your users are getting QPADEVxxxx sessions double-check that those on the iSeries aren't varied off.  You many also want to see if QAUTOCFG is set to on.
    12,650 pointsBadges:
    report
  • pdraebel
    I have also experienced sessions that could not reconnect. Mostly after a network outage on the iSeries the Workstation would still be seen as being "Active". Check system value QINACTITV. Mine is set to 5 minutes. In your case this could be a very high value as the device would have been in use over the weekend.
    7,545 pointsBadges:
    report
  • ToddN2000
    I'd double check to see if she has defined a device name in her configuration. Then check to see if that device still exists. If so you may need to do a vary *off then do a vary *ON with the reset *YES option (F4 to see this option)
    113,720 pointsBadges:
    report
  • MichaelBE
    Hi, we are having the same issues. Did you manage to solve this problem? I thought that it was a .net problem, an update that did this as it appeared this month.
    20 pointsBadges:
    report
  • TheRealRaven
    Why would you think it would be a .net problem? There shouldn't be much of a relationship with .net. If you have a reason to think so, it might help.
    28,455 pointsBadges:
    report
  • MichaelBE
    2 or 3 weeks ago nobody had problems with a black screen that suddenly appear in a session. And this is running almost 1 year without problems. Could it be an update problem then? If I open a call at IBM they will do 0 I think while they only will look on a fresh install without nothing on it but the IBM client app...
    20 pointsBadges:
    report
  • TheRealRaven
    I've never had to use anything but the problem system when working with IBM Support (U.S.A.), including normal non-IBM apps. But it might be different in other countries. If the IBM client app fails when other apps are installed, IBM needs to know.

    Does the problem show for multiple users? All users? Can you demonstrate the problem on demand?
    28,455 pointsBadges:
    report
  • ToddN2000
    It's been a while, but we sometimes had a similar problem where the devices that had the sign on info built into the configuration to auto connect was the problem. For some reason they were disabled and the users that tried to log in got a blank screen.
    113,720 pointsBadges:
    report
  • pdraebel
    I've had a problem Showing a black screen where the connection to the i existed. Apparently all text from the signon screen where blackened. Moving the cursor (with the arrow keys) would show the text that was previously hidden. The solution was to recreate the session configuration(s) that somehow got corrupted. No problems after that. Currently using the IBM i Access Solution (Java) iso Client Access.
    7,545 pointsBadges:
    report
  • southgor
    Try WRKCFGSTS *DEV WORKSTAID
    Usually Show *SIGNON STATUS.  The IBM communication has reestablished the connection but The interactive task has not. 
    VARY OFF and the connection will resync with the PC when you click connect.
    20 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: