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 profile in the HAP is not in JSON format. 1473. Necessary fields are missing in the profile. 148 149**Solution** 1501. Check whether the HAP is in ZIP format. 1512. Check whether the profile 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 profiles 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 Because 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. 2862. 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 Profile Does Not Exist 343 344**Error Message** 345 346Failed to get the profile because the specified profile is not found in the HAP. 347 348**Description** 349 350When an API for querying the profile is called, the profile does not exist. 351 352**Possible Causes** 353 3541. The metadata name passed in the API does not exist in the profile. 3552. The content of the profile is not in JSON format. 3563. The type of the profile to query does not exist. 357 358**Solution** 3591. Check whether the metadata name in the **ability** or **extensionAbility** to be queried exists. 3602. Check whether the content of the profile to be queried is in JSON format. 3613. Check whether the application contains a profile that matches the value of **profileType** passed in. 362 363## 17700025 Invalid Type 364 365**Error Message** 366 367The specified type is invalid. 368 369**Description** 370 371When an API of the **defaultAppManager** module is called, the type passed in is invalid. 372 373**Possible Causes** 3741. The type passed in the API is misspelled. 3752. The type passed in the API does not exist. 376 377**Solution** 3781. Check whether the spelling of type is correct. 3792. Enter a type that exists. 380 381## 17700026 Bundle Disabled 382 383**Error Message** 384 385The specified bundle is disabled. 386 387**Description** 388 389When an API for querying bundle information is called, the specified bundle is disabled. 390 391**Possible Causes** 392 393The bundle on the device has been disabled and cannot be queried. 394 395**Solution** 396 397Check whether the bundle on the device is disabled. 398 399## 17700027 Distributed Service Is Not Started 400 401**Error Message** 402 403The distributed service is not running. 404 405**Description** 406 407When an API of the **distributedBundle** module is called, the distributed service is not started. 408 409**Possible Causes** 410 411The device is not networked. 412 413**Solution** 414 415Check whether the device is networked. 416 417## 17700028 Mismatch Between Ability and Type 418 419**Error Message** 420 421The ability does not match the type. 422 423**Description** 424 425When the **setDefaultApplication** API of the **defaultAppManager** module is called, the **ability** and **type** passed in do not match. 426 427**Possible Causes** 428 429The ability and type are misspelled. 430 431**Solution** 432 433Check whether the spellings of ability and type are correct. 434 435## 17700029 Disabled Ability 436 437**Error Message** 438 439The specified ability is disabled. 440 441**Description** 442 443When an API for querying ability information is called, the specified ability is disabled. 444 445**Possible Causes** 446 447The specified ability is disabled. 448 449**Solution** 450 451Check whether the ability is disabled. You can run the [bm commands](../../../readme/bundle-management.md#bm-commands) to query the information. 452 453## 17700030 Failure in Clearing Cache Files 454 455**Error Message** 456 457The specified bundle does not support clearing of cache files. 458 459**Description** 460 461When the **cleanBundleCacheFiles** API of the **bundleManager** module is called, the specified bundle does not support cache file clearing. 462 463**Possible Causes** 464 465The application is a system application and the **AllowAppDataNotCleared** field is configured in the signing certificate. 466 467**Solution** 4681. 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**. 4692. 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**. 470 471## 17700031 HAP Installation Fails Due to Overlay Feature Verification Failure 472 473**Error Message** 474 475Failed to install the HAP because the overlay check of the HAP is failed. 476 477**Description** 478 479The 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. 480 481**Possible Causes** 4821. 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. 4832. The target application must be a preset application. 4843. The target application cannot be an application with the overlay feature. 4854. The target module cannot be a module with the overlay feature. 486 487**Solution** 4881. Ensure that the application with the overlay feature is a preset application. 4892. Ensure that the target application is a preset application. 4903. Ensure that the target application is not an application with the overlay feature. 4914. Ensure that the target module is not a module with the overlay feature. 492 493## 17700032 Application Does Not Contain a Module with the Overlay Feature 494 495**Error Message** 496 497The specified bundle does not contain any overlay module. 498 499**Description** 500 501An API is called to obtain the **overlayModuleInfo** object of another application, but that application does not contain a module with the overlay feature. 502 503**Possible Causes** 504 505The specified application does not contain a module with the overlay feature. 506 507**Solution** 508 509Check whether the application contains a module with the overlay feature. 510 511## 17700033 Module Is Not Configured with the Overlay Feature 512 513**Error Message** 514 515The specified module is not an overlay module. 516 517**Description** 518 519An API is called to obtain the **overlayModuleInfo** object of a module, but the module is not configured with the overlay feature. 520 521**Possible Causes** 522 523The specified module is not a module with the overlay feature. 524 525**Solution** 526 527Check whether the module is configured with the overlay feature. 528 529## 17700034 Module Is Configured with the Overlay Feature 530 531**Error Message** 532 533The specified module is an overlay module. 534 535**Description** 536 537An API is called to obtain the **overlayModuleInfo** object based on the target module name, but that module is configured with the overlay feature. 538 539**Possible Causes** 540 541The specified module is configured with the overlay feature. 542 543**Solution** 544 545Check whether the specified module is configured with the overlay feature. 546 547## 17700035 Application Contains Only Modules with the Overlay Feature 548 549**Error Message** 550 551The specified bundle is an overlay bundle. 552 553**Description** 554 555An 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. 556 557**Possible Causes** 558 559The specified application contains only modules with the overlay feature. 560 561**Solution** 562 563Check whether the application contains only modules with the overlay feature. 564 565## 17700036 Failure in Installing the Shared Library Because of No AllowAppShareLibrary Privilege 566 567**Error Message** 568 569Failed to install the HSP because lacks appropriate permissions. 570 571**Description** 572 573The shared library is not configured with the **AllowAppShareLibrary** privilege, resulting in security and privacy risks. As a result, the installation fails. 574 575**Possible Causes** 576 577The shared library does not request the **AllowAppShareLibrary** privilege before being released. 578 579**Solution** 580 581Configure the **AllowAppShareLibrary** privilege for the shared library, re-sign the library, and release it. 582 583## 17700037 Failure in Uninstalling the Shared Library Due to Dependency 584 585**Error Message** 586 587The version of shared bundle is dependent on other applications. 588 589**Description** 590 591Other applications depend on the shared library, causing the uninstall to fail. 592 593**Possible Causes** 5941. The version specified during the uninstall is the latest version of the shared library, and the shared library is depended on by other applications. 5952. 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. 596 597**Solution** 5981. Check whether the shared library to uninstall is depended on by other applications. 5992. Check whether the version of the shared library to uninstall is the latest version of the shared library. 600 601## 17700038 Shared Library to Uninstall Does Not Exist 602 603**Error Message** 604 605The specified shared bundle does not exist. 606 607**Description** 608 609The shared library to uninstall does not exist. 610 611**Possible Causes** 6121. The version specified during the uninstall is different from the version of the shared library installed. 6132. The shared library to uninstall is not installed. 614 615**Solution** 6161. Check whether the shared library exists. 6172. Check whether the version of the shared library is the same as that installed. 618 619## 17700039 Failure in Installing an Inter-Application Shared Library 620 621**Error Message** 622 623Failed to install because disallow install a shared bundle by hapFilePaths. 624 625**Description** 626 627During application installation, the installation package passed in is of the inter-application shared library type. 628 629**Possible Causes** 6301. When the Bundle Manager tool is used to install an application, the **-p** parameter is set to the installation package path of an inter-application shared library. 6312. When the **install** API is called to install an application, the **hapFilePaths** parameter is set to the installation package path of an inter-application shared library. 632 633**Solution** 6341. Use the **-s** parameter to specify the installation package path of an inter-application shared library. 6352. Use the **sharedBundleDirPaths** parameter in **installParam** to specify the installation package path of an inter-application shared library. 636 637## 17700040 Failure in Uninstalling an Inter-Application Shared Library 638 639**Error Message** 640 641The specified bundle is a shared bundle which cannot be uninstalled. 642 643**Description** 644 645During application uninstall, the bundle name of an inter-application shared library is passed in. 646 647**Possible Causes** 6481. When the Bundle Manager tool is used to uninstall an application, the **-n** parameter is set to the bundle name of an inter-application shared library. 6492. When the **install** API is called to uninstall an application, the **bundleName** parameter is set to the bundle name of an inter-application shared library. 650 651**Solution** 6521. Use the **-s** parameter to specify the application to be uninstalled as a shared library application. 6532. Use the **bundleName** and **versionCode** parameters in **UninstallParam** to specify the bundle name and version of the shared library to be uninstalled. 654 655## 17700041 Application Installation Is Not Allowed by Enterprise Device Management 656 657**Error Message** 658 659Failed to install because enterprise device management disallow install. 660 661**Description** 662 663The installation of this application is prohibited by enterprise device management. 664 665**Possible Causes** 666 667The enterprise device management does not allow the installation of this application. 668 669**Solution** 670 671Check whether the application installation is prohibited by the enterprise device management. 672 673## 17700042 Incorrect URI in the Data Proxy 674 675**Error Message** 676 677Failed to install the HAP because of incorrect URI in the data proxy. 678 679**Description** 680 681During application installation, the URI of the data proxy is incorrectly configured. 682 683**Possible Causes** 684 6851. The bundle name in the URI is different from that of the current application. 6862. The URI is duplicate. 687 688**Solution** 689 6901. Change the bundle name in the URI to that of the current application. 6912. Change duplicate URIs. Ensure that the URI of each data proxy is unique. 692 693## 17700043 Incorrect Permission Configuration in the Data Proxy 694 695**Error Message** 696 697Failed to install the HAP because of low APL in the non-system data proxy (required APL: system_basic or system_core). 698 699**Description** 700 701During 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**. 702 703**Possible Causes** 704 7051. No permission is configured for the data proxy of a non-system application. 7062. The permission level of the data proxy of a non-system application is too low. 707 708**Solution** 709 7101. Configure the read and write permissions in the data proxy. 7112. Change the read and write permissions in the data proxy and ensure that the permission level is **system_basic** or **system_core**. 712 713## 17700044 Field isolationMode in the HAP Conflicts with the Device Isolation Mode 714 715**Error Message** 716 717Failed to install the HAP because the isolationMode configured is not supported. 718 719**Description** 720 721During application installation, the value of **isolationMode** in the HAP conflicts with the isolation mode of the device. 722 723**Possible Causes** 7241. The device supports the isolation mode (the value of **persist.bms.supportIsolationMode** is **true**), whereas the value of **isolationMode** in the HAP is **nonisolationOnly**. 7252. 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**. 726 727**Solution** 728 729Set the **isolationMode** field in the HAP based on the isolation mode of the device. 730 731## 17700045 Application Uninstall Is Not Allowed by Enterprise Device Management 732 733**Error Message** 734 735Failed to uninstall because enterprise device management disallow uninstall. 736 737**Description** 738 739The uninstall of this application is prohibited by enterprise device management. 740 741**Possible Causes** 742 743The enterprise device management does not allow the uninstall of this application. 744 745**Solution** 746 747Check whether the application uninstall is prohibited by the enterprise device management. 748 749## 17700047 Application Version To Be Updated Is Not Later Than the Current Version 750 751**Error Message** 752 753Failed to install the HAP because the VersionCode to be updated is not greater than the current VersionCode. 754 755**Description** 756 757The version of the application to be updated is not later than the current version. 758 759**Possible Causes** 760 7611. The version number of the application to be updated is earlier than or equal to that of the current version number. 7622. When **installFlag** is set to **NORMAL**, the version number of the application to be updated must be later than the installed version number. 763 764**Solution** 765 7661. Set the version number of the application to be later than the current version number. 7672. If you want to update the application without changing the version number, set **installFlag** to **REPLACE_EXISTING**. 768 769## 17700048 Code Signature Verification Failure 770**Error Message** 771 772Failed to install the HAP because the code signature verification is failed. 773 774**Description** 775 776During application installation, the code signature file of the installation package fails to be verified. 777 778**Possible Causes** 779 7801. The module corresponding to the code signature file does not exist in the installation package. 7812. The path of the code signature file is invalid. 7823. The code signature file does not match the installation package. 783 784**Solution** 785 7861. Ensure that the module corresponding to the code signature file is contained in the installation package. 7872. Provide a valid path of the code signature file. 7883. Use the code signature file that matches the installation package. 789 790## 17700049 Update Failure Because of Incorrect Bundle Name 791 792**Error Message** 793 794Failed to install the HAP because the bundleName is different from the bundleName of the caller application. 795 796**Description** 797 798During the update of an enterprise MDM application, the bundleName passed in is different from that of the caller. 799 800**Possible Causes** 801 802The HAP or HSP to be installed does not belong to the current application. 803 804**Solution** 805 806Ensure that the HAP or HSP to be installed belongs to the current application. 807 808## 17700050 Enterprise Device Verification Failure 809 810**Error Message** 811 812Failed to install the HAP because enterprise normal/MDM bundle cannot be installed on non-enterprise device. 813 814**Description** 815 816Users try to install an enterprise Normal or MDM application on a non-enterprise device. 817 818**Possible Causes** 819 820The device is not an enterprise device. 821 822**Solution** 823 8241. Use an enterprise device. 825 8262. Ensure that **const.bms.allowenterprisebundle** is set to **true**. 827 828## 17700051 Update Failure Because of Incorrect Bundle Name 829 830**Error Message** 831 832Failed to install the HAP because the distribution type of caller application is not enterprise_mdm. 833 834**Description** 835 836During the update of an enterprise MDM application, the distribution type of the caller is not enterprise MDM. 837 838**Possible Causes** 839 840The distribution type of the caller is not enterprise MDM. 841 842**Solution** 843 844Ensure that the signature file of the application is correctly configured. 845 846## 17700052 Installation of Debugging Applications Allowed Only in Developer Mode 847 848**Error Message** 849 850Failed to install the HAP because debug bundle cannot be installed under non-developer mode. 851 852**Description** 853 854A debugging application can be installed only in the developer mode. 855 856**Possible Causes** 857 858The application is a debugging application, but the device is not in developer mode. 859 860**Solution** 861 862Run the **hdc shell param get const.security.developermode.state** command. If **false** is returned, a debugging application cannot be installed on the device. 863 864## 17700053 Not Invoked by AppGallery 865 866**Error Message** 867 868Not app gallery call. 869 870**Description** 871 872This API is called by AppGallery. 873 874**Possible Causes** 875 876The caller is not AppGallery. 877 878**Solution** 879 880Use AppGallery to call the API. 881 882## 17700054 Bundle Installation Failure Due to Permission Verification Failure 883 884**Error Message** 885 886Failed to install the HAP because the HAP requests wrong permissions. 887 888**Description** 889 890The application has applied for an incorrect permission, causing the installation to fail. 891 892**Possible Causes** 893 8941. The application is not an MDM application and has applied for the MDM permission. 8952. The ability privilege level (APL) of the application is lower than the level of the permission that the application has applied for. 896 897**Solution** 898 8991. Check whether the application has applied for the [MDM permission](../../security/AccessToken/permissions-for-mdm-apps.md), which is available only for MDM applications. 9002. Check whether the [permission level](../../security/AccessToken/permissions-for-all.md) is higher than the [application's APL](../../security/app-provision-structure.md#internal-structure-of-the-bundle-info-object). If the application uses the default APL, which is normal, it can require the system_basic or system_core permission only. Change the API in the **UnsgnedDebugProfileTemplate.json** file to **system_basic** or **system_core**, and sign and pack the application again. 901 902## 17700201 .abc File Verification Failure 903 904**Error Message** 905 906Failed to verify abc. 907 908**Description** 909 910Failed to verify the .abc file. 911 912**Possible Causes** 913 914The .abc file is untrusted. 915 916**Solution** 917 918Pass in the path of a trusted .abc file. 919 920## 17700202 .abc File Deletion Failure 921 922**Error Message** 923 924Failed to delete abc. 925 926**Description** 927 928Failed to delete the .abc file. 929 930**Possible Causes** 931 932The .abc file does not exist. 933 934**Solution** 935 936Pass in a valid path of the .abc file. 937