45 IRM-00001 to IRM-03012

IRM-00001: The class {0} cannot be found and cannot be unmarshalled by JAXB.

Cause: A class was specified in XML that could not be found.

Action: Verify that the class is available and on the class path.

Level: 1

Type: WARNING

Impact: Data

IRM-00002: The value {0} is not a valid UUID format and cannot be unmarshalled by JAXB.

Cause: A UUID was specified in XML that could not be parsed.

Action: Verify the format of the UUID.

Level: 1

Type: WARNING

Impact: Data

IRM-00003: Creating a field value resulted in an exception.

Cause: Creating a field value resulted in an exception.

Action: Review the exception cause for further information.

Level: 1

Type: WARNING

Impact: data

IRM-00501: The offline store cannot be accessed. It will be recreated.

Cause: The offline store is not from this instance.

Action: This is a notification and no action is required.

Level: 16

Type: NOTIFICATION

Impact: data

IRM-01001: The context identified with UUID {0} does not exist.

Cause: A context was specified that does not exist.

Action: Ensure that the context UUID value corresponds to a context stored in the server and retry the operation.

Level: 32

Type: TRACE

Impact: Data

IRM-01002: The test content identified by the name {0} does not exist.

Cause: Test content was specified that does not exist.

Action: Each piece of test content is identified by an unique name. Ensure that the provided test content name is correct.

Level: 32

Type: TRACE

Impact: Data

IRM-01003: There has been an error using a cryptography algorithm.

Cause: An error was encountered while using a cryptography algorithm.

Action: Most cryptography exceptions are caused by an exception from the cryptography algorithm implementation. Refer to the exception cause to further diagnose the error. Typical examples of a cryptography exception include attempting to generate a key for a key size that is not supported, or a failure to decrypt due to corrupt data.

Level: 1

Type: ERROR

Impact: Security

IRM-01004: Unknown or unsupported cryptography schema {0}.

Cause: The cryptographic schema is not known to the system.

Action: Ensure that the provided cryptographic schema identity value is supported by the system.

Level: 1

Type: ERROR

Impact: Security

IRM-01005: The cryptography schema \"{0}\" is unsupported on this platform or configuration.

Cause: An operation was attempted that would have caused a mix of FIPS and non-FIPS key sets to be present in the system.

Action: When a key set is created, the cryptography schema details are recorded with the key set. The server is unable to deliver a mix of FIPS and non-FIPS key sets to the desktop. Ensure that the cryptography schema used is compatible with the cryptography schemas already in use by the system.

Level: 1

Type: ERROR

Impact: Security

IRM-01006: The key set identified with UUID {0} already exists.

Cause: A key set was specified that already exists.

Action: Generate a new UUID for the key set and retry the operation.

Level: 32

Type: TRACE

Impact: Programmatic

IRM-01007: The key set identified with UUID {0} does not exist.

Cause: A key set was specified that does not exist.

Action: Ensure that the key set specified exists and retry the operation.

Level: 16

Type: TRACE

Impact: Data

IRM-01008: The {0} wrapping key algorithm is not supported.

Cause: An unsupported key type was supplied for the wrapping key.

Action: Ensure that the wrapping key stored in the key store uses a supported algorithm. The supported key types are AES, DESede, and RSA.

Level: 1

Type: ERROR

Impact: Security

IRM-01010: An exception occurred parsing sealed content: {0}.

Cause: Sealed content was provided that has been corrupted.

Action: Obtain a non-corrupted copy of the sealed content. The exception reason will provide more details of what part of the sealed content is corrupt.

Level: 16

Type: TRACE

Impact: Data

IRM-01011: The sealing process requires non-empty content.

Cause: Content was provided for sealing that was empty.

Action: Provide non-empty data to the sealing operation.

Level: 32

Type: TRACE

Impact: Data

IRM-01012: There has been an error using the key store.

Cause: An error was reported loading or accessing a key store.

Action: Examine the exception cause to diagnose the problem further. Typical reasons for this exception include the key store file not being in the configured location and incorrect passwords.

Level: 1

Type: ERROR

Impact: Data

IRM-01013: The key {0} does not exist in the key store {1}.

Cause: A key alias was provided that identified a key that does not exist in the key store.

Action: Use tools such as keytool to ensure that the contents of the key store include the key with the specified key alias.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01014: The MIME type {0} is syntactically invalid.

