|
Prompt Messages:
Prompt messages result from an action you take, such as choosing a menu command.
Bad IP Address for: nodename
You entered a bad IP address into the IP Address edit box of the Node Properties dialog box. The name is either not in the host file or doesn't conform with Internet dot notation (XXX.XXX.XXX.XXX).
Bad SNMP variable value
You entered a bad value into the Variable Value of the Edit MIB variables or Edit MIB Table dialog boxes. The value does not conform with the format defined in the MIB database. The Edit MIB Variables command value type is shown in a selected radio button. To find the Edit MIB Table command, click Expand to see the type.
Bad Table Name
You entered an unknown table name using the Display MIB Table or Edit MIB Table commands. Select a table from the list boxes.
Cannot create MIB database
The MIB compiler couldn't create the MIB database c:\ldnm\mibfiles\mib.dat. The file may be marked read-only or the disk may be full.
Cannot create temp file
The command you selected was unable to create a temporary file. The TEMP path variable may be set to an invalid directory or the disk may be full.
Cannot get printer info
The Print command could not find a printer definition in the win.ini file. Check the file to make sure the printer is defined there.
Cannot move node to itself
You have tried to move a hierarchy node into itself, or into one of its children hierarchies.
Cannot open file: filename
Network Manager could not open the specified file. This error may occur during an Open Map or Open Log command. It could also occur with the Compile MIB command if the index file, c:\ldnm\mibfiles\names.txt, is missing, or if this file contains the name of a MIB source file that does not exist.
Cannot write file: filename
Network Manager could not write to the specified file. This error can occur when using the Save Map, Save Window, or Compile MIB commands for any operation that writes to a temporary file, or when Network Manager writes to the log file. This is probably due to a full disk.
Corrupt MIB database entry
There is an error in the MIB database file, c:\ldnm\mibfiles\mib.dat. Exit Network Manager, manually delete this file, then start the application again. Network Manager recreates this file if it is missing. This may be caused by a disk error, so use the DOS chkdsk command before running Network Manager again.
DDE Channel Busy
You performed a Display MIB Table or Edit MIB Table Entry command from a Network Manager application while the command was active (dialog box open) in Network Manager.
End of MIB
You performed a GetNext operation using the Edit MIB Variables or Edit MIB Table commands, on the final variable in a MIB table. You can use GetNext to get to the next entry in a table, but not to reach the next table.
End of log view reached
You performed a Search Filter or Search Next command and no matching
entries were found.
File filename is corrupt
The Network Manager map file or config file is corrupt. You can ignore this error for a config file (config.txt) , as Network Manager will recreate the file when you exit the program. The file may have been corrupted by a disk error, in which case you should first use the DOS chkdsk command, then delete the file and recreate it.
Logged num-err mib compile errors to history.log (num-ok entries OK)
The Compile MIB command detects errors in the source files. Num-err is the number of errors that were detected. The error messages were written to the history log file. There were num-ok good MIB entries compiled.
Name not in MIB database
You entered a nonexistent object identifier as the variable name in the Edit MIB table, Edit MIB Variables, or Display MIB Table command.
Network error detected
An error was encountered while trying to access the TCP/IP protocol software. The software is not installed properly, is not running, or the device is not configured properly. Refer to the protocol documentation for instructions on how to setup and test the protocol software.
Unresolved host name
When adding a node, or changing a node's name, you selected a name that is not in the protocol host database. If you ignore this error, Network Manager won't be able to communicate with the node. If you don't know the host name, try using the IP address instead.
Node responding to SNMP
The node you polled with the Poll Node command is responding to SNMP requests.
Not enough memory
An operation failed to allocate required memory resources. Exit the command, close some windows (especially reports, log file windows, and tables), and try again.
No current node
You tried to perform a command that operates on a node, but you haven't selected a node or activated a map window.
No filter selected
You tried to add an event filter using the Notifications command (from the Config menu), but didn't specify a node event type to match.
No poll variables set for this node
You tried to poll a node which does not have a Node Identify or Node Status variables. From the Edit menu, choose Node Properties and click the Poll Vars button to set node polling variables.
No response from node
The selected node didn't respond to your SNMP request within the maximum number of retries.
Null filter entry
You tried to add a filter entry using the Notifications command, but no message matching criteria was provided. You must select one of the Event Type check boxes.
Problem processing bitmap name
You specified a bitmap name (using the Background Image command from the Map menu) that Network Manager could not read. The bitmap is the wrong format (perhaps a device specific format) or it's too big.
Request rejected by node for variable name
You performed an SNMP request (using the Edit MIB Table command or Edit MIB variables command) that could not be performed by the node. This is because you do not have write permission, the variable is not supported by the node, or the variable is read-only.
Variable name is read-only
You tried to perform an SNMP Set operation (using the Edit MIB Table or Edit MIB Variable command) on a variable that is read-only. This error can be generated by the SNMP Agent even if Network Manager believes the variable to be writable.
WinExec Failed
You tried to start an application program but there are too many running programs. Close some programs and try again.
This applies to:
| 
