Messages Reference

IPX/SPX

When using IPX/SPX on DOS, OS/2, or Unix systems, the following is a list of t_errnos which the user may encounter most frequently. It is NOT a complete list of errors. Error values can be found in the file tiuser.h. The t_errno number itself is in parentheses.

TBADF (4): Specified file handle does not refer to a transport endpoint.
TNOADDR (5): Transport provider could not allocate an address.
TOUTSTATE (6): A function was issued in the wrong sequence.
TSYSERR (8): A system error occurred during execution of this function.
TLOOK (9): An asynchronous event has occurred on this connection.
TNODATA (13): No data is currently available from the transport provider.
TADDRBUSY (23): Specified address is in use and the transport provider could not allocate a new address.

When the first error token specifies t_errno = TLOOK, the second error token specifies an event. Below is a list of events which the user may encounter most frequently. It is NOT a complete list of events. Events can be found in the file tiuser.h. The event value is in parentheses.

T_DISCONNECT (0x0010): Disconnect received.
This error could be caused by one of the following:
- The server was not started, or IPX/SPX support on the server was not started. Check the First Failure Service Log (DB2DIAG.LOG) at the server to see if messages have been logged.
- The node directory information specified on the client is incorrect.
- The client or server IPX/SPX communications stack was not installed and/or configured properly.
- The database agent at the server was forced off by the system administrator.
- A database agent could not be started at the server because the maxagents database manager configuration parameter has been exceeded. Check the First Failure Service Log (DB2DIAG.LOG) at the server to see if an error message has been logged.
- The database agent at the server was terminated due to an abnormal termination of a key database manager process.

When the first error token epecifies t_errno = TLOOK, and the second error token specifies the event T_DISCONNECT, the third error token specifies a disconnect reason code. Below is a list of disconnect reason codes which the user may encounter most frequently. It is NOT a complete list of reason codes. Disconnect reason codes can be found in the file tispxipx.h. The reason code value is in parentheses.

TLI_SPX_CONNECTION_TERMINATED (0xEC): Disconnect received from remote peer.
TLI_SPX_CONNECTION_FAILED (0xED): Connection failure.

For more information on TLI IPX/SPX communication errors, refer to the Transport Layer Interface documentation.

When using DOS, OS/2, or Windows IPX/SPX file server addressing mode, the following is a list of return values which the user may encounter most frequently. It is NOT a complete list of errors. Return values can be found in the file nwerror.h.

0x880F -

This is a "NO CONNECTION TO SERVER" error. Ensure that the file server specified is up and running, and can be accessed by the client and server workstations.

0x88FF -

If this error occurs when trying to connect to the database, and the function is NWAttachToFileServer, ensure that the IPX/SPX protocol support at the client has been installed correctly, and is started.

0x89EF -

This is an "INVALID NAME" error. Illegal characters were specified in the file server or object name. Control characters, the comma, semicolon, slash, backslash, question mark, asterisk, and tilde are invalid.

0x89F2

This is a "NO OBJECT READ PRIVILEGE" error. The client does not have access to read the DB2 server's object registered at the Netware file server.

0x89F4

This is a "NO OBJECT DELETE PRIVILEGE" error. Ensure that the userid/password specified during deregister has sufficient authority to delete an object and its properties, on the file server.

0x89F5

This is a "NO OBJECT CREATE PRIVILEGE" error. Ensure that the userid/password specified during register has sufficient authority to create an object and its properties, on the file server.

0x89F6

This is a "NO PROPERTY DELETE PRIVILEGE" error. Ensure that the userid/password specified during deregister has sufficient authority to delete an object and its properties, on the file server.

0x89F7

This is a "NO PROPERTY CREATE PRIVILEGE" error. Ensure that the userid/password specified during register has sufficient authority to create an object and its properties, on the file server.

0x89F8

This is a "NO PROPERTY WRITE PRIVILEGE" error. Ensure the that the userid/password specified during register has sufficient authority to write object property values, on the file server.

0x89FC -

This is an "UNKNOWN FILE SERVER" or "NO SUCH OBJECT" error.

