6.6 MIB Compiler Error Messages

MIBCERR102: Incorrect INDEX clause. The syntax should be INDEX {object name}

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Possible Cause: The syntax in the INDEX clause is incorrect.
Action: Ensure that the syntax of the INDEX clause is INDEX List of ObjectNames.

The list of object names should be separated by commas.

For example,

nwUserVolUsageEntry OBJECT-TYPE

INDEX nwUserVolUserID, nwUserVolVolID

The object names in this example are nwUserVolUserID and nwUserVolVolID.

MIBCERR103: Unable to parse the value for an unknown or aggregate type. Check the spelling and the format

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The MIB Compiler attempts to understand a value through the type that is referenced. If that type is not known, the MIB Compiler cannot interpret the value.
Possible Cause: The type is unknown and the MIB Compiler cannot interpret the value.
Action: Make sure the spelling and format of the type are correct.
Action: Delete any invalid non-white-space characters (characters other than the white space characters such as tab or space).

MIBCERR104: A duplicate number exists in the name-number list

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The named number lists contain elements consisting of a label and an associated number. The labels provide meaning to the assigned numbers. The numbers must be unique in a named number list.
Possible Cause: The same number has been incorrectly assigned to multiple list entries.
Action: Ensure that the numbers are unique.

MIBCERR105: Incorrect syntax: Expected ’(’

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The enumerated list consists of name strings and the associated integer value. The integers should be enclosed in parentheses.
Possible Cause: The MIB file has invalid characters or characters between the name string and the opening parenthesis.
Action: Make sure the name string is a single word and does not contain white space.
Possible Cause: The name string might be incorrectly made up of spaces, or other white space characters.
Action: Delete any non-white-space characters (characters other than the white space characters such as tab or space) between the name string and the integer value.
Possible Cause: The integer value might be missing entirely, or the enclosing parentheses might be missing or replaced by braces.
Action: Enclose the integer value in parentheses.

MIBCERR106: Incorrect syntax: Expected ’)’

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The integer value should be enclosed in parentheses. The closing right parenthesis was not found.
Possible Cause: Non-numerical or non-white-space characters (characters other than the white space characters such as tab or space) are present between the integer and the closing parentheses.
Possible Cause: The closing parenthesis for the integer value is missing.
Possible Cause: The value has non-numerical invalid characters inserted between digits.
Action: Ensure that there are no non-white-space characters between the integer value and that the closing parenthesis is present.

MIBCERR107: Incorrect syntax: Expected ’,’ or ’}’

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The possible lists are either an enumerated list or a variable list. The lists should be made up of list items, enclosed within opening and closing braces, and commas are used to separate the list items. This error is declared when this format is not present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present between the list items and the separating comma.
Possible Cause: The closing brace is missing.
Action: Delete any non-white-space characters between items in the list or between the last item and the closing braces. Separate list items with commas.

