1# backgroundTaskManager 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## 9800001 Memory Operation Failure 8 9**Error Message** 10 11Memory operation failed. 12 13**Description** 14 15This error code is reported when a memory operation fails. 16 17**Possible Causes** 18 191. A memory leak occurs. 202. The system memory is insufficient. 21 22**Solution** 23 241. Release the memory. 252. Check whether memory leak occurs. 26 27## 9800002 Parcel Operation Failure 28 29**Error Message** 30 31Failed to write data into parcel. Possible reasons: 1. Invalid parameters; 2. Failed to apply for memory. 32 33**Description** 34 35When an API related to a continuous task is called, the read or write operation fails during IPC. 36 37**Possible Causes** 38 391. The data object fails to be read or written during IPC. 402. The memory fails to be allocated for the read or write operation. 41<br>During RPC, the sender can use the **write()** method provided by **MessageParcel** to write data in specific format to a **MessageParcel** object. The receiver can use the **read()** method provided by **MessageParcel** to read data in specific format from a **MessageParcel** object. 42 43**Solution** 44 45Try again later or restart the device. 46 47## 9800003 IPC Failure 48 49**Error Message** 50 51Internal transaction failed. 52 53**Description** 54 55This error code is reported when IPC fails. 56 57**Possible Causes** 58 59IPC fails. 60 61**Solution** 62 63Try again later or restart the device. 64 65## 9800004 System Service Failure 66 67**Error Message** 68 69System service operation failed. 70 71**Description** 72 73When an API related to a continuous task is called, the client process fails to obtain the system service. 74 75**Possible Causes** 76 771. The system service is not started. 782. The system service is abnormal. 79 80**Solution** 81 82Try again later or restart the device. 83 84## 9800005 Continuous Task Verification Failure 85 86**Error Message** 87 88Continuous task verification failed. 89 90**Description** 91 92This error code is reported when continuous task verification fails. 93 94**Possible Causes** 95 961. The application repeatedly requests a continuous task. 972. The application repeatedly cancels a continuous task. 983. The value of **bgMode** is invalid because no continuous task type is configured for **backgroundModes** in the application's configuration file. 994. Only <!--RP1-->specific devices<!--RP1End--> can request continuous tasks of the KEEPING_TASK type. 100 101**Solution** 102 1031. Check the application code. 1042. Check whether the application has the system permissions. 1053. Check the type of the device where the application is located. 1064. Check the value of **backgroundModes**. 107 108## 9800006 Notification Verification Failure for a Continuous Task 109 110**Error Message** 111 112Notification verification failed for a continuous task. 113 114**Description** 115 116This error code is reported when notification verification in a continuous task fails. 117 118**Possible Causes** 119 1201. The continuous task resources cached in the resource subsystem fail to be loaded. 1212. The notification subsystem functions abnormally. 122 123**Solution** 124 1251. Check for the continuous task resources **ohos.backgroundtaskmgr.resources**. 1262. Try again later or restart the device. 127 128## 9800007 Continuous Task Storage Failure 129 130**Error Message** 131 132Continuous task storage failed. 133 134**Description** 135 136This error code is reported when information storage in a continuous task fails. 137 138**Possible Causes** 139 1401. Failed to create a file to store the task information. 1412. Failed to obtain the file path. 1423. Failed to open the file that stores the task information. 143 144**Solution** 145 1461. Check the **/data/service/el1/public/background_task_mgr/running_task** file. 1472. Try again later or restart the device. 148 149## 9900001 Caller Information Verification Failure for a Transient Task 150 151**Error Message** 152 153Caller information verification failed for a transient task. 154 155**Description** 156 157This error code is reported when caller information verification in a transient task fails. 158 159**Possible Causes** 160 1611. Failed to obtain the UID or PID of the caller. 1622. Failed to obtain the bundle name of the caller. 1633. The request ID passed in the API used to cancel the transient task is invalid. 164 165**Solution** 166 1671. Check whether the application UID exists. 1682. Check whether the application has requested a transient task. 1693. Try again later or restart the device. 170 171## 9900002 Transient Task Verification Failure 172 173**Error Message** 174 175Transient task verification failed. 176 177**Description** 178 179This error code is reported when transient task verification fails. 180 181**Possible Causes** 182 1831. The callback passed in **requestSuspendDelay()** already exists. 1842. The callback passed in **cancelSuspendDelay()** does not exist. 1853. The application attempts to request a transient task 5 seconds after it switches to the background. 1864. The application has already requested three transient tasks. 1875. The application's daily quota for transient tasks is used up. 188 189**Solution** 190 1911. Check the application code. 1922. The application should cancel transient tasks immediately after they are complete. 193 194## 9900003 Parcel Operation Failure 195 196**Error Message** 197 198Failed to write data into parcel. Possible reasons: 1. Invalid parameters; 2. Failed to apply for memory. 199 200**Description** 201 202When an API related to a transient task is called, the read or write operation fails during IPC. 203 204**Possible Causes** 205 2061. The data object fails to be read or written during IPC. 2072. The memory fails to be allocated for the read or write operation. 208<br>During RPC, the sender can use the **write()** method provided by **MessageParcel** to write data in specific format to a **MessageParcel** object. The receiver can use the **read()** method provided by **MessageParcel** to read data in specific format from a **MessageParcel** object. 209 210**Solution** 211 212Try again later or restart the device. 213 214## 9900004 System Service Failure 215 216**Error Message** 217 218System service operation failed. 219 220**Description** 221 222When an API related to a transient task is called, the client process fails to obtain the system service. 223 224**Possible Causes** 225 2261. The system service is not started. 2272. The system service is abnormal. 228 229**Solution** 230 231Try again later or restart the device. 232<!--Del--> 233## 18700001 Caller Information Verification Failure for an Energy Resource Request 234 235**Error Message** 236 237Caller information verification failed for an energy resource request. 238 239**Description** 240 241This error code is reported when caller information verification in an energy resource request fails. 242 243**Possible Causes** 244 2451. Failed to obtain the UID or PID of the caller. 2462. The value of **resourceTypes** for requesting energy resources exceeds the upper limit. 247 248**Solution** 249 250Check the input parameters. 251 252## 18700002 Parcel Operation Failure 253 254**Error Message** 255 256Failed to write data into parcel. Possible reasons: 1. Invalid parameters; 2. Failed to apply for memory. 257 258**Description** 259 260When an API related to efficiency resources is called, the read or write operation fails during IPC. 261 262**Possible Causes** 263 2641. The data object fails to be read or written during IPC. 2652. The memory fails to be allocated for the read or write operation. 266<br>During RPC, the sender can use the **write()** method provided by **MessageParcel** to write data in specific format to a **MessageParcel** object. The receiver can use the **read()** method provided by **MessageParcel** to read data in specific format from a **MessageParcel** object. 267 268**Solution** 269 270Try again later or restart the device. 271 272## 18700004 System Service Failure 273 274**Error Message** 275 276System service operation failed. 277 278**Description** 279 280When an API related to efficiency resources is called, the client process fails to obtain the system service. 281 282**Possible Causes** 283 2841. The system service is not started. 2852. The system service is abnormal. 286 287**Solution** 288 289Try again later or restart the device. 290<!--DelEnd--> 291