X Server Messages

Messages Common to All Modules

This section is an alphabetical listing of X server messages common to all modules. If you are looking for a message that is not listed here, refer to the sections that follow.

BADACCEPT, unable to accept on protocol socket: message

Severity:: Error

Explanation:: The reporting module cannot accept a connection on the specified network socket. The included message describes the reason for the error.

User Action:: If you encounter this error message, please contact NCD Technical Support.

BADBIND, unable to bind protocol socket: message

Severity:: Error

Explanation:: The reporting module cannot assign a name to the specified network socket. The included message describes the reason for the error.

User Action:: If you encounter this error message, please contact NCD Technical Support.

BADCOMPFMT, invalid compression format in file: file

Severity:: Error

Explanation:: The specified file does not contain the expected compression factor, and therefore the X server cannot confirm that the file is compressed.

User Action:: Confirm that the specified file is compressed.

BADCOMPSIZE, wrong compression factor (use 12 bits) in file: file

Severity:: Error

Explanation:: The specified file indicates that it is using a compression factor different from that which the X server expects; NCDware software uses a 12- bit compression factor.

User Action:: Confirm that 12-bit compression was specified when the file was compressed (for example, by the command-line option -b12).

BADCONNECT, unable to connect to protocol socket: message

Severity:: Error

Explanation:: The X server cannot connect to the specified network socket for the reason given.

User Action:: Verify that the network address is correct and confirm that the desired host is available on the network.

BADGETSOCKETOPT, unable to get protocol socket option option: message

Severity:: Error

Explanation:: The reporting module cannot use the specified socket option for the reason given.

User Action:: If you encounter this message, please contact NCD Technical Support.

BADLISTEN, unable to listen on protocol socket: message

Severity:: Error

Explanation:: The reporting module is unable to listen for network connections.

User Action:: If you encounter this message, please contact NCD Technical Support.

BADNET, client, unknown network: message

Severity:: Error

Explanation:: The specified client could not create a connection to the specified transport. This situation usually occurs with the DECwindows login client.

User Action:: If you encounter this message, please contact NCD Technical Support.

BADREAD, read error on file: message

Severity:: Error

Explanation:: The X server cannot read the specified file for the reason given.

User Action:: Verify that:

The filename is specified correctly.
The file service table contains an entry for the specified file.
The file has read access.

BADREFCNT, resource, bad reference count n

Severity:: Error

Explanation:: The X server cannot reconcile the reference count for the specified resource. This message typically appears when the reference count should be zero because no one is using the resource, but the reported count is greater than zero.

User Action:: If you encounter this message, please contact NCD Technical Support.

BADSETSOCKETOPT, unable to set protocol socket option option: message

Severity:: Error

Explanation:: The reporting module cannot set the specified socket option for the reason given.

User Action:: If you encounter this message, please contact NCD Technical Support.

BADSOCKET, module: unable to create protocol socket: message

Severity:: Error

Explanation:: The X server cannot create the specified socket for the reason given.

User Action:: If the reason given is "no buffer space," try increasing the buffers allocated in the net-minimum-data-buffers parameter. Otherwise, please contact NCD Technical Support.

BADWRITE, write error on file: message

Severity:: Error

Explanation:: The X server cannot write to the specified file for the reason given. This situation usually occurs if the file does not have write access or if there is not enough memory.

User Action:: Verify that:

The file has write access.
The filename is specified correctly.
There is sufficient memory to perform the operation.

CLOSE, closing file_type: file

Severity:: Information

Explanation:: The reporting module is closing the specified file as requested.

User Action:: None

INITUI, unable to initialize user interface

Severity:: Fatal

Explanation:: The reporting module cannot create a dialog box to display an X server message. The message appears but it is not contained in a dialog box. This situation usually occurs when the terminal is low on memory.

User Action:: Check the terminal's memory level. Close any inactive local clients to free local memory.

NOACCESS, access denied to font_server font_server_name

Severity:: Error

Explanation:: The terminal cannot access font_server_name.

User Action:: Make sure that the named font server is available.

NODECOMP, error installing decompression for file file: message

Severity:: Error

Explanation:: The X server cannot decompress the specified file for the reason given. This message usually indicates the terminal is low on memory.

User Action:: Check the available memory to make sure that it is sufficient to perform the desired decompression. Close any local clients that are not being used to free memory.

NOHOSTADDR, unable to find address for host name: host

Severity:: Error

Explanation:: The reporting module cannot locate the network address for the specified host.

User Action:: Make sure the hostname is correct. If it is, verify that the terminal's configuration database correctly identifies the system that is to provide name service for the terminal.

NOLICENSE, this unit not licensed for feature

Severity:: Error

Explanation:: The terminal does not have a license for the specified feature, such as DPS.

User Action:: Contact NCD to obtain a valid license for the specified feature and enter it in the terminal's configuration file, NVRAM, or license.dat file.

NOMEM, function, out of memory for data_structure

Severity:: Error

Explanation:: The X server does not have sufficient memory to perform the requested function.

User Action:: Close any unused local clients to free memory for the desired function.

NOOPEN, unable to open file_type: file

Severity:: Error

Explanation:: The reporting module cannot open the specified file.

User Action:: Make sure:

The filename is correct.
The file exists in the specified directory.
The file service table contains an entry for the specified directory.
The specified file has read access.

NOPROC, unable to create new process for client

Severity:: Error

Explanation:: The X server cannot start the requested client. This situation generally occurs when the X server is running low on memory or when there are too many clients running for the amount of available memory.

User Action:: Close any unused local clients to free memory for the desired function.

NOREAD, unable to read file_type: file

Severity:: Error

Explanation:: The reporting module cannot read the specified file.

User Action:: Make sure:

The filename is correct.
The file exists in the specified directory.
The file service table contains an entry for the specified directory.
The specified file has read access.

NOWRITE, unable to write file_type: file, message

Severity:: Error

Explanation:: The reporting module cannot write information to the specified file for the specified reason.

User Action:: Make sure:

The filename is correct.
The file exists in the specified directory.
The file service table contains an entry for the specified directory.
The specified file has write access.

NOX, unable to connect to display display

Severity:: Fatal

Explanation:: The reporting module cannot connect to the specified terminal.

User Action:: Make sure that the name specified is correct for the desired terminal. If the terminal name is correct, verify that the network is operational and that the terminal is running and is connected to the network.

OPEN, opening file_type: file

Severity:: Information

Explanation:: The reporting module is opening the specified file as requested.

User Action:: None

READ, reading file_type: file

Severity:: Information

Explanation:: The reporting module is reading the specified file as requested.

User Action:: None

START, starting up

Severity:: Information

Explanation:: The specified module is starting as requested.

User Action:: None

STOP, shutting down

Severity:: Information

Explanation:: The specified module is shutting down as requested.

User Action:: None

WRITE, writing file_type: file

Severity:: Information

Explanation:: The specified module is writing information to the specified file.

User Action:: None

XKILLED, connection closed by X server

Severity:: Fatal

Explanation:: In the process of shutting down, the X server has stopped the reporting module.

User Action:: Check the application(s) that were running when the X server closed the connection to ensure that the clients exited gracefully and did not lose any information.

[Top] [Prev] [Next] [Contents] [Index]

Send comments, suggestions, or questions about this document to the NCD Technical Publications Department by Internet e-mail. Write to us at techpubs@ncd.com.