Oracle® Java ME Embedded Getting Started Guide for the Reference Platform (Keil) Release 3.3.1 E38140-02 |
|
Previous |
Next |
Table B-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 B-1 Installer Error Codes
Constant | Error Code | Description |
---|---|---|
|
78 |
Application Level Access Authorization: The alias definition is missing. |
|
80 |
Application Level Access Authorization: The alias definition is wrong. |
|
79 |
Application Level Access Authorization: An alias has multiple entries that match. |
|
77 |
Application Level Access Authorization: The |
|
39 |
The JAD matches a version of a suite already installed. |
|
69 |
Application Integrity Failure: two or more dependencies exist on the component with the same name and vendor, but have different versions or hashs. |
|
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. |
|
68 |
Application Integrity Failure: hash mismatch. |
|
50 |
A attribute in both the JAD and JAR manifest does not match. |
|
49 |
Application authorization failure, possibly indicating that the application was not digitally signed. |
|
60 |
Indicates that the trusted certificate authority (CA) for this suite has been disabled for software authorization. |
|
101 |
Canceled by user. |
|
35 |
The server does not support basic authentication. |
|
64 |
Circular dynamic component dependency. |
|
65 |
Dynamic component dependencies limit exceeded. |
|
72 |
The namespace used by a component is the same as another. |
|
55 |
The installation of a content handler would conflict with an already installed handler. |
|
71 |
A dependency has a corrupt hash code. |
|
36 |
An entry could not be read from the JAR. |
|
5 |
The content provider certificate cannot be decoded. |
|
8 |
The JAR signature cannot be decoded. |
|
40 |
The device does not support either the configuration or profile in the JAD. |
|
88 |
Duplicated JAD/manifest key attribute |
|
12 |
The certificate authority's public key has expired. |
|
11 |
The content provider certificate has expired. |
|
82 |
A font that is contained with the JAR cannot be loaded. |
|
30 |
Not enough storage for this suite to be installed. |
|
54 |
The |
|
37 |
The server did not have a resource with the correct type or the JAD downloaded has the wrong media type. |
|
43 |
The JAD URL is invalid. |
|
38 |
The server did not have a resource with the correct type or the JAR downloaded has the wrong media type. |
|
44 |
The JAR URL is invalid. |
|
28 |
A key for an attribute is not formatted correctly. |
|
85 |
A native library contained within the JAR cannot be loaded. |
|
87 |
A dependency cannot be satisfied. |
|
58 |
Indicates that the payment information provided with the IMlet suite is incomplete or incorrect. |
|
7 |
The signature of the content provider certificate is invalid. |
|
76 |
The server did not have a resource with the correct type or the JAD downloaded has the wrong media type. |
|
73 |
The RMS data file URL is invalid. |
|
86 |
A LIBlet that exports a service with a LIBlet Services attribute does not contain the matching service provider configuration information. |
|
9 |
The signature of the JAR is invalid. |
|
29 |
A value for an attribute is not formatted correctly. |
|
16 |
The format of the version is invalid. |
|
102 |
A low-level hardware error has occurred. |
|
34 |
The JAD URL for an installed suite is different than the original JAD URL. |
|
2 |
The JAD was not found. |
|
1 |
The server for the JAD was not found. |
|
56 |
Not all classes within JAR package can be successfully verified with class verifier. |
|
100 |
Component or MIDlet or IMlet suite is locked by the system. |
|
20 |
The JAR was not found at the URL given in the JAD. |
|
19 |
The server for the JAR was not found at the URL given in the JAD. |
|
31 |
The JAR downloaded was not the same size as given in the JAD. |
|
41 |
The configuration is missing from the manifest. |
|
67 |
A dependency hash code is missing. |
|
66 |
A dependency JAD URL is missing. |
|
21 |
The JAR size is missing. |
|
18 |
The URL for the JAR is missing. |
|
42 |
The profile is missing from the manifest. |
|
4 |
The content provider certificate is missing. |
|
13 |
The name of MIDlet or IMlet suite is missing. |
|
14 |
The vendor is missing. |
|
15 |
The version is missing. |
|
32 |
This suite is newer that the one currently installed. |
|
0 |
No error. |
|
89 |
A certificate is not yet valid. |
|
90 |
A CA's public key is not yet valid. |
|
17 |
This suite is older that the one currently installed. |
|
103 |
Other errors. |
|
51 |
Indicates that the user must first authenticate with the proxy. |
|
48 |
The class in a push attribute is not in |
|
45 |
The connection in a push entry is already taken. |
|
46 |
The format of a push attribute has an invalid format. |
|
47 |
The connection in a push attribute is not supported. |
|
62 |
The certificate has been revoked. |
|
83 |
Indicates that a password is required to decrypt RMS data. |
|
84 |
Indicates that a password is required to encrypt RMS data. |
|
75 |
The RMS data file was not found at the specified URL. |
|
74 |
The server for the RMS data file was not found at the specified URL. |
|
81 |
Failure to import RMS data. |
|
25 |
The MIDlet or IMlet suite name does not match the one in the JAR manifest. |
|
53 |
Indicates that either the JAD or manifest has too many properties to fit into memory. |
|
52 |
Indicates that the user tried to overwrite a trusted suite with an untrusted suite during an update. |
|
33 |
Web server authentication failed or is required. |
|
6 |
The certificate authority (CA) that issued the content provider certificate is unknown. |
|
63 |
The certificate is unknown to OCSP server. |
|
10 |
The content provider certificate has an unsupported version. |
|
61 |
Indicates that the character encoding specified in the MIME type is not supported. |
|
57 |
Indicates that the payment information provided with the MIDlet or IMlet suite is incompatible with the current implementation. |
|
59 |
Indicates that the MIDlet or IMlet suite has payment provisioning information but it is not trusted. |
|
27 |
The vendor does not match the one in the JAR manifest. |
|
26 |
The version does not match the one in the JAR manifest. |