Log File Errors
Log file errors, generated if logging is enabled, provide detailed information concerning errors sent to the client.
Message |
Vers. |
Possible Cause(s) |
Possible Solution(s) |
Client at connection C task could not allocate B bytes |
Novell |
A workstation memory shortage prevented the Data Server from responding to a request. |
Add or free up memory on the client. |
Invalid request Unknown command |
Novell |
General network failure. |
Ensure that the network is operating properly. Network failures can be caused by faulty Network Interface Cards or cabling, bad drivers/client kits, or electrical interference. |
License conflict: serial number S already registered |
NT, UNIX |
Two or more hosts are using the same serial number. |
Remove the Data Server from the other server(s). |
logging out for relogin reconnect after reset |
Novell |
A PRO/5 client terminated abnormally (via Ctrl-Alt-Del, etc.), and will restart and reestablish contact with the Data Server. |
For informational purposes only. |
No free user slots |
Novell |
All licensed connections are filled. |
As this indicates that all licensed slots are filled, clients will either have to be disconnected to allow for further connections or more licenses purchased. |
reset: connection C task reason R |
Novell |
A connection is no longer valid because a workstation has failed or has been turned off or reset without closing all files. |
For informational purposes only. |
error getting packet size |
ODBC |
The data dictionary is either corrupt or missing. |
Ensure that all of the data dictionary files exist. If necessary, restore from a reliable backup or investigate the files with the _FIX utility. |
Bad Start Packet |
NT, UNIX |
A new connection was opened to a 2.10+ version of Visual PRO/5 via a pre-2.10 version of the Data Server. |
Upgrade the Data Server to version 2.10 or later. |
root access not permitted |
UNIX |
A root user tried to access a Data Server that was started by root. |
Ensure that the client login is not using the root account. |
Server out of memory Unable to start thread Could not assign task number |
Novell |
The file host server experienced a memory shortage. |
Check available system memory on the server. |
server: can't allocate lockbyte |
UNIX |
All licensed connections are being used. |
As this indicates that all licensed slots are filled, clients will either have to be disconnected to allow for further connections or more licenses purchased. |
server: error cannot malloc receive buffer |
NT, UNIX |
Not enough memory to run the Data Server. |
Check available system memory on the server. Under NT, ensure that other applications are not monopolizing the system's resources. |
server: fork failed: errno: E |
UNIX |
The system cannot create any more processes. |
Usually adjustable by tuning the kernel. |
server: license expired |
NT, UNIX |
The time limit for the evaluation version of the Data Server has expired. |
Restart the Data Server or purchase a fully-functional version. |
[date time]: connect error, gethostbyaddr failed errno: 0, h_errno: 2 |
NT, UNIX |
Host server cannot resolve the workstation's host name from its IP address. |
Ensure that the server can resolve the workstation's name from its IP address. This may be defined in the client's hosts file, the DNS setup, the WINS server or DHCP server. For additional information, please contact your system administrator. |
user not in passwd, user: U ruserok failure, host: H user: U localuser: L (uid:N) |
UNIX |
Connection to the Data Server was not validated by TCP/IP security. |
Ensure that proper access is given to the specified login. This is done via the login's .rhosts file or via the system's hosts.equiv file. For additional information, please contact your system administrator. |