Re: Navigator For i

[DrFranken <midrange@xxxxxxxxxxxx>]

Be very positive in no uncertain terms that the IP address used to 
access the server and the FQDN for the server match up. Also make sure 
that the rDNS record matches that IP address. Be sure to test this FROM 
the IBM i partition. If these do not match many things (IBM Navigator 
for i INCLUDED) will not work correctly.

Second be sure you have all the correct Java components installed and 
have current PTF groups for HTTP, JAVA, TCP and that the HIPER group is 
reasonably current as well.

Also if a lot of things start when your system starts and you don't have 
very many disk arms. Try ending and restarting the *ADMIN server when 
the system isn't very busy. I have seen that on systems with few arms 
where everything starts at once that the *ADMIN server doesn't finish 
starting correctly and this is one of the issues that surfaces.

        - Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 10/21/2013 12:43 PM, Buzz Fenner wrote:

> I make use of IBM Navigator For i (mainly in lieu of -not- being able to use
> Ops Nav in iAccess For Windows on my Win 8 laptop). A week ago we ported
> over from a Model 520 to an 8202 (both @ v7r1). I now find almost all the
> selections are generating server communication errors, namely TCTUI1003E.
> Google has not been my friend, so far. Has anyone run into this problem?
>
>
>
> --
>
> Buzz Fenner
>
> Business Systems Analyst/Systems Administrator
>
> City Water & Light
>
> 870.930.3374 | 870.219.5229
>
> bfenner@xxxxxxxxxxxxxxxx