Log Error Messages

The following error messages are only written to the log file, which is located in the logs subdirectory of the working directory for the data source. These messages are prefixed by the timestamp hh:mm:ss, where hh is hours, mm is minutes, and ss is seconds. For a complete list of error messages that appear both in the log and onscreen, see Appendix A, Error Messages.

Accept call for remote console failed

This error indicates that a sockets error occurred when the service attempted to respond to a connection request.

Add_DataSource: chdir failed for working directory "wdir", errno=number (errortext)

When adding a data source the service creates the working directory for the data source and its subdirectories. It then updates the service’s configuration file and changes its current directory to be data source’s working directory and creates the client’s configuration file. When done it creating the clients configuration file it changes the working directory back to the service’s working directory. This message is used to indicate that the attempt to change the programs current directory failed. The directory wdir is the target directory for which the chdir command failed. The system error number and associated text should help determine why the operation failed.

Add_ExistingDS: chdir failed for directory "dir", errno = number (errortext)

When adding an existing data source the service changes its current directory to the data sources working directory and verifies that its sub-directories exit. When done it changes the current directory back to the service’s working directory. This message is used to indicate that the attempt to change the programs current directory failed. The directory wdir is the target directory for which the chdir command failed. The system error number and associated text should help determine why the operation failed.

Add_ExistingDS: chdir failed for working directory "wdir", errno = number (errortext)

When adding an existing data source, the service uses a series of chdir commands to determine if the Client working directory contains the required sub-directories. This message is used to indicate that the attempt to change the programs current directory failed, wdir is the target sub-directory for which the chdir command failed. The system error number and associated text should help determine why the operation failed. The most likely cause is that the target directory does not exist.

Bad input line 'text_line' in "globalprofile.ini"

(UNIX only) This message indicates that the file globalprofile.ini has a bad line that is displayed. This file should be created starting from the sample file that is provided with the release. If you are careful when editing it and just change the values of the parameters you will never see this error.

Bad section header 'text_line' in file"globalprofile.ini"

This message is limited to the UNIX daemon. The only section header used in the file globalprofile.ini is [dbridge]. This file should be created starting from the sample file that is provided with the release. If you are careful when editing it and just change the values of the parameters you will never see this error.

Bad user id 'userid' specified in file "globalprofile.ini"

(UNIX only) This message indicates that the userid provided on the line “userid = name”, is not recognized as being a valid user-id.

Binary configuration file "name" has the wrong check word

The service only handles binary configuration files; such file start with an 8-byte pattern that must that is used to determine if the file is binary or not. If the pattern does not match this message is displayed. The most likely reason for this would be that the file is not a binary file.

Binary configuration file "name" has a bad checksum

Binary configuration files use a checksum to ensure that the file is not corrupt. Do not try to use a binary editor to update a binary configuration file. If you change even a single byte the checksum will be wrong. You should use the Console, the Client Configurator or the dbctrlconfigure utility (export/import commands) to update the service’s configuration file. The most likely reason for this error would be that the file was patched or the file is corrupt.

chdir failed for working directory "name", errno = number (errortext)

During normal operations, the service uses the chdir command to switch the current directory to something other the working directory of the service and then back. This error indicates that the service was unable to change the working directory to a client working directory or back to the service’s working directory. The path of the target directory is specified by “name”.

Client configuration file "name" has bad checksum

If you use the service, you must use binary files for all Client configuration files. Binary configuration files start with an 8-byte pattern. If a Client configuration file doesn't start with this pattern, or if the binary file has been edited and the checksum corrupted, this message occurs.

Client configuration file "name" is corrupt, errno = errno (errortext)

This message indicates that the binary configuration file was edited using a binary editor or patched and was corrupted as a result. Using binary editors to update a binary configuration file should be strictly avoided altering a single byte will render the checksum as wrong. To update the client configuration files, use the available options in the Console and the Client Configurator, or use the dbutility export/import commands if you need to make manual edits.

Close failed for binary configuration file "name", errno = number (errortext)

This error indicates that an I/O occurred when the service tried to close its binary configuration file after rewriting it. To determine why the error occurred, refer to the system error number and associated text.

Close failed for client configuration file "name", errno = number (errortext)

This error indicates that an I/O occurred when the service tried to close the client’s binary configuration file after rewriting it. The system error number and associated text should help in determining why the close failed.

CreateMutex failed for 'daemon_cs', errno = number (errortext)