Cause: A MIME type was specified that is syntactically invalid.

Action: Correct the MIME type value. The MIME type should consist of a type and subtype (for example, text/plain).

Level: 16

Type: TRACE

Impact: Data

IRM-01015: Unknown content type/format.

Cause: The content format could not be determined as the content-type HTTP header was missing.

Action: Ensure the web service correctly specifies the content type in the HTTP response.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01016: Unsupported content type: {0}.

Cause: An unsupported content type was provided for sealing.

Action: None. Sealing cannot be performed on a format that is not supported.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01017: Group accounts are not supported. The group {0} cannot be used in this context.

Cause: A group account was provided to an operation that does not support the use of group accounts.

Action: Specify a user and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01018: An error has occurred accessing user or group information.

Cause: An internal exception occurred when accessing the user and group repository (for example LDAP).

Action: Refer to the exception cause to further diagnose the error.

Level: 1

Type: WARNING

Impact: Data

IRM-01019: The account identified by {0} is unknown.

Cause: An unknown account was specified.

Action: Correct the account UUID or name and retry the operation.

Level: 16

Type: TRACE

Impact: Data

IRM-01020: The classification is unknown to the system. The classification may have been deleted, may have never existed, or the classification details may be incorrect.

Cause: The classification is unknown to the system. The classification may have been deleted, may have never existed, or the classification details may be incorrect.

Action: Correct the classification details and retry the operation.

Level: 16

Type: TRACE

Impact: Data

IRM-01021: The classification system {0} is not supported.

Cause: A classification system was specified that the server does not support.

Action: Check with the server administrator and ensure that the classification system is supported.

Level: 16

Type: TRACE

Impact: Data

IRM-01022: The configuration setting {0} is not specified, is invalid, or cannot be read.

Cause: A required configuration setting is missing from the configuration, is invalid, or could not be read.

Action: Correct the configuration settings.

Level: 1

Type: ERROR

Impact: Configuration

IRM-01023: The desktop is repudiated.

Cause: A user's desktop software has been repudiated and can no longer contact the server.

Action: Ensure that the client has the appropriate software installed.

Level: 16

Type: NOTIFICATION

Impact: Security

IRM-01024: The feature with id {0} is not present in the list of available features.

Cause: A feature was specified that is not present in the list of available features.

Action: Correct the feature id and retry the operation.

Level: 32

Type: TRACE

Impact: Programmatic

IRM-01025: Licenses are available, but are on the following device(s): {0}.

Cause: A license was requested but all licenses available were in use on other devices.

Action: Check in licenses from the listed devices and retry opening content. If licenses must be used on multiple devices at the same time increase the server device count configuration setting.

Level: 1

Type: TRACE

Impact: Other

IRM-01026: An exception occurred processing a desktop SOAP message: {0}.

Cause: An error occurred while processing a desktop SOAP request or response message.

Action: Review the reason property of the exception for further details. This exception typically means that a corrupt or incorrect message was sent to the server.

Level: 1

Type: ERROR

Impact: Security

IRM-01027: Unsupported protocol version {0}. The required protocol version is {1}.

Cause: A desktop protocol version was provided that the server does not support.

Action: Use a lower protocol version and retry the request. The valid range of protocol versions will be specified in the exception details.

Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

IRM-01028: A new version ({0}) of the desktop is available.

Cause: An upgrade was available for a client's desktop software.

Action: Upgrade the desktop software on the client.

Level: 1

Type: TRACE

Impact: Requests/Responses

IRM-01029: The account \"{0}\" has already been assigned an administrator role.

Cause: An account could not be assigned the administrator role because it is already assigned.

Action: No action is required.

Level: 32

Type: TRACE

Impact: Programmatic

IRM-01030: The account \"{0}\" has already been assigned the role \"{1}\".

Cause: An account could not be assigned the specified role because it is already assigned.

Action: No action is required.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01031: The account \"{0}\" has already been assigned an inspector role.

Cause: An account could not be assigned the inspector role because it is already assigned.

Action: No action is required.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01032: The account \"{0}\" has already been assigned a manager role.

Cause: An account could not be assigned the manager role because it is already assigned.

Action: No action is required.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01033: The specified accounts cannot be removed as this action would remove all administrators.

Cause: The specified accounts could not be removed because there must be at least one administrator for a Domain.

Action: Ensure that an administrator will remain following the request and then retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01034: The context \"{0}\" cannot be deleted as there are rights assigned within this context.

