WBEM Error Messages
This appendix discusses the error messages generated by components of Solaris WBEM Services and the Solaris WBEM SDK, and covers the following topics:
About WBEM Error Messages
The CIM Object Manager generates error messages that are used by both the Managed Object Format (MOF) Compiler and CIM WorkShop. The MOF Compiler appends a line to the error message that indicates the line number in which the error occurs in the .mof file.
Note - For more information on the MOF compiler, see mofcomp(1M).
Parts of an Error Message
An error message consists of the following parts:
Unique identifier - A character string that identifies the error message. You can search for the unique identifier in the Javadoc reference pages to see an explanation of the content of the error message.
Parameters - Placeholders for the specific classes, methods, and qualifiers that are cited in the exception message.
Example A-1 Parts of an Error Message
The MOF compiler returns the following error:
REF_REQUIRED = Association class CIM_Docked needs at least two refs. Error in line 12. |
REF_REQUIRED is the unique identifier.
CIM_Docked is a parameter.
line 12 indicates the line number in the .mof file in which the error occurred.
List of Error Messages
This section describes the WBEM error messages, sorted by unique identifier.
ABSTRACT_INSTANCE
Description: This error message uses one parameter, {0}, which is replaced by the name of the abstract class.
Cause: A create instance was attempted for the instance. However, the specified class is an abstract class, and abstract classes cannot have instances.
Solution: Create instances for concrete classes.
CANNOT_ASSUME_ROLE
Description: This error message uses two parameters:
{0} is replaced by the user name.
{1} is replaced by the role name.
Cause: The specified principal cannot assume the specified role.
Solution: Make sure that the user has the appropriate rights to assume the given role. If the user does not have the appropriate rights, contact your system administrator.
CHECKSUM_ERROR
Description: This error message does not use parameters.
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.
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. Then 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.
Solution: Resend the message using Solaris WBEM Services security features. For information about Solaris WBEM Services security, see "Administering Security" in the Solaris WBEM Services Administration Guide.
CIM_ERR_ACCESS_DENIED
Description: This error message does not use parameters.
Cause: This error message is displayed when a user does not have the appropriate privileges and permissions to complete an action.
Solution: See your system administrator or the person who is responsible for your CIM Object Manager to request privileges to complete the operation.
CIM_ERR_ALREADY_EXISTS
Instance 1: CIM_ERR_ALREADY_EXISTS
Description: This instance uses one parameter, {0}, which is replaced by the name of the duplicate class.
Cause: The class you attempted to create uses the same name as an existing class.
Solution: In CIM WorkShop, search for existing classes to see the class names that are in use. Then create the class by using a unique class name.
Instance 2: CIM_ERR_ALREADY_EXISTS
Description: This instance uses one parameter, {0}, which is replaced by the name of the duplicate instance.
Cause: The instance for a class you attempted to create uses the same name as an existing instance.
Solution: In CIM WorkShop, search for existing instances to see the names that are in use. Then create the instance by using a unique name.
Instance 3: CIM_ERR_ALREADY_EXISTS
Description: This instance uses one parameter, {0}, which is replaced by the name of the duplicate namespace.
Cause: The namespace you attempted to create uses the same name as an existing namespace.
Solution: In CIM WorkShop, search for existing namespaces to see the names that are in use. Then create the namespace by using a unique name.
Instance 4: CIM_ERR_ALREADY_EXISTS
Description: This instance uses one parameter, {0}, which is replaced by the name of the duplicate qualifier type.
Cause: The qualifier type you attempted to create uses the same name as an existing qualifier type of the property it modifies.
Solution: In CIM WorkShop, search for qualifier types that exist for the property to see the names that are in use. Then create the qualifier type by using a unique name.
CIM_ERR_CLASS_HAS_CHILDREN
Description: This error message uses one parameter, {0}, which is replaced by the class name.
Cause: This exception is thrown by the CIM Object Manager to disallow invalidation of the subclasses by a super class deletion. Clients must explicitly delete the subclasses first. The check for subclasses is made before the check for class instances.
Solution: Remove the subclasses of the given class.
CIM_ERR_CLASS_HAS_INSTANCES
Description: This error message uses one parameter, {0}, which is replaced by the class name.
Cause: This exception is thrown if you attempt to delete a class that has instances.
Solution: Remove the instances of the given class.
CIM_ERR_FAILED
Description: This error message uses one parameter, {0}, which is replaced by a message that explains the error condition and its possible cause.
Cause: This error message is generic and can be displayed for many different error conditions.
Solution: The solution varies depending on the error condition.
CIM_ERR_INVALID_PARAMETER
Description: This error message uses one parameter, {0}, which is replaced by the name of the invalid parameter.
Cause: The name of the parameter or the method is invalid.
Solution: Fix the parameter.
CIM_ERR_INVALID_QUERY
Description: This error message uses two parameters:
{0} is replaced by the invalid part of the query.
{1} is replaced by additional information, including the actual error in the query.
Cause: The given query either has syntactical errors or semantic errors.
Solution: Fix the errors based on the exception details. In addition, make sure that the query string and query language match.
CIM_ERR_INVALID_SUPERCLASS
Description: This error message uses two parameters:
{0} is replaced by the name of the specified subclass.
{1} is replaced by the name of the class for which a specified subclass does not exist.
Cause: A class is specified to belong to a subclass from a superclass, but the superclass does not exist. The specified superclass might be misspelled, or a non-existent superclass name might have been specified in place of the intended superclass name. Or, the superclass and the subclass might have been interpolated. That is, the specified superclass may be a subclass of the 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 that it is correct. Ensure that the superclass exists in the namespace.
CIM_ERR_LOW_ON_MEMORY
Description: This error message does not use parameters.
Cause: The CIM Object Manager is low on memory.
Solution: Delete some class definitions and static instances to free up memory.
CIM_ERR_NOT_FOUND
Instance 1: CIM_ERR_NOT_FOUND
Description: This instance uses one parameter, {0}, which is replaced by the name of the non-existent class.
Cause: A class is specified, but it does not exist. The specified class might be misspelled, or a non-existent class name might have been accidentally specified in place of the intended class name.
Solution: Check the spelling and the name of the class to ensure that it is correct. Ensure that the class exists in the namespace.
Instance 2: CIM_ERR_NOT_FOUND