MIBCERR108: Incorrect syntax: Expected ’{’ after DEFVAL

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: DEFVAL defines a predefined value for a variable. The value to be used should be enclosed within opening and closing braces.
Possible Cause: Non-white-space characters (characters other than the white space characters such as tab or space) are present between the DEFVAL and the opening brace.
Action: Delete any non-white-space characters. Enclose characters within opening and closing braces.

MIBCERR109: Incorrect syntax: Expected ’{’ after VARIABLES

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The VARIABLES keyword is followed by a list of object names in the MIB. The names should be separated by commas and enclosed within opening and closing braces.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present between the VARIABLES keyword and the opening braces.
Action: Delete any non-white-space characters.
Possible Cause: The opening brace is missing.
Action: Enclose characters within opening and closing braces.

MIBCERR110: Incorrect syntax: Expected ’{’

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The SEQUENCE keyword is followed by a list of items making up a sequence. Each item of the list is made up of an object name and an object value pair. The list items should be separated by commas and enclosed within opening and closing braces.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present between the SEQUENCE keyword and the opening brace.
Action: Delete any invalid characters between the SEQUENCE keyword and the opening brace.
Possible Cause: The opening brace is missing.
Action: Specify the opening parenthesis.

MIBCERR111: Incorrect syntax: Specify a non-negative integer

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The integer can be digits from 0 to 9 only. The format allows for leading zeros.
Possible Cause: The specified integer value is incorrect.
Action: Check that the integer value is expressed in the expected format.

MIBCERR112: Incorrect syntax: Specify the SMI type

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The SMI type can either be a built-in standard SMI type or a user-defined type.
Possible Cause: The SMI type does not refer to a built-in standard SMI type or a user-defined type.
Action: Ensure that the SMI type is a valid type defined in the MIB file. Use the IMPORT statement to add the SMI type from a MIB file. Ensure that the spelling of the SMI type is correct.

MIBCERR113: Incorrect syntax: Specify an integer

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The integer can be digits from 0 to 9 only. The format allows for leading zeros and a sign (optional). White space can exist between the sign and the digits.
Possible Cause: The specified integer value is incorrect.
Action: Ensure that the integer value is expressed in the expected format.

MIBCERR114: Incorrect syntax: Specify an octet string

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The string should be enclosed in quotes. It can be standard text (alphanumerical with punctuation characters), binary string (0s and 1s), or hexadecimal string (all digits, A,B,C,D,E,F, a, b, c, d, e, f).
Possible Cause: The required string is not present.
Action: Ensure that the string is provided and is expressed in the expected format.

MIBCERR115: Incorrect syntax: Specify a filename after HELP

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The HELP clause is optional. The HELP keyword should be followed by a filename, which is used for the alarm system in ConsoleOne.
Possible Cause: The expected filename is missing after the HELP keyword.
Action: Check that a filename is provided after the HELP keyword.

MIBCERR116: Incorrect syntax: Specify the HELPTAG number after HELPTAG

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The integer number corresponds to the appropriate offset in the online help file named in the HELP clause.
Possible Cause: No number was found after the HELPTAG keyword.
Action: Delete the non-negative integer after the HELPTAG keyword.
Possible Cause: The number was not in the expected integer format.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR117: Incorrect syntax: Specify an identifier after ACCESS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ACCESS clause defines the access levels in terms of identifiers. The identifiers can be:

  • read-only

  • read-write

  • write-only

  • not-accessible

Possible Cause: The keyword in the ACCESS clause does not belong to the defined set.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space). Specify a valid identifier.

MIBCERR118: Incorrect syntax: Specify an identifier after STATUS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The STATUS clause defines the implementation support required for this object using identifiers. The supported values are:

  • mandatory, optional (support is mandatory or optional)

  • deprecated (must be supported, but might be removed from the next version)

  • obsolete (the managed nodes no longer need to support this object)

Possible Cause: The identifier is absent completely.
Action: Specify a valid identifier.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present between the STATUS and the identifier.
Action: Delete any non-white-space characters.
Possible Cause: The keyword in the OBJECT clause might not be a valid identifier.
Action: Specify a valid identifier.
Action: Delete any non-white-space characters.

MIBCERR119: Incorrect syntax: Specify an identifier

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The TRAP-TYPE macro contains either an enumerated list or a variable list. The list should be made up of items separated with commas and enclosed within opening and closing braces.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present before the name.
Action: Delete any non-white-space characters between the list items.
Possible Cause: The name was not found.
Action: Enclose list items within opening and closing braces, without any invalid non-white-space characters.
Possible Cause: An identifier after the GROUP clause is not present.
Action: Specify a valid identifier. Delete non-white-space characters.

MIBCERR120: Incorrect syntax: Specify the index object or the index type

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The INDEX clause contains a list of object names separated by commas. The list of object names should be enclosed within opening and closing braces.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present.
Action: Delete any non-white-space characters in the clause.
Possible Cause: The Index Object type or Index type is not the name of an object in the MIB.
Action: Express names in the proper format.

MIBCERR121: Incorrect syntax: Specify the module reference

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: When the MIB Compiler applies ASN.1 syntax, by convention, the module names should begin with an uppercase letter.
Possible Cause: The name of the module starts with a lowercase letter.
Action: Ensure that the module name begins with an uppercase letter.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR122: Incorrect syntax: Specify a number between 0 and 9

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The integer can be digits from 0 to 9 only. The format allows for leading zeros and a sign (optional). White space can be between the sign and the digits.
Possible Cause: The integer value is incorrect.
Action: Ensure that the integer value is expressed in the expected format.

MIBCERR123: Incorrect syntax: Expected a string after DESCRIPTION

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The DESCRIPTION clause has a quoted string, which is the description for that particular object in the MIB.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks.
Action: Use double quotation marks (" ") on any quotes within the string quoted to avoid confusion with the closing quotation marks.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present before the beginning of the string.
Action: Ensure that non-white-space characters do not precede the string.

MIBCERR124: Incorrect syntax: Specify a string after REFERENCE

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The REFERENCE clause has a quoted string, which is the description for that particular object in the MIB.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotes.
Action: Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Non-white-space characters are present before the beginning of the string.
Action: Ensure that non-white-space characters do not precede the string.

MIBCERR125: Incorrect trap annotation: Expected a string after SUMMARY

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The SUMMARY clause has a quoted string, which is the description for that particular object in the MIB.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks.
Action: Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Non-white-space (characters other than the white space characters such as tab or space) might be present before the beginning of the string.
Action: Ensure that non-white-space characters do not precede the string.

MIBCERR126: Incorrect trap annotation: Specify a string after TYPE

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: In the TRAP-TYPE macro, the TRAP TYPE clause has a quoted string, which is the description for that particular trap in the MIB.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks.
Action: Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Non-white-space characters might be present before the beginning of the string.
Action: Ensure that non-white-space characters do not precede the string.

MIBCERR127: Incorrect trap annotation: Specify a time index number after TIMEINDEX

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The integer can be digits from 0 to 9 only. The format allows for leading zeros and a sign (optional). White space can exist between the sign and the digits.
Possible Cause: The non-negative integer value is incorrect or is not present.
Action: Check that the integer value is expressed in the expected format.

MIBCERR128: Specify the keyword as INTEGER or OPTIONAL

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The OPTIONAL keyword signifies that the preceding term in the INDEX clause is not mandatory. It must be the last term in the clause and must be preceded by an INTEGER only.
Possible Cause: The OPTIONAL keyword is not the last term in the INDEX clause.
Action: Ensure that the keyword is the last term in the clause.
Possible Cause: The OPTIONAL keyword is preceded by a type other than INTEGER.
Action: Ensure that the term preceding the OPTIONAL keyword is INTEGER. Delete any invalid non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR129: Incorrect syntax: Expected ::=

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The symbol ::= has multiple uses, such as in object definitions, textual conventions, and demarcation of MIB modules.
Possible Cause: The ::= symbol is missing.
Action: Ensure that the expression has the correct form. This is important for object definitions when macros are being used.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present between the previous term and the ::= symbol.
Action: Delete any non-white-space characters in the expression.

MIBCERR130: Incorrect syntax: Expected ACCESS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: In ASN.1 syntax, the ACCESS keyword forms part of the OBJECT-TYPE macro, which defines the access level of that particular object.
Possible Cause: The ACCESS keyword is missing.
Action: Ensure that the ACCESS keyword is present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present in the place of the ACCESS keyword.
Action: Delete any non-white-space characters.

MIBCERR131: Incorrect syntax: Expected BEGIN

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ASN.1 syntax notation allows for objects to be defined within a separate module. A MIB file can contain one or more modules. These modules, by definition, begin with module_name DEFINITIONS::=BEGIN.
Possible Cause: The BEGIN keyword is missing.
Action: Ensure that the BEGIN keyword is present. Delete any invalid non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR132: Incorrect syntax: Expected DEFINITIONS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ASN.1 syntax notation allows for objects to be defined within a separate module. A MIB file can contain one or more modules. These modules, by definition, begin with module_name DEFINITIONS::=BEGIN.
Possible Cause: The DEFINITIONS keyword is missing.
Action: Ensure that the DEFINITIONS keyword is present. Delete any invalid non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR133: Incorrect syntax: Expected ENTERPRISE

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ENTERPRISE keyword forms part of the TRAP-TYPE macro and describes to which ENTERPRISE the trap belongs. The ENTERPRISE is usually the group that defines that particular MIB.
Possible Cause: The ENTERPRISE keyword is missing.
Action: Ensure that the ENTERPRISE keyword is present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present in the place of the ENTERPRISE keyword.
Action: Delete any non-white-space characters before the ENTERPRISE keyword.

MIBCERR134: Incorrect syntax: Specify HELPTAG after HELP

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The HELPTAG and HELP items form part of the trap definition. The item HELP defines the Help files to be used for the alarm system on the console. The HELPTAG refers to a particular offset in that file, pertaining to this particular trap.
Possible Cause: The HELPTAG item is not present.
Possible Cause: The keyword has been spelled incorrectly or is not present.
Action: Ensure that the keyword is present and is spelled correctly.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present in the place of the ENTERPRISE keyword.
Action: Delete any non-white-space characters before the ENTERPRISE keyword.

MIBCERR135: Incorrect syntax: Expected NULL

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The MIB Compiler understands the following ASN.1 types:

  • INTEGER

  • OBJECT IDENTIFIER

  • OCTET STRING

It also has built-in support for the following standard SMI types:

  • Counter

  • Gauge

  • TimeTicks

  • NetAddress

  • IPAddress

  • Opaque

Possible Cause: Attempting to use an undefined type results in this error.
Action: Ensure that the type is one of those supported by the MIB Compiler and is spelled correctly. Delete any invalid non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR136: Incorrect syntax: Specify an identifier after STATUS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The STATUS keyword forms part of the OBJECT-TYPE macro, defining the implementation support required for that particular object, whether it is Mandatory, Optional, Deprecated, or Obsolete.
Possible Cause: The STATUS keyword is missing.
Action: Ensure that the STATUS keyword is present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present in the place of the STATUS keyword.
Action: Delete any non-white-space characters.

MIBCERR137: Incorrect syntax: Expected SYNTAX

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: In ASN.1 syntax, the SYNTAX keyword forms part of the OBJECT-TYPE macro, defining the format of the value taken by the object.

In SNMP Version 2 syntax, the SYNTAX keyword forms part of the OBJECT-TYPE and TEXTUAL-CONVENTIONS macro, describing any of these types.

Possible Cause: The SYNTAX keyword is missing.
Action: Ensure that the SYNTAX keyword is present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present in the place of the SYNTAX keyword.
Action: Delete any non-white-space characters.

MIBCERR138: Incorrect syntax: Expected ’,’ or FROM

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The FROM keyword refers to objects defined in other MIB modules.
Possible Cause: The FROM keyword is missing or is spelled incorrectly.
Action: Check that the keyword is present and is spelled correctly.
Possible Cause: Non-white-space characters (characters other than the white space characters such as tab or space) are present where the word was expected.
Action: Delete any non-white-space characters.

MIBCERR139: Specify an identifier or SMI type in the IMPORT clause

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: Terms defined in other MIB modules can be referenced with the IMPORT clause. Only identifiers, types, and object identifiers can be used with the IMPORT clause.
Possible Cause: The term present in the IMPORT clause is neither an identifier nor a type.
Action: Check that the items with the IMPORT clause are either identifiers or types. Standard SMI macros such as OBJECT-TYPE and TRAP-TYPE can also be imported.

MIBCERR140: Specify a valid SMI type in the INDEX clause

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: In an INDEX clause, the following types of objects are supported:

  • Integers

  • Octet strings

  • Object identifiers

  • Internet addresses

  • IP addresses

Possible Cause: The type is not one of those supported by the INDEX clause.
Action: Ensure that the types of the objects named in the INDEX clause are supported by the INDEX clause.

MIBCERR141: Insufficient memory to compile the MIBs

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: This error occurs when the operating system is incapable of supplying required memory to this application.
Possible Cause: There are too many active applications.
Action: Close some open applications. Retry the operation. You might need to shut down and restart the operating system.

MIBCERR142: Check for the premature truncation of the file

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The end of the file was reached while the compilation was in an incomplete state. Each MIB source file contains one or more modules. Each module contains related object definitions. If the end of the file was found before the MIB Compiler finished compiling the current module, this error is generated.

The END keyword, which denotes the end of a MIB module, must be found before the end of the file occurs.

Possible Cause: The file might be truncated or is incomplete.
Action: Check that the MIB source file was not truncated or incomplete by checking the original version. If the file was downloaded from the Internet, it might be incomplete. You must download the file again.

MIBCERR143: A syntax error occurred in the object ID

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The object ID might be in the form of the name of the node, by itself, or with references to its parents, in their named form. For example, the following are allowed:

dodiso(1) org (3) dod (6)

Possible Cause: The object ID might be improperly formed or is nonexistent.
Action: Ensure that the object ID is correctly formed. Delete any invalid non-white-space characters (characters other than the white space characters such as tab or space).

MIBCERR147: Incorrect alarm trap annotation: Too many arguments after ARGUMENTS.

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: There is a limit on the number of arguments that can be declared.
Possible Cause: There are too many arguments declared after the ARGUMENTS keyword.
Action: Ensure that the number of arguments does not exceed the maximum number of arguments allowed.

MIBCERR148: Specify the identifier

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: Each MIB module is made up of a collection of definitions of objects that make up a portion of the MIB tree. Each definition relates the current definition to some other existing object in the MIB. Either the referred object is defined within the same MIB, or it is referenced from an external module using the IMPORT statement.
Possible Cause: The identifier is not be defined in the current MIB.
Action: Ensure that the referred identifier has been spelled correctly and the referred identifier exists within the module.
Possible Cause: The identifier is not correctly imported from the appropriate MIB, or the spelling might be incorrect.
Action: Ensure that the referred identifier is referenced correctly from an external module using the IMPORT statement, and that the MIB is being compiled.
Action: Delete any invalid non-white-space characters (characters other than the white space characters such as a tab or space) where the identifier is expected.
Action: Ensure that the identifier is included in the MIB in which it is accessed, or is included among the imported MIBs.

MIBCERR149: Specify the SMI type

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: Each MIB module is made up of a collection of definitions of objects that make up a portion of the MIB tree. Each definition includes some type information. ASN.1 provides basic types, but user-defined types can be added. These types are either defined within the same MIB, or else they are referenced from an external module using the IMPORT statement.
Possible Cause: The type is not be defined in the current MIB.
Action: Ensure that the referred type exists within the module.
Possible Cause: The type is not correctly imported from the appropriate MIB.
Action: Ensure that the referred type is referenced correctly from an external module using the IMPORT statement, and that the MIB is being compiled.
Possible Cause: The spelling is incorrect.
Action: Ensure that the referred type has been spelled correctly,
Action: Delete any invalid non-white-space characters (characters other than the white space characters such as a tab or space) where the identifier is expected.

MIBCERR150: Specify the module name in the IMPORT statement

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: Identifiers and types might be referenced from other MIB modules using the IMPORT statement. This error is generated if a module named in the IMPORT statement is missing.
Possible Cause: The MIB source file is not available for compilation.
Action: The MIB source file containing the referenced MIB module is currently being compiled currently. It should be present in the MIB Server Pool.
Possible Cause: The name of the module is missing or is incorrectly spelled.
Action: Ensure that the name of the module is spelled correctly.
Action: Ensure that invalid non-white-space characters (characters other than the white space characters such as a tab or space) are not present in the name.

MIBCERR151: The definition already exists

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: There is a single namespace for the symbols being defined in each MIB module of the MIB tree. This means that there cannot be more than one object of the same name in the same MIB module.
Possible Cause: This name is used for some other identifier or type in the MIB module.
Action: Ensure that there are no other occurrences of the name in the MIB.

MIBCERR152: Specify the missing term in the OBJECT IDENTIFIER definition

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The definition of an object should be terminated with the following:

::= {reference to parent MIB tree child number}

The reference to the parent can either be qualified as the name of the parent, or in terms of its parents.

For example, the following would be accepted:

::= {iso org(3) dod (6) 1}

The child number describes the object being described in terms of its parent, as in the first child of parent node dod.

Possible Cause: The child number of the node being defined is not found.
Possible Cause: The reference to the parent token is incorrect.
Action: Ensure that the reference to the parent is correct, and that the child number is unique to the parent.

MIBCERR153: Specify a valid token

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The MIB Compiler allows only alphanumeric and underscore characters ([a-z A-Z 0-9_]) in names. These characters can occur in any order.
Possible Cause: The word contains invalid characters.
Action: Ensure that the word used is made up only of valid characters.

MIBCERR154: Specify a valid SMI type after SEQUENCE OF

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The SEQUENCE OF keywords must be followed by a type name, which defines the objects in the SEQUENCE.
Possible Cause: The SEQUENCE OF keywords were not followed by a type name or were followed by an invalid type name.
Action: Ensure that a valid type name occurs after the SEQUENCE OF keywords.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space).

MIBCERR155: Unrecognized ASN.1 type after SYNTAX

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The name referenced by the SYNTAX clause should define the abstract syntax for the object, either in terms of the universal types or user-supplied types.
Possible Cause: The type referenced after the SYNTAX command was not found.
Action: Ensure that the type referenced in the SYNTAX clause is either a universal type or a user-defined type.
Action: Delete any non-white-space characters after the SYNTAX keyword.

MIBCERR156: Unrecognized value for SEVERITY

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The standard annotations for the TRAP-TYPE macro include a field for SEVERITY. This field can include any of the following four defined values:

  • CRITICAL

  • MAJOR

  • MINOR

  • INFORMATIONAL

Possible Cause: The value listed after the SEVERITY keyword is not one of the four defined values.
Action: Ensure that the value for SEVERITY is one of the four defined values.

MIBCERR157: The print operation is aborted

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: This error is generated when the user interrupts the printing or when the printer is unable to execute the command.
Possible Cause: The printer is not connected or the printer is offline.
Possible Cause: The user canceled the command.
Action: Correct the printer problem and issue the command again.

MIBCERR158: Incorrect syntax: Specify a string after DISPLAY-HINT

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The DISPLAY-HINT clause has a quoted string, which is the description for that particular object in the MIB.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks. Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present before the beginning of the string.
Action: Delete any non-white-space characters before the string.

MIBCERR201: Incorrect syntax: Specify a string after UNITS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The UNITS clause defines the units for the OBJECT-TYPE, such as minutes and seconds.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks. Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present before the beginning of the string.
Action: Delete any non-white-space characters before the string.

MIBCERR205: Incorrect syntax: Expected OBJECTS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The OBJECTS keyword forms part of the OBJECT-GROUP and NOTIFICATION-TYPE macro, defining the members of the group.
Possible Cause: The OBJECTS keyword is missing.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space) before the OBJECTS keyword. Ensure that the OBJECTS keyword is present.

