test

Solaris WBEM Services Administrator's Guide

Generated CIM Exceptions

The following section lists and describes the CIM exceptions generated by the MOF Compiler, CIM Object Manager, and WBEM client applications.


ABSTRACT_INSTANCE
Description:

The ABSTRACT_INSTANCE exception has one parameter, which is the name of the abstract class.

Example:

ABSTRACT_INSTANCE = Abstract class ExampleClass cannot have instances.

Cause:

A client application tried to create an instance for the specified class. However, the specified class is an abstract class, and abstract classes cannot have instances.

Solution:

Remove the programmed instances, as the client application cannot create such instances.


CHECKSUM_ERROR

The CHECKSUM_ERROR exception has no parameters.

Example:

CHECKSUM_ERROR = Checksum not valid.

Cause:

The message could not be sent because it was damaged or corrupted. The damage could have occurred accidentally in transit or by a malicious third party.

Solution:

Resend the message.

Note -

This error message is displayed when the CIM Object Manager receives an invalid checksum. A checksum is the number of bits in a packet of data passed over the network. This number is used by the sender and the receiver of the information to ensure that the transmission is secure and that the data has not been corrupted or intentionally modified during transit.

An algorithm is run on the data before transmission, and the checksum is generated and included with the data to indicate the size of the data packet. When the message is received, the receiver can recompute the checksum and compare it to the sender's checksum. If the checksums match, the transmission was secure and the data was not corrupted or modified.


CIM_ERR_ACCESS_DENIED
Description:

The CIM_ERR_ACCESS_DENIED exception does not have parameters.

Example:

CIM_ERR_ACCESS_DENIED = Insufficient privileges.

Cause:

This exception is displayed when a user does not have the appropriate privileges to complete an action.

Solution:

See your WBEM administrator to request privileges to complete the operation.


CIM_ERR_FAILED
Description:

Description

The CIM_ERR_FAILED exception has one parameter which is replaced by a character string, a message that explains the error condition and its possible cause.

Example:

Example

CIM_ERR_FAILED=Invalid entry.

Cause:

Cause

The CIM_ERR_FAILED exception is a generic message that can be displayed for a large number of different error conditions.

Solution

Because CIM_ERR_FAILED is a generic exception, many types of conditions can cause the message. The solution varies depending on the error condition.


CIM_ERR_INVALID_PARAMETER
Description:

The CIM_ERR_INVALID_PARAMETER exception has one parameter which gives more information about the parameter that caused the error.

Example:

CIM_ERR_INVALID_PARAMETER = Class System has no schema prefix.

Cause:

An operation was performed and the parameter was invalid. For example, a class was created without providing a schema prefix in front of the class name. The Common Information Model requires that all classes are provided with a schema prefix. For example, classes developed as part of the CIM Schema require a CIM prefix: CIM_Container. Classes developed as part of the Solaris Schema require a Solaris prefix: Solaris_System.

Solution:

Provide the correct parameter. In the example above, the correct parameter would be CIM_Container. Find all instances of the class missing the prefix and replace them with the class name and prefix.


CIM_ERR_INVALID_SUPERCLASS
Description:

The parameter CIM_ERR_INVALID_SUPERCLASS has two parameters:

  • The name of the specified super class.

  • The name of the sub class which caused the error.

Example:

CIM_ERR_INVALID_SUPERCLASS = Superclass CIM_Chassis for class CIM_Container does not exist.

Cause:

A class is specified to belong to a particular superclass, but the superclass does not exist. The specified superclass may be misspelled, or a non-existent superclass name may have been specified accidentally in place of the intended superclass name. Or, the superclass and the subclass may have been interpolated: the specified superclass actually may be a subclass of the specified subclass. In the previous example, CIM_Chassis is specified as the superclass of CIM_Container, but CIM_Chassis is a subclass of CIM_Container.

Solution:

Check the spelling and the name of the superclass to ensure it is correct. Ensure that the superclass exists in the namespace.


