Re: V4R5: Client Access isn't working after scratch reload - FIXED

[Tom <tomh@xxxxxxxxx>]

Fixed!  I ran CHKPRDOPT on all of my licpgms.  A problem was found in
5769SS1 option 3 OS/400 Extended Base Directory Support.  I re-installed it
from my original CDs (no IPL).  Client Access started just fine after that.

I'll reload my cum PTF this weekend and do an IPL, just in case.

tomh=WgFEu9fVc9EAvxtiuMwx3w@public.gmane.org wrote in
aopac2$clo$1@main.gmane.org:">news:aopac2$clo$1@main.gmane.org:

> A customer of mine had a load disk fail a few days ago, and I was the
> one who had the dubious pleasure of reloading the system from SAVSYS
> backup (thank Heaven we had _two_ of 'em!).
>
> Everything is working as before, with one exception - we cannot get a
> signon session thru Client Access.  I can get one with telnet, and
> also with the Mochasoft emulator.
>
> I start a new session, and I'm prompted for the system name, user ID
> and password (via the 'Signon to AS400' Windows dialog). I enter my
> user id and password, click OK.  I'm then presented with an error
> dialog: CWBSY1000 - Communication error while validating security
> information on system AS400.
>
> I look at the History Log, and it shows 3 errors at the same time:
> CWBCO1003 - Winsock error, function connect returned 10061
> CWBCO1006 - Unable to connect to server mapper (port 449) on system
> CWBCO1000 - Communication error while validating ...
>
> Clicking on error CWBCO1003 lets me see that 10061 means that the
> AS400 refused the connection, and suggests that I issue the command
> STRHOSTSVR *ALL (I have), and to make sure that the QUSER profile is
> enabled (it gives a command line entry to enter to set some parameters
> for the QUSER profile as well, which I've done).
>
> Still, the connection fails.  Is there something else I should look
> at?
>
>