Cause: A context could not be deleted because there are rights assigned with the context.

Action: Remove all rights assigned with the context and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01035: The context template \"{0}\" cannot be deleted.

Cause: A context template could not be deleted because there are context instances that refer to it.

Action: Remove all context instances that refer to the template and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01036: The document role \"{0}\" cannot be deleted as there are rights assigned to this role.

Cause: A document role could not be deleted because there are rights assigned to the role.

Action: Remove all rights assigned to the role and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01037: The specified accounts cannot be removed as this action would remove all managers.

Cause: An account could not be removed because there must be at least one manager for a Domain.

Action: Ensure that a manager will remain following the request and then retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01038: A context with \"{0}\" already exists.

Cause: A context instance UUID was specified that already exists.

Action: Use a different context UUID.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01039: The context template \"{0}\" already exists.

Cause: A context template UUID was specified that already exists.

Action: Use a different context template UUID. A context template UUID must be unique within the same domain.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01040: The document role \"{0}\" already exists.

Cause: A document role UUID was specified that already exists within the domain.

Action: Use a different document role UUID. A role UUID must be unique within the same domain.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01041: The domain \"{0}\" already exists.

Cause: A domain UUID was specified that already exists.

Action: Use a different UUID.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01042: There are no domains created in the system.

Cause: No domains were available in the system.

Action: Create at least one domain in the system.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01043: The context template \"{0}\" is inactive and cannot be used to create contexts.

Cause: An inactive context template was specified.

Action: Activate the context template and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01044: The role \"{0}\" cannot be used with template \"{1}\" as their domains do not match.

Cause: An attempt was made to add a role to a template that does not belong to the same domain.

Action: Specify a role from the same domain as the template.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01045: The \"{0}\" role must have at least one primary feature.

Cause: A specified document role did not have a primary feature.

Action: Add at least one primary feature to the role.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01046: The \"{0}\" role must have a refresh period greater that one minute.

Cause: A document role specified an invalid time period.

Action: Provide a refresh period greater than one minute.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01047: The context template with UUID \"{0}\" on domain \"{1}\" does not exist.

Cause: An unknown context template was specified.

Action: Correct the context template UUID and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01048: The right with UUID \"{0}\" does not exist.

Cause: An unknown right was specified.

Action: Ensure that the UUID corresponds to a right.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01049: The document role with UUID \"{0}\" on domain \"{1}\" does not exist.

Cause: An unknown document role was specified.

Action: Ensure that the UUID corresponds to a document role.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01050: The domain with UUID \"{0}\" does not exist.

Cause: An unknown domain was specified.

Action: Ensure that the UUID corresponds to a domain.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01051: The context \"{1}\" does not support role \"{0}\".

Cause: A role was assigned to a account which was not supported by the context.

Action: Add the role to the related context template.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01052: A dynamic class contains either two stubs or head slices. The duplicate slice class is {0}.

Cause: A dynamic class contained either more than one stub slice or more than one head slice.

Action: Alter the dynamic class configuration such that it has at most one stub and one head slice.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01053: The dynamic class {0} [{1}] does not contain any implementation slices.

Cause: A dynamic class did not contain any implementation slices.

Action: Alter the dynamic class configuration such that it has at least one implementation slice.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01054: An error occurred during injection of the {1} on class {0}.

Cause: Injected data was provided for a dynamic class and an error occurred injecting that data.

Action: Ensure that the injected data is valid for the dynamic class.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01055: Injection data cannot be found for the mandatory injected field {1} on class {0}.

Cause: Injected data was not provided for a dynamic class that required it.

Action: Ensure that all mandatory injected data is provided for the dynamic class.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01056: The class {0} cannot be used as a slice.

Cause: A dynamic class contained a class that could not be used as a slice.

Action: Ensure that the class is derived from the appropriate slice class.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01057: The method {1} is not a supported method on the {0} class.

Cause: A slice class provided a list of implemented methods that contained a method not supported by the slice class.

Action: Ensure that all implemented methods in the definition are supported by the slice class.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01058: The class {0} must implement all the slice methods.

Cause: A dynamic class definition included a stub class that did not implement all of the methods available.

Action: Correct the definition of the stub class.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01059: The slice purpose annotation on class {0} is not specified.

Cause: A slice class did not specify its purpose using the aspect annotation.

