Client Errors

Client errors indicate client-specific problems.

Message	Vers.	Possible Cause(s)	Possible Solution(s)
!ERROR=8	NT, Novell, UNIX	Data Server and Client revision levels do not match.	Ensure that compatible versions of the Data Server and Client are installed. The Client version must be at the same level as the Server, or higher, in order to communicate properly.
!ERROR=12	NT, Novell, UNIX	The Data Server or the service name could not be located. The specified file is a duplicate or missing. Network problems such as lost connection, bad cable, etc.	Ensure that the Data Server is running on the correct port with the correct service name, and that the Client has enabled network access via the SETOPTS vector (byte 4, bit $20$). Additionally, ensure that the Client and Server can resolve each other's host names and IP addressed correctly under UNIX and NT. For a Windows client, ensure that the current drive is not excluded via DSKSYN, and the TCP/IP product is being used. Under Novell, ensure that the Data Server is using a separate config.bbx file than the clients. Specify a file that is known to exist on the server. In most cases, open the directory on the server to test the communication, as in: open(1)"<server,port=xxxx>" Ensure that the Client and Server machines can communicate readily.
!ERROR=18	UNIX, TCP/IP Client	The login lacks the proper permissions to a file or device. A root user tried to access a Data Server that was started by root. The prefix contains a directory that the login does not have permissions to access. Using the TCP/IP Client to access a UNIX Data Server without specifying a userid.	Correct any permissions problem that may exist. Ensure that the client is not logged in under the root account. Ensure that the client has sufficient privileges on all directories contained in the prefix, as they may be used when searching for a file or device. Ensure that the userid is set correctly. This can be done via the -u command line parameter or via the USERID environment variable. When the ushered is set properly, INFO(3,2) will return the userid.
!ERROR=60	NT, Novell, UNIX, ODBC	A general I/O error occurred. Diagnosing the problem requires the TCB(10) value immediately after the problem occurs. A TCB(10) of -161 under Windows indicates: The userid isn't set properly. The network access SETOPTS bit (byte 4, bit $20$) is not set. Problems with the .rhosts file. This may occur when the leading slash is missing on the open: open(1)"<server>/usr/bbx/data/"	Ensure that the userid is set correctly. This can be done via the -u command line parameter or via the USERID environment When the userid is set properly, INFO(3,2) will return the userid. Enable network access via the SETOPTS bit. INFO(3,4) should return the correct hostname for the workstation if this bit is set. Ensure that the client has sufficient remote login privileges. This is accomplished by including the remote host in the system's hosts.equiv file or the login's .rhosts file. The remote host entry in these files should be the same as the value returned when printing INFO(3,4) from the client. Additionally, the permissions on the .rhosts file should be set to 644 and the user has to be the owner of the .rhosts file - it cannot be owned by root or any other account Ensure that the OPEN was performed correctly: open(1)"/<server>/usr/bbx/data/"
!ERROR=60	Novell	!Attempting a RENAME on a long name space-configured volume.	Currently, it is not possible to use RENAME on a long name space configured volume.
!ERROR=60 (TCB(10)=-251)	Novell	On Netware 4, attempting to access the Data Server with a client that has only an authenticated connection obtained from the NetWare directory services to the server.	The work station using the Data Server must have a licensed connection to the NetWare Server that is running the Data Server NLM. This can be accomplished by mapping a drive to any volume on the server.
!ERROR=60 (TCB(10)=-35228)	Novell	Unable to access a remote-spooled printer when using NDS.	Specify the server= mode in the config.bbx file.
!ERROR=70	NT, UNIX	The .rhosts file is missing, lacks the proper permissions, or lacks the workstation listing. The Data Server's log file will typically have more information regarding the error.	Ensure that the client has sufficient remote login privileges. This is accomplished by including the remote host in the system's hosts.equiv file or the login's .rhosts file. The remote host entry in these files should be the same as the value returned when printing the INFO(3,4) from the client. Additionally, the permissions on the .rhosts file should be set to 644 and the user has to be the owner of the .rhosts file - it cannot be owned by root or any other account
!ERROR=71	NT, Novell, UNIX	The connection has failed, possibly because a cable was briefly disconnected. Potentially recoverable. The Data Server's log file may have more information regarding the error.	Restart the Data Server with the logging enabled. Recreate the exact error. The log file should identify the cause of the error.
!ERROR=72	NT, Novell, UNIX	The connection has failed and is not recoverable. The Data Server's log file may have more information regarding the error.	Restart the Data Server with the logging enabled. Recreate the exact error. The log file should identify the cause of the error.
!ERROR=151	NT, Novell, UNIX	The client and Data Server are incompatible.	Ensure that compatible versions of the Data Server and Client are installed. The Client and Data Server must be at the same major revision level in order to communicate properly.
fserr=5, fserrs=-21	ODBC	The DICTIONARY and DATA entries in the CONFIG.TPM file are not written in all caps. Equal signs (=) in the entries are preceded by one or more blank spaces. The path to the data files in the Data Dictionary definition is hard coded rather than set via the DATA global. The Network User ID field (in the advanced section of the Data Source Setup in the ODBC Administrator) is blank.	Ensure that DATA and DICTIONARY are in upper case in the CONFIG.TPM file. Remove all blank spaces in the DICTIONARY and DATA entries. Ensure that the file's location as specified in the Data Dictionary is correct. Typically, this should be prefixed with the DATA global so that the Data Server can be specified for a client's CONFIG.TPM file. Ensure that a valid login is entered in the Network User ID field
fserr=61 fserrs=-161	ODBC	The CONFIG.TPM paths for DICTIONARY and DATA may contain one or more spaces on either side of the equals (=) sign. There is a leading slash missing from the server specification in the DATA or DICTIONARY path in the CONFIG.TPM. The 'Network User ID' field in the data source configuration section of the Windows ODBC Administrator is blank or incorrect.	Remove all blank spaces in the DICTIONARY and DATA entries. Ensure that the DATA and DICTIONARY paths are correct. Ensure that a valid login is entered in the Network User ID field.
fserr=3, fserrs=3 or fserr=17, fserrs=17	ODBC	Multiple applications or sessions attempted to connect to the same data source from the same workstation. (Occurs in evaluation versions only.)	Invoke only one session at a time.
[BASIS] [BASIS ODBC Driver] No such table in catalogSQLGetTypeInfo Critical Signal: No such table in catalog	ODBC	The data dictionary is damaged or incorrect.	Force the ODBC driver to recreate the shadow data dictionary. First, physically remove the old shadow data dictionary by removing the *.dat files in the data dictionary directory. Then turn off the `Fast Connect' and `No Shadow Data Dictionary Consistency Check' options in the ODBC Administrator's Advanced dialog. Finally, reconnect to the Data Source.
fserr=13, fserrs=13	ODBC	Filename case differs from CONFIG.TPM file setting case. The file referenced cannot be found.	Ensure that the specified file's case is correct. The file's case must be taken into account when describing its location in the Data Dictionary. Ensure that the file exists.
fserr=70 (PRO/5 ERROR 69)	ODBC	Possible license conflict.	As this can occur when multiple workstations use the same ODBC Driver, ensure that each workstation has a unique copy and serial number for the ODBC Driver. The Data Server's log will indicate which machines the serial number is installed on.
fserr=71 (PRO/5 ERROR 70)	ODBC	The Data Server's .rhosts file does not contain the user's host name.	Include the user's host name in the Data Server's .rhosts file.
TCB(10)=-10061	TCP/IP Client	Windows socket 'Connection Refused' error. This can occur when: An incorrect port is specified when attempting to open a file or device. The Data Server is not running. The .rhosts file is missing, lacks the proper permissions, or lacks the workstation listing. The Data Server's logfile will typically have more information regarding the error.	Ensure that the correct port is specified in the OPEN or that the default port is set correctly in the services file. Ensure that the Data Server is running. Ensure that the client has sufficient remote login privileges. This is accomplished by including the remote host in the system's hosts.equiv file or the login's .rhosts file. The remote host entry in these files should be the same as the value returned when printing the INFO(3,4) from the client. Additionally, the permissions on the .rhosts file should be set to 644.