Solaris WBEM SDK Developer's Guide

Solution: Set the CIM Object Manager class path. Ensure that the CIM Object Manager Solaris Provider is set and the provider qualifier is correct.

NO_OVERRIDDEN_METHOD

Description: This error message uses two parameters:
{0} is replaced by the name of the method that has overridden the method represented by {1}.

{1} is replaced by the name of the method that has been overridden.

Cause: The method of a subclass is trying to override the method of the superclass. However, the method that you are trying to override does not exist in the class hierarchy because it has not been defined.
When you override a method, you override its implementation and its signature.

Solution: Ensure that the method exists in the superclass.

NO_OVERRIDDEN_PROPERTY

Description: This error message uses two parameters:
{0} is replaced by the name of the property that has overridden {1}.

{1} is replaced by the name of the overriding property.

Cause: The property of a subclass is trying to override the property of the superclass. However, the property that you are trying to override does not exist in the class hierarchy because it has not been defined.

Solution: Ensure that the property exists in the superclass.

NO_PROPERTY_PROVIDER

Description: This error message uses two parameters:
{0} is replaced by the name of the class for which the property provider cannot be found.

{1} is replaced by the name of the property provider class that was specified.

Cause: The Java class of the specified property provider is not found. This error message indicates that the class path of the CIM Object Manager is missing 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: Set the CIM Object Manager class path. Ensue that the CIM Object Manager is running on the host to which you are trying to connect. If the CIM Object Manager is not running on that host, connect to a host running the CIM Object Manager.

NO_QUALIFIER_VALUE

Description: This error message uses two parameters:
{0} is replaced by the name of the qualifier that modifies the element {1}.

{1} is the element to which the qualifier refers. Depending on the qualifier, {1} can be a class, property, method, or reference.

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 DMTF CIM Specification at http://www.dmtf.org.

NO_SUCH_METHOD

Description: This error message uses two parameters:
{0} is replaced by the name of the specified method.

{1} is replaced by the name of the specified class.

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

Solution: Define the method for the specified class. Ensure that the method name and the class name are spelled correctly.

NO_SUCH_PRINCIPAL

Description: This error message uses one parameter, {0}, which is replaced by the name of the principal, a user account.

Cause: The specified user account cannot be found. The user name might have been misspelled, or a the user does not have a user account.

Solution: Ensure that the user name is spelled and typed correctly upon login. Ensure that the user has a user account.

NO_SUCH_QUALIFIER1

Description: This error message uses one parameter, {0}, which is replaced by the name of the undefined qualifier.

Cause: A new qualifier was specified but it was not defined as part of the extension schema. The qualifier must be defined as part of the CIM Schema or part of an extension schema to be recognized as a valid qualifier for a property or method of a particular class.

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 DMTF CIM Specification at: http://www.dmtf.org.

NO_SUCH_QUALIFIER2

Description: This error message uses two parameters:
{0} is replaced by the name of the class, property, or method that the qualifier modifies.

{1} is replaced by the name of the qualifier that cannot be found.

Cause: A new qualifier was specified to modify a property or method of a particular class. The qualifier was not defined as part of the extension schema. The qualifier must be defined as part of the CIM Schema or part of an extension schema to be recognized as a valid qualifier for a property or method of a particular class.

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 DMTF CIM Specification at: http://www.dmtf.org.

NO_SUCH_ROLE

Description: This error message uses one parameter, {0}, which is replaced by the role name.

Cause: The specified role cannot be found or is not a role identity.

Solution: Make sure that the input role exists. If the role is required, contact your system administrator to set up the role.

NO_SUCH_SESSION

Description: This error message uses one parameter, {0}, which is replaced by the session identifier.

Cause: The session has been closed and is being used subsequently.

Solution: Do not close the session.

NOT_HELLO

Description: This error message does not use parameters.

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: No action is available in response to this error message. For information about Solaris WBEM Services security features, see "Administering Security" in the Solaris WBEM Services Administration Guide.