(Windows only) This message, which can occur during the startup of the service, indicates that a Windows internal error has occurred while attempting to create a mutex resource. If this error occurs, contact Attachmate Technical Support.

Createprocess failed for client run, errno = number (errortext)

(Windows only) This message, which can occur when the service launches a run of DBClient or DBClntCfgServer, indicates that the attempt to create the process failed. The system error number and associated text should help determine the reason for the failure. This error can occur if edit the service configuration file and provide the wrong directory for the Client. We recommend that you update the service configuration file by using the Client Console; or when upgrading, the migrate utility.

CreateThread failed for 'notify_thread', errno = number (errortext)

(Windows only) This message indicates that a Windows internal error occurred while trying to create the notify thread. The notify thread fields all requests from the NOTIFY program on the mainframe. To determine the reason for the failure, refer to the system error number and associated text.

Data source name not found during IPC signon processing

This message indicates that, after successfully connected to the service, a spawned client provided a bad data source name in the signon RPC data. If this error occurs, contact Attachmate Technical Support.

Execute_Command returned status -- killing RC session

This message indicates that the service encountered a problem when trying to execute an RPC received from the Client Console or the Client Configurator. The error is fatal and causes the session to terminate. If this error causes the Client Console to hang, restart the Client Console and then reconnect to the service. If the problem persists make sure that you are running a version of the Console that is consistent with the service.

Get_IPC_Response(): seq_no validation error; send_no=hhhh, cnt= hhhh, recv_no= hhhh

This message indicates that an internal error occurred when processing a response to an RPC that had been sent to a spawned client. For the service to correctly identify and process an RPC response, the response must have the same sequence number as the RPC command. If the response has a different sequence number, this message is logged and an RPC error status is returned to the Client Console or the Client Configurator.

Execute_IPC_Response returned status

This message indicates that the service encountered an error while processing the response to an RPC that had been sent to a spawned client. The message is usually preceded by another message that provides information about why the failure occurred.

getcwd failed, error = errno(errortext)

The service uses the getcwd command to get the current directory. If the command fails this message is logged. The system error number and associated text that is provided should help determine the reason why this operation failed.

Launch of client failed, errno = errno(errortext) -- see file "fork.log" for clues

(UNIX only) This message indicates that the daemon was unable to launch the Client either when starting a run of DBClient or DBClntCfgServer. This error can occur if you enter the wrong directory for the Client when editing service configuration file. We recommend that you update the service configuration file by using the Client Console; or when upgrading, the migrate utility. To determine why the operation failed, refer to the system error number and associated text, and to the file fork.log. The daemon create this file in its working directory when this error occurs.

Notify protocol error (nnn), ip_address = ipaddr

This message indicated that the notify thread received an invalid message from the NOTIFY program on the mainframe. Make sure that you use the correct version of the NOTIFY program on the mainframe.

Open failed for binary configuration file "name", error = errno (errortext)

This message indicates that the service received an error when it tried to open (and write to) the service binary configuration file. To determine why the operation failed, refer to the system error number and associated text.

Open failed for client configuration file "name", errno = errno (errortext)

This message indicates that the service received an error when it tried to open (and read) the Client binary configuration file. To determine why the operation failed, refer to the system error number and associated text.

Open failed for global configuration file "globalprofile.ini"

(UNIX only) This message indicates that the program was unable to access the file globalprofile.ini in the directory /etc/Attachmate/DATABridge/6.2. This file must be created before attempting to do any Client operations.

pthread_create failed for 'notify_thread', errno = errno (errortext)

(UNIX only)This message, which can occur during the startup of the daemon, indicates that a system error occurred when the notify thread was being created. The notify thread fields all requests from the NOTIFY program on the mainframe. To determine the reason for the failure, refer to the system error number and associated text.

RC session no longer exists, destination index nn for CNS Session nn

This message indicates that an IPC response for a Console or Client Configurator session was received, but an attempt to find the matching session failed because the session no longer exist. This error is not fatal; the response is simply discarded.

Read failed for binary configuration file "name"

This message indicates that the program was unable to read the service binary configuration file dbcontrol.cfg. To determine the reason for the failure, refer to the system error number and associated text.

Read failed for client configuration file "name", errno=errno (errortext)

This message indicates that the client’s binary configuration file dbridge.cfg could not be read. To determine the reason for the failure, refer to the system error number and associated text.

Read failed for file "name", errno= errno (errortext)

This message indicates that the attempt to read the log file descriptor from the file log.cfg failed. To determine the reason for the failure, refer to the system error number and associated text.