Action: Add an appropriate aspect annotation to the slice class implementation.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01060: The dynamic class definition file {1} for {0} cannot be loaded.

Cause: The definition for a dynamic class could not be found.

Action: Correct the resource path specified for the dynamic class.

Level: 1

Type: WARNING

Impact: Programmatic

IRM-01061: Not authorized to perform this operation.

Cause: A sealed content operation was attempted which was not authorized.

Action: Ensure that the authenticated user has the appropriate license to perform the sealing, resealing, peeking, or unsealing operation. Check that the classification key set is valid. Check the the classification URL is correct. Check that the licenses are not checked out to a different device.

Level: 1

Type: NOTIFICATION

Impact: Security

IRM-01062: A duplicate {0} element is supplied where a duplicate is not allowed or expected.

Cause: A duplicate element was provided where a duplicate is not allowed/expected.

Action: Ensure that the input data does not contain duplicates.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01063: The parameter {1} passed into {0} has an illegal value.

Cause: An illegal value was passed as a method argument.

Action: Correct the invalid value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01064: The {0} {1} property cannot exceed {4} characters in length. The invalid value provided was {2}, which has {3} characters.

Cause: A value was used as a property which exceeded the maximum permitted length.

Action: Correct the invalid property and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01065: The {0} {1} property has an illegal value.

Cause: An illegal value was specified for a property.

Action: Correct the invalid value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01066: The {0} {1} is immutable and cannot be modified.

Cause: An attempt was made to alter a property that is read-only or immutable.

Action: Make a copy of the property to make changes.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01067: An unexpected error has occurred. If this exception does not include details of the cause, then examine the diagnostic logs for more details.

Cause: An unexpected error occurred.

Action: Review the exception cause for further details.

Level: 1

Type: WARNING

Impact: Other

IRM-01068: The parameter {1} passed into {0} is mandatory.

Cause: A mandatory argument was not specified.

Action: Provide the value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01069: The {0} {1} property is mandatory.

Cause: A mandatory property was not specified.

Action: Provide the value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01070: The enumeration value {0} is unsupported in this context.

Cause: An unsupported enumeration value was provided.

Action: Correct the value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01071: A response could not be found for method {0} on class %Class%.

Cause: A method invocation required a fixed response and one could not be found.

Action: Correct the fixed responses provided to the response slice.

Level: 1

Type: TRACE

Impact: Programmatic

IRM-01072: The transaction has been rolled back. If this exception does not include details of the cause then examine the diagnostic logs for more details.

Cause: A transaction commit failed.

Action: Review the exception cause for further information.

Level: 1

Type: TRACE

Impact: Data

IRM-01073: The response or method {0} is unsupported by class {1}.

Cause: A response or the method provided to a response slice is not supported.

Action: Correct the fixed responses provided to the response slice.

Level: 1

Type: TRACE

Impact: Programmatic

IRM-01074: The web service endpoint address for the service {0} is missing.

Cause: A web service endpoint address was not specified.

Action: Provide the endpoint address for the endpoint.

Level: 1

Type: WARNING

Impact: Configuration

IRM-01075: The credentials for the web service could not be determined.

Cause: Web service credentials were not provided.

Action: Provide the credentials in the IRM credential store using the web service address as the key.

Level: 1

Type: WARNING

Impact: Configuration

IRM-01076: Status page redirected to URI.

Cause: A status page request has been redirected to another system.

Action: This is not an error and no action is required by the system administrator.

Level: 16

Type: TRACE

Impact: Requests/Responses

IRM-01076: The item constraints for role \"{0}\" cannot be altered as the role has been assigned to a user or group.

Cause: An attempt has been made to alter the role item constraints for a role that has been assigned to a user or group.

Action: Unassign the users and groups that are using the role.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01077: The encrypted content block size must be a direct multiple of the cipher block size. The cipher block size is {0}, but the encrypted content block size has been set as {1}.

Cause: An illegal encrypted content block size was provided during sealing.

Action: Use a block size that is a direct multiple of the cipher block size. Block sizes are typically multiples of 16.

Level: 32

Type: TRACE

Impact: Programmatic

IRM-01078: The public header cannot exceed {1} bytes in length. The current public header when written as XML has a length of {0} bytes. Reduce the amount of data provided in the custom data or classification cookie.

Cause: A public header exceeded the maximum length.

