1# Application Access Control Error Codes 2 3> **NOTE** 4> 5> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](errorcode-universal.md). 6 7## 12100001 Invalid Parameters 8 9**Error Message** 10 11Parameter invalid, message is ${messageInfo}. 12 13**Possible Causes** 14 15This error code is reported if an error occurs during parameter verification. The possible causes are as follows: 16- The value of **tokenId** is **0**. 17- The permission name is empty or exceeds 256 characters. 18- The **flag** value in the permission authorization or revocation request is invalid. 19- The input parameters specified for registering a listener are incorrect. 20 21**Solution** 22 23Correct the invalid parameter values. 24 25 26## 12100002 TokenId Does Not Exist 27 28**Error Message** 29 30TokenId does not exist. 31 32**Possible Causes** 33 34- The specified **tokenId** does not exist. 35- The process of the specified **tokenId** is not an application process. 36 37**Solution** 38 39Set **tokenId** correctly. 40 41 42## 12100003 Permission Does Not Exist 43 44**Error Message** 45 46Permission does not exist. 47 48**Possible Causes** 49 50- The specified **permissionName** does not exist. 51- The specified **permissionName** does not match the **tokenId** in the permission authorization or revocation scenario. 52- The specified **permissionName** is not a sensitive permission that requires user authorization. 53 54**Solution** 55 56Set the **permissionName** parameter correctly. For details, see [permission-list](../../security/permission-list.md). 57 58 59## 12100004 Listener APIs Not Used in Pairs 60 61**Error Message** 62 63The interface is not used together. 64 65**Possible Causes** 66 67This error code is reported if listener APIs are not used in pairs. The possible causes are as follows: 681. The listener APIs that need to be used in pairs are repeatedly called. 692. The listener APIs that need to be used in pairs are independently called. 70 71**Solution** 72 731. Check whether the API needs to be used in pairs. That is, if an API is called to enable listening, an API with the same input parameters cannot be called unless an API is called to stop listening first. 742. Check whether the API needs to be used in pairs. That is, an API for disabling listening or unregistering a listener can only be called after the API for enabling listening or registering a listener is called. 75 76 77## 12100005 Listener Overflow 78 79**Error Message** 80 81The number of listeners exceeds the limit. 82 83**Possible Causes** 84 85The number of listeners exceeds 200 (the upper limit). 86 87**Solution** 88 89Release unused listeners in a timely manner. 90 91 92## 12100006 Permission Granting or Revocation Not Supported for the Specified Application 93 94**Error Message** 95 96The specified application does not support the permissions granted or ungranted as specified. 97 98**Possible Causes** 99 1001. The specified **tokenId** is the identity of the remote device. Distributed permission granting and revocation are not yet supported. 1012. The specified **tokenId** belongs to a sandbox application, which is not allowed to apply for the specified permission. 102 103**Solution** 104 1051. Check whether the method of obtaining **tokenId** is correct. 1062. Check whether the sandbox application works in restrictive mode. Most permissions cannot be granted to a sandbox application in restrictive mode. 107 108 109## 12100007 System Services Not Working Properly 110 111**Error Message** 112 113Service is abnormal. 114 115**Possible Causes** 116 117This error code is reported if system services are not working properly. The possible causes are as follows: 118- The permission management service cannot start properly. 119- The read or write of IPC data fails. 120 121**Solution** 122 123System services do not work properly. Try again later or restart the device. 124 125 126## 12100008 Out of Memory 127 128**Error Message** 129 130Out of memory. 131 132**Possible Causes** 133 134The system memory is insufficient. 135 136**Solution** 137 138Try again later or restart the device. 139