MIBCERR212: Incorrect syntax: Expected LAST-UPDATED

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: In the MODULE-IDENTITY macro, the LAST-UPDATED clause describes the date and time when the module was last updated. The date and time are expressed in universal time format (UTC).
Possible Cause: The LAST-UPDATED keyword is missing.
Action: Ensure that the LAST-UPDATED keyword is present.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space) before the LAST-UPDATED keyword.

MIBCERR214: Incorrect syntax: Expected ORGANIZATION

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ORGANIZATION clause gives the name of the organization that created the module.
Possible Cause: The ORGANIZATION keyword is missing.
Action: Ensure that the ORGANIZATION keyword is present.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space) between the quoted string after LAST-UPDATED and ORGANIZATION.

MIBCERR215: Incorrect syntax: Specify a string after ORGANIZATION

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ORGANIZATION clause has a quoted string, which gives the name of the organization that created the module.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks.
Action: Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Invalid non-white-space characters (characters other than the white space characters such as a tab or space) are present before the beginning of the string.
Action: Delete any non-white-space characters before the string.

MIBCERR216: Incorrect syntax: Specify a string after CONTACT-INFO

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The CONTACT-INFO clause has a quoted string, which gives the information about the contact for any queries for this MIB module.
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks. Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Invalid non-white-space characters (characters other than the white space characters such as a tab or space) are present between the quoted string after the ORGANIZATION and CONTACT-INFO keywords.
Action: Delete any non-white-space characters between the quoted string after the ORGANIZATION and CONTACT-INFO keywords.