Action: Reduce the amount of data provided in the classification labels or custom data.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01079: The parameter {1} passed into {0} cannot exceed {4} characters in length. The invalid value provided was {2} which has {3} characters.

Cause: A value was passed as a method argument which exceeded the permitted length.

Action: Correct the invalid value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01080: Licenses are available, but they cannot be used for the following reasons: {0}.

Cause: A license was available to the user but could not be used for the specified classification.

Action: Check the exception for the list of licenses and associated availability status. The availability will provide the reason why the license cannot be used. For example, the license may not support the requested feature or the license may have time constraints that disallow use of the license at the time of the license request.

Level: 1

Type: TRACE

Impact: Other

IRM-01081: A wrapping key {1} bits in size is insufficient to wrap a {0} bit key.

Cause: A wrapping key could not be used to wrap a key as it was of insufficient size.

Action: Increase the size of the wrapping key used or reduce the size of the key being wrapped.

Level: 1

Type: ERROR

Impact: Security

IRM-01081: The expected size of the unsealed content was {0} bytes in length. The actual number of bytes read from the input stream was {1}.

Cause: The unsealed content size does not match the amount of data read from a stream.

Action: Ensure the unsealed content size matches the amount of data provided in the input stream.

Level: 16

Type: TRACE

Impact: Data

IRM-01082: The locale value {0} is unsupported. Supported locales are {1}.

Cause: An unsupported locale value was specified.

Action: Use one of the supported locale values and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01083: The device count {0} must be greater than zero and less than or equal to {1}.

Cause: An illegal device count value was specified.

Action: Change the device count to a valid value and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01084: The refresh period {0} is too small. Specify a refresh period of one minute or greater.

Cause: An illegal refresh period was specified.

Action: Use a refresh period of one minute or greater and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-01085: The scheduled task interval of {0} is illegal. Specify a positive time period.

Cause: An illegal task interval was specified.

Action: Use a positive time period greater and retry the operation.

Level: 16

Type: TRACE

Impact: Programmatic

IRM-03001: An exception occurred retrieving the rights for the context.

Cause: An exception occurred retrieving the rights for a context.

Action: Review the exception cause for further information.

Level: 1

Type: ERROR

Impact: Data

IRM-03002: An exception occurred retrieving the context managers.

Cause: An exception occurred retrieving context managers.

Action: Review the exception cause for further information.

Level: 1

Type: ERROR

Impact: Data

IRM-03003: An exception occurred reading the uploaded file - {0}.

Cause: An exception occurred reading an uploaded file.

Action: Review the exception cause for further information.

Level: 1

Type: WARNING

Impact: Data

IRM-03004: An exception occurred retrieving the refresh periods.

Cause: An exception occurred retrieving refresh periods.

Action: Review the exception cause for further information.

Level: 1

Type: SEVERE

Impact: Data

IRM-03005: An exception occurred retrieving the global features.

Cause: An exception occurred retrieving the global features.

Action: Review the exception cause for further information.

Level: 1

Type: SEVERE

Impact: Data

IRM-03006: An exception occurred retrieving the primary features.

Cause: An exception occurred retrieving the primary features.

Action: Review the exception cause for further information.

Level: 1

Type: SEVERE

Impact: Data

IRM-03007: An exception occurred retrieving the feature labels.

Cause: An exception occurred retrieving the feature labels.

Action: Review the exception cause for further information.

Level: 1

Type: SEVERE

Impact: Data

IRM-03008: An exception occurred determining the available locales.

Cause: An exception occurred determining the available locales.

Action: Review the exception cause for further information.

Level: 1

Type: WARNING

Impact: Data

IRM-03009: IRM EJBs are not deployed.

Cause: The IRM EJBs could not be found by the management console.

Action: Ensure that the IRM EJBs are deployed and accessible by the web application.

Level: 1

Type: SEVERE

Impact: Installation

IRM-03010: Domain is not seeded.

Cause: No domain was found.

Action: Log in to the management console to trigger seeding of the initial domain.

Level: 1

Type: SEVERE

Impact: Configuration

IRM-03011: User has no role.

Cause: No role could be found for a user.

Action: Assign an appropriate role to the user.

Level: 32

Type: TRACE

Impact: Configuration

IRM-03012: An exception occurred retrieving user details.

Cause: An exception occurred retrieving user details.

Action: Review the exception cause for further information.

Level: 1

Type: WARNING

Impact: Data