Windows / Modules / storagewmi.dll
storagewmi.dll
WMI Provider for Storage Management
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Description |
|---|---|
| 0x00000002 | There are no drive letters available.%0 |
| 0x00000003 | The operation failed with return code %1!u! %0 |
| 0x00000004 | Discovering provider objects%0 |
| 0x00000005 | The requested name could not be applied to the newly created object.%0 |
| 0x00000006 | %1%0 |
| 0x00000007 | Gathering storage subsystem diagnostic information%0 |
| 0x00000008 | Capturing diagnostic information. This may take time depending on the information being gathered.%0 |
| 0x00000009 | Copying diagnostic file %1%0 |
| 0x0000000A | The operation succeeded with warnings.%0 |
| 0x0000000B | One or more specified parameters are not supported by the target provider in the current version of the subsystem. Unsupported Parameters: %1%0 |
| 0x00000101 | Windows can't check the disk while it's in use. Do you want to check for hard disk errors the next time you start your computer? |
| 0x00000102 | Windows can't check the volume while it's in use. Do you want to dismount this volume first? Note: All opened handles to this volume will become invalid. |
| 0x00000103 | Scanning%0 |
| 0x00000104 | Repairing%0 |
| 0x00000105 | You do not have sufficient rights to check this drive. |
| 0x00000106 | The disk is write protected. |
| 0x00000107 | %1 |
| 0x00000108 | Volume compression was not enabled because it is not supported for the specified file system. |
| 0x00000109 | Modifying short file name support is not supported for the specified file system. |
| 0x0000010A | The specified file system is not supported on the drive. |
| 0x0000010B | Windows cannot format this volume. Close any disk utilities or other programs that are using this volume, and make sure that no window is displaying the contents of the volume. Then try formatting again. |
| 0x0000010C | This disk cannot be quick formatted. |
| 0x0000010D | The volume label is not valid. |
| 0x0000010E | The specified cluster size is too small. |
| 0x0000010F | The specified cluster size is too large. |
| 0x00000110 | The specified volume is too small. |
| 0x00000111 | The specified volume is too large. |
| 0x00000112 | The number of clusters exceeds 32 bits. |
| 0x00000113 | The specified UDF version is not supported. |
| 0x00000114 | The format might take a long time. You should not shut down the computer until the format is complete. |
| 0x00000115 | A hardware error occurred while formatting this disc. You can try again with a different disc, but if this problem persists, using the Live File System on this drive is not recommended. The Mastered option should be used instead. |
| 0x00000116 | Warning, all data on the volume will be lost! |
| 0x00000117 | Access Denied due to insufficient privileges. This utility must be run in elevated mode. |
| 0x00000118 | Windows could not open the volume for direct access. |
| 0x00000119 | Windows could not determine the file system of volume %1. |
| 0x0000011A | Formatting%0 |
| 0x0000011B | Volume integrity was not enabled because it is not supported for the specified file system. |
| 0x0000011C | Creating new volume%0 |
| 0x0000011D | Resizing volume%0 |
| 0x0000011E | Optimizing volume%0 |
| 0x0000011F | Repairing volume%0 |
| 0x00000120 | Formatting volume%0 |
| 0x00000201 | The changes you have requested are not supported on partition %1!u! on disk %2!u! |
| 0x00000202 | This will erase all data on disk %1!u! partition %2!u!. |
| 0x00000203 | This will resize disk %1!u! partition %2!u!. |
| 0x00000204 | This will modify disk %1!u! partition %2!u! which could result in a disruption of services. |
| 0x00000205 | This will remove the access path "%3" from disk %1!u! partition %2!u!. |
| 0x00000301 | This will erase all data on disk %1!u! "%2". |
| 0x00000302 | This will modify disk %1!u! "%2". |
| 0x00000303 | Clearing disk%0 |
| 0x00000304 | Enabling High Availability on disk%0 |
| 0x00000305 | Disabling High Availability on disk%0 |
| 0x00000501 | This will remove the StoragePool "%1". |
| 0x00000502 | Removing a physical disk will cause problems with the fault tolerance capabilities of the following storage pool: "%1". |
| 0x00000503 | An operation was attempted on the primordial storage pool which was not supported. This operation might have succeeded for other objects in the pipeline. |
| 0x00000504 | Creating new storage pool%0 |
| 0x00000505 | Deleting storage pool%0 |
| 0x00000506 | This will upgrade the StoragePool "%1" to the latest version. This is an irreversible action. |
| 0x00000507 | Optimizing storage pool%0 |
| 0x00000601 | This will remove the VirtualDisk "%1" and will erase all of the data that it contains. |
| 0x00000602 | Creating new virtual disk%0 |
| 0x00000603 | Deleting virtual disk%0 |
| 0x00000604 | Showing virtual disk to host system%0 |
| 0x00000605 | Hiding virtual disk from host system%0 |
| 0x00000606 | Creating a virtual disk snapshot%0 |
| 0x00000607 | Creating a virtual disk clone%0 |
| 0x00000608 | Resizing virtual disk%0 |
| 0x00000609 | Repairing virtual disk%0 |
| 0x00000701 | Adding physical disks%0 |
| 0x00000702 | Removing physical disks%0 |
| 0x00000801 | This will remove the InitiatorID with address "%1". |
| 0x00000901 | This will remove the MaskingSet "%1". |
| 0x00000902 | Creating new masking set%0 |
| 0x00000903 | A unique version of the requested masking set already exists%0 |
| 0x00000904 | Deleting masking set%0 |
| 0x00000905 | Adding initiator Id%0 |
| 0x00000906 | Adding target port%0 |
| 0x00000907 | Removing initiator Id%0 |
| 0x00000908 | Removing target port%0 |
| 0x00000909 | Adding virtual disk%0 |
| 0x00000910 | Removing virtual disk%0 |
| 0x00001001 | Resizing storage tier%0 |
| 0x00001002 | Creating new storage tier%0 |
| 0x00001003 | Deleting storage tier%0 |
| 0x00001004 | This will remove the StorageTier "%1". |
| 0x00001101 | Creating new file server%0 |
| 0x00001201 | Creating new file share%0 |
| 0x00001301 | Creating new replication group%0 |
| 0x00001302 | Creating new replication group relationship%0 |
| 0x00007858 | r for Storage Management 0x00000001 There was an error while using the storage provider "%1" with ID "%2". ErrorCode=%3!08lX! |
| 0x00008001 | Thin provisioning is not supported on clustered subsystems.%0 |
| 0x00008002 | A size must be specified for every storage tier specified.%0 |
| 0x00008003 | Thin provisioning is not supported with storage tiers.%0 |
| 0x00008004 | Enclosure aware allocation requires physical disks to be in storage enclosures which support the SES protocol.%0 |
| 0x00008005 | Check if the storage enclosures support the SES protocol.%0 |
| 0x00008006 | Check if the FaultDomainAwareness parameter is set to PhysicalDisk.%0 |
| 0x00008007 | Check if the FaultDomainAwarenessDefault property of the storage pool is set to PhysicalDisk.%0 |
| 0x00008008 | The storage pool does not have sufficient eligible resources for the creation of the specified virtual disk.%0 |
| 0x00008009 | Choose a value for NumberOfColumns that is less than or equal to the number of physical disks in the storage fault domain selected for the virtual disk.%0 |
| 0x00008010 | Add more physical disks to the storage pool.%0 |
| 0x00008011 | The CSVFS_NTFS and CSVFS_ReFS file systems can only be used on cluster subsystems.%0 |
| 0x00008012 | Clustered storage pools must maintain a minimum of 3 physical disks.%0 |
| 0x00008013 | Storage Spaces pools only support a usage of "Other".%0 |
| 0x00008014 | One or more physical disks are not in the specified storage subsystem. Physical Disks: %1%0 |
| 0x00008015 | Other usage information can be set using the "OtherUsageDescription" parameter.%0 |
| 0x00008016 | One or more physical disks encountered an error while creating the storage pool. Physical Disks: %1%0 |
| 0x00008017 | One or more physical disks encountered an error during addition to the storage pool. Physical Disks: %1%0 |
| 0x00008018 | One or more physical disks encountered an error during removal from the storage pool. Physical Disks: %1%0 |
| 0x00008019 | The storage pool does not have sufficient capacity to relocate data from the specified physical disks.%0 |
| 0x00008020 | Free capacity by deleting unneeded virtual disks.%0 |
| 0x00008021 | The Windows Storage Provider does not support shrinking virtual disks.%0 |
| 0x00008022 | This operation cannot be performed with more than %1 physical disks. |
| 0x00008023 | Add/Remove physical disks in batches after the initial operation completes.%0 |
| 0x00008024 | The disk associated with the virtual disk created could not be not found.%0 |
| 0x00008025 | The parameters GptType, IsHidden, and IsDAX cannot be used on an MBR disk.%0 |
| 0x00008026 | The parameters MbrType and IsActive cannot be used on a GPT disk.%0 |
| 0x00008027 | Removable media cannot be set to offline.%0 |
| 0x00008028 | The operation requires that the disk is either RAW or GPT with only MSR partition.%0 |
| 0x00008029 | Clear the disk.%0 |
| 0x00008030 | The partition is already the requested size.%0 |
| 0x00008031 | The volume cannot be extended. The number of clusters will exceed the maximum number of clusters supported by the file system.%0 |
| 0x00008032 | Only the first 2TB are usable on large MBR disks.%0 |
| 0x00008033 | Convert the disk to a GPT layout in order to use capacity beyond 2TB.%0 |
| 0x00008034 | The size of the extent is less than the minimum of 1MB.%0 |
| 0x00008035 | The specified shrink size is too big and will cause the volume to be smaller than the minimum volume size.%0 |
| 0x00008036 | The specified shrink size is less than then minimum shrink size allowed.%0 |
| 0x00008037 | One or more physical disks encountered an error when gathering information on node %1. Physical Disks: %2%0 |
| 0x00008038 | Check connectivity to the physical disks. |
| 0x00008039 | Enable Storage Spaces Direct if using local storage.%0 |
| 0x00008040 | Cluster shared volume does not support drive letter.%0 |
| 0x00008041 | Use mount point.%0 |
| 0x00008042 | A warning or error has been encountered during storage firmware update. %1%0 |
| 0x00008043 | One or more physical disks host data for virtual disks that are either Simple or have lost redundancy. Physical Disks: %1%0 |
| 0x00008044 | Attach all associated virtual disks.%0 |
| 0x00008045 | Repair associated virtual disks that have lost their redundancy.%0 |
| 0x00008046 | To continue with the operation use the 'IgnoreDetachedVirtualDisks' parameter. The associated virtual disks may be unable to attach until maintenance mode is disabled on these physical disks.%0 |
| 0x00008047 | Check if you have the necessary privileges to perform the operation.%0 |
| 0x00008048 | Perform the operation from Failover Cluster Manager if the resource is clustered.%0 |
| 0x00008049 | The storage node name needs to be specified.%0 |
| 0x00008050 | Choose a combination of FaultDomainAwareness and NumberOfDataCopies (or PhysicalDiskRedundancy) supported by the storage pool.%0 |
| 0x00008051 | The virtual disk has lost data and cannot repair.%0 |
| 0x00008052 | One or more physical disks encountered an error while repairing the virtual disk. Physical Disks: %1%0 |
| 0x00008053 | The storage pool could not relocate data from one or more physical disks. Physical Disks: %1%0 |
| 0x00008054 | One or more physical disks host data for virtual disks that are detached. Physical Disks: %1%0 |
| 0x00008055 | One or more physical disks are in the Primordial storage pool for which the operation is not supported. The operation might have succeeded for physical disks in a concrete storage pool.%0 |
| 0x00008056 | One or more physical disks host data for virtual disks that have a lower fault domain awareness than the fault domain object specified. Physical Disks: %1%0 |
| 0x00008057 | The physical disk must be in maintenance mode to perform this operation.%0 |
| 0x00008058 | One or more virtual disks are not healthy. Virtual Disks: %1%0 |
| 0x00008059 | To continue with the operation do not use the 'VirtualDisksHealthy' flag. The associated virtual disks may be at a greater risk of becoming unavailable.%0 |
| 0x00008060 | The specified storage fault domain object does not support maintenance mode.%0 |
| 0x00008061 | One or more physical disks encountered an error while enabling maintenance mode. Physical Disks: %1%0 |
| 0x00008062 | Check physical disk compatibility if using Storage Spaces Direct.%0 |
| 0x00008063 | Detach associated virtual disks to offline data on them and retry the operation with the 'IgnoreDetachedVirtualDisks' parameter. The virtual disks may be unable to attach until maintenance mode is disabled on these physical disks.%0 |
| 0x00008064 | The cluster health resource was not found. This method requires the cluster health resource to be present.%0 |
| 0x00008065 | SBL failed to start the operation to change the disk write cache. Physical disks: %1%0 |
| 0x00008066 | SBL failed to change the disk write cache operation mode. Physical disks: %1%0 |
| 0x00008067 | The file system on the volume is not supported for reports.%0 |
| 0x00008068 | No faults were found for the monitoring object.%0 |
| 0x00008069 | The report count must be a value between 1 and 300.%0 |
| 0x00008070 | The operational status of the volume is not online. The volume must be online to gather reports.%0 |
| 0x05200000 | The operation was successful |
| 0x05300000 | Success |
| 0x05301000 | Method Parameters Checked - Job Started |
| 0x50000002 | Error |
| 0x50000004 | Information |
| 0x85200001 | A general error occurred, not covered by a more specific error code. |
| 0x85200002 | Access to a CIM resource is not available to the client. |
| 0x85200003 | The target namespace does not exist. |
| 0x85200004 | One or more parameter values passed to the method are not valid. |
| 0x85200005 | The specified class does not exist. |
| 0x85200006 | The requested object cannot be found. |
| 0x85200007 | The requested operation is not supported. |
| 0x85200008 | The operation cannot be invoked because the class has subclasses. |
| 0x85200009 | The operation cannot be invoked because the class has instances. |
| 0x8520000A | The operation cannot be invoked because the superclass does not exist. |
| 0x8520000B | The operation cannot be invoked because an object already exists. |
| 0x8520000C | The specified property does not exist. |
| 0x8520000D | The value supplied is not compatible with the type. |
| 0x8520000E | The query language is not recognized or supported. |
| 0x8520000F | The query is not valid for the specified query language. |
| 0x85200010 | The extrinsic method cannot be invoked. |
| 0x85200011 | The specified extrinsic method does not exist. |
| 0x85200014 | The specified namespace is not empty. |
| 0x85200015 | The enumeration identified by the specified context is invalid. |
| 0x85200016 | The specified operation timeout is not supported by the CIM Server. |
| 0x85200017 | The Pull operation has been abandoned. |
| 0x85200018 | The attempt to abandon a concurrent Pull operation failed. |
| 0x85200019 | Using a filter in the enumeration is not supported by the CIM server. |
| 0x8520001A | The CIM server does not support continuation on error. |
| 0x8520001B | The operation failed because server limits were exceeded. |
| 0x8520001C | The CIM server is shutting down and cannot process the operation. |
| 0x85300001 | Not Supported |
| 0x85300002 | Unknown Error |
| 0x85300003 | Timeout |
| 0x85300004 | Failed |
| 0x85300005 | Invalid Parameter |
| 0x85300006 | In Use |
| 0x85300007 | This operation is not supported on x86 running in x64 environment |
| 0x85300008 | Object Not Found |
| 0x85301001 | Size not supported |
| 0x85301002 | Timeout not supported |
| 0x85301003 | The device is busy |
| 0x85301004 | Job terminated |
| 0x85309C40 | Not enough available capacity |
| 0x85309C41 | Access Denied |
| 0x85309C42 | There are not enough resources to complete the operation. |
| 0x85309C43 | Cache out of date |
| 0x85309C44 | An unexpected I/O error has occured |
| 0x85309C45 | You must specify a size by using either the Size or the UseMaximumSize parameter. You can specify only one of these parameters at a time. |
| 0x85309C46 | The object or object type requested does not exist in cache. |
| 0x85309C47 | The request failed due to a fatal device hardware error. |
| 0x85309C48 | The destination path is not accessible. |
| 0x85309C49 | The operation is not supported while the cluster is being upgraded. |
| 0x85309C4A | The operation is not supported on cluster. |
| 0x85309C4B | You must specify a size by using the Size parameter. |
| 0x85309C4C | You may specify a write cache size by using either the WriteCacheSize or AutoWriteCacheSize parameter, but not both. |
| 0x85309C4D | Relative paths are not supported. |
| 0x85309C4E | You must specify the enclosure awareness (either the IsEnclosureAware or EnclosureAwareDefault parameter) or the fault domain awareness (either the FaultDomainAwareness or FaultDomainAwarenessDefault parameter), but not both. |
| 0x85309C4F | The provider does not support a value for fault domain awareness other than physical disk or storage enclosure. |
| 0x85309C50 | The provider does not support the fault domain awareness parameter. |
| 0x85309C51 | Unable to create the destination path. |
| 0x85309C52 | Unable to capture a live dump of the storage subsystem. |
| 0x85309C53 | Unable to gather the operational log of the storage subsystem. |
| 0x85309C54 | One or more files failed to copy. |
| 0x85309C55 | The diagnostic log has already been started for this storage subsystem. |
| 0x85309C56 | No diagnostic logs were enabled for this storage subsystem. |
| 0x85309C57 | Exceeded the number of trace sessions that can enable the provider. |
| 0x85309C58 | The provider does not support the allocation unit size parameter. |
| 0x85309C59 | This combination of parameters is unsupported. |
| 0x85309C5A | One or more storage devices are unresponsive. |
| 0x8530A028 | The disk has not been initialized. |
| 0x8530A029 | The disk has already been initialized. |
| 0x8530A02A | The disk is read only. |
| 0x8530A02B | The disk is offline. |
| 0x8530A02C | The disk's partition limit has been reached. |
| 0x8530A02D | The specified partition alignment is not valid. It must be a multiple of the disk's sector size. |
| 0x8530A02E | A parameter is not valid for this type of partition |
| 0x8530A02F | Cannot clear with OEM partitions present. To clear OEM partitions, use the RemoveOEM flag. |
| 0x8530A030 | Cannot clear with data partitions present. To clear data partitions, use the RemoveData flag. |
| 0x8530A031 | Operation not supported on a critical disk. |
| 0x8530A032 | The specified partition type is not valid. |
| 0x8530A033 | Only the first 2 TB are usable on MBR disks. |
| 0x8530A034 | The specified offset is not valid. |
| 0x8530A035 | Cannot convert the style of a disk with data or other known partitions on it. |
| 0x8530A036 | The disk is not large enough to support a GPT partition style. |
| 0x8530A037 | There is no media in the device. |
| 0x8530A038 | Operation not supported on a non-empty removable disk. |
| 0x8530A039 | The specified partition layout is invalid. |
| 0x8530A03A | The specified object is managed by the Microsoft Failover Clustering component. The disk must be in cluster maintenance mode and the cluster resource status must be online to perform this operation. |
| 0x8530A03B | The specified object is managed by the Microsoft Failover Clustering component. The disk must be removed from the cluster to perform this operation. |
| 0x8530A03C | High Availability could not be enabled for this storage object. |
| 0x8530A03D | Scale Out could not be enabled for this storage object. |
| 0x8530A03E | High Availability could not be disabled for this storage object. |
| 0x8530A03F | Scale Out could not be disabled for this storage object. |
| 0x8530A410 | The partition was deleted, although its access paths were not. |
| 0x8530A411 | The extended partition still contains other partitions. |
| 0x8530A412 | The requested access path is already in use. |
| 0x8530A414 | Cannot assign access paths to hidden partitions. |
| 0x8530A415 | Cannot remove a volume GUID path. |
| 0x8530A416 | Cannot remove the drive letter of a boot or paging file partition. |
| 0x8530A417 | The access path is not valid. |
| 0x8530A418 | Cannot shrink a partition containing a volume with errors. |
| 0x8530A419 | Cannot resize a partition containing an unknown file system. |
| 0x8530A41A | The operation is not allowed on a system or critical partition. |
| 0x8530A41B | This operation is only supported on data partitions. |
| 0x8530A41C | Cannot assign multiple drive letters to a partition. |
| 0x8530A41D | Cannot assign drive letter to this type of partition. |
| 0x8530A41E | The volume still has access path to it. |
| 0x8530A7F8 | The specified cluster size is invalid. |
| 0x8530A7F9 | The specified file system is not supported. |
| 0x8530A7FA | The volume cannot be quick formatted. |
| 0x8530A7FB | The number of clusters exceeds 32 bits. |
| 0x8530A7FC | The specified UDF version is not supported. |
| 0x8530A7FD | The cluster size must be a multiple of the disk's physical sector size. |
| 0x8530A7FE | Cannot perform the requested operation when the drive is read only. |
| 0x8530A7FF | The repair failed. |
| 0x8530A800 | The scan failed. |
| 0x8530A801 | A snapshot error occurred while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix. |
| 0x8530A802 | A scan is already running on this drive. Chkdsk can not run more than one scan on a drive at a time. |
| 0x8530A803 | A snapshot error occurred while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix. |
| 0x8530A804 | A snapshot error occurred while scanning this drive. Run an offline scan and fix. |
| 0x8530A805 | Cannot open drive for direct access. |
| 0x8530A806 | Cannot determine the file system of the drive. |
| 0x8530A807 | This setting may not be changed due to the group policy setting. |
| 0x8530A808 | This setting may not be changed due to the global registry setting. |
| 0x8530A809 | You must specify a name for this volume. |
| 0x8530A80A | You must specify a file server to expose this volume to. |
| 0x8530A80B | The volume is not exposed to the specified file server. |
| 0x8530A80C | Deduplication feature is not available. |
| 0x8530A80D | Deduplication is not enabled for the volume. |
| 0x8530A80E | The volume optimization operation requested is not supported by the hardware backing the volume. |
| 0x8530A80F | Volume optimization was unable to complete because the disk backing the volume is full. |
| 0x8530A810 | Another volume optimization operation is currently in progress on the volume. |
| 0x8530A811 | This volume cannot be optimized. |
| 0x8530A812 | The volume to be optimized is corrupted. |
| 0x8530A813 | The user cancelled the operation. |
| 0x8530A814 | A file on the disk could not be opened. |
| 0x8530A815 | Volume optimization aborted because the storage slab size changed while performing the operation. |
| 0x8530A816 | Slab size is too small. |
| 0x8530A817 | The volume alignment is invalid for the slab consolidation/trim operation requested. |
| 0x8530A818 | The storage optimizer could not continue because the file system's master file table is too fragmented. |
| 0x8530A819 | Read cache is only supported by the ReFS filesystem. |
| 0x8530A81A | Starting offset of the thinly provisioned or DAX partition is not aligned to a cluster boundary. |
| 0x8530B3B0 | Cannot connect to the storage provider. |
| 0x8530B3B1 | The storage provider cannot connect to the storage subsystem. |
| 0x8530B3B2 | The storage provider does not support a required profile. |
| 0x8530B3B3 | The storage provider does not support a required association. |
| 0x8530B3B4 | Cannot register/unregister the storage subsystem on local host. |
| 0x8530B3B5 | The storage subsystem is not registered. |
| 0x8530B3B6 | This subsystem is already registered. |
| 0x8530B3B7 | This subsystem is already registered with another user's credentials. Use the -Force flag to remove the existing registration and add a new one anyway. |
| 0x8530B3B8 | Failover clustering could not be enabled for this storage object. |
| 0x8530B3B9 | Discover failed for the root object. |
| 0x8530B3BA | Discover failed on one or more subsystems. |
| 0x8530B3BB | Failover clustering was enabled for the storage object but it failed to come online. |
| 0x8530B3BC | Failed to offline the storage object in Failover clustering. |
| 0x8530B798 | No storage pools were found that can support this virtual disk configuration. |
| 0x8530B799 | This subsystem does not support creation of virtual disks with the specified provisioning type. |
| 0x8530B79A | The operation could not be completed because the associated subsystem has stopped functioning. |
| 0x8530BB80 | This operation is not supported on primordial storage pools. |
| 0x8530BB81 | The storage pool is reserved for special usage only. |
| 0x8530BB82 | The specified resiliency setting is not supported by this storage pool. |
| 0x8530BB84 | There are not enough eligible physical disks in the storage pool to create the specified virtual disk configuration. |
| 0x8530BB85 | The specified storage pool could not be found. |
| 0x8530BB86 | The storage pool could not complete the operation because its health or operational status does not permit it. |
| 0x8530BB87 | The storage pool could not complete the operation because its configuration is read-only. |
| 0x8530BB88 | The storage pool contains virtual disks. |
| 0x8530BB89 | The number of thin provisioning alert thresholds specified exceeds the limit for this storage pool. |
| 0x8530BB8A | You must specify the size info (either the Size or UseMaximumSize parameter) or the tier info (the StorageTiers and StorageTierSizes parameters), but not both size info and tier info. |
| 0x8530BB8B | The storage pool could not complete the operation because the health or operational status of one or more virtual disks in it does not permit it. |
| 0x8530BB8C | You must specify the FileSystem parameter. |
| 0x8530BB8D | This storage pool does not support the creation of tiered virtual disks with custom allocation unit sizes. |
| 0x8530BF68 | No resiliency setting with that name exists. |
| 0x8530BF69 | The value for NoSinglePointOfFailure is not supported. |
| 0x8530BF6A | The value for PhysicalDiskRedundancy is outside of the supported range of values. |
| 0x8530BF6B | The value for NumberOfDataCopies is outside of the supported range of values. |
| 0x8530BF6C | The value for ParityLayout is outside of the supported range of values. |
| 0x8530BF6D | The value for Interleave is outside of the supported range of values. |
| 0x8530BF6E | The value for NumberOfColumns is outside of the supported range of values. |
| 0x8530BF6F | The value for NumberOfGroups is outside of the supported range of values. |
| 0x8530C350 | The specified virtual disk could not be found. |
| 0x8530C351 | Could not repair the virtual disk because too many physical disks failed. Not enough information exists on the remaining physical disks to reconstruct the lost data. |
| 0x8530C352 | The virtual disk could not complete the operation because another computer controls its configuration. |
| 0x8530C353 | The virtual disk could not complete the operation because its health or operational status does not permit it. |
| 0x8530C354 | The virtual disk could not complete the operation because its Manual Attach status does not permit it. |
| 0x8530C355 | The value for WriteCacheSize is outside of the supported range of values. |
| 0x8530C356 | The virtual disk could not complete the operation because it is in cluster maintenance mode. |
| 0x8530C357 | The value for ReadCacheSize is outside of the supported range of values. |
| 0x8530C358 | Could not attach the virtual disk because too many physical disks have failed or gone missing. |
| 0x8530C359 | The virtual disk repair operation encountered failures. |
| 0x8530C738 | One or more physical disks are not supported by this operation. |
| 0x8530C739 | Not enough physical disks were specified to successfully complete the operation. |
| 0x8530C73A | One or more physical disks are already in use. |
| 0x8530C73B | One or more physical disks use a sector size that is not supported by this storage pool. |
| 0x8530C73C | One or more physical disks could not be removed because they are still in use. |
| 0x8530C73D | One or more physical disks are not connected to the nodes on which the pool is being created. |
| 0x8530C73E | One or more physical disks are not in the pool. |
| 0x8530C73F | One or more physical disks could not be removed. The policy on this storage pool requires a minimum number of physical disks to remain present. |
| 0x8530CB20 | The device number specified is not valid. |
| 0x8530CB21 | The HostType requested is not supported. |
| 0x8530CB22 | DeviceAccess must be specified for each virtual disk. |
| 0x8530CF08 | The initiator address specified is not valid. |
| 0x8530CF09 | Only one initiator address is acceptable for this operation. |
| 0x8530D2F0 | The target port address specified is not valid. |
| 0x8530D6D8 | One or more slot numbers provided are not valid. |
| 0x8530D6D9 | The enclosure does not support identification of the enclosure element. |
| 0x8530D6DA | The given page number has not been implemented. |
| 0x8530DAC0 | The specified volume does not support storage tiers. |
| 0x8530DAC1 | The Storage Tiers Management service detected that the specified volume is in the process of being dismounted. |
| 0x8530DAC2 | The file identifier specified is not valid on the volume. |
| 0x8530DAC3 | Storage tier operations must be called on the clustering node that owns the metadata volume. |
| 0x8530DAC4 | The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid. |
| 0x8530DAC5 | The Storage Tiers Management service is already optimizing the storage tiers on the specified volume. |
| 0x8530DAC6 | The requested object type cannot be assigned to a storage tier. |
| 0x8530DEA8 | No extended status object was found for the storage job. |
| 0x8530E290 | You must specify a name for this file share. |
| 0x8530E291 | You must specify a sharing protocol for this file share. |
| 0x8530E292 | You must specify a volume for this file share. |
| 0x8530E293 | At least one account name needs to be specified. |
| 0x8530E294 | You must specify an access right. |
| 0x8530E295 | The specified user account could not be found. |
| 0x8530E678 | Failed to communicate with cluster health resource. |
| 0x8530E679 | Method not supported in this subsystem. |
| 0x8530E67A | You must specify a name. |
| 0x8530E67B | The name specified is invalid. |
| 0x8530E67C | You must specify a value. |
| 0x8530E67D | The value specified is invalid. |
| 0x8530E67E | The Storage Health is not online. |
| 0x8530E67F | The Storage Object is not supported for report. |
| 0x8530EE48 | The specified ProvisioningType is not supported. |
| 0x8530EE49 | The value for AllocationUnitSize must be a multiple of 256 MB. |
| 0x8530EE4A | The specified FaultDomainAwareness, ColumnIsolation, or both are not valid. |
| 0x90000001 | Microsoft-Windows-StorageManagement |
| 0xB0000001 | %1 %2(%3) |
| 0xB0000002 | %1 %2 %3(%4) |
| 0xB0000004 | An error has occurred during method execution. Class:%t%t%1 Method:%t%t%2 Error Code:%t%3 Error Message: %4 |
| 0xB0000005 | An error has occurred during method execution. Class:%t%t%1 Method:%t%t%2 Error Code:%t%3 |
| 0xB0000006 | The Windows Storage Provider host service failed to start. Error Code: %1 |
| 398 entries | |