C AMS Installer Error Codes

Table C-1 lists the error codes that the AMS command-line interface shows when the installation of an IMlet fails. The description of each code contains more information about the problem that caused the error.

Table C-1 Installer Error Codes

Constant	Error Code	Description
`ALAA_ALIAS_NOT_FOUND`	78	Application Level Access Authorization: The alias definition is missing.
`ALAA_ALIAS_WRONG`	80	Application Level Access Authorization: The alias definition is wrong.
`ALAA_MULTIPLE_ALIAS`	79	Application Level Access Authorization: An alias has multiple entries that match.
`ALAA_TYPE_WRONG`	77	Application Level Access Authorization: The `MIDlet-Access-Auth-Type` has missing parameters.
`ALREADY_INSTALLED`	39	The JAD matches a version of a suite already installed.
`APP_INTEGRITY_FAILURE_DEPENDENCY_CONFLICT`	69	Application Integrity Failure: two or more dependencies exist on the component with the same name and vendor, but have different versions or hashs.
`APP_INTEGRITY_FAILURE_DEPENDENCY_MISMATCH`	70	Application Integrity Failure: there is a component name or vendor mismatch between the component JAD and IMlet or component JAD that depends on it.
`APP_INTEGRITY_FAILURE_HASH_MISMATCH`	68	Application Integrity Failure: hash mismatch.
`ATTRIBUTE_MISMATCH`	50	A attribute in both the JAD and JAR manifest does not match.
`AUTHORIZATION_FAILURE`	49	Application authorization failure, possibly indicating that the application was not digitally signed.
`CA_DISABLED`	60	Indicates that the trusted certificate authority (CA) for this suite has been disabled for software authorization.
`CANCELED`	101	Canceled by user.
`CANNOT_AUTH`	35	The server does not support basic authentication.
`CIRCULAR_COMPONENT_DEPENDENCY`	64	Circular dynamic component dependency.
`COMPONENT_DEPS_LIMIT_EXCEEDED`	65	Dynamic component dependencies limit exceeded.
`COMPONENT_NAMESPACE_COLLISION`	72	The namespace used by a component is the same as another.
`CONTENT_HANDLER_CONFLICT`	55	The installation of a content handler would conflict with an already installed handler.
`CORRUPT_DEPENDENCY_HASH`	71	A dependency has a corrupt hash code.
`CORRUPT_JAR`	36	An entry could not be read from the JAR.
`CORRUPT_PROVIDER_CERT`	5	The content provider certificate cannot be decoded.
`CORRUPT_SIGNATURE`	8	The JAR signature cannot be decoded.
`DEVICE_INCOMPATIBLE`	40	The device does not support either the configuration or profile in the JAD.
`DUPLICATED_KEY`	88	Duplicated JAD/manifest key attribute
`EXPIRED_CA_KEY`	12	The certificate authority's public key has expired.
`EXPIRED_PROVIDER_CERT`	11	The content provider certificate has expired.
`INCORRECT_FONT_LOADING`	82	A font that is contained with the JAR cannot be loaded.
`INSUFFICIENT_STORAGE`	30	Not enough storage for this suite to be installed.
`INVALID_CONTENT_HANDLER`	54	The `MicroEdition-Handler-`<n> JAD attribute has invalid values.
`INVALID_JAD_TYPE`	37	The server did not have a resource with the correct type or the JAD downloaded has the wrong media type.
`INVALID_JAD_URL`	43	The JAD URL is invalid.
`INVALID_JAR_TYPE`	38	The server did not have a resource with the correct type or the JAR downloaded has the wrong media type.
`INVALID_JAR_URL`	44	The JAR URL is invalid.
`INVALID_KEY`	28	A key for an attribute is not formatted correctly.
`INVALID_NATIVE_LIBRARY`	85	A native library contained within the JAR cannot be loaded.
`INVALID_PACKAGING`	87	A dependency cannot be satisfied.
`INVALID_PAYMENT_INFO`	58	Indicates that the payment information provided with the IMlet suite is incomplete or incorrect.
`INVALID_PROVIDER_CERT`	7	The signature of the content provider certificate is invalid.
`INVALID_RMS_DATA_TYPE`	76	The server did not have a resource with the correct type or the JAD downloaded has the wrong media type.
`INVALID_RMS_DATA_URL`	73	The RMS data file URL is invalid.
`INVALID_SERVICE_EXPORT`	86	A LIBlet that exports a service with a LIBlet Services attribute does not contain the matching service provider configuration information.
`INVALID_SIGNATURE`	9	The signature of the JAR is invalid.
`INVALID_VALUE`	29	A value for an attribute is not formatted correctly.
`INVALID_VERSION`	16	The format of the version is invalid.
`IO_ERROR`	102	A low-level hardware error has occurred.
`JAD_MOVED`	34	The JAD URL for an installed suite is different than the original JAD URL.
`JAD_NOT_FOUND`	2	The JAD was not found.
`JAD_SERVER_NOT_FOUND`	1	The server for the JAD was not found.
`JAR_CLASSES_VERIFICATION_FAILED`	56	Not all classes within JAR package can be successfully verified with class verifier.
`JAR_IS_LOCKED`	100	Component or MIDlet or IMlet suite is locked by the system.
`JAR_NOT_FOUND`	20	The JAR was not found at the URL given in the JAD.
`JAR_SERVER_NOT_FOUND`	19	The server for the JAR was not found at the URL given in the JAD.
`JAR_SIZE_MISMATCH`	31	The JAR downloaded was not the same size as given in the JAD.
`MISSING_CONFIGURATION`	41	The configuration is missing from the manifest.
`MISSING_DEPENDENCY_HASH`	67	A dependency hash code is missing.
`MISSING_DEPENDENCY_JAD_URL`	66	A dependency JAD URL is missing.
`MISSING_JAR_SIZE`	21	The JAR size is missing.
`MISSING_JAR_URL`	18	The URL for the JAR is missing.
`MISSING_PROFILE`	42	The profile is missing from the manifest.
`MISSING_PROVIDER_CERT`	4	The content provider certificate is missing.
`MISSING_SUITE_NAME`	13	The name of MIDlet or IMlet suite is missing.
`MISSING_VENDOR`	14	The vendor is missing.
`MISSING_VERSION`	15	The version is missing.
`NEW_VERSION`	32	This suite is newer that the one currently installed.
`NO_ERROR`	0	No error.
`NOT_YET_VALID_PROVIDER_CERT`	89	A certificate is not yet valid.
`NOT_YET_VALID_CA_KEY`	90	A CA's public key is not yet valid.
`OLD_VERSION`	17	This suite is older that the one currently installed.
`OTHER_ERROR`	103	Other errors.
`PROXY_AUTH`	51	Indicates that the user must first authenticate with the proxy.
`PUSH_CLASS_FAILURE`	48	The class in a push attribute is not in `MIDlet-`<n> attribute.
`PUSH_DUP_FAILURE`	45	The connection in a push entry is already taken.
`PUSH_FORMAT_FAILURE`	46	The format of a push attribute has an invalid format.
`PUSH_PROTO_FAILURE`	47	The connection in a push attribute is not supported.
`REVOKED_CERT`	62	The certificate has been revoked.
`RMS_DATA_DECRYPT_PASSWORD`	83	Indicates that a password is required to decrypt RMS data.
`RMS_DATA_ENCRYPT_PASSWORD`	84	Indicates that a password is required to encrypt RMS data.
`RMS_DATA_NOT_FOUND`	75	The RMS data file was not found at the specified URL.
`RMS_DATA_SERVER_NOT_FOUND`	74	The server for the RMS data file was not found at the specified URL.
`RMS_INITIALIZATION_FAILURE`	81	Failure to import RMS data.
`SUITE_NAME_MISMATCH`	25	The MIDlet or IMlet suite name does not match the one in the JAR manifest.
`TOO_MANY_PROPS`	53	Indicates that either the JAD or manifest has too many properties to fit into memory.
`TRUSTED_OVERWRITE_FAILURE`	52	Indicates that the user tried to overwrite a trusted suite with an untrusted suite during an update.
`UNAUTHORIZED`	33	Web server authentication failed or is required.
`UNKNOWN_CA`	6	The certificate authority (CA) that issued the content provider certificate is unknown.
`UNKNOWN_CERT_STATUS`	63	The certificate is unknown to OCSP server.
`UNSUPPORTED_CERT`	10	The content provider certificate has an unsupported version.
`UNSUPPORTED_CHAR_ENCODING`	61	Indicates that the character encoding specified in the MIME type is not supported.
`UNSUPPORTED_PAYMENT_INFO`	57	Indicates that the payment information provided with the MIDlet or IMlet suite is incompatible with the current implementation.
`UNTRUSTED_PAYMENT_SUITE`	59	Indicates that the MIDlet or IMlet suite has payment provisioning information but it is not trusted.
`VENDOR_MISMATCH`	27	The vendor does not match the one in the JAR manifest.
`VERSION_MISMATCH`	26	The version does not match the one in the JAR manifest.