NOT_INSTANCE_PROVIDER

Description: This error message uses two parameters:
{0} is replaced by the name of the instance for which the InstanceProvider interface is being defined.

{1} is replaced by the name of the Java provider class that does not implement the InstanceProvider interface. The InstanceProvider interface must be implemented to enumerate all instances of the specified class.

Cause: The path to the Java provider class specified by the CLASSPATH environment variable does not implement the InstanceProvider interface.

Solution: Ensure that the provider is correct and register the provider implements.

NOT_METHOD_PROVIDER

Description: This error message uses two parameters:
{0} is replaced by the name of the method for which the MethodProvider interface is being defined. The MethodProvider interface causes a specified method to be implemented in a program and enacted.

{1} is replaced by the name of the Java provider class that does not implement the MethodProvider interface.

Cause: The Java provider class present in the class path does not implement the MethodProvider interface.

Solution: Ensure that the Java provider class present in the class path implements the MethodProvider interface. Use the following command when you declare the provider: public Solaris implements MethodProvider.

NOT_PROPERTY_PROVIDER

Description: This error message uses two parameters:
{0} is replaced by the name of the method for which the PropertyProvider interface is being defined. The PropertyProvider interface is required to retrieve the values of the specified property.

{1} is replaced by the name of the Java provider class that does not implement the PropertyProvider interface.

Cause: The Java provider class present in the class path does not implement the PropertyProvider interface.

Solution: Ensure that the Java provider class present in the class path implements the PropertyProvider interface. Use the following command when you declare the provider: public Solaris implements PropertyProvider.

NOT_RESPONSE

Description: This error message does not use parameters.

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

Solution: No action is available in response to this error message. For information about Solaris WBEM Services security features, see "Administering Security" in the Solaris WBEM Services Administration Guide.