MIBCERR217: Incorrect syntax: Specify a string after REVISION

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The REVISION clause has a quoted string, which is the date and time expressed in universal time format (UTC).
Possible Cause: The enclosing quotation marks for the string are missing.
Action: Enclose the string within quotation marks. Use double quotation marks (" ") on any quotes within the string to avoid confusion with the closing quotation marks.
Possible Cause: Invalid non-white-space characters (characters other than the white space characters such as tab or space) are present between the quoted string after the CONTACT-INFO keyword and the REVISION keyword.
Action: Delete any non-white-space characters between the quoted string after the keywords CONTACT-INFO and REVISION.

MIBCERR218: Incorrect syntax: Expected CONTACT-INFO

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The CONTACT-INFO keyword forms part of the MODULE-IDENTITY macro, and gives the information about the contact for any queries for this MIB module.
Possible Cause: The CONTACT-INFO keyword is missing.
Action: Ensure that the CONTACT-INFO keyword is present.
Action: Delete any non-white-space characters (characters other than the white space characters such as a tab or space) before the CONTACT-INFO keyword.

MIBCERR219: Incorrect syntax: Expected DESCRIPTION

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: In ASN.1 syntax, the DESCRIPTION keyword forms part of the OBJECT-TYPE macro, defining the implementation support required for that particular object, whether it be Mandatory, Optional, Deprecated, or Obsolete.