CLASS_REFERENCE
Description:

The CLASS_REFERENCE exception has two parameters.

  • The name of the class that contains the reference.

  • The name of the reference property.

Example:

CLASS_REFERENCE = Class SolarisExample1 must be declared as an association to have reference SolarisExample2

Cause:

A class has been defined with a reference property. However, the class is not an association. A class can only be defined to have a reference property if it is an association.

Solution:

Declare the class as an association by using the -association qualifier.


INVALID_CREDENTIAL
Description:

The INVALID_CREDENTIAL exception does not have parameters.

Example:

INVALID_CREDENTIAL = Invalid credentials.

Cause:

This exception is displayed when an invalid password has been entered.

Solution:

Retype the command and type the correct password.


INVALID_QUALIFIER_NAME
Description:

The INVALID_QUALIFIER_NAME exception has one parameter which is replaced by the Managed Object Format notation that depicts an empty qualifier name.

Example:

INVALID_QUALIFIER_NAME = Invalid qualifier name " "

Cause:

A qualifier was created for a property, but a qualifier name was not specified.

Solution:

Include the qualifier name in the context of the qualifier definition.


KEY_OVERRIDE
Description:

The KEY_OVERRIDE exception has two parameters:

  • The overriding property.

  • The overridden property.

Example:

KEY_OVERRIDE = Non-key Qualifier SolarisCard cannot override key Qualifier SolarisLock.

Cause:

The client has defined a class where a non-Key property is trying to override a Key property. In CIM, all concrete classes require at least one Key property, and a non-Key class cannot override a class that has a Key.

Solution:

The operation is not allowed as specified in the CIM specification.


KEY_REQUIRED
Description:

The KEY_REQUIRED exception has one parameter which is the name of the class that requires the key.

Example:

KEY_REQUIRED = Concrete (non-abstract) class ClassName needs at least one key.

Cause:

A Key qualifier was not provided for a concrete class. In CIM, all non-abstract classes, referred to as concrete classes, require at least one Key qualifier.

Solution:

Create a Key qualifier for the class.


METHOD_OVERRIDDEN
Description:

The METHOD_OVERRIDDEN command has three parameters:

  • The name of the overriding method.

  • The name of the overridden method.

  • The name of the method that has overridden the second parameter.

Example:

METHOD_OVERRIDDEN = Method Resume () cannot override Stop() which is already overridden by Start()

Cause:

A method is specified to override another method that has already been overridden by a third method. Once a method has been overridden, it cannot be overridden again.

Solution:

This operation is illegal.


NEW_KEY
Description:

The NEW_KEY exception has two parameters.

  • The name of the key.

  • The name of the class that is trying to define a new key.

Example:

NEW_KEY = Class CIM_PhysicalPackage cannot define new key [Key]

Cause:

A class is trying to define a new key when keys already have been defined in a superclass. Once keys have been defined in a superclass, new keys cannot be introduced into the subclasses.

Solution:

No action can be taken. 


NO_CIMOM
Description:

The NO_CIMOM exception has one parameter, which is the name of the host that is expected to be running the CIM Object Manager.

Example:

NO_CIMOM = CIMOM molly not detected.

Cause:

The CIM Object Manager is not running on the specified host.

Solution:

Start the CIM Object Manager by typing the command init.wbem start or connect to a host that is running the CIM Object Manager.


NO_INSTANCE_PROVIDER
Description:

The NO_INSTANCE_PROVIDER exception has two parameters:

  • The name of the class for which the instance provider cannot be found.

  • The name of the instance provider class that was specified.

Example:

NO_INSTANCE_PROVIDER = Instance provider RPC_prop for class RPC_Agent not found.

Cause:

The Java class of the specified instance provider is not found. This error message indicates that the class path of the CIM Object Manager does not contain one or more of the following:

  • Name of the provider class

  • Parameters of the provider class

  • CIM class for which the provider is defined

Solution:

Make sure the instance provider is present in the CIM Object Manager class path.