Select failed, errno=errno (errortext)

This message indicates that a sockets select call returned a count less than zero. The error is ignored and the operation is retried after a brief delay.

Unable to allocate nnnn bytes of memory

This message indicates that the operating system cannot allocate the specified block of storage because there isn't enough installed memory or a memory leak occurred.

Unable to create client configuration file "name", errno = errno (errortext)

This message indicates that an error occurred when the service tried to open and write to the client binary configuration file. To determine why the operation failed, refer to the system error number and associated text.

Unable to create working directory for the daemon

(UNIX only) This message can occur if the daemon is started from the command line under a user ID that doesn't have the necessary privileges to create the daemon’s working directory. Typically this message would not occur; the scripts that launch the daemon require that the working directory be created in advance.

You should normally not see this message as the scripts we use to launch the daemon require that the working directory be created a head of time.

Unable to expand {config | XDR} buffer

This message indicates that the operating system is unable to expand the specified buffer, either because there isn't enough installed memory or a memory leak occurred.

Unexpected RPC response received for index dd of {CNS | IPC} Session nn

This message indicates that the service received an unexpected RPC response. If the problem persists, contact Attachmate Technical Support.

Unimplemented command rpcnumber

This message indicates that the Console or Client Configurator sent the service an RPC whose number is not known by the service. Unless you have you are using a service that is older than the Console, you should never get this error.

Unknown session type dd encountered in Kill_Session()

This message indicates that an internal error occurred caused by an illegal type in a session. If this error occurs, contact Attachmate Technical Support.

Write failed for binary configuration file "name", errno = errno (errortext)

This message indicates that the program was unable to write the service binary configuration file dbcontrol.cfg. The system error number and associated text should help determine the reason for the failure.

Write failed for client configuration file "name", errno = errno (errortext)

This message indicates that the program was attempt to create the Client binary configuration file dbridge.cfg. To determine the reason for the failure, refer to the system error number and associated text.

Write failed for file "name", errno = errno (errortext)

This message indicates that the program was unable to create the log descriptor file log.cfg.

XDR_Copy failed; RC_Sess_buflen = 0xhhhh, IPC_Sess_buflen = 0xhhhh

This message indicates that an internal error occurred when the RPC data from a console session run is copied to a send buffer. If this error occurs, contact Attachmate Technical Support.

XDR receive failure for sockettype socket nnn

This message indicates that the attempt to read and decode the data for an RPC failed for the specified socket type. The socket type can be CONSOLE, IPC, or LIMBO. LIMBO indicates that the connection type is not yet known. This error typically occurs when the connection closes.

You must be 'su' or userid 'userid' to run the daemon

(UNIX only) This message indicates that the script used to run the service uses a different userid than the one specified in the file globalprofile.ini. To switch the service to a user other than that in globalprofile.ini, start the service after you start a run as the root user.

SOCKETS ERROR: bind call failed for remote console TCP port number nnn, errno = errno (errortext)

This message indicates that the service was unable to bind the ipc_port to the given socket. To resolve this problem specify a different port for the ipc_port parameter in the service configuration file. This error usually occurs when the service starts.

SOCKETS ERROR: listen call failed for remote console, errno = errno (errortext)

This message indicates that the service was unable to listen for incoming calls on the specified port. To resolve this problem, specify a different port for the ipc_port parameter in the service configuration file. This error usually occurs when the service starts.

SOCKETS ERROR: recv call failed for {CNS | IPC} Session nn, errno = errno (errortext)

This message indicates that the service encountered an error while receiving data. This typically occurs when the connection is reset.

SOCKETS ERROR: recv call for {CNS | IPC} Session nn detected a closed connection

This message indicates that the service detected a closed connection while receiving data.

SOCKETS ERROR: send call failed for {CNS | IPC} Session nn, errno = errno (errortext)

This message indicates that the service encountered an error while sending data. This typically occurs when the connection is closed or reset.

SOCKETS ERROR: setsockopt(SO_REUSEADDR) call failed for remote console TCP port, errno = errno (errortext)

This message, which can occur when the service starts up, indicates that the attempt to set the specified socket option failed.

SOCKETS ERROR: socket call failed for remote console TCP port, errno = errno (errortext)

This message indicates that the system is out of sockets. Reboot the system.

SOCKETS ERROR: WSAStartup error nnn

(Windows Only) This message indicates that the attempt to initialize Windows sockets failed. The only thing to do is to reboot and hope that the problem goes away.