Search
Support & Downloads
Networking Connectivity
LANDesk* Network Manager
MIB Compiler Errors

The MIB compiler errors are generated when you choose Compile MIB from the Config menu. The log file event type is MIB. The MIB compiler generates fatal errors and nonfatal warnings. The general format of a MIB compiler error is:

    c:\ldnm\mibfiles\foo.mib(nnnn) Type: Message

The MIB source file name is shown first, followed by the line number of parenthesis. The Type keyword is either error or warning. The Message is a description of the error or warning.

error: bad write to database
The MIB compiler couldn't write to the MIB database file c:\ldnm\mibfiles\mib.dat. The disk is probably full.

error: can't open database
During normal operation, the MIB database failed to open. This could be caused by a file sharing violation, or because the database was removed while Network Manager was running.

error: can't open index
The MIB compiler couldn't open the MIB source index file c:\ldnm\mibfiles\names.txt.

error: can't open source file
The MIB compiler couldn't open a MIB source file that is referenced in the index file c:\ldnm\mibfiles\names.txt.

error: got badtok, expected oktok(s)
An unexpected word, badtok, was found in the MIB. Oktok(s) is the list of possible words that were expected. The MIB compiler was unable to recover from this error and some MIB source was skipped.

error: got badtok, expected semicolon
The MIB compiler didn't detect a semicolon at the end of the imports section, or there were too many imports.

error reading mib database
An I/O error was encountered while trying to read the MIB database, c:\ldnm\mibfiles\mib.dat. The file is probably corrupt, possible due to a file system error. Remove the file, run the DOS chkdsk command, then start Network Manager again.

error: Too many errors - file skipped
The MIB compiler aborted processing of the MIB source file because more than twenty errors were detected.

error: Too many sequence entries 'seqname' on line num
The MIB compiler cancelled processing of the sequence definition seqname because it had more than fifty entries. The error was encountered on line num of the MIB source file named file.

error: Unexpected EOF
The MIB compiler detected an end of file condition while processing an object definition, or before detecting the "end" keyword.

error: unresolved object identifier word
An object identifier named word was used as part of another object identifier, but was not defined in the MIB file and could not be found in other MIB files.

warning: Too many trap types, maximum allowed is 800
Network Manager can only compile a total of 800 TRAP-TYPE entries. Other trap definitions were ignored.

warning: got badtok, expected oktok(s)
An unexpected word, badtok, was found in the MIB. Oktok(s) is the list of possible words that were expected. The MIB compiler recovered from this error.

warning: skipped source from line NN
After an error was encountered, the MIB compiler skipped lines up to line number NN before it was able to resynchronize.

warning: Unresolved SEQUENCE item word (possible spelling error)
An element in a sequence definition didn't have a matching variable definition in the MIB file. The MIB compiler deleted the element from the sequence.

warning: Unresolved INDEX word
An element named "word" in an INDEX clause didn't have a matching variable definition in the MIB file. The MIB compiler deleted the element from the INDEX clause.

This applies to:
LANDesk* Network Manager



Solution ID: CS-015283
Date Created: 30-Aug-2004
Last Modified: 01-Sep-2004
Back to Top