This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.
Error Message
The asset is not found.
Possible Cause
Solution
Error Message
The asset already exists.
Possible Cause
An asset with the same alias (asset.Tag.ALIAS) already exists.
Solution
Check whether the alias of the asset to add is correct. If the alias is incorrect, use the correct alias. If the alias is correct, perform either of the following operations:
Error Message
Access denied.
Possible Cause
The user authentication required before the access to the asset fails.
The challenge value does not match the authorization token.
Solution
Perform user authentication.
Pass in the challenge value and authorization token that are matched with each other.
Error Message
The screen lock status does not match.
Possible Cause
Solution
Set a lock screen password or unlock the screen before accessing the asset.
Error Message
Insufficient memory.
Possible Cause
The system memory is insufficient.
Solution
Close unnecessary applications to release memory and initiate a processing request again.
Error Message
The asset is corrupted.
Possible Cause
The asset file is corrupted due to device power-off or storage system exceptions.
Solution
Restore factory settings.
Error Message
The database operation failed.
Possible Cause
Solution
Error Message
The cryptography operation failed.
Possible Cause
The cryptographic operation fails.
Solution
Locate the cause of the operation failure based on error information.
Error Message
IPC failed.
Possible Cause
The IPC failed.
Solution
Locate the cause of the IPC failure based on error information.
Error Message
Calling the Bundle Manager service failed.
Possible Cause
The Bundle Manager service is abnormal.
Solution
Locate the cause of the exception based on error information.
Error Message
Calling the OS Account service failed.
Possible Cause
The account service is abnormal.
Solution
Locate the cause of the exception based on error information.
Error Message
Calling the Access Token service failed.
Possible Cause
The Access Token service is abnormal.
Solution
Locate the cause of the exception based on error information.
Error Message
The file operation failed.
Possible Cause
Solution
Restart the device. If the problem persists, restore factory settings of the device.
Error Message
Getting the system time failed.
Possible Cause
The system time is tampered with.
Solution
Correct the system time.
Error Message
The cache exceeds the limit.
Possible Cause
asset.postQuery is not called to release resources after asset.preQuery is called.
Solution
Call asset.postQuery to release resources after asset.preQuery is called.
Error Message
The capability is not supported.
Possible Cause
The API is supported, but certain sub-features of the API, for example, querying plaintext of assets in batches, are not supported.
Solution
Adjust API parameters and use alternative APIs, for example, invoking the alternative API multiple times to query assets.
Error Message
Parameter verify failed.
Possible Cause
The input argument is invalid.
Solution
Adjust the API arguments based on the error information and call the API again.
Error Message
Each value of Tag.GROUP_ID and Tag.REQUIRE_ATTR_ENCRYPTED in the array is not consistent.
Possible Cause
During batch operations, the GROUP_ID and REQUIRE_ATTR_ENCRYPTED attribute values of each key asset in the array are inconsistent.
Solution
Ensure that the GROUP_ID and REQUIRE_ATTR_ENCRYPTED attribute values of all key assets in the batch operations array are consistent, and call the API again.