Re: CWBDB0058

["Steve Landess" <steve_landess@xxxxxxxxxxx>]

>From the messages section of the Express User Guide:

CWBCO1008

Cause
The AS/400 Service Mapper was successfully contacted on the AS/400 system,
but connecting to the specified application server on that AS/400 system
failed, probably because the host server is not running. The error code is
specified.

Recovery
Verify that the host server is ready to receive connections by doing the
following on the AS/400 system:

1 Enter the NETSTAT command.
2 Select option 3, Work with TCP/IP connection status.
3 Search for an entry for which the Local Port is the name of the server
application specified in the message. This name may be truncated for display
in NETSTAT.
4 Press F14 (Display port numbers) and note what port number that server is
using; also note what the state of the server is.

 If the entry exists but the port number shown is different from the one
listed in the CWBCO1022 message text, then either the Client Access Express
configuration for the system specifies to lookup the remote port on the PC,
or the services table on the AS/400 system is incorrect. Have your systems
administrator AS/400 system services table to verify that the entry for the
specified host server is correct. See AS/400 Connection Properties for
information on configuring the connection to the AS/400 system.

 If there is no such entry, or if the State listed for the entry is not
Listen, the server application is not ready to accept connections; see How
to Start AS/400 Host Socket Servers
. You may have to stop and re-start the host socket servers.

 If the entry exists and the state is Listen, there may be a problem
related to one or more routers in your network not allowing connections to
be made through them. Contact your system administrator for assistance.

See CWBCO1003 and CWBCO1034 for details on the error code specified.

Steve Landess
Austin, Texas
(512) 423-0935


----- Original Message ----- 
From: "Smith, Dave" <DSmith@xxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, May 28, 2003 7:45 PM
Subject: CWBDB0058


> HELP!
>
>
>
> I have a client and their iSeries access data transfer quit working today
(it was working this morning but now its not.)   The error I am getting is:
CWBDB0058 Unable to start database server due to communications error.
>
>
>
> Their system was upgraded to V5R2 last week but they have done transfers
since.  I've gone through STRPJ on QZDAINIT now in library QSYS (says itâs
already started).   I've done a STRHOSTSVR *ALL and Iâve run CWBPING which
gives me a CWBCO1008 - Unable to connect to server application Data Access,
Returned 8006.   I also got the same thing on application Network Print.  I
ended the PJ and restarted it and even had the luxury of being able to IPL
the system (No comments please)   I get the same error on all PCâs that
attempt an iseries access transfer.   I canât find any error messages via
the green screen side.  iSeries Navigator says the database server is
running, Iâm not seeing any other error messages and everything else seems
to be working.
>
>
>
> I know I can use FTP to get these files to the iSeries please do not
suggest that as a way around this.  I want to fix what is broken first, and
if I can not then I will go the FTP route.  I did a slow search (they have a
painfully slow internet connection) for PTFâs but did not find anything.
>
>
>
> Iâll be away from this email address tomorrow but be checking responses
via the painfully slow web.   All help is greatly appreciated!
>
>
>
> David Smith
>
> IT Consultant
>
> dsmith@xxxxxxxxxx
>
>


----------------------------------------------------------------------------
----


> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>