In SNMP Version 2 syntax, the DESCRIPTION keyword forms part of the OBJECT-TYPE, TEXTUAL-CONVENTION, OBJECT-IDENTITY, NOTIFICATION-TYPE, OBJECT-GROUP, and MODULE-IDENTITY macros, describing any of these types.

Possible Cause: The DESCRIPTION keyword is missing.
Action: Ensure that the DESCRIPTION keyword is present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present in the place of the DESCRIPTION keyword.
Action: Delete any non-white-space characters.

MIBCERR223: Specify a correct symbol in the IMPORT statements

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The MIB object used must be defined or referenced from other MIB modules using the IMPORT statement or there is a spelling error in the MIB object.
Possible Cause: The MIB source file does not have the definition of the MIB object.
Action: Contact the vendor of the MIB source file to fix this issue.
Possible Cause: The MIB object is not a part of the IMPORT statements of the MIB source file.
Action: Contact the vendor of the MIB source file to fix this issue. As a workaround, from the appropriate MIB module, import the MIB object in the IMPORT statements in the MIB source file.
Possible Cause: The MIB object is defined or is a part of the IMPORT statements in the MIB source file, but is used with a spelling error.
Action: Contact the vendor of the MIB source file to fix this issue. As a workaround, correct the spelling error of the MIB object in the MIB source file.

