1# Bundle Error Codes 2<!--Kit: Ability Kit--> 3<!--Subsystem: BundleManager--> 4<!--Owner: @wanghang904--> 5<!--Designer: @hanfeng6--> 6<!--Tester: @kongjing2--> 7<!--Adviser: @Brilliantry_Rui--> 8 9> **NOTE** 10> 11> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](../errorcode-universal.md). 12 13## 17700001 Bundle Name Does Not Exist 14 15**Error Message**<br> 16The specified bundle name is not found. 17 18**Description**<br> 19When a query API is called, the bundle name passed in does not exist. 20 21**Possible Causes**<br> 22 231. The bundle name is misspelled. 242. The corresponding bundle is not installed. 25 26**Solution**<br> 271. Check whether the spelling of the bundle name is correct. 282. Check whether the corresponding bundle is installed. 29 30## 17700002 Module Name Does Not Exist 31 32**Error Message**<br> 33The specified module name is not found. 34 35**Description**<br> 36When a query API or an installation-free API is called, the module name passed in does not exist. 37 38**Possible Causes**<br> 391. The module name is misspelled. 402. The module is not installed. 41 42**Solution**<br> 431. Check whether the spelling of the module name is correct. 442. Check whether the module is installed. 45 46## 17700003 Ability Name Does Not Exist 47 48**Error Message**<br> 49The specified ability name is not found. 50 51**Description**<br> 52When a query API is called, the ability name passed in does not exist. 53 54**Possible Causes**<br> 551. The ability name is misspelled. 562. The application does not have the ability specified by **abilityName**. 57 58**Solution**<br> 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**<br> 65The specified user ID is not found. 66 67**Description**<br> 68When a user-related API is called, the user ID passed in does not exist. <!--Del-->When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error.<!--DelEnd--> 69 70**Possible Causes**<br> 711. Incorrect username. 722. The user does not exist in the system. 73 74**Solution**<br> 751. Check whether the user ID is correct. 762. Check whether the user exists. 77<!--Del--> 78## 17700005 appId Is an Empty String 79 80**Error Message**<br> 81The specified app ID is an empty string. 82 83**Description**<br> 84When an API of the [appControl module](../apis-ability-kit/js-apis-appControl-sys.md) is called, the appId passed in does not exist. 85 86**Possible Causes**<br> 87**appId** is an empty string. 88 89**Solution**<br> 90Check whether **appId** is an empty string. 91 92## 17700006 Permission Does Not Exist 93 94**Error Message**<br> 95The specified permission is not found. 96 97**Description**<br> 98When the [getPermissionDef](../apis-ability-kit/js-apis-bundleManager-sys.md#bundlemanagergetpermissiondef) API of the bundleManager module is called, the permission passed in does not exist. 99 100**Possible Causes**<br> 1011. The permission name is misspelled. 1022. The permission does not exist. 103 104**Solution**<br> 1051. Check whether the spelling of the permission name is correct. 1062. Check whether the permission exists. 107 108## 17700007 Incorrect Device ID 109 110**Error Message**<br> 111The specified device ID is not found. 112 113**Description**<br> 114When an API of the [distributedBundle module](../apis-ability-kit/js-apis-distributedBundleManager-sys.md) is called, the device ID passed in does not exist. 115 116**Possible Causes**<br> 1171. The device ID is incorrect. 1182. The device ID does not exist. 119 120**Solution**<br> 1211. Check whether the device ID is correct. 1222. Check whether the device ID exists. 123 124## 17700010 Bundle Installation Failure Due to File Parsing Failure 125 126**Error Message**<br> 127Failed to install the HAP because the HAP fails to be parsed. 128 129**Description**<br> 130When the install API of the [install module](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) is called, the HAP passed in fails to be parsed. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 131 132**Possible Causes**<br> 1331. The HAP is not in ZIP format. 1342. The profile in the HAP is not in JSON format. 1353. Necessary fields are missing in the profile. 136 137**Solution**<br> 1381. Check whether the HAP is in ZIP format. 1392. Check whether the profile is in [JSON format](../../quick-start/application-configuration-file-overview-stage.md). 1403. Check whether an error message is displayed when DevEco Studio compiles the HAP. If necessary fields are missing, an error message will be displayed. 141 142## 17700011 Bundle Installation Failure Due to Signature Verification Failure 143 144**Error Message**<br> 145Failed to install the HAP because the HAP signature fails to be verified. 146 147**Description**<br> 148Calling the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API of the installer module to install the bundle fails due to signature verification failure. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 149 150**Possible Causes**<br> 151 1521. The HAP is not signed. 1532. The source of the HAP signature information is unreliable. 1543. The signature information of the HAP to update is different from that of the installed HAP. 1554. The signature information of multiple HAPs is inconsistent. 156 157**Solution**<br> 1581. Check whether the HAP is signed. 1592. Ensure that the signing certificate of the HAP is applied for from the application market. 1603. Check whether the same certificate is used for signing multiple HAPs. 1614. Check whether the certificate used for signing the HAP to update is the same as the certificate used for signing the installed HAP. 162 163## 17700012 Bundle Installation Failure Due to Invalid File Path or Too Large File 164 165**Error Message**<br> 166Failed to install the HAP because the HAP path is invalid or the HAP is too large. 167 168**Description**<br> 169Calling the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API of the installer module to install the bundle fails because the HAP path is invalid or the HAP is too large. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 170 171**Possible Causes**<br> 1721. The path of the HAP does not exist. 1732. The path of the HAP is inaccessible. 1743. The size of the HAP exceeds the upper limit 4 GB. 175 176**Solution**<br> 1771. Check whether the HAP path exists. 1782. Check whether the HAP is read only or executable. 1793. Check whether the size of the HAP exceeds 4 GB. 180 181## 17700015 Bundle Installation Failure Due to Different Configuration Information of Multiple HAPs 182 183**Error Message**<br> 184Failed to install the HAPs because they have different configuration information. 185 186**Description**<br> 187Calling the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API of the installer module to install the bundle fails because the HAPs have different configuration information. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 188 189**Possible Causes**<br> 190The fields under **app** in the profiles of these HAPs are inconsistent. 191 192**Solution**<br> 193Check whether the fields under **app** are the same. 194 195## 17700016 Bundle Installation Failure Due to Insufficient System Disk Space 196 197**Error Message**<br> 198Failed to install the HAP because of insufficient system disk space. 199 200**Description**<br> 201Calling the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API of the installer module to install the bundle fails due to insufficient system disk space. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 202 203**Possible Causes**<br> 204The system disk space is insufficient. 205 206**Solution**<br> 207Check whether the system has sufficient disk space. 208 209## 17700017 Bundle Installation Failure Because the Version to Install is Too Earlier 210 211**Error Message**<br> 212Failed to install the HAP since the version of the HAP to install is too early. 213 214**Description**<br> 215Calling the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API of the installer module to install the bundle fails because the version to install is earlier than the version in use. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 216 217**Possible Causes**<br> 218The version number is earlier than the version in use. 219 220**Solution**<br> 221Ensure that the version of the bundle to install is not earlier than the version in use. 222 2231. To query the version of an existing application, use [the HDC tool](../../dfx/hdc.md#environment-setup). 224``` 225// Obtain the last field from the dump output. 226hdc shell bm dump -n com.xxx.demo |grep versionCode 227``` 228 229 230 2312. To query the version of a newly installed application, use DevEco Studio to open the HAP or HSP file and check the value of **versionCode** in the **module.json** file. 232 233 234 235## 17700018 Bundle Installation Failure Because the Dependent Module Does Not Exist 236 237**Error Message**<br> 238Failed to install the HAP or HSP because the dependent module does not exist. 239 240**Description**<br> 241The dependent module does not exist during the HAP or HPS installation. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 242 243**Possible Causes**<br> 244The dependent module is not installed. 245 246**Solution**<br> 247Install the dependent modules first. 248 249## 17700020 Failure to Uninstall Preinstalled Applications 250 251**Error Message**<br> 252The preinstalled app cannot be uninstalled. 253 254**Description**<br> 255Calling the [uninstall](../apis-ability-kit/js-apis-installer-sys.md#bundleinstalleruninstall) API of the installer module to uninstall a preinstalled application fails. 256 257**Possible Causes**<br> 2581. You might want to uninstall a non-preinstalled application but passed the bundle name of a preinstalled app. 2592. The preinstalled application cannot be uninstalled. 260 261**Solution**<br> 2621. Check whether the bundle name is correct. 2632. Check whether the preinstalled application can be uninstalled.<!--DelEnd--> 264 265## 17700021 Invalid UID 266 267**Error Message**<br> 268The specified uid is invalid. 269 270**Description**<br> 271When the [getBundleNameByUid](../apis-ability-kit/js-apis-bundleManager.md#bundlemanagergetbundlenamebyuid14) API of the bundleManager module is called, the UID passed in is invalid. 272 273**Possible Causes**<br> 2741. The UID is misspelled. 2752. The UID does not exist. 276 277**Solution**<br> 2781. Check whether the UID is correct. 2792. Check whether the UID exists. 280<!--Del--> 281## 17700022 Invalid Source File 282 283**Error Message**<br> 284The input source file is invalid. 285 286**Description**<br> 287When the [getBundleArchiveInfo](../apis-ability-kit/js-apis-bundleManager-sys.md#bundlemanagergetbundlearchiveinfo) API of the bundleManager module is called, the HAP path passed in is invalid. 288 289**Possible Causes**<br> 2901. The source file to be parsed does not exist. 2912. The source file to be parsed is not in ZIP format. 292 293**Solution**<br> 2941. Check whether the source file to be parsed exists. 2952. Check whether the source file to be parsed is in ZIP format. 296 297## 17700023 Default Application Does Not Exist 298 299**Error Message**<br> 300The specified default app does not exist. 301 302**Description**<br> 303When the [getDefaultApplication](../apis-ability-kit/js-apis-defaultAppManager-sys.md#defaultappmanagergetdefaultapplication) API of the defaultAppManager module is called, the specified default application does not exist. 304 305**Possible Causes**<br> 306No default application is set for the device. 307 308**Solution**<br> 309Check whether the default application is set on the device.<!--DelEnd--> 310 311## 17700024 Profile Does Not Exist 312 313**Error Message**<br> 314Failed to get the profile because the specified profile is not found in the HAP. 315 316**Description**<br> 317When an API for querying the profile is called, the profile does not exist. 318 319**Possible Causes**<br> 3201. The metadata name passed in the API does not exist in the profile. 3212. The content of the profile is not in JSON format. 3223. The type of the profile to query does not exist. 323 324**Solution**<br> 3251. Check whether the metadata name in the **ability** or **extensionAbility** to be queried exists. 3262. Check whether the content of the profile to be queried is in JSON format. 3273. Check whether the application contains a profile that matches the value of **profileType** passed in. 328<!--Del--> 329## 17700025 Invalid Type 330 331**Error Message**<br> 332The specified type is invalid. 333 334**Description**<br> 335When an API of the defaultAppManager module is called, the type passed in is invalid. 336 337**Possible Causes**<br> 3381. The type passed in the API is misspelled. 3392. The type passed in the API does not exist. 340 341**Solution**<br> 3421. Check whether the spelling of type is correct. 3432. Enter a type that exists.<!--DelEnd--> 344 345## 17700026 Bundle Disabled 346 347**Error Message**<br> 348The specified bundle is disabled. 349 350**Description**<br> 351When an API for querying bundle information is called, the specified bundle is disabled. 352 353**Possible Causes**<br> 354The bundle on the device has been disabled and cannot be queried. 355 356**Solution**<br> 357Check whether the bundle on the device is disabled. 358<!--Del--> 359## 17700027 Distributed Service Is Not Started 360 361**Error Message**<br> 362The distributed service is not running. 363 364**Description**<br> 365When an API of the [distributedBundle module](../apis-ability-kit/js-apis-distributedBundleManager-sys.md) is called, the distributed service is not started. 366 367**Possible Causes**<br> 368The device is not networked. 369 370**Solution**<br> 371Check whether the device is networked. 372## 17700028 Mismatch Between Ability and Type 373 374**Error Message**<br> 375The ability does not match the type. 376 377**Description**<br> 378When the [setDefaultApplication](../apis-ability-kit/js-apis-defaultAppManager-sys.md#defaultappmanagersetdefaultapplication) API of the defaultAppManager module is called, the ability and type passed in do not match. 379 380**Possible Causes**<br> 381The ability and type are misspelled. 382 383**Solution**<br> 384Check whether the spellings of ability and type are correct.<!--DelEnd--> 385 386## 17700029 Disabled Ability 387 388**Error Message**<br> 389The specified ability is disabled. 390 391**Description**<br> 392When an API for querying ability information is called, the specified ability is disabled. 393 394**Possible Causes**<br> 395The specified ability is disabled. 396 397**Solution**<br> 398Check whether the ability is disabled. You can use [Bundle Manager](../../tools/bm-tool.md) to query the information. 399<!--Del--> 400## 17700030 Failure in Clearing Cache Files 401 402**Error Message**<br> 403The specified bundle does not support clearing of cache files. 404 405**Description**<br> 406When the [cleanBundleCacheFiles](../apis-ability-kit/js-apis-bundleManager-sys.md#bundlemanagercleanbundlecachefiles) API of the bundleManager module is called, the specified bundle does not support cache file clearing. 407 408**Possible Causes**<br> 409The application is a system application and the **AllowAppDataNotCleared** field is configured in the signing certificate. 410 411**Solution**<br> 4121. Check whether the application is a system application. You can use [Bundle Manager](../../tools/bm-tool.md) to query the application information and check whether the value of **isSystemApp** is **true**. 4132. Check whether the **AllowAppDataNotCleared** field is configured for the application. You can use [Bundle Manager](../../tools/bm-tool.md) to query the application information and check whether the value of **userDataClearable** is **true**. 414 415## 17700031 HAP Installation Fails Due to Overlay Feature Verification Failure 416 417**Error Message**<br> 418Failed to install the HAP because the overlay check of the HAP failed. 419 420**Description**<br> 421The target application and the to-be-installed application with the overlay feature are not preset applications, or the target application or target module is one with the overlay feature. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 422 423**Possible Causes**<br> 4241. To use the overlay feature between applications, the following conditions must be met:<br>The application with the overlay feature must be a preset application. 4252. The target application must be a preset application. 4263. The target application cannot be an application with the overlay feature. 4274. The target module cannot be a module with the overlay feature. 428 429**Solution**<br> 4301. Ensure that the application with the overlay feature is a preset application. 4312. Ensure that the target application is a preset application. 4323. Ensure that the target application is not an application with the overlay feature. 4334. Ensure that the target module is not a module with the overlay feature.<!--DelEnd--> 434 435## 17700032 Application Does Not Contain a Module with the Overlay Feature 436 437**Error Message**<br> 438The specified bundle does not contain any overlay module. 439 440**Description**<br> 441An API is called to obtain the overlayModuleInfo object of another application, but that application does not contain a module with the overlay feature. 442 443**Possible Causes**<br> 444The specified application does not contain a module with the overlay feature. 445 446**Solution**<br> 447Check whether the application contains a module with the overlay feature. 448 449## 17700033 Module Is Not Configured with the Overlay Feature 450 451**Error Message**<br> 452The specified module is not an overlay module. 453 454**Description**<br> 455An API is called to obtain the overlayModuleInfo object of a module, but the module is not configured with the overlay feature. 456 457**Possible Causes**<br> 458The specified module is not a module with the overlay feature. 459 460**Solution**<br> 461Check whether the module is configured with the overlay feature. 462 463## 17700034 Module Is Configured with the Overlay Feature 464 465**Error Message**<br> 466The specified module is an overlay module. 467 468**Description**<br> 469An API is called to obtain the overlayModuleInfo object based on the target module name, but that module is configured with the overlay feature. 470 471**Possible Causes**<br> 472The specified module is configured with the overlay feature. 473 474**Solution**<br> 475Check whether the specified module is configured with the overlay feature. 476<!--Del--> 477## 17700035 Application Contains Only Modules with the Overlay Feature 478 479**Error Message**<br> 480The specified bundle is an overlay bundle. 481 482**Description**<br> 483An API is called to obtain the overlayModuleInfo object based on the target module name of another application, but that application contains only modules with the overlay feature. 484 485**Possible Causes**<br> 486The specified application contains only modules with the overlay feature. 487 488**Solution**<br> 489Check whether the application contains only modules with the overlay feature. 490 491## 17700036 Failure in Installing the Shared Library Because of No AllowAppShareLibrary Privilege 492 493**Error Message**<br> 494Failed to install the HSP due to the lack of required permission. 495 496**Description**<br> 497The shared library is not configured with the **AllowAppShareLibrary** privilege, resulting in security and privacy risks. As a result, the installation fails. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 498 499**Possible Causes**<br> 500The shared library does not request the **AllowAppShareLibrary** privilege before being released. 501 502**Solution**<br> 503Configure the **AllowAppShareLibrary** privilege for the shared library, re-sign the library, and release it. 504 505## 17700037 Failure in Uninstalling the Shared Library Due to Dependency 506 507**Error Message**<br> 508The version of the shared bundle is dependent on other applications. 509 510**Description**<br> 511Other applications depend on the shared library, causing the uninstall to fail. 512 513**Possible Causes**<br> 5141. The version specified during the uninstall is the latest version of the shared library, and the shared library is depended on by other applications. 5152. No version is not specified during the uninstall, meaning that all versions of the shared library will be uninstalled, and the shared library is depended on by other applications. 516 517**Solution**<br> 5181. Check whether the shared library to uninstall is depended on by other applications. 5192. Check whether the version of the shared library to uninstall is the latest version of the shared library. 520 521## 17700038 Shared Library to Uninstall Does Not Exist 522 523**Error Message**<br> 524The specified shared bundle does not exist. 525 526**Description**<br> 527The shared library to uninstall does not exist. 528 529**Possible Causes**<br> 5301. The version specified during the uninstall is different from the version of the shared library installed. 5312. The shared library to uninstall is not installed. 532 533**Solution**<br> 5341. Check whether the shared library exists. 5352. Check whether the version of the shared library is the same as that installed. 536 537## 17700039 Failure in Installing an Inter-Application Shared Library 538**Error Message**<br> 539Failed to install the HSP because installing a shared bundle specified by hapFilePaths is not allowed. 540 541**Description**<br> 542During application installation, the installation package passed in is of the inter-application shared library type. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 543 544**Possible Causes**<br> 5451. When [Bundle Manager](../../tools/bm-tool.md) is used to install an application, the **-p** parameter is set to the installation package path of an inter-application shared library. 5462. When the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API is called to install an application, the **hapFilePaths** parameter is set to the installation package path of an inter-application shared library. 547 548**Solution**<br> 5491. Use the **-p** parameter to specify the installation package path of an inter-application shared library. 5502. Use the **sharedBundleDirPaths** parameter in **installParam** to specify the installation package path of an inter-application shared library. 551 552## 17700040 Failure in Uninstalling an Inter-Application Shared Library 553**Error Message**<br> 554The specified bundle is a shared bundle which cannot be uninstalled. 555 556**Description**<br> 557During application uninstall, the bundle name of an inter-application shared library is passed in. 558 559**Possible Causes**<br> 5601. When [Bundle Manager](../../tools/bm-tool.md) is used to uninstall an application, the **-n** parameter is set to the bundle name of an inter-application shared library. 5612. hen the [uninstall](../apis-ability-kit/js-apis-installer-sys.md#bundleinstalleruninstall) API is called to uninstall a bundle, the **bundleName** parameter is set to the bundle name of an inter-bundle shared library. 562 563**Solution**<br> 5641. Use the **-n** parameter to specify the application to be uninstalled as a shared library application. 5652. Use the **bundleName** and **versionCode** parameters in **UninstallParam** to specify the bundle name and version of the shared library to be uninstalled. 566 567## 17700041 Application Installation Is Not Allowed by Enterprise Device Management 568**Error Message**<br> 569Failed to install the HAP because the installation is forbidden by enterprise device management. 570 571**Description**<br> 572The installation of this application is prohibited by enterprise device management. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 573 574**Possible Causes**<br> 575The enterprise device management does not allow the installation of this application. 576 577**Solution**<br> 578Check whether the application installation is prohibited by the enterprise device management. 579 580## 17700042 Incorrect URI in the Data Proxy 581**Error Message**<br> 582Failed to install the HAP because of incorrect URI in the data proxy. 583 584**Description**<br> 585During application installation, the URI of the data proxy is incorrectly configured. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 586 587**Possible Causes**<br> 5881. The bundle name in the URI is different from that of the current application. 5892. The URI is duplicate. 590 591**Solution**<br> 5921. Change the bundle name in the URI to that of the current application. 5932. Change duplicate URIs. Ensure that the URI of each data proxy is unique. 594 595## 17700043 Incorrect Permission Configuration in the Data Proxy 596**Error Message**<br> 597Failed to install the HAP because of low APL in the non-system data proxy (required APL: system_basic or system_core). 598 599**Description**<br> 600During application installation, the permission level of the data proxy of a non-system application is too low. The permission level should be **system_basic** or **system_core**. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 601 602**Possible Causes**<br> 6031. No permission is configured for the data proxy of a non-system application. 6042. The permission level of the data proxy of a non-system application is too low. 605 606**Solution**<br> 6071. Configure the read and write permissions in the data proxy. 6082. Change the read and write permissions in the data proxy and ensure that the permission level is **system_basic** or **system_core**. 609 610## 17700044 Field isolationMode in the HAP Conflicts with the Device Isolation Mode 611**Error Message**<br> 612Failed to install the HAP because the isolationMode configured is not supported. 613 614**Description**<br> 615During application installation, the value of **isolationMode** in the HAP conflicts with the isolation mode of the device. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 616 617**Possible Causes**<br> 6181. The device supports the isolation mode (the value of **persist.bms.supportIsolationMode** is **true**), whereas the value of **isolationMode** in the HAP is **nonisolationOnly**. 6192. The device does not support the isolation mode (the value of **persist.bms.supportIsolationMode** is **false**), whereas the value of **isolationMode** in the HAP is **isolationOnly**. 620 621**Solution**<br> 622Set the **isolationMode** field in the HAP based on the isolation mode of the device. 623 624## 17700045 Application Uninstall Is Not Allowed by Enterprise Device Management 625**Error Message**<br> 626Failed to uninstall the HAP because the uninstall is forbidden by enterprise device management. 627 628**Description**<br> 629The uninstall of this application is prohibited by enterprise device management. 630 631**Possible Causes**<br> 632The enterprise device management does not allow the installation of this application. 633 634**Solution**<br> 635Check whether the application uninstall is prohibited by the enterprise device management. 636 637## 17700047 Application Version To Be Updated Is Not Later Than the Current Version 638**Error Message**<br> 639Failed to install the HAP because the VersionCode to be updated is not greater than the current VersionCode. 640 641**Description**<br> 642The version of the application to be updated is not later than the current version. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 643 644**Possible Causes**<br> 6451. The version number of the application to be updated is earlier than or equal to that of the current version number. 6462. When **installFlag** is set to **NORMAL**, the version number of the application to be updated must be later than the installed version number. 647 648**Solution**<br> 6491. Set the version number of the application to be later than the current version number. For details about how to check the version number, see [17700017 Bundle Installation Failure Because the Version to Install is Too Earlier](#17700017-bundle-installation-failure-because-the-version-to-install-is-too-earlier). 6502. If you want to update the application without changing the version number, set **installFlag** to **REPLACE_EXISTING**. 651 652## 17700048 Code Signature Verification Failure 653**Error Message**<br> 654Failed to install the HAP because the code signature verification failed. 655 656**Description**<br> 657During application installation, the code signature file of the installation package fails to be verified. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 658 659**Possible Causes**<br> 6601. The module corresponding to the code signature file does not exist in the installation package. 6612. The path of the code signature file is invalid. 6623. The code signature file does not match the installation package. 663 664**Solution**<br> 6651. Ensure that the module corresponding to the code signature file is contained in the installation package. 6662. Provide a valid path of the code signature file. 6673. Use the code signature file that matches the installation package. 668 669## 17700049 Update Failure Because of Incorrect Bundle Name 670**Error Message**<br> 671Failed to install the HAP because the bundleName is different from the bundleName of the caller application. 672 673**Description**<br> 674During the update of an enterprise MDM application, the bundleName passed in is different from that of the caller. 675 676**Possible Causes**<br> 677The HAP or HSP to be installed does not belong to the current application. 678 679**Solution**<br> 680Ensure that the HAP or HSP to be installed belongs to the current application. 681 682## 17700050 Enterprise Device Verification Failure 683**Error Message**<br> 684Failed to install the HAP because an enterprise normal/MDM bundle cannot be installed on non-enterprise devices. 685 686**Description**<br> 687Users try to install an enterprise Normal or MDM application on a non-enterprise device. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 688 689**Possible Causes**<br> 690The device is not an enterprise device. 691 692**Solution**<br> 6931. Use an enterprise device. 6942. Ensure that **const.bms.allowenterprisebundle** is set to **true**. 695 696## 17700051 HAP Installation Failure Due to Incorrect Distribution Type in the Signing Certificate Profile of the Caller 697**Error Message**<br> 698Failed to install the HAP because the distribution type of the caller application is not enterprise_mdm. 699 700**Description**<br> 701When an enterprise MDM application attempts to upgrade itself, the distribution type specified in the caller's [signing certificate profile](https://developer.huawei.com/consumer/en/doc/app/agc-help-add-releaseprofile-0000001914714796) is not **enterprise_mdm**. 702 703**Possible Causes**<br> 704The distribution type specified in the caller's signing certificate profile is not **enterprise_mdm**. 705 706**Solution**<br> 707Ensure that the signature file of the application is correctly configured. 708 709## 17700052 Installation of Debugging Applications Allowed Only in Developer Mode 710**Error Message**<br> 711Failed to install the HAP because a debug bundle can be installed only in developer mode. 712 713**Description**<br> 714A debugging application can be installed only in the developer mode. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 715 716**Possible Causes**<br> 717The application is a debugging application, but the device is not in developer mode. 718 719**Solution**<br> 720Run the **hdc shell param get const.security.developermode.state** command. If **false** is returned, a debugging application cannot be installed on the device. 721 722## 17700053 Not Invoked by AppGallery 723**Error Message**<br> 724The caller is not AppGallery. 725 726**Description**<br> 727This API is called by AppGallery. 728 729**Possible Causes**<br> 730The caller is not AppGallery. 731 732**Solution**<br> 733Use AppGallery to call the API. 734 735## 17700054 Bundle Installation Failure Due to Permission Verification Failure 736**Error Message**<br> 737Failed to install the HAP because the HAP requests wrong permissions. 738 739**Description**<br> 740The application has applied for an incorrect permission, causing the installation to fail. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 741 742**Possible Causes**<br> 7431. The application is not an MDM application and has applied for the MDM permission. 7442. The ability privilege level (APL) of the application is lower than the level of the permission that the application has applied for. 745 746**Solution**<br> 7471. Check whether the application has applied for the [MDM permission](../../security/AccessToken/permissions-for-mdm-apps.md), which is available only for MDM applications. 7482. Check whether the requested permission is open. For details, see [Permission List](../../security/AccessToken/app-permissions.md).<!--DelEnd--> 749 750## 17700055 Invalid Link 751 752**Error Message**<br> 753The specified link is invalid. 754 755**Description**<br> 756When the [canOpenLink](../apis-ability-kit/js-apis-bundleManager.md#bundlemanagercanopenlink12) API of the bundleManager module is called, the link passed in is invalid. 757 758**Possible Causes**<br> 759The format of the link is incorrect. 760 761**Solution**<br> 762Check whether the link format is correct. 763 764## 17700056 Scheme of the Link Not Configured in querySchemes 765 766**Error Message**<br> 767The scheme of the specified link is not in the querySchemes. 768 769**Description**<br> 770When the [canOpenLink](../apis-ability-kit/js-apis-bundleManager.md#bundlemanagercanopenlink12) API of the bundleManager module is called, the scheme of the link is not configured in the **querySchemes** field. 771 772**Possible Causes**<br> 773The scheme of the link is not configured in the **querySchemes** field. 774 775**Solution**<br> 776Check whether the URL scheme is configured in the **querySchemes** field. 777<!--Del--> 778## 17700057 Specified Application Is Not a Preset Application 779 780**Error Message**<br> 781Failed to uninstall updates because the HAP is not pre-installed. 782 783**Description**<br> 784When the [uninstallUpdates](../apis-ability-kit/js-apis-installer-sys.md#bundleinstalleruninstallupdates12) API of the installer module is called, the specified application is not a preset application. 785 786**Possible Causes**<br> 787The **uninstallUpdates** API can only be used to uninstall the updates of a preset application. 788 789**Solution**<br> 790Check whether the specified application is a preset application. 791 792## 17700058 Specified Application Cannot Be Installed on this Device or by this User 793 794**Error Message**<br> 795Failed to install the HAP because this application is prohibited from being installed on this device or by specified users. 796 797**Description**<br> 798The specified application cannot be installed on this device or by this user. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 799 800**Possible Causes**<br> 8011. The device in use has undergone a whitewashing process. 8022. The specified application is prohibited from being installed by the specified user. 803 804**Solution**<br> 8051. Check whether the device has undergone a whitewashing process. 8062. Install the application as another user. 807 808## 17700059 Specified Developer ID Does Not Exist 809 810**Error Message**<br> 811The specified developerId is invalid. 812 813**Description**<br> 814When the [getAllBundleInfoByDeveloperId](../apis-ability-kit/js-apis-bundleManager-sys.md#bundlemanagergetallbundleinfobydeveloperid12) API of the bundleManager module is called, the developer ID passed in is invalid. 815 816**Possible Causes**<br> 817Applications with the specified developer ID are not installed on the device. 818 819**Solution**<br> 820Check the validity of the developer ID. 821 822## 17700060 Specified Application Cannot Be Uninstalled 823 824**Error Message**<br> 825The specified application cannot be uninstalled. 826 827**Description**<br> 828When the [uninstall](../apis-ability-kit/js-apis-installer-sys.md#bundleinstalleruninstall) API of the BundleInstaller module or the [switchUninstallState](../apis-ability-kit/js-apis-bundleManager-sys.md#bundlemanagerswitchuninstallstate12) API of the bundleManager module is called, the specified application cannot be uninstalled. 829 830**Possible Causes**<br> 8311. When the **uninstall** API is called, the specified application rejects the uninstallation attempt due to the ongoing operation of its own services. 8322. When the **switchUninstallState** API is called, the specified application has a privilege that prevents it from being uninstalled. 833 834**Solution**<br> 8351. Check the reason why the application cannot be uninstalled and perform related operations. 8362. Check whether the specified application is uninstallable. 837 838## 17700061 appIndex for a Clone Is Invalid 839 840**Error Message**<br> 841The appIndex is invalid. 842 843**Description**<br> 844When an API related to the app clone feature is called, the specified **appIndex** is invalid. 845 846**Possible Causes**<br> 8471. The index is out of range. 8482. The application does not have a clone of the specified index. 8493. The index already exists when you create the clone. 850 851**Solution**<br> 8521. Check whether the index is within the allowed range. 8532. Check whether the application has a clone of the specified index. 8543. Check whether **createAppClone** is called with an existing index. 855 856## 17700062 Failed to Uninstall an Application Configured with an Uninstallation Disposed Rule 857 858**Error Message**<br> 859Failed to uninstall the app because the app has uninstall rule. 860 861**Description**<br> 862The application cannot be directly uninstalled because it is configured with an uninstallation disposed rule. 863 864**Possible Causes**<br> 865The application to uninstall is configured with an uninstallation disposed rule. 866 867**Solution**<br> 868Check whether the application is configured with an uninstallation disposed rule. The entity that set the rule is responsible for handling. 869 870## 17700065 Ability Specified by want in the ShortcutInfo Struct Cannot Be Started 871 872**Error Message**<br> 873The ability specified by want in the ShortcutInfo struct cannot be started. 874 875**Description**<br> 876When the [startShortcut](../apis-ability-kit/js-apis-launcherBundleManager-sys.md#launcherbundlemanagerstartshortcut12) API of the launcherBundleManager module is called, the ability specified by **want** in the **ShortcutInfo** struct fails to start. 877 878**Possible Causes**<br> 879The ability specified by **want** in the **ShortcutInfo** struct does not exist, or the ability specified by **want** in the **ShortcutInfo** struct cannot be started. 880 881**Solution**<br> 882Check the validity of **want** in the **ShortcutInfo** struct. 883 884## 17700066 Failed to Install the Native Software Package 885 886**Error Message**<br> 887Failed to install the HAP because installing the native package failed. 888 889**Description**<br> 890The native software package fails to be installed during HAP installation. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 891 892**Possible Causes**<br>The configuration of the native software package is incorrect. 893 894**Solution**<br>Check the configuration of the native software package. 895 896## 17700067 Failed to Uninstall the Native Software Package 897 898**Error Message**<br> 899Failed to uninstall the HAP because uninstalling the native package failed. 900 901**Description**<br>The native software package fails to be uninstalled during application uninstall. 902 903**Possible Causes**<br>The native software package to be uninstalled is occupied. 904 905**Solution**<br>Check whether any process occupies the native software package. 906 907## 17700069 AppClone Instance Cannot Be Created for an Application in Multi-App Mode Not Set to appClone 908 909**Error Message**<br> 910The app does not support the creation of an appClone instance. 911 912**Description**<br> 913An AppClone instance cannot be created for an application that is not in appClone mode. 914 915**Possible Causes**<br> 916The multi-app mode is set to another mode other than appClone. 917 918**Solution**<br> 919Check whether the application to update supports clones. 920 921## 17700070 Invalid Shortcut ID 922 923**Error Message**<br> 924The specified shortcut id is illegal. 925 926**Description**<br> 927The specified shortcut ID is invalid. 928 929**Possible Causes**<br> 930A shortcut with the same bundle name, clone index, user ID, and shortcut ID already exists, or the passed-in shortcut ID does not exist or is empty. 931 932**Solution**<br> 933Check whether the bundle name and shortcut ID are correct. 934 935## 17700071 Enterprise Applications Cannot Be Installed 936**Error Message**<br> 937It is not allowed to install the enterprise bundle. 938 939**Description**<br> 940It is not allowed to install enterprise applications through a [specific installation API](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstallpreexistingapp12). 941 942**Possible Causes**<br> 943Due to policy control, enterprise applications cannot be installed through the specific API. 944 945**Solution**<br> 946Use the [install](../apis-ability-kit/js-apis-installer-sys.md#bundleinstallerinstall) API instead.<!--DelEnd--> 947 948 949## 17700072 Launch Want Does Not Exist 950**Error Message**<br> 951The launch want is not found. 952 953**Description**<br> 954The launch want does not exist. 955 956**Possible Causes**<br> 957The application does not have an ability, or does not have an ability for which **entities** is set to **entity.system.home** and **actions** is set to **ohos.want.action.home**. 958 959**Solution**<br> 960Configure an ability with **entities** set to **entity.system.home** and **actions** set to **ohos.want.action.home** for the application. 961 962<!--Del--> 963## 17700073 Installation Failure Caused by an Application with the Same Bundle Name but Different Signature Information 964**Error Message**<br> 965Failed to install the HAP because an application with the same bundle name but different signature information exists on the device. 966 967**Description**<br> 968The installation fails because an application with the same bundle name but different signature information exists on the device. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 969 970**Possible Causes**<br> 971 9721. An application with the same bundle name but different signature information exists on the device. 9732. An application with the same bundle name but different signature information has been uninstalled with data retained. 974 975**Solution**<br> 9761. Uninstall the application with the same bundle name. 9772. Install the application that has been uninstalled with data retained, and then uninstall the application without data retained. 978 979## 17700074 Invalid appIdentifier 980 981**Error Message**<br> 982The specified appIdentifier is invalid. 983 984**Description**<br> 985When an API of the [appControl module](../apis-ability-kit/js-apis-appControl-sys.md) is called, the appIdentifier passed in does not exist. 986 987**Possible Causes**<br> 988**appIdentifier** is an empty string. 989 990**Solution**<br> 991Check whether **appIdentifier** is an empty string. 992 993## 17700075 Bundle Name Specified in want Is Inconsistent with That of the Caller 994 995**Error Message**<br> 996The specified bundleName of want is not the same with caller. 997 998**Description**<br> 999When setting an uninstallation disposed rule, the bundle name specified in **want** is different from that of the caller. 1000 1001**Possible Causes**<br> 1002When setting an uninstallation disposed rule, the bundle name specified in **want** is different from that of the caller. 1003 1004**Solution**<br> 1005Change the value of **bundleName** in **want** to be the same as that of the caller. 1006 1007## 17700076 Application Installation Failure Due to Unsupported Distribution Type in the Signing Certificate Profile 1008**Error Message**<br> 1009Failed to install the HAP or HSP because the app distribution type is not allowed. 1010 1011**Description**<br> 1012The application fails to be installed on the device because the distribution type in the signing certificate profile is not supported. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 1013 1014**Possible Causes**<br> 1015The type of the [signing certificate profile](https://developer.huawei.com/consumer/en/doc/app/agc-help-add-releaseprofile-0000001914714796) of the application is not supported on the device. 1016 1017**Solution**<br> 1018Change the type of the signing certificate profile. 1019 1020## 17700077 Application Installation Fails but Preinstallation Is Successful 1021 1022**Error Message**<br> 1023Failed to install the HAP and restore to preinstalled bundle. 1024 1025**Description**<br> 1026If the preinstalled application corresponding to the specified application has been uninstalled, the system first attempts to reinstall the preinstalled application. If the preinstalled application is successfully reinstalled but the specified application fails to install afterward, this error code is reported. When [BundleInstaller.install](js-apis-installer-sys.md#bundleinstallerinstall) throws this error code, an internal error code, for example, [8519687], is added to the error message to pinpoint the reason for the error. 1027 1028**Possible Causes**<br> 1029The version number of the application to be installed is earlier than or the same as the version number of the preinstalled application. 1030 1031**Solution**<br> 10321. Ensure that the version number of the specified application is later than that of the preinstalled application. 10332. Reinstall the specified application. 1034<!--DelEnd--> 1035 1036<!--Del--> 1037## 17700080 Invalid Source Paths 1038 1039**Error Message**<br> 1040The source paths are invalid. 1041 1042**Description**<br> 1043The source paths are invalid. 1044 1045**Possible Causes**<br> 10461. The source path array is empty. 10472. A source path includes the special sequence **../**. 10483. None of the paths can be resolved to the intended location. 1049 1050**Solution**<br> 1051Pass in a valid path that does not include the special sequence **../**. 1052 1053## 17700081 Invalid Destination Path 1054 1055**Error Message**<br> 1056The destination path is invalid. 1057 1058**Description**<br> 1059The destination path is invalid. 1060 1061**Possible Causes**<br> 10621. The destination path is empty. 10632. The destination path includes the special sequence **../**. 10643. The destination path cannot be resolved to the intended location. 1065 1066**Solution**<br> 1067Pass in a valid path that does not include the special sequence **../**. 1068 1069## 17700082 User Authentication Failed 1070 1071**Error Message**<br> 1072User authentication failed. 1073 1074**Description**<br> 1075User authentication fails. 1076 1077**Possible Causes**<br> 10781. The current system does not support user authentication. 10792. The current user has not enabled user authentication. 10803. User authentication information is incorrect or the user cancels authentication. 1081 1082**Solution**<br> 10831. Check whether the current system supports user authentication. If not, the API cannot be used. 10842. Ensure that user authentication is enabled for the current user. 10853. Have the user re-enter accurate authentication details to ensure successful authentication. 1086 1087## 17700083 User Authentication Times Out 1088 1089**Error Message**<br> 1090Waiting for user authentication timeout. 1091 1092**Description**<br> 1093Waiting for user authentication times out. 1094 1095**Possible Causes**<br> 1096The user authentication process exceeds the 5-minute waiting period. 1097 1098**Solution**<br> 1099Ensure that the user completes the authentication process within the allowed time. 1100 1101## 17700084 No Read Permissions for Source Paths 1102 1103**Error Message**<br> 1104There are inaccessible path in the source paths. 1105 1106**Description**<br> 1107Some paths in the source path array lack read permissions. 1108 1109**Possible Causes**<br> 1110Read permissions are not enabled for some source paths. 1111 1112**Solution**<br> 1113Provide a valid path with read permissions enabled. 1114 1115## 17700085 No Write Permissions for the Destination Path 1116 1117**Error Message**<br> 1118The destination path cannot be accessed. 1119 1120**Description**<br> 1121The destination path cannot be accessed. 1122 1123**Possible Causes**<br> 1124Write permissions are not enabled for the destination path. 1125 1126**Solution**<br> 1127Provide a valid path with write permissions enabled. 1128 1129## 17700086 System Error 1130 1131**Error Message**<br> 1132System error occurred during copy execution. 1133 1134**Description**<br> 1135A system error occurred during the copy operation. 1136 1137**Possible Causes**<br> 1138Errors related to file operations occurs, such as insufficient space at the destination or the removal of files from the source path. 1139 1140**Solution**<br> 11411. Ensure that the destination path has sufficient space. 11422. Ensure the files in the source path are still present. 1143 1144## 17700087 Unsupported Plugin Installation 1145 1146**Error Message**<br> 1147Failed to install the plugin because the current device does not support plugins. 1148 1149**Description**<br> 1150The plugin fails to be installed on the current device. 1151 1152**Possible Causes**<br> 1153The device does not have the plugin capability. 1154 1155**Solution**<br> 1156Use the [param tool](../../tools/param-tool.md) to set **const.bms.support_plugin** to **true**, that is, run the **hdc shell param set const.bms.support_plugin true** command. 1157 1158## 17700088 Plugin Installation Failure Due to No Permission 1159 1160**Error Message**<br> 1161Failed to install the plugin because the host application lacks ohos.permission.kernel.SUPPORT_PLUGIN. 1162 1163**Description**<br> 1164The plugin fails to be installed because the application does not have the ohos.permission.kernel.SUPPORT_PLUGIN permission. 1165 1166**Possible Causes**<br> 11671. The application does not have the ohos.permission.kernel.SUPPORT_PLUGIN permission. 11682. The application has requested the permission, but the permission does not take effect. 1169 1170**Solution**<br> 11711. Request the [ohos.permission.kernel.SUPPORT_PLUGIN permission](../../security/AccessToken/restricted-permissions.md#ohospermissionkernelsupport_plugin) by referring to [Declaring Permissions](../../security/AccessToken/declare-permissions.md). 11722. The permission APL is system_basic. If the [application APL](../../security/AccessToken/app-permission-mgmt-overview.md#basic-concepts-in-the-permission-mechanism) is lower than system_basic, request the permission by referring to [Requesting Restricted Permissions](../../security/AccessToken/declare-permissions-in-acl.md). 1173 1174## 17700089 Plugin Installation Failure Because of Plugin ID Parsing Failure 1175 1176**Error Message**<br> 1177Failed to install the plugin because the plugin id fails to be parsed. 1178 1179**Description**<br> 1180The plugin fails to be installed because its ID fails to be parsed. 1181 1182**Possible Causes**<br> 1183The **pluginDistributionIDs** in the signing certificate profile does not conform to the specifications. 1184 1185**Solution**<br> 1186Reconfigure the **app-services-capabilities** field in the [profile](../../security/app-provision-structure.md) as follows: 1187``` 1188"app-services-capabilities":{ 1189 "ohos.permission.kernel.SUPPORT_PLUGIN":{ 1190 "pluginDistributionIDs":"value-1,value-2,···" 1191 } 1192} 1193``` 1194 1195 1196## 17700090 Plugin Installation Failure Because of Plugin ID Verification Failure 1197 1198**Error Message**<br> 1199Failed to install the plugin because the plugin id fails to be verified. 1200 1201**Description**<br> 1202The **pluginDistributionIDs** between the plugin and the application do not share any common values, leading to a failed verification and preventing the plugin from being installed on this application. 1203 1204**Possible Causes**<br> 1205The **pluginDistributionIDs** between the plugin and the application do not share any common values. 1206 1207**Solution**<br> 1208Reconfigure the **pluginDistributionIDs** field in the [profile](../../security/app-provision-structure.md) as follows: 1209``` 1210"app-services-capabilities":{ 1211 "ohos.permission.kernel.SUPPORT_PLUGIN":{ 1212 "pluginDistributionIDs":"value-1,value-2,···" 1213 } 1214} 1215``` 1216 1217## 17700091 Plugin Installation Failure Because of the Same Plugin Name and Host Bundle Name 1218 1219**Error Message**<br> 1220Failed to install the plugin because the plugin name is the same as the host bundle name. 1221 1222**Description**<br> 1223The plugin fails to be installed because the plugin name is the same as the host bundle name. 1224 1225**Possible Causes**<br> 1226The bundle name of the plugin is the same as that of the application. 1227 1228**Solution**<br> 1229Reconfigure the plugin bundle name. 1230 1231## 17700092 Plugin Uninstall Failure Because of Nonexistent Plugin Bundle Name 1232 1233**Error Message**<br> 1234Failed to uninstall the plugin because the specified plugin is not found. 1235 1236**Description**<br> 1237The plugin bundle name does not exist, leading to a failed plugin uninstall. 1238 1239**Possible Causes**<br> 1240The plugin is not installed in the application. 1241 1242**Solution**<br> 1243Run the [bm dump -n command](../../tools/bm-tool.md#dump) to query application information and check whether the plugin is installed. 1244 1245<!--DelEnd--> 1246 1247## 17700101 Bundle Manager Service Abnormal 1248**Error Message**<br> 1249Bundle manager service is excepted. 1250 1251**Description**<br> 1252The Bundle Manager service is abnormal. 1253 1254**Possible Causes**<br> 1255Scenario 1: 1256 1257An unknown system exception occurs. 1258 1259Scenario 2: 1260 1261The system throws an uncaught error code, such as IPC failure or file copy failure. 1262 1263**Solution**<br> 12641. Restart the phone and try again. 1265 12662. If the request still fails after the preceding steps are performed for three to five times, check whether a crash file containing **foundation** exists in the **/data/log/faultlog/faultlogger/** directory of the device. 1267 1268 ``` 1269 hdc shell 1270 cd /data/log/faultlog/faultlogger/ 1271 ls -ls 1272 ``` 1273 12743. Export the crash file and log file and submit them to [online tickets](https://developer.huawei.com/consumer/en/support/feedback/#/) for help. 1275 1276 ``` 1277 hdc file recv /data/log/faultlog/faultlogger/ 1278 hdc file recv /data/log/hilog/ 1279 ``` 1280 1281<!--Del--> 1282## 17700201 .abc File Verification Failure 1283**Error Message**<br> 1284Failed to verify the abc file. 1285 1286**Description**<br> 1287Failed to verify the .abc file. 1288 1289**Possible Causes**<br> 1290The .abc file is untrusted. 1291 1292**Solution**<br> 1293Pass in the path of a trusted .abc file. 1294 1295## 17700202 .abc File Deletion Failure 1296**Error Message**<br> 1297Failed to delete the abc file. 1298 1299**Description**<br> 1300Failed to delete the .abc file. 1301 1302**Possible Causes**<br> 1303The .abc file does not exist. 1304 1305**Solution**<br> 1306Pass in a valid path of the .abc file. 1307 1308## 17700301 Failed to Add Extended Resources 1309**Error Message**<br> 1310Failed to add extended resources. 1311 1312**Description**<br> 1313Failed to add the extended resources. 1314 1315**Possible Causes**<br> 1316The .hsp file does not exist or is untrusted. 1317 1318**Solution**<br> 1319Pass in a correct and trusted .hsp file path. 1320 1321## 17700302 Failed to Delete Extended Resources 1322**Error Message**<br> 1323Failed to remove extended resources. 1324 1325**Description**<br> 1326Failed to delete the extended resources. 1327 1328**Possible Causes**<br> 1329The HSP corresponding to the module name does not exist. 1330 1331**Solution**<br> 1332Pass in a valid module name. 1333 1334## 17700303 Failed to Obtain Extended Resources 1335**Error Message**<br> 1336Failed to obtain extended resources. 1337 1338**Description**<br> 1339Failed to obtain the extended resources. 1340 1341**Possible Causes**<br> 1342The HSP corresponding to the bundle name does not exist. 1343 1344**Solution**<br> 1345Pass in a valid bundle name. 1346 1347## 17700304 Failed to Enable the Dynamic Icon 1348**Error Message**<br> 1349Failed to enable the dynamic icon. 1350 1351**Description**<br> 1352Failed to enable the dynamic icon. 1353 1354**Possible Causes**<br> 1355The HSP does not contain the correct icon resource. 1356 1357**Solution**<br> 1358Before enabling the dynamic icon, ensure that the HSP corresponding to the module name is valid and contains the icon resource. 1359 1360## 17700305 Failed to Disable the Dynamic Icon 1361**Error Message**<br> 1362Failed to disable the dynamic icon. 1363 1364**Description**<br> 1365Failed to disable the dynamic icon. 1366 1367**Possible Causes**<br> 1368The HSP does not contain the correct icon resource. 1369 1370**Solution**<br> 1371Before disabling the dynamic icon, ensure that the HSP corresponding to the bundle name contains the icon resource. 1372 1373## 17700306 Failed to Obtain the Dynamic Icon 1374**Error Message**<br> 1375Failed to obtain the dynamic icon. 1376 1377**Description**<br> 1378Failed to obtain the dynamic icon. 1379 1380**Possible Causes**<br> 1381The HSP does not contain the correct icon resource. 1382 1383**Solution**<br> 1384Before querying the dynamic icon, ensure that the HSP corresponding to the bundle name contains the icon resource. 1385 1386## 17700307 Dynamic Icon Does Not Take Effect Because of a Custom Theme 1387**Error Message**<br> 1388Dynamic icons cannot take effect due to existing custom themes. 1389 1390**Description**<br> 1391Dynamic icons cannot take effect because a custom theme is used. 1392 1393**Possible Causes**<br> 1394The user uses a custom theme (for example, a non-official theme set in the theme application), and the theme package contains icon resources for the corresponding application. When the caller attempts to enable the dynamic icon for the application, it fails and throws the error code 17700307. 1395 1396**Solution**<br> 13971. Check whether the current theme is a custom theme.<br> 13982. Switch to an official theme and retry the API call.<!--DelEnd--> 1399
