Ref: 99980011 Title: Connection Service Error Messages Date: 8/1/86 Copyright 3Com Corporation, 1991. All rights reserved. Connection Service Error Messages This section provides an alphabetical list of all error messages generated by the Connection Service and describes the probable causes of each message. Unless specifically noted, the error messages apply to call Connection Service servers. The error code listed for each message is the number generated if the port's InterAction parameter is set to Brief, which causes the server to return errors as numeric codes rather than as text strings. .h1;Text Messages .h2;Aborted .br;Error code: 50 This message appears if the user terminates the interactive setting of a port's default parameters by pressing the escape key before the system has stepped through all parameters. All parameters set prior to the escape take effect, but the system does not prompt for more values. The interactive setting of all default parameters for a port is initiated by entering the SETDefault command without specifying any parameters. .h2;Ambiguous, try one of: .br;Error code: 55 This message appears if the user types an incomplete command name. The system lists all possible commands that could be made from the incomplete entry. Reenter the command using an unambiguous abbreviation of the command name. .h2;Ambiguous parameter name, try one of: .br;Error code: 46 This message appears if the user types an incomplete parameter abbreviation in one of the commands that sets or displays a parameter value. The system lists all parameter names that could be assumed from the incomplete entry. Reenter the command using an unambiguous abbreviation of the parameter. .h2;Autodisconnect timer expired .br;Error code: 12 This message appears if the user's port has been inactive longer than the interval specified by the AUToDisconnect parameter of the destination port. The default value of the AUToDisconnect parameter is 60 minutes for all ports whose DeVice parameter is set to Host; the parameter does not apply to ports whose DeVice parameter is set to Terminal and does not apply to GS/1 virtual ports. .h2;Broadcast is not enabled for that port .br;Error code: 78 This message appears if the user attempts to broadcase a message to a port whose InterAction parameter is set to BroadcastOFF. .h2;Can't - diskette write protected .br;Error code: 28 This message appears if the user issues a command requiring information to be stored on the system diskette while a write- protect tab is in place on the diskette. First remove the write- protect tab from the diskette, then enter the command again. If this message appears in response to the Name command, the system may have placed a protective lock on the clearinghouse database. In this case, a subsequent attempt to enter the Name command results in a disk I/O error. To recover, reboot the server, using a system diskette that it not write-protected. .h2;Can't - no memory .br;Error code: 37 This message appears if the system does not have enough memory available at the time a command is entered to complete execution of the command. In most cases, this is a temporary situation caused by un unusual circumstance, such as multiple users issuing simultaneous requests for a complex macro file. Wait until system activity has decreased and enter the command again. If this message appears in response to the DE command, the specified macro file may contain too many complex display commands. if the system fills all available buffers while waiitng for a display to complete, it terminates the process (i.e., places the port in Listening mide). .h2;Can't DEFine from a macro .br;Error code: 73 This message appears when a macro file that contains a DEFine command is executed with the DO command. Macro files cannot contain the DEFine command. Macro files can, however, contain the DO command to call a different, predefined macro. .h2;Can't REMoteSET this parameter .br;Error Code: 75 This message appears if the user tries to use the REMoteSET command to change a parameter that can be changed only with the SET or SETDefault command. The REMoteSET command can be used to change come but not all of the parameters that can be changed with the SET command. To display a list of all parameters that can be set with the REMoteSET command, enter the command followed by a question mark. .h2;Can't save -- directory full .br;Error Code: 30 This message appears on disk-based servers if the user tries to add another configuration or macro file after all available disk space for these files is used. A disk-based CS/1 holds up to 96 configuration files and up to 96 macro files; a GS/1 holds up to 48 configuration files and up to 48 macro files; a disk-based CS/100 holds up to 32 configuration files and up to 32 macro files. .h2;Can't SET yet -- no session .br;Error Code: 77 This message appears if the user tries to set an active session parameter for a port with no current sessions. When a port changes from Listening to Command mode, the system creates a working table of active port parameters by copying the port parameter portions of the port's default parameter table. When a connection with a remote device is established on that port, the server completes the active parameter table by copying the session parameters from the default parameter table. The SET command can be used only to change parameters that have an active value. .h2;Can't SETD this parameter .br;Error Code: 76 This message appears if the user tries to change the default value of the PRIvilege parameter. For security purposes, the default value of the PRIvilege parameter is always User for all ports. In order to access higher privilege levels, the user must issue the SET PRIvilege command and enter the appropriate password. The higher privilege level remains in effect only as long as the port remains active. .h2;Clearinghous is out of memory .br;Error Code: 19 This message appears if the system does not have enough memory available to process the command when a clearinghouse access request is entered. In most cases, this is a temporary situation caused by an unusually high level of system use. Wait until demand for the system resources is lower and reissue the command. .h2;Clearinghouse name in use .br;Error code: 6 This message appears if the user specifies in the Name command a clearinghouse name that is already defined in the local clearinghouse. To change to assignment of a name that has already been defined, first removed the name from the clearinghouse with the UNName command, and then redefine it with the Name command. .h2;Clearinghouse name invalid .br;Error code: 2 This message appears if the user specifies an illegal clearinghouse name in the Name or Connect command. The local name field in a clearinghouse name can include up to 10 alphanumeric characters, the first of which must be an alphabetic character, or up to 18 numeric digits. .h2;Clearinghouse name not found .br;Error code: 11 This message appears if the server is unable to locate in any clearinghouse on the network a name specified in the Connect or SHow CHN command. A failure to locate the name can mean either that the name has not been defined or that the server on which the name is defined is not currently available. .h2;Clearinghouse name table is full .br;Error code 18 This message appears if the clearinghouse name table is already full when the user issues the Name command. The Series/1 servers that boot from a local disk drive each support up to 80 clearinghouse names. A CS/100 that boots from a local disk drive supports up to 18 clearinghouse names. An NCS/150 supports up to 4,096 clearinghouse names for all of its client servers. .h2;Clearinghouse received no response .br;Error code: 22 This message appears if a Communications Server that boots from an NCS receives no answer to a clearinghouse access request sent to the NCS. The message could mean that athe NCS is turned off or disconnected from the network, or that the NCS is momentarily busy handling other requests. .h2;Clearinghouse value invalid .br;Error code: 16 This message appears if the user issues a command containing a logical name longer than 120 characters; the message does not appear as a GS/1 error message. .h2;Directory empty .br;Error code: 31 This message appears if the user requests a display of the stored macro or configuration files before any files have been established. .h2;DISKIO read error .br;Error code: 25 This message appears if the system is unable to complete a diskette read process. The most likely cause of the read error is deterioration of the diskette medium. Try replacing the working diskette with a backup copy. .h2;DISKIO seek error .br;Error code: 24 This message appears if the system is unable to complete a diskette seek process. The most likely cause of the seek error is deterioration of the diskette medium. Try replacing the working diskette with a backup copy. .h2;DISKIO write error .br;Error code: 26 This message appears if the system is unable to complete a diskette write process. The most likely cause of the write error is deterioration of the diskette medium. Try replacing the working diskette with a backup copy. .h2;Drive door open or diskette missing .br;Error code: 27 This message appears if an attempt to read or write to the diskette fails because the drive door is open of the diskette is not in place in the drive. .h2:File not found or in use .br:Error code: 29 This message appears if the NCS/150 fails to respond to a request from a client server for access to a configuration or macro file. The message may mean only that another device on the network is currently accessing the file. If the message appears repeatedly, however, the requested file may not exist. .h2;Illegal request -- wrong state .br;Error code: -1 This message appears if the user issues a command that has no meaning for the port in its current state. This message appears, for example, in response to the DEQueue command issued at a port that has no queued connection request. .h2;Insufficient privilege .br;Error code: 36 This message appears when a user issues a command that requires a higher privilege level than is currently in effect at the local port. There are three privilege levels: User, Local Network Manager, and Global Network Manager. .h2;Invalid syntax .br;Error code: 33 This message indicates a syntax error in the last command issued. The error could be with one of the fields in the command line or with the structure of the command line. For a syntax description of a command, enter the command name followed by a question mark. .h2;Invalid DATe .br;Error code: 70 This message indicates a syntax mistake in the SET DATE command. The date entered must follow one of these formats: yy/mm/dd hh:mm[:ss] mm/dd/yy hh:mm[:ss] .h2;Invalid command .br;Error code 39 This message appears when the user issues a command that the server does not recognize. The message usually indicates a typing mistake, although it sometimes appears in response to a syntax error. The message may also appear in response to a Connection Service command that is not available on the model of the server with which the user is interacting. To display a list of all available commands, enter a single question make. .h2;Invalid remote command .br;Error code: 68 This message appears when a user in remote communication with a distant server issues a command that is not available in remote mode. Only a subset of the starndard commands are available in remote mode. Specifically, commands used to create and manipulate new sessions are restricted. The REMoteSET, REMoteSHow, and RESume commands are unavailable on the Communications Server. On the Communications Servers and the GS/ 1, the Connect command may be used only to interconnect remote ports, and the SWitch and Transmit commands are unavailable. To display a list of available command, enter a single question mark. .h2;Invalid session number .br;Error code: 42 This message appears when the user specifies an inappropriate session number in a command that accepts a session number as an argument. Either the specified session number does not exist or it is not a valid session number. Valid session numbers are the digits 1 through 8. Sessions are numbered sequentially in the order in which they are created: each session retains its original session number even if sessions with lower numbers are subsequently terminated. .h2;Macro definition too long .br;Error code: 72 This message appears in response to the DEFine command if the defined macro includes more than 256 characters. If the commands to be included in the macro require more than 256 characters, split the contents into two or mote macro files, and imbed the DO command in one of them to call the others. .h2;Macros nested too deeply .br;Error code: 74 This message appears when a user executes with the DO command a macro that initiates a sequence of more then ten calls to other macros. Although the DO command may be embedded in a macro in order to call another macro, the nesting of macros is limited to ten. .h2;Missing '=' after parameter .br;Error code: 43 This message appears in response to the SET, SETDefault, or REMoteSET command if the user omits the equal sign (=) between the parameter name and the parameter value. .h2;Missing after parameter .br;Error code: 44 This message indicates that the parameter value is missing in the SET, SETDefault, or REMoteSET command. To display a list of all values that can be specified for a given parameter, enter this command: set = ? .h2;Name Server is out of memory .br;Error code: 19 This message appears if the system does not have enough memory available to process the command when a Name Server access request is entered. In most cases, this is a termporary situation caused by an unusually high level of system use. Wait until the demand for system resources is lower and reissue the command. .h2;Name Server name in use .br;Error code: 6 This message appears if the user specifies in the Name command an internet name that is already defined in the local Name Server. On a server running XNS protocols, this message appears if the user specifies a clearinghouse name that is already defined on the local clearinghouse. To change the assignment of the name, first remove the name with the UNName command, and then redefine it with the Name command. .h2;Name Server name invalid .br;Error code: 2 This message appears if the user specifies an illegal internet name in the Name or Connect command. .h2;Name Server name not found .br;Error code: 11 This message appears if the server is unable to locate in any Name Server on the network a name specified in the Connect or SHow NAmes command. A failure to locate the name can mean either that the name has not been defined or that the server on which the name is defined is not currently available. .h2;Name Server name table is full .br;Error code: 18 This message appears on TCP servers if the internet name table is already full when the user issues the Name command. A CS/2 supports up to 64 internet names; a CS/100 supports up to 24 internet names. .h2;Name Server value invalid .br;Error code: 16 This message appears if the user issues a command containing a logical name longer than 120 characters. .h2;No access allowed .br;Error code: -13 This message appears if a user unable to provide the correct password after issuing a connection request to an access- controlled port. If the user's port was configured to allow access to the device, then this message does not appear because the user is not required to issue a password. First ascertain the password needed to make the connection, then reissue the connection request. To set up the port permanently for unrestricted access to the destination device, set the AccessWord parameter of the source port to match at least one value in the AccessGroup parameter of the destination port. .h2;No current session .br;Error code: 40 This message appears if the user issues a command that affects a session when no session exists. The RESume, SWitch, and DEQueue commands, for example, have no meaning unless a suspended or queued session exists on the port. .h2;No memory resource .br;Error code: -2 This message appears if the system does not have enough memory available to complete execution of the last command entered. In most cases, this is a temporary situtation caused by an unusually high demand for system resources. Wait until the system activity levels are lower and reissue the command. .h2;No more sessions for this port .br;Error code: -9 This message appears in response to the Connect command if the source port is already connected to as many devices as followed for the port. The default maximum number of sessions of each port is two. This maximum can be changed with the MaxSessions parameter. .h2;No other sessions .br;Error code: 41 This message appears if the user issues the SWitch command to change to another session when only one session exists on the port. .h2;No response .br;Error code: -10 This message appears when a session has been terminated by the server at the host end because no activity has taken place on the circuit for the period of time specified by the AUToDisconnect parameter. The message may also appear if the server at the host end stops responding to packets from the server at the terminal end. .br;Parameter may not be SET, use SETD .br;Error code: 69 This message appears if the user tries to adjust a parameter with the SET command that can be changed only with the SETDefault command. The parameters that can be set only with SETDefault are InitMacro, DataBits, GlobalPassWord, GroupxPasswd, LocalPassWord, NMPrompt, PROMPt, and WelcomeString. .h2;Parameter : Value is illegal .br;Error code: 47 This message appears if the user specifies a value that is not available for the parameter being set. Some parameters accept numeric or string values, and some parameters accept only values from a list of system-defined options. To display a list of all settings available for a specific parameter, enter the SET command followed by the parameter name and a question mark. .h2;Parameter : Value is out of range .br;Error code: 48 This message appears if the user specifies an illegal value for one of the parameters that accepts numberic values. To display the acceptable range for a parameter value, enter the SET command followed by the parameter name and a question mark. .h2;Parameter unknown .br;Error code: 34 This message appears if the user enters a word the server does not recognize in a place where the server expects a parameter name. This message could appear if, for example, the user inserts an address or parameter value at the wrong place in a command. To invoke a screen display of the parameters available with a specific command, enter the command name followed by a question mark: ? .h2;Portid out of range .br:Error code: 59 This message appears if the user specifies a port number that is not available on the server that implements the command. The CS/1 uses physical port numbers 0 through 31 and virtual port number 32 through 95; the CS/100 uses physical port numbers 0 through 13 and virtual port number 14; the GS/1 uses virtual port numbers 0 through 47. .h2;Remote is busy .br;Error code: -5 This message appears in response to the Connect command if the requested destination port is already part of another virtual circuit. .h2;Remote is disabled or nonexistent .br;Error code: -4 This message appears in response to the Connect command if the requested destination port does not response to the connection request. Usually, this message indicates that the destination device is turned off or disconnected. It can also mean that the port configuration of the destination device is actually available, check the setting of the UseDTRin parameter on the destination port. Ordinarily this parameter is set to AsDTR for a host port. If, however, the host does not generate a DTR signal, the UseDTRin parameter should be set to Ignore or AsDCD. .h2;Remnote received bad address .br;Error code: -6 This message appears if the user specifies an invalid port number as all or part of the destination address in a connection request. .h2;Remote received bad parameters .br;Error code: -8 This message occurs only if a connection is made between a Bridge server and a non-Bridge server. When the connection is established, a set of parameters is exchanged between the two servers. If either server does not recognize one or more of the parameters, it sends this message to the other end of the connection. .h2;Remote software incompatible .br;Error code: -3 This message appears if a user tries to interact with a remote server that is running a version of the communications software incompatible with the version running on the local server. This occurs only if one or more servers on the network is running an obsolete version of software. Use the SHow VERSion command on each server to determine which is running obsolete software. .h2;Reserved timer expired .br;Error code: -14 This message appears if the user failed to complete a queued connection within five minutes of being informed that the queued connection is available. When this message appears, the user's port is removed from the connection queue and the connection is given to the next port in the queue, if any. To complete a queued connection when it becomes available, the user issues the RESume command. If a different session is active on the user's port when the notification is received, the user must first issue the SWitch command so that the queued session is current. .h2;Rotary number out of range .br;Error code: 58 This message appears if the user specifies an illegal rotary number. Rotary numbers can be established in the range 128 through 135. .h2;SET what? .br;Error code: 45 This message appears if the user omits the parameter name from the SET command. For a list of all parameters that can be set, enter the SET command followed by a question mark: .br; set ? .h2;SHow parameters for which port? .br;Error code: 71 This message appears if a user issues the SHow PARAmeters command in remote mode without specifying a port number. Since a user in remote mode is communicating with a virtual network manager port, the SHow PARAmeters command cannot assume the local port as the default. .h2;SHow what? .br;Error code: 51 This message appears if the user omits the keyword from the SHow command. For a list of all variations on the SHow command, enter the command followed by a question mark: .br; show? .h2;Sorry .br;Error code: 49 This message appears if the user failed to supply the correct password while trying to change privilege levels or connect to an access-controlled destination address. If the user fails to supply the correct password on the previous 1000 attempts to change privilege level, no passwork prompt appears. Instead, this message appears immediately after the request. Passwords must be entered in the correct case and must match exactly the password established by the network manager. The default vaule for all passwords on a new server is null (""). .h2;String truncated .br;Error code: 54 This message appears if the user enters a string that is too long for the command in which it is included. The local name field of a clearinghouse name can contain up to 10 alphanumeric characters or up to 18 all-numeric characters. The domain and organization fields of a clearinghouse name can contain up to 10 alphanumeric characters. Filenames, passwords, and prompts can contain up to 14 characters. The welcome string can be up to 80 characters long. The Broadcast, Echo, and Transmit commands accept strings up to 82 characters long. .h2;Timeout failure .br;Error code: -11 This message appears if a server receives no answer to a request for information accress the network. The message most often means that the server to which the request is directed is turned off or disconnected. .h2;Unknown errors .br;Error code: -7 This message appears if the server is unable to complete the last command entered and is unable to indentify the source of the problem. .h2;Unknown command .br;Error code: 38 This message appears if the server does not recognize the first word in a command. The message usually indicates a typing mistake, but can also mean that the user has entered a valid command that is not available on the local server. For example, a server running an early software version may not recognize the DEQueue command. For a list of all commands available to the local port at its current privilege level, enter a question mark. .h1;Brief Mode Error Codes Brief Mode Error Codes Error Code Equivalent Message ------------------------------------------------- -14 "Reserved timer expired" -13 "No access allowed" -12 "Autodisconnect timer expired" -11 "Timeout failure" -10 "No response" -9 "No more sessions for this port" -8 "Remote received bad parameters" -7 "Unknown errors" -6 "Remote received bad address" -5 "Remote is busy" -4 "Remote is disabled or nonexistent" -3 "Remote software incompatible" -2 "No memory resource" -1 "Illegal request -- wrong state" 0 No error 1 (1) 2 "[Clearinghouse|Name Server]name invalid" 3-5 (1) 6 "[Clearinghouse|Name Server]name in use" 7-10 (1) 11 "[Clearinghouse|Name Server]name not found" 12-15 (1) 16 "[Clearinghouse|Name Server]value invalid" 17 (1) 18 "[Clearinghouse|Name Server]name table is full" 19 "[Clearinghouse|Name Server]is out of memory" 20 (1) 21 (1) 22 "Clearinghouse received no response" (2) 23 (1),(3) 24 "DISKIO see error" 25 "DISKIO read error" 26 "DISKIO write error" 27 "Drive door open or diskette missing" 28 "Can't - diskette write protected" 29 "File not found or in use" 30 "Can't save -- directory full" 31 "Directory empty" 33 "Invalid syntax" 34 "Parameter unknown" 35 (1) 36 "Insufficient privilege" 37 "Can't - no memory" 38 "Unknown command" 40 "No current session" 41 "No other sessions" 42 "Invalid session number" 43 "Missing '=' after parameter " 44 "Missing after parameter " 45 "SET what?"