The argument to a cmdtool(1) or a shelltool(1) window looks like it is supposed to be a command, but the system cannot find the command.
To run this command inside a cmdtool(1) or a shelltool(1), make sure the command is spelled correctly and is in your search path. If necessary, use a full path name. If you intended this argument as an option setting, use a minus sign (-) at the beginning of the option.
Both the cmdtool(1) and the shelltool(1) are OpenWindows terminal emulators.
Solstice backup utility fails and displays the following error: access violation unknown host IP address on Networker 4.2.2. This error is usually caused by a corrupted host name in the host NIS/NIS+ map/table.
Check the Networker client configuration for an incorrect host name. If all else fails, as a workaround, add the entry to /etc/hosts.
The system is trying to exec(2) an a.out that requires that it be linked in a static shared library, and exec(2) could not load the static shared library. The static shared library is probably corrupted.
The symbolic name for this error is ELIBBAD, errno=84.
The user attempted to use an address already in use, and the protocol does not allow this.
The symbolic name for this error is EADDRINUSE, errno=125.
An address incompatible with the requested protocol was used.
The symbolic name for this error is EAFNOSUPPORT, errno=124.
AdminTool could not start a display method, because a remote procedure, which had been called, timed out; therefore, it could not send the request. You receive this error when admintool(1M) tries to access the NIS or NIS+ tables and networking is not enabled.
Verify the system network status with ifconfig -a to make sure the system is connected to the network. Make sure the Ethernet cable is connected and the system is configured to run NIS or NIS+.
This error is RFS specific. It occurs when users try to advertise a resource already advertised, try to stop RFS while there are resources still advertised, or try to forceably unmount a resource that is still advertised.
The symbolic name for this error is EADV, errno=68.
The AnswerBook navigator window comes up, but the document viewer window does not. This message appears on the console, and the message Could not start new viewer appears in the navigator window. This situation indicates that you have an unknown client or a problem with the network naming service.
Run the ypmatch(1) or nismatch(1) command to determine if the client host name is in the host's map. If not, add it to the NIS hosts map on the NIS master server. Then, make sure the /etc/hosts file on the client contains an IP address and entry for that host name, which is followed by loghost.
Reboot, if you changed the /etc/hosts file.
For more information on the NIS hosts map, see the section on the default search criteria in the NIS+ and FNS Administration Guide. If you are using AnswerBook online documentation, "NIS hosts map" is a good search string.
This error can occur when attempting to add or remove AP databases with the apdb command.
From /var/adm/messages you find the reason for the apdb command failure, as shown below:
Jan 15 14:00:51 Starfire2 apd: /etc/system: could not find: * End AP database info (do not edit) Jan 15 14:00:52 Starfire2 apd: failed to patch the system file!
* Begin AP database info (do not edit) set ap:apdb_dblist="sd:5 sd:8" * End AP database info (do not edit)
The system could not handle the number of arguments given to a command or program when it combined those arguments with the environment's exported shell variables. The argument list limit is the size of the argument list plus the size of the environment's exported shell variables.
The easiest solution is to reduce the size of the parent process environment by unsetting extraneous environment variables. (See the man page for the shell you are using to find out how to list and change your environment variables.) Then run the program again.
An argument list longer than ARG_MAX bytes was presented to a member of the exec(2) family of system calls.
The symbolic name for this error is E2BIG, errno=7.
This message is a programming error or a data input error.
Ask the program's author to fix this condition or to supply data in a different format.
This indicates an attempt to evaluate a mathematical programming function at a point where its value is not defined. The argument of a programming function in the math package is out of the domain of the function. This could happen when taking the square root, power, or log of a negative number, when computing a power to a non-integer, or when passing an out-of-range argument to a hyperbolic programming function.
To help pinpoint a program's math errors, use the matherr(3M) facility.
The symbolic name for this error is EDOM, errno=33.
This C shell error message indicates that too many arguments follow a command. For example, this can happen by invoking rm * in a huge directory. The C shell cannot handle more than 1706 arguments.
Temporarily start a Bourne shell with sh(1) and run the command again. The Bourne shell dynamically allocates command line arguments. Return to your original shell by typing exit.
An unexpected condition in the program has occurred.
Contact the vendor or author of the program to ask why it failed. If you have the source code for the program, you can look at the file and line number where the assertion failed. This might give you an idea of how to run the program differently.
This message is the result of a diagnostic macro called assert(3C) that a programmer inserted into the specified line of a source file. The untrue expression precedes the file name and line number.
The system is trying to exec(2) an a.out that requires more static shared libraries than is allowed on the current configuration of the system.
The symbolic name for this error is ELIBMAX, errno=86.
The file specified after the first colon is not a valid mount point, because it is not a directory.
Ensure that the mount point is a directory and not a regular file or a symbolic link.
This automounter message indicates that the system tried to mount a file system from an NFSTM server that is either down or extremely slow to respond. In some cases, this message indicates that the network link to the NFS server is broken, although that condition produces other error messages as well.
If you are the system administrator responsible for the non-responding NFS server, check to see whether the machine needs repair or rebooting. Encourage your user community to report such problems quickly, but only once. When the NFS server is back in operation, the automounter can access the requested file system.
For more information on NFS failures, see the section on NFS troubleshooting in the System Administration Guide, Volume 3. If you are using AnswerBook online documentation, a good search string is "NFS Service."