If this error occurs when running the REGISTER/DEREGISTER command, ensure that:

An object name has been specified in the database manager configuration file, and the name contains valid characters.
A file server name has been specified in the database manager configuration file, and the name contains valid characters.

If this error occurs when trying to connect to the database, and the function is NWScanProperty, ensure that:

The network address of the database manager has been successfully registered at the NetWare file server. This is done by running the REGISTER command at the server.
The object name specified in the IPXSPX node directory entry at the client, matches the object name specified in the database manager configuration file at the server.
The file server name specified in the IPXSPX node directory entry at the client, matches the file server name specified in the database manager configuration file at the server.

If this error occurs on function NWAttachToFileServer, ensure that the files server name was configured correctly in the database manager configuration file.

If this error occurs on function NWLoginToFileServer, ensure that the userid specified on the register/deregister is valid for logging into the file server.

0x89FF -

This is a "NO SUCH OBJECT OR BAD PASSWORD" error. Ensure that the password you have specified is defined, and has not expired.

For more information on IPX/SPX file server addressing mode errors, refer to the NetWare Client API for C documentation.

When using Unix IPX/SPX file server addressing mode, the following is a list of error generators that identify what location generated the error.

0x00 - File server
0x10 - API
0x20 - API

When using Unix IPX/SPX file server addressing mode, the following is a list of error codes which the user may encounter most frequently. It is NOT a complete list of errors. On AIX, error codes can be found in the file nwerrors.h.

0x02 -

This is a "TRANSPORT OPEN" error. Ensure that IPX/SPX communications was installed and configured correctly.

0xDE -

This is a "BAD PASSWORD" error. Ensure that the password specified on register/deregister is valid for logging into the file server.

0xEF -

This is an "INVALID NAME" error. Ensure that the file server and object name specified in the database manager configuration file is valid. Check that the name does not contain illegal characters.

0xF2 -

This is a "NO OBJECT READ PRIVILEGE" error. The client does not have access to read the DB2 server's object registered at the Netware file server.

0xF4 -

This is a "NO OBJECT DELETE PRIVILEGE" error. Ensure that the userid/password specified during deregister has sufficient authority to delete an object and its properties, on the file server.

0xF5 -

This is a "NO OBJECT CREATE PRIVILEGE" error. Ensure that the userid/password specified during register has sufficient authority to create an object and its properties, on the file server.

0xF6 -

This is a "NO PROPERTY DELETE PRIVILEGE" error. Ensure that the userid/password specified during deregister has sufficient authority to delete an object and its properties.

0xF7

This is a "NO PROPERTY CREATE PRIVILEGE" error. Ensure that the userid/password specified during register has sufficient authority to create an object and its properties.

0xF8 -

This is a "NO PROPERTY WRITE PRIVILEGE" error. Ensure the that the userid/password specified during register has sufficient authority to write object property values, on the file server.

0xFC -

This is a "UNKNOWN FILE SERVER" or "NO SUCH OBJECT" error.

If this error occurs when running the REGISTER/DEREGISTER command, ensure that:

An object name has been specified in the database manager configuration file, and the name contains valid characters.
A file server name has been specified in the database manager configuration file, and the name contains valid characters.

If this error occurs when trying to connect to the database, and the function is NWScanProperty, ensure that:

The network address of the database manager has been successfully registered at the NetWare file server. This is done by running the REGISTER command at the server.
The object name specified in the IPXSPX node directory entry at the client, matches the object name specified in the database manager configuration file at the server.
The file server name specified in the IPXSPX node directory entry at the client, matches the file server name specified in the database manager configuration file at the server.

If this error occurs on function NWAttachToServerPlatform, ensure that the files server name was configured correctly in the database manager configuration file.

If this error occurs on function NWLoginToServerPlatform, ensure that the userid specified on the register/deregister is valid for logging into the file server.

0xFF -

This is a "NO RESPONSE FROM FILE SERVER". Ensure that the file server is up and running and accessible by the DB2 server and client.

For more information on IPX/SPX file server addressing mode errors, refer to the NetWare C Interface for UNIX API reference.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]