MIBCERR226: Incorrect Syntax: Specify an identifier after OBJECTS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The OBJECT -GROUP macro is one of the four macros which forms a part of the conformance statement of SNMPv2 specification. The OBJECTS clause lists all the objects contained in the conformance group.
Possible Cause: The identifiers to be declared after the OBJECTS clause are missing.
Action: Specify a valid identifier following the OBJECTS clause.
Action: If you have specified the identifier, check for any existing non-white spaces (for example, tab or blank space) between the OBJECT clause and the identifier and delete them.

MIBCERR227: Incorrect syntax: Expected NOTIFICATIONS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The NOTIFICATIONS -GROUP macro is a part of the four macros of the conformance statements for SNMPv2 specification. The NOTIFICATIONS clause identifies all the notifications.
Possible Cause: The NOTIFICATIONS keyword is missing.
Action: Specify the NOTIFICATIONS keyword.
Action: If you have specified the NOTIFCATIONS keyword, check for any existing non-white spaces (for example, tab or blank space) before the NOTIFCATIONS keyword and delete them.

MIBCERR228: Incorrect syntax: Specify an identifier after NOTIFICATIONS

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The NOTIFICATIONS -GROUP macro is a part of the four macros of the conformance statements for SNMPv2 specification. The NOTIFICATIONS clause identifies lists all the notifications contained in the conformance group.
Possible Cause: The identifiers to be declared after the NOTIFICATIONS clause are missing.
Action: Specify a valid identifier following the NOTIFICATIONS clause.
Action: If you have specified the identifier, check for any existing non-white spaces (for example, a tab or blank space) between the NOTIFICATIONS clause and the identifier and delete them.

