Re: CWBDB0058

[Colin.Swain@xxxxxxxxxxx]

Thanks for the reply Evan.  I ended (ENDHOSTSVR) and started (STRHOSTSVR) 
the host server and the data transfer is now functioning.  Not sure what 
caused the issue though.

Col



----- Message from Evan Harris <spanner@xxxxxxxxxx> on Fri, 20 Jan 2006 
08:14:09 +1300 -----
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject:
Re: CWBDB0058

Hi Col

I don't suppose you changed your password this morning by any chance ?

Regards
Evan Harris

At 06:17 a.m. 20/01/2006, you wrote:
>Hi,
>
>I have taken a look through the site and I cannot find any complete
>solution that works for me.
>
>Here's the problem:
>
>When trying to browse to a File Name in a Data Transfer Window I get the
>following error message:
>
>"
>CWBDB0058
>
>Unable to start database server due to communications error. Return code:
>%1 "
>
>Cause
>
>The database access API attempted to initiate a connection with the 
AS/400
>database server. The connection attempt failed due to a communications
>error. Possible causes for this error are:
>
>·       There is no connection configured to the AS/400.
>·       The AS/400 server jobs are not started.
>·       An internal Client Access/400 communications error has occurred.
>
>Recovery
>
>Do one of the following:
>
>·       Configure a connection to the AS/400.
>·       Verify the communications configuration is correct.
>·       Use the STRPJ command on the AS/400 to start program QZDAINIT in
>library QIWS, under subsystem QSERVER.
>·       If using a TCP/IP connection use the STRHOSTSVR command on the
>AS/400 to start *ALL or *DATABASE servers.
>·       If using a TCP/IP connection, use the PC program CWBPING to 
verify
>that the AS/400 servers are running.
>"
>
>This was working fine this morning but for some reason it is not now.  I
>have been renaming libraries, but I am sure that cannot be the reason for
>a communications problem - I changed all the names back again just in 
case
>and it had no effect.
>
>Any help greatly appreciated
>
>Col

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________