NO_METHOD_PROVIDER
Description:

The NO_METHOD_PROVIDER exception has two parameters:

  • The name of the class for which the method provider cannot be found.

  • The name of the method provider class that was specified.

Example:

NO_METHOD_PROVIDER = Method provider Start_prop for class RPC_Agent not found.

Cause:

The Java class of the specified method provider is not found. This error message indicates that the class path of the CIM Object Manager does not contain one or more of the following:

  • Name of the provider class

  • Parameters of the provider class

  • CIM class for which the provider is defined

Solution:

Make sure the method provider is present in the CIM Object Manager class path.


NO_OVERRIDDEN_METHOD
Description:

The NO_OVERRIDDEN_METHOD exception has two parameters:

  • The name of the overriding method.

  • The name of the overridden method.

Example:

NO_OVERRIDDEN_METHOD = Method Write overridden by Read does not exist in class hierarchy.

Cause:

The method of a subclass is trying to override a method of the superclass which does not exist anywhere in the class hierarchy.

Solution:

Ensure that the method exists in the class hierarchy


NO_OVERRIDDEN_PROPERTY
Description:

The NO_OVERRIDDEN_PROPERTY exception has two parameters.

  • The name of the overriding property.

  • The name of the overridden property.

Example:

NO_OVERRIDDEN_PROPERTY = Property A overridden by B does not exist in class hierarchy.

Cause:

The property of a subclass is trying to override the property of the superclass which does not exist anywhere in the class hierarchy.

Solution:

Ensure that the property exists in the superclass hierarchy.


NO_PROPERTY_PROVIDER
Description:

The NO_PROPERTY_PROVIDER error message uses two parameters:

  • The name of the class for which the property provider cannot be found.

  • The name of the property provider class that was specified.

Example:

NO_PROPERTY_PROVIDER = Property provider Write_prop for class RPC_Agent not found.

Cause:

The Java class of the specified property provider is not found. This error message indicates that the class specified in the path of the CIM Object Manager does not contain the class specified in the second parameter.

Solution:

Set the CIM Object Manager class path.


NO_QUALIFIER_VALUE
Description:

The NO_QUALIFIER_VALUE exception has two parameters:

  • The name of the qualifier causing the error.

  • The element to which the qualifier refers. Depending on the qualifier, the second parameter can be a class, property, method, or reference.

Example:

NO_QUALIFIER_VALUE = Qualifier [SOURCE] for Solaris_ComputerSystem has no value.

Cause:

A qualifier was specified for a property or method, but values were not included for the qualifier. For example, the qualifier VALUES requires a string array to be specified. If the VALUES qualifier is specified without the required string array, the NO_QUALIFIER_VALUE error message is displayed.

Solution:

Specify the required parameters for the qualifier. For information about what attributes are required for which qualifiers, see the CIM Specification by the Distributed Management Task Force at the following URL: http://dmtf.org/spec/cims.html.


NO_SUCH_METHOD
Description:

The NO_SUCH_METHOD exception has two parameters:

  • The name of the specified method

  • The name of the specified class

Example:

NO_SUCH_METHOD = Method Configure() does not exist in class Solaris_ComputerSystem

Cause:

Most likely, the method was not defined for the specified class. If the method is defined for the specified class, another method name may have been misspelled or typed differently in the definition.

Solution:

Define the method for the specified class. Otherwise, ensure that the method name and class name were typed correctly.


NO_SUCH_PRINCIPAL
Description:

The NO_SUCH_PRINCIPAL exception has one parameter which is the name of the principal, a user account.

Example:

NO_SUCH_PRINCIPAL = Principal molly not found.

Cause:

The specified user account cannot be found. The user name may have been mistyped upon login, or a user account has not been set up for the user.

Solution:

Ensure that the user name is spelled and typed correctly upon login. Ensure that a user account has been set up for the user.


NO_SUCH_QUALIFIER1
Description:

The NO_SUCH_QUALIFIER1 exception has one parameter which is the name of the undefined qualifier.