PROPERTY_OVERRIDDEN


	Solution: Set the CIM Object Manager class path. Ensure that the CIM Object Manager Solaris Provider is set and the provider qualifier is correct. `NO_OVERRIDDEN_METHOD` Description: This error message uses two parameters: `{0}` is replaced by the name of the method that has overridden the method represented by `{1}`. `{1}` is replaced by the name of the method that has been overridden. Cause: The method of a subclass is trying to override the method of the superclass. However, the method that you are trying to override does not exist in the class hierarchy because it has not been defined. When you override a method, you override its implementation and its signature. Solution: Ensure that the method exists in the superclass. `NO_OVERRIDDEN_PROPERTY` Description: This error message uses two parameters: `{0}` is replaced by the name of the property that has overridden `{1}`. `{1}` is replaced by the name of the overriding property. Cause: The property of a subclass is trying to override the property of the superclass. However, the property that you are trying to override does not exist in the class hierarchy because it has not been defined. Solution: Ensure that the property exists in the superclass. `NO_PROPERTY_PROVIDER` Description: This error message uses two parameters: `{0}` is replaced by the name of the class for which the property provider cannot be found. `{1}` is replaced by the name of the property provider class that was specified. Cause: The Java class of the specified property provider is not found. This error message indicates that the class path of the CIM Object Manager is missing 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: Set the CIM Object Manager class path. Ensue that the CIM Object Manager is running on the host to which you are trying to connect. If the CIM Object Manager is not running on that host, connect to a host running the CIM Object Manager. `NO_QUALIFIER_VALUE` Description: This error message uses two parameters: `{0}` is replaced by the name of the qualifier that modifies the element `{1}`. `{1}` is the element to which the qualifier refers. Depending on the qualifier, `{1}` can be a class, property, method, or reference. 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 DMTF CIM Specification at `http://www.dmtf.org`. `NO_SUCH_METHOD` Description: This error message uses two parameters: `{0}` is replaced by the name of the specified method. `{1}` is replaced by the name of the specified class. Cause: Most likely, the method was not defined for the specified class. If the method is defined for the specified class, another method name might have been misspelled or typed differently in the definition. Solution: Define the method for the specified class. Ensure that the method name and the class name are spelled correctly. `NO_SUCH_PRINCIPAL` Description: This error message uses one parameter, `{0}`, which is replaced by the name of the principal, a user account. Cause: The specified user account cannot be found. The user name might have been misspelled, or a the user does not have a user account. Solution: Ensure that the user name is spelled and typed correctly upon login. Ensure that the user has a user account. `NO_SUCH_QUALIFIER1` Description: This error message uses one parameter, `{0}`, which is replaced by the name of the undefined qualifier. Cause: A new qualifier was specified but it was not defined as part of the extension schema. The qualifier must be defined as part of the CIM Schema or part of an extension schema to be recognized as a valid qualifier for a property or method of a particular class. 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 DMTF CIM Specification at: `http://www.dmtf.org`. `NO_SUCH_QUALIFIER2` Description: This error message uses two parameters: `{0}` is replaced by the name of the class, property, or method that the qualifier modifies. `{1}` is replaced by the name of the qualifier that cannot be found. Cause: A new qualifier was specified to modify a property or method of a particular class. The qualifier was not defined as part of the extension schema. The qualifier must be defined as part of the CIM Schema or part of an extension schema to be recognized as a valid qualifier for a property or method of a particular class. 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 DMTF CIM Specification at: `http://www.dmtf.org`. `NO_SUCH_ROLE` Description: This error message uses one parameter, `{0}`, which is replaced by the role name. Cause: The specified role cannot be found or is not a role identity. Solution: Make sure that the input role exists. If the role is required, contact your system administrator to set up the role. `NO_SUCH_SESSION` Description: This error message uses one parameter, `{0}`, which is replaced by the session identifier. Cause: The session has been closed and is being used subsequently. Solution: Do not close the session. `NOT_HELLO` Description: This error message does not use parameters. 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: No action is available in response to this error message. For information about Solaris WBEM Services security features, see "Administering Security" in the Solaris WBEM Services Administration Guide. `NOT_INSTANCE_PROVIDER` Description: This error message uses two parameters: `{0}` is replaced by the name of the instance for which the `InstanceProvider` interface is being defined. `{1}` is replaced by the name of the Java provider class that does not implement the `InstanceProvider` interface. The `InstanceProvider` interface must be implemented to enumerate all instances of the specified class. Cause: The path to the Java provider class specified by the `CLASSPATH` environment variable does not implement the `InstanceProvider` interface. Solution: Ensure that the provider is correct and register the provider implements. `NOT_METHOD_PROVIDER` Description: This error message uses two parameters: `{0}` is replaced by the name of the method for which the `MethodProvider` interface is being defined. The `MethodProvider` interface causes a specified method to be implemented in a program and enacted. `{1}` is replaced by the name of the Java provider class that does not implement the `MethodProvider` interface. Cause: The Java provider class present in the class path does not implement the `MethodProvider` interface. Solution: Ensure that the Java provider class present in the class path implements the `MethodProvider` interface. Use the following command when you declare the provider: `public Solaris implements MethodProvider`. `NOT_PROPERTY_PROVIDER` Description: This error message uses two parameters: `{0}` is replaced by the name of the method for which the `PropertyProvider` interface is being defined. The `PropertyProvider` interface is required to retrieve the values of the specified property. `{1}` is replaced by the name of the Java provider class that does not implement the `PropertyProvider` interface. Cause: The Java provider class present in the class path does not implement the `PropertyProvider` interface. Solution: Ensure that the Java provider class present in the class path implements the `PropertyProvider` interface. Use the following command when you declare the provider: `public Solaris implements PropertyProvider`. `NOT_RESPONSE` Description: This error message does not use parameters. Cause: This error message is displayed when the data in a first response message from the CIM Object Manager is corrupted. Solution: No action is available in response to this error message. For information about Solaris WBEM Services security features, see "Administering Security" in the Solaris WBEM Services Administration Guide. `PROPERTY_OVERRIDDEN`