MIBCWAR001: Unrecognized ACCESS type

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The ACCESS clause defines the access levels in terms of identifiers. The following identifiers can be included:

  • read-only

  • read-write

  • write-only

  • not-accessible

Possible Cause: The identifier is not found.
Action: Specify a valid identifier.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) might be present between ACCESS and the identifier.
Action: Delete any non-white-space characters.

MIBCWAR002: Unrecognized STATUS type

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The STATUS keyword forms part of the OBJECT-TYPE macro, defining the implementation support required for that particular object, whether it be Mandatory, Optional, Deprecated, or Obsolete.
Possible Cause: The term to define the STATUS is not recognized.
Possible Cause: The term is spelled incorrectly.
Action: Ensure that the term is present.
Possible Cause: Non-white-space characters (characters other than the white space characters such as a tab or space) are present where this word was expected.
Action: Delete any invalid non-white-space characters.

MIBCWAR003: The value in the name-number list has exceeded 32767

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The MIB Compiler works with the largest integer that can be represented as 32767. If a named number occurs that has a value larger than 32767, the MIB Compiler generates this error.
Possible Cause: The value of the named number is greater than that which can be represented on this machine.
Action: Ensure that numbers used in named number lists are correctly listed with values less than 32767.

MIBCWAR004: Specify the missing trap annotation

Source: ZENworks Server Management; Management and Monitoring Services; MIB Compiler
Explanation: The definition of the TRAP-TYPE macro requires supplemental information, in the following form:

–#TYPE "FileSys: Directory write err (no vol)"

–#SUMMARY "Error occurred writing to "–#SUMMARY "extended directory space on server %s."

–#ARGUMENTS {0}

–#SEVERITY CRITICAL

–#TIMEINDEX 1

–#HELP "nwalarm.hlp"

–#HELPTAG 2

–#STATE DEGRADED

These annotations are used by the Alarm Manager System of ZENworks Server Management.

IMPORTANT:These annotations are prefixed with- –#, and are ignored by other compilers incapable of understanding them. However, they are relevant to this MIB Compiler and should not be removed or mistaken as comments because these annotations start with a dash (–).

Possible Cause: The standard defined trap annotation is missing.
Action: Ensure that the annotations are present for the TRAP-TYPE definitions and that they have meaningful values.