Example:

NO_SUCH_QUALIFIER1 = Qualifier [LOCAL] not found.

Cause:

The qualifier does not exist in the namespace.

Solution:

Define the qualifier. For information about standard CIM qualifiers and the usage of qualifiers in the CIM schema, see the CIM Specification by the Distributed Management Task Force at the following URL: http://www.dmtf.org/spec/cims.html.


NO_SUCH_QUALIFIER2
Description:

The NO_SUCH_QUALIFIER2 exception has two parameters:

  • The name of the class, property, or method that the qualifier modifies.

  • The name of the qualifier that cannot be found.

Example:

NO_SUCH_QUALIFIER2 = Qualifier [LOCAL] not found for CIM_LogicalElement

Cause:

A qualifier was specified to modify a property or method of a particular class. The qualifier was not defined as part of the any schema. The qualifier is required to be defined as part of the CIM schema or an extension schema to be recognized as a valid qualifier.

Solution:

Define the qualifier as part of the extension schema or use a standard CIM qualifier. For information about standard CIM qualifiers and the usage of qualifiers in the CIM schema, see the CIM Specification by the Distributed Management Task Force at the URL, http://www.dmtf.org/spec/cims.html.


NO_SUCH_SESSION
Description:

The NO_SUCH_SESSION exception has one parameter which is the session identifier.

Example:

NO_SUCH_SESSION = No such session 4002.

Cause:

The exception is displayed when the client session cannot be found. The CIM Object Manager removes the session for security reasons. Chapter 3, Administering Security.

Solution:

Ensure that your CIM environment is secure.


NOT_HELLO
Description:

The NOT_HELLO exception has no parameters.

Example:

NOT_HELLO = Not a Hello message.

Cause:

This error message is displayed if the data in the hello message--the first message sent to the CIM Object Manager--is corrupted.

Solution:

Try to reconnect.


NOT_INSTANCE_PROVIDER
Description:

The NOT_INSTANCE_PROVIDER exception has two parameters:

  • The name of the class for which the InstanceProvider is defined.

  • The name of the offending Java class.

Example:

NOT_INSTANCE_PROVIDER = device_prop_provider for class Solaris_Provider does not implement InstanceProvider.

Cause:

The path to the Java class specified as the provider does not implement the InstanceProvider interface.

Solution:

Ensure that the Java class in the second parameter implements the InstanceProvider interface. 


NOT_METHOD_PROVIDER
Description:

The NOT_METHOD_PROVIDER exception has two parameters:

  • The name of the method for which the MethodProvider interface is defined.

  • The name of the offending Java class.

Example:

NOT_METHOD_PROVIDER = Provider device_method_provider for class Solaris_Provider does not implement MethodProvider.

Cause:

The path to the Java method specified in the second parameter does not implement the MethodProvider interface.

Solution:

Ensure that the Java class in the second parameter implements the MethodProvider interface.


NOT_PROPERTY_PROVIDER
Description:

The NOT_PROPERTY_PROVIDER exception has two parameters:

  • The name of the method for which the PropertyProvider interface is defined.

  • The name of the offending Java class.

Example:

NOT_PROPERTY_PROVIDER = Provider device_property_provider for class Solaris_Provider does not implement PropertyProvider.

Cause:

The path to the Java class in the second parameter does not implement the PropertyProvider interface.

Solution:

Ensure that the Java class in the second parameter implements the PropertyProvider interface. 


NOT_RESPONSE
Description:

The NOT_RESPONSE exception has no parameters.

Example:

NOT_RESPONSE = Not a response message.

Cause:

This exception is displayed when the data in a first response message from the CIM Object Manager is corrupted.

Solution:

Try to reconnect.


PROPERTY_OVERRIDDEN
Description:

The PROPERTY_OVERRIDDEN exception has three parameters:

  • The name of the overriding property.

  • The name of the overridden property.

  • The name of the method that has overridden the second parameter.

Example:

