Edit

Share via

Errors 1001 through 1010

  • Article

Describes WMI SNMP provider errors 1001 through 1010.

Fatal Error 1001

Fatal Error 1002

Fatal Error 1003

Warning 1004

Warning 1005

Fatal Error 1006

Fatal Error 1008

Fatal Error 1001

<1001, Fatal>: "<fileName>:<line#>: SYNTAX clause of OBJECT-TYPE does not resolve to allowed types"

OBJECT-TYPE macro invocation module semantic error. The SYNTAX clause of the OBJECT-TYPE macro must resolve to a type or subtype, formed by using the SIZE or range specification that the SNMPv1 or SNMPv2C SMI allows. If this is not the case, fatal error 1001 is reported.

This error can occur when compiling either an SNMPv1 or SNMPv2C MIB.

Types allowed by the SNMPv1 SMI are:

  • INTEGER
  • NULL
  • OCTET STRING
  • OBJECT IDENTIFIER
  • NetworkAddress
  • IpAddress
  • Counter
  • Gauge
  • TimeTicks
  • Opaque
  • DisplayString
  • PhysAddress

Types allowed by the SNMPv2C SMI are:

  • INTEGER
  • OCTET STRING
  • OBJECT IDENTIFIER
  • BITS
  • Integer32
  • IpAddress
  • Counter32
  • TimeTicks
  • Opaque
  • Counter64
  • Unsigned32
  • DisplayString
  • PhysAddress
  • MacAddress
  • TruthValue
  • TestAndIncr
  • AutonomousType
  • InstancePointer
  • VariablePointer
  • RowPointer
  • RowStatus
  • TimeStamp
  • TimeInterval
  • DateAndTime
  • StorageType
  • Tdomain
  • Taddress

Fatal Error 1002

<1002, Fatal>: "<fileName>:<line#>: Invalid ACCESS clause <clause>"

OBJECT-TYPE macro invocation module semantic error. For SNMPv1, the ACCESS clause of the OBJECT-TYPE macro must be "read-only," "write-only," "read/write," or "not-accessible."

For SNMPv2C, the MAX-ACCESS clause must be "read-only," "read-create," "read/write," or "not-accessible."

Fatal Error 1003

<1003, Fatal>: "<fileName>:<line#>: Invalid STATUS clause <clause>"

OBJECT-TYPE macro invocation module semantic error. For SNMPv1, the STATUS clause of an OBJECT-TYPE macro invocation must be "mandatory," "optional," "obsolete," or "deprecated."

For SNMPv2C, the STATUS clause of an OBJECT-TYPE macro invocation must be "current," "deprecated," or "obsolete."

Warning 1004

<1004, Warning>: "<fileName>:<line#>: OBJECT-TYPE <identifier>, whose syntax resolves to one of the Counter types does not end with the letter 's' "

OBJECT-TYPE macro invocation module semantic warning. The identifier for an object of SYNTAX Counter (SNMPv1) or Counter32 and Counter64 (SNMPv2C) must be plural.

This warning can occur when compiling either an SNMPv1 or SNMPv2C MIB.

Warning 1005

<1005, Warning>: "<fileName>:<line#>: OBJECT-TYPE with SYNTAX "SEQUENCE OF", should have an ACCESS clause "not-accessible"

OBJECT-TYPE macro invocation module semantic warning. A table or conceptual row (SEQUENCE OF or SEQUENCE object types, respectively) must be "not-accessible."

This warning can occur in either SNMPv1 or SNMPv2C.

Fatal Error 1006

<1006, Fatal>: "<fileName>:<line#> OBJECT-TYPE <identifier>, which is of SYNTAX SEQUENCE, does not have an INDEX or AUGMENTS clause"

OBJECT-TYPE macro invocation module semantic error. For SNMPv1, the INDEX clause must be present for an OBJECT-TYPE definition whose SYNTAX resolves to a SEQUENCE type.

For SNMPv2C, either the INDEX or the AUGMENTS clause must be present for a conceptual row declaration.

Fatal Error 1008

<1008, Fatal>: "<fileName>:<line#>: OBJECT-TYPE <identifier>, which is of SYNTAX "SEQUENCE" has not been referenced"

OBJECT-TYPE macro invocation module semantic error. An OBJECT-TYPE with the SYNTAX clause as a SEQUENCE type must figure in the SYNTAX clause of exactly one OBJECT-TYPE invocation that stands for a table declaration, that is, an object with the SYNTAX clause as a SEQUENCE OF type. The <line#> parameter refers to the second point of reference.

This error can occur in either SNMPv1 or SNMPv2C.