1# Bundle 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## 17700001 Bundle Name Does Not Exist 8 9**Error Message** 10 11The specified bundle name is not found. 12 13**Description** 14 15When a query API is called, the bundle name passed in does not exist. 16 17**Possible Causes** 18 191. The bundle name is misspelled. 202. The corresponding bundle is not installed. 21 22**Solution** 231. Check whether the spelling of the bundle name is correct. 242. Check whether the corresponding bundle is installed. 25 26## 17700002 Module Name Does Not Exist 27 28**Error Message** 29 30The specified module name is not found. 31 32**Description** 33 34When a query API or an installation-free API is called, the module name passed in does not exist. 35 36**Possible Causes** 371. The module name is misspelled. 382. The module is not installed. 39 40**Solution** 411. Check whether the spelling of the module name is correct. 422. Check whether the module is installed. 43 44## 17700003 Ability Name Does Not Exist 45 46**Error Message** 47 48The specified ability name is not found. 49 50**Description** 51 52When a query API is called, the ability name passed in does not exist. 53 54**Possible Causes** 551. The ability name is misspelled. 562. The application does not have the ability specified by **abilityName**. 57 58**Solution** 591. Check whether the spelling of the ability name is correct. 602. Check whether the application has the ability specified by **abilityName**. 61 62## 17700004 User ID Does Not Exist 63 64**Error Message** 65 66The specified user ID is not found. 67 68**Description** 69 70When a user-related API is called, the user ID passed in does not exist. 71 72**Possible Causes** 731. Incorrect username. 742. The user does not exist in the system. 75 76**Solution** 771. Check whether the user ID is correct. 782. Check whether the user exists. 79 80## 17700005 appId Is an Empty String 81 82**Error Message** 83 84The specified app ID is empty string. 85 86**Description** 87 88When an API of the **appControl** module is called, the application ID passed in does not exist. 89 90**Possible Causes** 91 92**appId** is an empty string. 93 94**Solution** 95 96Check whether **appId** is an empty string. 97 98## 17700006 Permission Does Not Exist 99 100**Error Message** 101 102The specified permission is not found. 103 104**Description** 105 106When the **getPermissionDef** API of the **bundleManager** module is called, the permission passed in does not exist. 107 108**Possible Causes** 1091. The permission name is misspelled. 1102. The permission does not exist. 111 112**Solution** 1131. Check whether the spelling of the permission name is correct. 1142. Check whether the permission exists. 115 116## 17700007 Incorrect Device ID 117 118**Error Message** 119 120The specified device ID is not found. 121 122**Description** 123 124When an API of the **distributedBundle** module is called, the device ID passed in does not exist. 125 126**Possible Causes** 1271. The device ID is incorrect. 1282. The device ID does not exist. 129 130**Solution** 1311. Check whether the device ID is correct. 1322. Check whether the device ID exists. 133 134## 17700010 Bundle Installation Failure Due to File Parsing Failure 135 136**Error Message** 137 138Failed to install the HAP because the HAP fails to be parsed. 139 140**Description** 141 142When the **install** API of the **installer** module is called, the HAP passed in fails to be parsed. 143 144**Possible Causes** 1451. The HAP is not in ZIP format. 1462. The configuration file in the HAP is not in JSON format. 1473. Necessary fields are missing in the configuration file. 148 149**Solution** 1501. Check whether the HAP is in ZIP format. 1512. Check whether the configuration file is in [JSON format](../../quick-start/application-configuration-file-overview-stage.md). 1523. Check whether an error message is displayed when DevEco Studio compiles the HAP. If necessary fields are missing, an error message will be displayed. 153 154## 17700011 Bundle Installation Failure Due to Signature Verification Failure 155 156**Error Message** 157 158Failed to install the HAP because the HAP signature fails to be verified. 159 160**Description** 161 162Calling the **install** API of the **installer** module to install the bundle fails due to signature verification failure. 163 164**Possible Causes** 165 1661. The HAP is not signed. 1672. The source of the HAP signature information is unreliable. 1683. The signature information of the HAP used for an upgrade is different from that of the installed HAP. 1694. The signature information of multiple HAPs is inconsistent. 170 171**Solution** 1721. Check whether the HAP is signed. 1732. Ensure that the signing certificate of the HAP is applied for from the application market. 1743. Check whether the same certificate is used for signing multiple HAPs. 1754. Check whether the certificate used for signing the upgrade HAP is the same as the certificate used for signing the installed HAP. 176 177## 17700012 Bundle Installation Failure Due to Invalid File Path or Too Large File 178 179**Error Message** 180 181Failed to install the HAP because the HAP path is invalid or the HAP is too large. 182 183**Description** 184 185Calling the **install** API of the **installer** module to install the bundle fails because the HAP path is invalid or the HAP is too large. 186 187**Possible Causes** 1881. The path of the HAP does not exist. 1892. The path of the HAP is inaccessible. 1903. The size of the HAP exceeds the upper limit 4 GB. 191 192**Solution** 1931. Check whether the HAP path exists. 1942. Check whether the HAP is read only or executable. 1953. Check whether the size of the HAP exceeds 4 GB. 196 197## 17700015 Bundle Installation Failure Due to Different Configuration Information of Multiple HAPs 198 199**Error Message** 200 201Failed to install the HAPs because they have different configuration information. 202 203**Description** 204 205Calling the **install** API of the **installer** module to install the bundle fails because the HAPs have different configuration information. 206 207**Possible Causes** 208 209The fields under **app** in the configuration files of these HAPs are inconsistent. 210 211**Solution** 212 213Check whether the fields under **app** are the same. 214 215## 17700016 Bundle Installation Failure Due to Insufficient System Disk Space 216 217**Error Message** 218 219Failed to install the HAP because of insufficient system disk space. 220 221**Description** 222 223Calling the **install** API of the **installer** module to install the bundle fails due to insufficient system disk space. 224 225**Possible Causes** 226 227The system disk space is insufficient. 228 229**Solution** 230 231Check whether the system has sufficient disk space. 232 233## 17700017 Bundle Installation Failure Because the Version to Install is Too Earlier 234 235**Error Message** 236 237Failed to install the HAP since the version of the HAP to install is too early. 238 239**Description** 240 241Calling the **install** API of the **installer** module to install the bundle fails because the version to install is earlier than the version in use. 242 243**Possible Causes** 244 245The version number is earlier than the version in use. 246 247**Solution** 248 249Ensure that the version of the bundle to install is not earlier than the version in use. 250 251## 17700018 Bundle Installation Failure Becase the Dependent Module Does Not Exist 252 253**Error Message** 254 255Failed to install because the dependent module does not exist. 256 257**Description** 258 259The dependent module does not exist during the HAP or HPS installation. 260 261**Possible Causes** 262 263The dependent module is not installed. 264 265**Solution** 266 267Install the dependent modules first. 268 269## 17700020 Failure to Uninstall Preinstalled Applications 270 271**Error Message** 272 273The preinstalled app cannot be uninstalled. 274 275**Description** 276 277Calling the **uninstall** API of the **installer** module to uninstall a preinstalled application fails. 278 279**Possible Causes** 280 2811. You might want to uninstall a non-preinstalled application but passed the bundle name of a preinstalled app. 2822. The preinstalled application cannot be uninstalled. 283 284**Solution** 2851. Check whether the bundle name is correct. 2861. Check whether the preinstalled application can be uninstalled. 287 288## 17700021 Invalid UID 289 290**Error Message** 291 292The specified uid is invalid. 293 294**Description** 295 296When the **getBundleNameByUid** API of the **bundleManager** module is called, the UID passed in is invalid. 297 298**Possible Causes** 2991. The UID is misspelled. 3002. The UID does not exist. 301 302**Solution** 3031. Check whether the UID is correct. 3042. Check whether the UID exists. 305 306## 17700022 Invalid Source File 307 308**Error Message** 309 310The input source file is invalid. 311 312**Description** 313 314When the **getBundleArchiveInfo** API of the **bundleManager** module is called, the HAP path passed in is invalid. 315 316**Possible Causes** 3171. The source file to be parsed does not exist. 3182. The source file to be parsed is not in ZIP format. 319 320**Solution** 3211. Check whether the source file to be parsed exists. 3222. Check whether the source file to be parsed is in ZIP format. 323 324## 17700023 Default Application Does Not Exist 325 326**Error Message** 327 328The specified default app does not exist. 329 330**Description** 331 332When the **getDefaultApplication** API of the **defaultAppManager** module is called, the specified default application does not exist. 333 334**Possible Causes** 335 336No default application is set for the device. 337 338**Solution** 339 340Check whether the default application is set on the device. 341 342## 17700024 Configuration File Does Not Exist 343 344**Error Message** 345 346Failed to get the profile because there is no profile in the HAP. 347 348**Description** 349 350When an API for querying the profile is called, the configuration file does not exist 351 352**Possible Causes** 353 3541. The metadata name passed in the API does not exist in the configuration file. 3552. The content of the configuration file is not in JSON format. 356 357**Solution** 3581. Check whether the metadata name in the **ability** or **extensionAbility** to be queried exists. 3592. Check whether the content of the profile to be queried is in JSON format. 360 361## 17700025 Invalid Type 362 363**Error Message** 364 365The specified type is invalid. 366 367**Description** 368 369When an API of the **defaultAppManager** module is called, the type passed in is invalid. 370 371**Possible Causes** 3721. The type passed in the API is misspelled. 3732. The type passed in the API does not exist. 374 375**Solution** 3761. Check whether the spelling of type is correct. 3772. Enter a type that exists. 378 379## 17700026 Bundle Disabled 380 381**Error Message** 382 383The specified bundle is disabled. 384 385**Description** 386 387When an API for querying bundle information is called, the specified bundle is disabled. 388 389**Possible Causes** 390 391The bundle on the device has been disabled and cannot be queried. 392 393**Solution** 394 395Check whether the bundle on the device is disabled. 396 397## 17700027 Distributed Service Is Not Started 398 399**Error Message** 400 401The distributed service is not running. 402 403**Description** 404 405When an API of the **distributedBundle** module is called, the distributed service is not started. 406 407**Possible Causes** 408 409The device is not networked. 410 411**Solution** 412 413Check whether the device is networked. 414 415## 17700028 Mismatch Between Ability and Type 416 417**Error Message** 418 419The ability does not match the type. 420 421**Description** 422 423When the **setDefaultApplication** API of the **defaultAppManager** module is called, the **ability** and **type** passed in do not match. 424 425**Possible Causes** 426 427The ability and type are misspelled. 428 429**Solution** 430 431Check whether the spellings of ability and type are correct. 432 433## 17700029 Disabled Ability 434 435**Error Message** 436 437The specified ability is disabled. 438 439**Description** 440 441When an API for querying ability information is called, the specified ability is disabled. 442 443**Possible Causes** 444 445The specified ability is disabled. 446 447**Solution** 448 449Check whether the ability is disabled. You can run the [bm commands](../../../readme/bundle-management.md#bm-commands) to query the information. 450 451## 17700030 Failure in Clearing Cache Files 452 453**Error Message** 454 455The specified bundle does not support clearing of cache files. 456 457**Description** 458 459When the **cleanBundleCacheFiles** API of the **bundleManager** module is called, the specified bundle does not support cache file clearing. 460 461**Possible Causes** 462 463The application is a system application and the **AllowAppDataNotCleared** field is configured in the signing certificate. 464 465**Solution** 4661. Check whether the application is a system application. You can run the [bm commands](../../../readme/bundle-management.md#bm-commands) to query the application information and check whether the value of **isSystemApp** is **true**. 4672. Check whether the **AllowAppDataNotCleared** field is configured for the application. You can run the [bm commands](../../../readme/bundle-management.md#bm-commands) to query the application information and check whether the value of **userDataClearable** is **true**. 468 469 470