Windows / Modules / mispace.dll

mispace.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x18.11011Data is striped across physical disks, maximizing capacity and increasing throughput, but decreasing reliability. This storage layout requires at least one disk and does not protect you from a disk failure.
0x21011Data is striped across physical disks, creating two or three copies of your data. This increases reliability, but reduces capacity. To protect against a single disk failure, use at least two disks (three if you're using a cluster); to protect against two disk failures, use at least five disks.
0x31011Data and parity information are striped across physical disks, increasing reliability, but somewhat reducing capacity and performance. To protect against a single disk failure, use at least three disks; to protect against two disk failures, use at least seven disks.
0x48.11011%1: Could not connect to subsystem "%2" on host "%3". Please check the credentials used and if this subsystem requires elevation.
0x58.11011%1: An error was encountered while enumerating objects from subsystem "%2" on host "%3". Error encountered was %4 = "%6" (%5!u!).
0x68.11011%1: An error was encountered while enumerating storage nodes or child objects for host %2. Error encountered was %3 = "%5" (%4!u!).
0x78.11011%1: An error was encountered while enumerating storage nodes or child objects because it requires elevation.
0x88.11011%1: An error was encountered while enumerating masking sets or child objects for host %2. Error encountered was %3 = "%5" (%4!u!).
0x98.11011%1: An error was encountered while enumerating masking sets or child objects because it requires elevation.
0xa8.11011%1: An error was encountered while enumerating initiator ids or child objects for host %2. Error encountered was %3 = "%5" (%4!u!).
0xb8.11011%1: An error was encountered while enumerating initiator ids or child objects because it requires elevation.
0xc8.11011Cache out of date
0xd8.11011The access path that you provided was not applied to the CSV.
0x1011011Windows 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?
0x1021011Windows 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.
0x1031011Scanning
0x1041011Repairing
0x1051011You do not have sufficient rights to check this drive.
0x1061011The disk is write protected.
0x1071011%1
0x1081011Volume compression was not enabled because it is not supported for the specified file system.
0x1091011Modifying short file name support is not supported for the specified file system.
0x10a1011The specified file system is not supported on the drive.
0x10b1011Windows 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.
0x10c1011This disk cannot be quick formatted.
0x10d1011The volume label is not valid.
0x10e1011The specified cluster size is too small.
0x10f1011The specified cluster size is too large.
0x1101011The specified volume is too small.
0x1111011The specified volume is too large.
0x1121011The number of clusters exceeds 32 bits.
0x1131011The specified UDF version is not supported.
0x1141011The format might take a long time. You should not shut down the computer until the format is complete.
0x1151011A 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.
0x1161011Warning, all data on the volume will be lost!
0x1171011Access Denied due to insufficient privileges. This utility must be run in elevated mode.
0x1181011Windows could not open the volume for direct access.
0x1191011Windows could not determine the file system of volume %1.
0x11a1011Formatting
0x11b1011Volume integrity was not enabled because it is not supported for the specified file system.
0x11c1011Creating new volume
0x11d1011Resizing volume
0x2011011%1: No objects are returned from a subsystem on host "%2" because that subsystem doesn't support this type of object. Subsystem: "%3".
0x2021011%1: No objects are returned from a subsystem on host "%2" because that subsystem doesn't support remotely working with this type of object. Subsystem: "%3".
0x3001011Unable to retrieve stored credentials for subsystem %1 [%2]. >>>> Primary error = 0x%3!x!; Secondary error = 0x%4!x!
0x3011011Unable to impersonate the stored user %1 to access subsystem %2 [%3]. >>>> Primary error = 0x%4!x!; Secondary error = 0x%5!x!
0x3021011Unable to establish a connection to computer %1. >>>> Primary error = 0x%2!x!; Secondary error = 0x%3!x!
0x3031011Unable to capture diagnostic info for computer %1. >>>> Primary error = 0x%2!x!; Secondary error = 0x%3!x!
0x3041011Unable to clean up temporary diagnostic files on computer %1. >>>> Primary error = 0x%2!x!; Secondary error = 0x%3!x!
0x3051011Failed to start traces on computer %1. >>>> Primary error = 0x%2!x!; Secondary error = 0x%3!x!
0x3061011Failed to stop traces on computer %1. >>>> Primary error = 0x%2!x!; Secondary error = 0x%3!x!
0x3071011Unable to copy diagnostic file for computer %1. >>>> Source [%2]; >>>> Destination [%3]; >>>> Primary error = 0x%4!x!; Secondary error = 0x%5!x!
0x500000021011Error
0x500000031011Warning
0x500000041011Information
0x5100000110Critical
0x900000011011Microsoft-Windows-StorageManagement-WSP-Spaces
0x910000011011Microsoft-Windows-StorageManagement-WSP-Host
0xb00007d010The Windows Storage Provider could not start the remote storage subsystem. Storage Subsystem ID: %1 Storage Subsystem URI: %2 Username: %3 Error Code: %4 Error String: %5 Ensure that the remote storage subsystem is online and connected to the network. Check if the user attempting to connect to the subsystem has the necessary permissions.
0xb00007d110The Windows Storage Provider has lost its connection to the cluster. Error Code: %1
0xb00007d210The Windows Storage Provider has established a connection to the cluster.
0xb00007d310An error occurred during method execution. Class: %1 Method: %2 ObjectId: %3 Error Code: %4
0xb00007d410An error was posted by the Windows Storage Provider during the course of an operation. Message: %1
0xb00007d510An error occurred during storage job execution. Job Name: %1 Error Code: %2
0xb00007d610An error occurred during a get instance operation. Class: %1 ObjectId: %2 Error Code: %3
0xb00007d710An error occurred during object enumeration. Class: %1 Error Code: %2
0xb00007d810An error occurred during method execution. Class: %1 Method: %2 ObjectId: %3 MI_Result: %4
0xb00007d910An error occurred while trying to perform a diagnostic operation. Computer name: %1 Error Code: %2 Secondary Error: %3
0xb00107da10The Windows Storage Spaces and Disk provider was loaded. Load time (milliseconds): %1 Miresult: %2
0xb00107db10Cluster state initialization succeeded. Cluster name: %1
0xb00107dc10Cluster state initialization failed. Cluster Name: %1 Initialization Phase: %2 HRESULT: %3
0xb00107dd10Cluster node arrived. Node: %1 Node State: %2
0xb00107de1011Cluster node %1 was deleted.
0xb00107df1011Cluster node %1 came online.
0xb00107e01011Cluster node %1 went offline.
0xb00107e110It took longer than usual for this target node to respond to the following control code. Control Code: %1 (%2) Response time (milliseconds): %3
0xb00107e210It took longer than usual for this initiator node to complete the following control code. Control Code: %1 (%2) Complete time (milliseconds): %3
0xb00107e310One or more nodes did not respond to the cluster broadcast. Control Code: %1 (%2) Nodes: %3 Unresponsive Nodes: %4
0xb10003e810A Windows Storage Provider failed to load. Provider: %1 Provider DLL: %2 Error Code: %3 Load Phase: %4 This failure is indicative of a bad installation, or a missing or corrupt DLL.
0xd00000011011Open connection to cluster
0xd00000021011Get cluster FQDN
0xd00000031011Get computer name
0xd00000041011Open handle to local cluster node
0xd00000051011Get local cluster node ID
0xd00000061011Read cluster registry key SpacesSubSystemAutomaticClusteringEnabled
0xd00000071011Read cluster registry key RepairQueueDepth
0xd00000081011Read cluster registry key FDAwarenessDefault
0xd00000091011Read cluster registry key S2DEnabled
0xd000000a1011Load cluster message pipe
0xd000000b1011Load cluster APIs
0xd000000c1011Enumerate cluster nodes
0xd000000d1011Unknown
0xd000000e1011Up
0xd000000f1011Down
0xd00000101011Joining
0xd00000111011Paused
0xd10000011011Loading DLL
0xd100000210Find ShutdownCallback
0xd100000310Find WMI Entrypoint
0xd100000410Launch Hosted Provider
0xb00107d011The Windows Storage Provider could not start the remote storage subsystem. Storage Subsystem ID: %1 Storage Subsystem URI: %2 Username: %3 Error Code: %4 Error String: %5 Ensure that the remote storage subsystem is online and connected to the network. Check if the user attempting to connect to the subsystem has the necessary permissions.
0xb00107d111The Windows Storage Provider has lost its connection to the cluster. Error Code: %1
0xb00107d211The Windows Storage Provider has established a connection to the cluster.
0xb00107d311An error occurred during method execution. Class: %1 Method: %2 ObjectId: %3 Error Code: %4
0xb00107d411An error was posted by the Windows Storage Provider during the course of an operation. Message: %1
0xb00107d511An error occurred during storage job execution. Job Name: %1 Error Code: %2
0xb00107d611An error occurred during a get instance operation. Class: %1 ObjectId: %2 Error Code: %3
0xb00107d711An error occurred during object enumeration. Class: %1 Error Code: %2
0xb00107d811An error occurred during method execution. Class: %1 Method: %2 ObjectId: %3 MI_Result: %4
0xb00107d911An error occurred while trying to perform a diagnostic operation. Computer name: %1 Error Code: %2 Secondary Error: %3
0xb00107da11The Windows Storage Spaces and Disk provider was loaded. Load time (milliseconds): %1 Miresult: %2
0xb00107db11Cluster state initialization succeeded. Cluster name: %1
0xb00107dc11Cluster state initialization failed. Cluster Name: %1 Initialization Phase: %2 HRESULT: %3
0xb00107dd11Cluster node arrived. Node: %1 Node State: %2
0xb00107e111It took longer than usual for this target node to respond to the following control code. Control Code: %1 (%2) Response time (milliseconds): %3
0xb00107e211It took longer than usual for this initiator node to complete the following control code. Control Code: %1 (%2) Complete time (milliseconds): %3
0xb00107e311One or more nodes did not respond to the cluster broadcast. Control Code: %1 (%2) Nodes: %3 Unresponsive Nodes: %4
0xb00107e411An unmapped error was encountered. Function: %1 HResult: %2 MI_Result: %3
0xb00107e511It is taking longer than usual for this target node to respond to the following control code. Control Code: %1 (%2)
0xb00107e611It is taking longer than usual for this initiator node to complete the following control code. Control Code: %1 (%2)
0xb00107e711Successfully initialized the Storage Management Provider. Function: %1 Duration (milliseconds): %2
0xb00107e811Failed to initialize the Storage Management Provider. Function: %1 Callee: %2 MI_Result: %3
0xb00107e911Successfully cleaned up the Storage Management Provider. Function: %1 Duration (milliseconds): %2
0xb00107ea11Failed to clean up the Storage Management Provider. Function: %1 Callee: %2 MI_Result: %3
0xb00107eb11Successfully initialized Extended Storage Spaces API. Function: %1 Duration (milliseconds): %2
0xb00107ec11Failed to initialize Extended Storage Spaces API. Function: %1 Callee: %2 Error: %3
0xb00107ed11Successfully cleaned up Extended Storage Spaces API. Function: %1 Duration (milliseconds): %2
0xb00107ee11Failed to clean up Extended Storage Spaces API. Function: %1 Callee: %2 Error: %3
0xb00107ef11Successfully Converted PhysicalDisk to Space. Function: %1 Duration (milliseconds): %2 DriveId: %3 PoolName: %4 PoolVersion: %5 PoolMetadataLength: %6 PoolMinimumAllocationSize: %7 SpaceName: %8 SpaceProvisioningType: %9 SpaceAllocationSize: %10 SpaceResiliencyType: %11 MinimumFreeSizeRequired: %12
0xb00107f011Failed to Convert PhysicalDisk to Space. Function: %1 Callee: %2 Error: %3 DriveId: %4 PoolName: %5 PoolVersion: %6 PoolMetadataLength: %7 PoolMinimumAllocationSize: %8 SpaceName: %9 SpaceProvisioningType: %10 SpaceAllocationSize: %11 SpaceResiliencyType: %12 MinimumFreeSizeRequired: %13
0xb00107f111It is taking longer than usual to execute the following function. Function: %1
0xb00107f211It took longer than usual to complete the following function. Function: %1 Response time (milliseconds): %2
0xb00107f411Failed to query ReFSDedupSvc. Function: %1 Stage: %2 ErrorMessage: %3 VolumeName: %4 HRESULT: %5
0xb00207d311An error occurred during method execution. Class: %1 Method: %2 ObjectId: %3 Error Code: %4 ExtendedStatusMsgId: %5
0xb00207d811An error occurred during method execution. Class: %1 Method: %2 ObjectId: %3 MI_Result: %4 ExtendedStatusMsgId: %5
0xb10103e911A Windows Storage Provider was loaded successfully. Provider: %1 Provider DLL: %2
0xb10103ea11Shutdown has been initiated for the Windows Storage Provider host service.
0xb10103eb11Shutdown for the Windows Storage Provider host service has been completed.
0xb10203e811A Windows Storage Provider failed to load. Provider: %1 Provider DLL: %2 Error Code: %3 Load Phase: %4 This failure is indicative of a bad installation, or a missing or corrupt DLL.
0xb201006511Failed to get disk properties. Function: %1 Disk Number: %2 Callee: %3 HResult: %4
0xb201006611The disk was onlined successfully. Function: %1 Disk Path: %2 Duration: %3 us
0xb201006711Failed to online the disk. Function: %1 Disk Path: %2 Callee: %3 HResult: %4
0xb201006811The disk was set to read-only successfully. Function: %1 Disk Path: %2 Duration: %3 us
0xb201006911Failed to set the disk read-only. Function: %1 Disk Path: %2 Callee: %3 HResult: %4
0xb201006a11The disk was set to read-write successfully. Function: %1 Disk Path: %2 Duration: %3 us
0xb201006b11Failed to set the disk read-write. Function: %1 Disk Path: %2 Callee: %3 HResult: %4
0xb201006c11The disk was offlined successfully. Function: %1 Disk Path: %2 Duration: %3 us
0xb201006d11Failed to offline the disk. Function: %1 Disk Path: %2 Callee: %3 HResult: %4
0xb201006e11The disk was initialized successfully. Function: %1 Disk Number: %2 Partition Style: %3 Duration: %4 us
0xb201006f11Failed to initialize the disk. Function: %1 Disk Number: %2 Partition Style: %3 Callee: %4 HResult: %5
0xb201007011The disk was cleaned successfully. Function: %1 Disk Number: %2 Duration: %3 us
0xb201007111Failed to clean the disk. Function: %1 Disk Number: %2 Callee: %3 HResult: %4
0xb20100c911Failed to get partition properties. Function: %1 Disk Number: %2 Partition Number: %3 Callee: %4 HResult: %5
0xb20100ca11The partition was created successfully. Function: %1 Disk Number: %2 Offset: %3 Size : %4 Alignment: %5 Partition Style: %6 MbrPartitionType: %7 MbrBootIndicator: %8 GptPartitionType: %9 GptPartitionId: %10 GptAttributes: %11 GptName: %12 Duration: %13 us
0xb20100cb11Failed to create the partition. Function: %1 Disk Number: %2 Offset: %3 Size : %4 Alignment: %5 Partition Style: %6 MbrPartitionType: %7 MbrBootIndicator: %8 GptPartitionType: %9 GptPartitionId: %10 GptAttributes: %11 GptName: %12 Callee: %13 HResult: %14
0xb20100cc11The partition was deleted successfully. Function: %1 Disk Number: %2 Partition Number: %3 Duration: %4 us
0xb20100cd11Failed to delete the partition. Function: %1 Disk Number: %2 Partition Number: %3 Callee: %4 HResult: %5
0xb20100cf11Failed to get partition access paths. Function: %1 Disk Number: %2 Partition Number: %3 Callee: %4 HResult: %5
0xd100000211Find SetShutdownCallback
0xd100000311Find SmpUnload
0xd100000411Find PreShutdown
0xd100000511Find MI_Main
0xd100000611Launch Hosted Provider
0xd200000111MBR
0xd200000211GPT
0xd200000311RAW
0x28.1Data is duplicated on two or three physical disks, increasing reliability, but reducing capacity. This storage layout requires at least two disks to protect you from a single disk failure, or at least five disks to protect you from two simultaneous disk failures.
0x38.1Data and parity information are striped across physical disks, increasing reliability, but somewhat reducing capacity. This storage layout requires at least three disks to protect you from a single disk failure and at least seven disks to protect you from two disk failures.
168 entries