PROPERTY_OVERRIDDEN = Property Volume cannot override MaxCapacity which is already overridden by RawCapacity

Cause:

A property is specified to override another method that has already been overridden by a third method. Once a property has been overridden, it cannot be overridden again.

Solution:

Specify a different property to override.


PS_UNAVAILABLE
Description:

The PS_UNAVAILABLE exception has one parameter which is a message that describes why the persistent store became unavailable.

Example:

PS_UNAVAILABLE = The persistent store is unavailable.

Cause:

When the repository becomes unavailable, the first parameter gives more information on the cause.

Solution:

As this exception is a general error condition, try to use the description details to see what causes the error. 


REF_REQUIRED
Description:

The REF_REQUIRED exception has one parameter which is the name of the association.

Example:

REF_REQUIRED = Association class CIM_Chassis needs at least two references.

Cause:

An association was defined without the necessary references. The rules of the Common Information Model specify that an association must contain two or more references.

Solution:

Add the required references to the association in the first parameter.


SCOPE_ERROR
Description:

The SCOPE_ERROR exception has three parameters:

  • The name of the element the specified qualifier modifies.

  • The name of the specified qualifier.

  • The Meta element type of the first parameter.

Example:

SCOPE_ERROR = Qualifier [UNITS] for CIM_Container does not have a Property scope.

Cause:

A qualifier was specified in a manner that conflicts with the requirements of the scope definition. For example, in the CIM Specification, the [READ] qualifier is defined with a scope property. Hence, if you use [READ] to qualify a class, you will get a scope exception.

Note -

The CIM Specification defines the types of CIM elements that a CIM qualifier can modify. This definition of the way in which a qualifier can be used is referred to as its scope. Most qualifiers, by definition, have a scope that directs them to modify properties or methods or both. Many qualifiers have a scope that directs them to modify parameters, classes, associations, indications, or schemas.

Solution:

Confirm the scope of the specified qualifier. Refer to the section, "1.Qualifiers" of the CIM Specification by the Distributed Management Task Force at the following URL:http://www.dmtf.org/spec/cim_spec_v20 for the standard definitions of CIM qualifiers. Use a different qualifier for the results you want to achieve, or change your program to use the qualifier according to its CIM definition.


SIGNATURE_ERROR
Description:

The SIGNATURE_ERROR exception has no parameters.

Example:

SIGNATURE_ERROR = Signature not verified

Cause:

This exception is displayed when a message is corrupted either accidentally or maliciously. It differs from the checksum error in that the message has a valid checksum, but the signature cannot be verified by the public key of the client. This protection ensures that even though the session key has been compromised, only the initial client which created the session is authenticated.

Solution:

No action is provided for this message, which is displayed when a session has been infringed upon by an intruder. For information about Solaris WBEM Services security features, see Chapter 3, Administering Security.


TYPE_ERROR
Description:

The TYPE_ERROR exception has five parameters:

  • The name of the specified element, such as a property, method, or qualifier.

  • The name of the class to which the specified element belongs.

  • The type defined for the element.

  • The type of value assigned.

  • The actual value assigned.

Example:

TYPE_ERROR = Cannot convert sint16 4 to a string for VolumeLabel in class Solaris_DiskPartition

Cause:

The value of a property or method parameter and its defined type are mismatched.

Solution:

Match the value of the property or method with its defined type.


UNKNOWNHOST
Description:

The UNKNOWNHOST exception has one parameter which is the name of the host.

Example:

UNKNOWNHOST = Unknown host molly

Cause:

The client tried to connect to a host that cannot be located.

Solution:

Check the spelling of the host name or contact your administrator. 


VER_ERROR
Description:

The VER_ERROR exception has one parameter which is the version number of the CIM Object Manager to which the client tried to connect.

Example:

VER_ERROR = Unsupported version 0.

Cause:

The CIM Object Manager you are trying to connect to does not support the client version.

Solution:

Either upgrade the client API or upgrade the CIM Object Manager.