- 4000 (0xFA0)
WINS encountered an error while processing the command.
- 4001 (0xFA1)
The local WINS cannot be deleted.
- 4002 (0xFA2)
The importation from the file failed.
- 4003 (0xFA3)
The backup failed. Was a full backup done before?
- 4004 (0xFA4)
The backup failed. Check the directory to which you are backing the database.
- 4005 (0xFA5)
The name does not exist in the WINS database.
- 4006 (0xFA6)
Replication with a nonconfigured partner is not allowed.
- 4050 (0xFD2)
The version of the supplied content information is not supported.
- 4051 (0xFD3)
The supplied content information is malformed.
- 4052 (0xFD4)
The requested data cannot be found in local or peer caches.
- 4053 (0xFD5)
No more data is available or required.
- 4054 (0xFD6)
The supplied object has not been initialized.
- 4055 (0xFD7)
The supplied object has already been initialized.
- 4056 (0xFD8)
A shutdown operation is already in progress.
- 4057 (0xFD9)
The supplied object has already been invalidated.
- 4058 (0xFDA)
An element already exists and was not replaced.
- 4059 (0xFDB)
Can not cancel the requested operation as it has already been completed.
- 4060 (0xFDC)
Can not perform the reqested operation because it has already been carried out.
- 4061 (0xFDD)
An operation accessed data beyond the bounds of valid data.
- 4062 (0xFDE)
The requested version is not supported.
- 4063 (0xFDF)
A configuration value is invalid.
- 4064 (0xFE0)
The SKU is not licensed.
- 4065 (0xFE1)
PeerDist Service is still initializing and will be available shortly.
- 4066 (0xFE2)
Communication with one or more computers will be temporarily blocked due to recent errors.
- 4100 (0x1004)
The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
- 4200 (0x1068)
The GUID passed was not recognized as valid by a WMI data provider.
- 4201 (0x1069)
The instance name passed was not recognized as valid by a WMI data provider.
- 4202 (0x106A)
The data item ID passed was not recognized as valid by a WMI data provider.
- 4203 (0x106B)
The WMI request could not be completed and should be retried.
- 4204 (0x106C)
The WMI data provider could not be located.
- 4205 (0x106D)
The WMI data provider references an instance set that has not been registered.
- 4206 (0x106E)
The WMI data block or event notification has already been enabled.
- 4207 (0x106F)
The WMI data block is no longer available.
- 4208 (0x1070)
The WMI data service is not available.
- 4209 (0x1071)
The WMI data provider failed to carry out the request.
- 4210 (0x1072)
The WMI MOF information is not valid.
- 4211 (0x1073)
The WMI registration information is not valid.
- 4212 (0x1074)
The WMI data block or event notification has already been disabled.
- 4213 (0x1075)
The WMI data item or data block is read only.
- 4214 (0x1076)
The WMI data item or data block could not be changed.
- 4250 (0x109A)
This operation is only valid in the context of an app container.
- 4251 (0x109B)
This application can only run in the context of an app container.
- 4252 (0x109C)
This functionality is not supported in the context of an app container.
- 4253 (0x109D)
The length of the SID supplied is not a valid length for app container SIDs.
- 4300 (0x10CC)
The media identifier does not represent a valid medium.
- 4301 (0x10CD)
The library identifier does not represent a valid library.
- 4302 (0x10CE)
The media pool identifier does not represent a valid media pool.
- 4303 (0x10CF)
The drive and medium are not compatible or exist in different libraries.
- 4304 (0x10D0)
The medium currently exists in an offline library and must be online to perform this operation.
- 4305 (0x10D1)
The operation cannot be performed on an offline library.
- 4306 (0x10D2)
The library, drive, or media pool is empty.
- 4307 (0x10D3)
The library, drive, or media pool must be empty to perform this operation.
- 4308 (0x10D4)
No media is currently available in this media pool or library.
- 4309 (0x10D5)
A resource required for this operation is disabled.
- 4310 (0x10D6)
The media identifier does not represent a valid cleaner.
- 4311 (0x10D7)
The drive cannot be cleaned or does not support cleaning.
- 4312 (0x10D8)
The object identifier does not represent a valid object.
- 4313 (0x10D9)
Unable to read from or write to the database.
- 4314 (0x10DA)
The database is full.
- 4315 (0x10DB)
The medium is not compatible with the device or media pool.
- 4316 (0x10DC)
The resource required for this operation does not exist.
- 4317 (0x10DD)
The operation identifier is not valid.
- 4318 (0x10DE)
The media is not mounted or ready for use.
- 4319 (0x10DF)
The device is not ready for use.
- 4320 (0x10E0)
The operator or administrator has refused the request.
- 4321 (0x10E1)
The drive identifier does not represent a valid drive.
- 4322 (0x10E2)
Library is full. No slot is available for use.
- 4323 (0x10E3)
The transport cannot access the medium.
- 4324 (0x10E4)
Unable to load the medium into the drive.
- 4325 (0x10E5)
Unable to retrieve the drive status.
- 4326 (0x10E6)
Unable to retrieve the slot status.
- 4327 (0x10E7)
Unable to retrieve status about the transport.
- 4328 (0x10E8)
Cannot use the transport because it is already in use.
- 4329 (0x10E9)
Unable to open or close the inject/eject port.
- 4330 (0x10EA)
Unable to eject the medium because it is in a drive.
- 4331 (0x10EB)
A cleaner slot is already reserved.
- 4332 (0x10EC)
A cleaner slot is not reserved.
- 4333 (0x10ED)
The cleaner cartridge has performed the maximum number of drive cleanings.
- 4334 (0x10EE)
Unexpected on-medium identifier.
- 4335 (0x10EF)
The last remaining item in this group or resource cannot be deleted.
- 4336 (0x10F0)
The message provided exceeds the maximum size allowed for this parameter.
- 4337 (0x10F1)
The volume contains system or paging files.
- 4338 (0x10F2)
The media type cannot be removed from this library since at least one drive in the library reports it can support this media type.
- 4339 (0x10F3)
This offline media cannot be mounted on this system since no enabled drives are present which can be used.
- 4340 (0x10F4)
A cleaner cartridge is present in the tape library.
- 4341 (0x10F5)
Cannot use the inject/eject port because it is not empty.
- 4350 (0x10FE)
This file is currently not available for use on this computer.
- 4351 (0x10FF)
The remote storage service is not operational at this time.
- 4352 (0x1100)
The remote storage service encountered a media error.
- 4390 (0x1126)
The file or directory is not a reparse point.
- 4391 (0x1127)
The reparse point attribute cannot be set because it conflicts with an existing attribute.
- 4392 (0x1128)
The data present in the reparse point buffer is invalid.
- 4393 (0x1129)
The tag present in the reparse point buffer is invalid.
- 4394 (0x112A)
There is a mismatch between the tag specified in the request and the tag present in the reparse point.
- 4400 (0x1130)
Fast Cache data not found.
- 4401 (0x1131)
Fast Cache data expired.
- 4402 (0x1132)
Fast Cache data corrupt.
- 4403 (0x1133)
Fast Cache data has exceeded its max size and cannot be updated.
- 4404 (0x1134)
Fast Cache has been ReArmed and requires a reboot until it can be updated.
- 4420 (0x1144)
Secure Boot detected that rollback of protected data has been attempted.
- 4421 (0x1145)
The value is protected by Secure Boot policy and cannot be modified or deleted.
- 4422 (0x1146)
The Secure Boot policy is invalid.
- 4423 (0x1147)
A new Secure Boot policy did not contain the current publisher on its update list.
- 4424 (0x1148)
The Secure Boot policy is either not signed or is signed by a non-trusted signer.
- 4425 (0x1149)
Secure Boot is not enabled on this machine.
- 4426 (0x114A)
Secure Boot requires that certain files and drivers are not replaced by other files or drivers.
- 4440 (0x1158)
The copy offload read operation is not supported by a filter.
- 4441 (0x1159)
The copy offload write operation is not supported by a filter.
- 4442 (0x115A)
The copy offload read operation is not supported for the file.
- 4443 (0x115B)
The copy offload write operation is not supported for the file.
- 4500 (0x1194)
Single Instance Storage is not available on this volume.
- 5001 (0x1389)
The operation cannot be completed because other resources are dependent on this resource.
- 5002 (0x138A)
The cluster resource dependency cannot be found.
- 5003 (0x138B)
The cluster resource cannot be made dependent on the specified resource because it is already dependent.
- 5004 (0x138C)
The cluster resource is not online.
- 5005 (0x138D)
A cluster node is not available for this operation.
- 5006 (0x138E)
The cluster resource is not available.
- 5007 (0x138F)
The cluster resource could not be found.
- 5008 (0x1390)
The cluster is being shut down.
- 5009 (0x1391)
A cluster node cannot be evicted from the cluster unless the node is down or it is the last node.
- 5010 (0x1392)
The object already exists.
- 5011 (0x1393)
The object is already in the list.
- 5012 (0x1394)
The cluster group is not available for any new requests.
- 5013 (0x1395)
The cluster group could not be found.
- 5014 (0x1396)
The operation could not be completed because the cluster group is not online.
- 5015 (0x1397)
The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.
- 5016 (0x1398)
The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.
- 5017 (0x1399)
The cluster resource could not be created in the specified resource monitor.
- 5018 (0x139A)
The cluster resource could not be brought online by the resource monitor.
- 5019 (0x139B)
The operation could not be completed because the cluster resource is online.
- 5020 (0x139C)
The cluster resource could not be deleted or brought offline because it is the quorum resource.
- 5021 (0x139D)
The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.
- 5022 (0x139E)
The cluster software is shutting down.
- 5023 (0x139F)
The group or resource is not in the correct state to perform the requested operation.
- 5024 (0x13A0)
The properties were stored but not all changes will take effect until the next time the resource is brought online.
- 5025 (0x13A1)
The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.
- 5026 (0x13A2)
The cluster resource could not be deleted since it is a core resource.
- 5027 (0x13A3)
The quorum resource failed to come online.
- 5028 (0x13A4)
The quorum log could not be created or mounted successfully.
- 5029 (0x13A5)
The cluster log is corrupt.
- 5030 (0x13A6)
The record could not be written to the cluster log since it exceeds the maximum size.
- 5031 (0x13A7)
The cluster log exceeds its maximum size.
- 5032 (0x13A8)
No checkpoint record was found in the cluster log.
- 5033 (0x13A9)
The minimum required disk space needed for logging is not available.
- 5034 (0x13AA)
The cluster node failed to take control of the quorum resource because the resource is owned by another active node.
- 5035 (0x13AB)
A cluster network is not available for this operation.
- 5036 (0x13AC)
A cluster node is not available for this operation.
- 5037 (0x13AD)
All cluster nodes must be running to perform this operation.
- 5038 (0x13AE)
A cluster resource failed.
- 5039 (0x13AF)
The cluster node is not valid.
- 5040 (0x13B0)
The cluster node already exists.
- 5041 (0x13B1)
A node is in the process of joining the cluster.
- 5042 (0x13B2)
The cluster node was not found.
- 5043 (0x13B3)
The cluster local node information was not found.
- 5044 (0x13B4)
The cluster network already exists.
- 5045 (0x13B5)
The cluster network was not found.
- 5046 (0x13B6)
The cluster network interface already exists.
- 5047 (0x13B7)
The cluster network interface was not found.
- 5048 (0x13B8)
The cluster request is not valid for this object.
- 5049 (0x13B9)
The cluster network provider is not valid.
- 5050 (0x13BA)
The cluster node is down.
- 5051 (0x13BB)
The cluster node is not reachable.
- 5052 (0x13BC)
The cluster node is not a member of the cluster.
- 5053 (0x13BD)
A cluster join operation is not in progress.
- 5054 (0x13BE)
The cluster network is not valid.
- 5056 (0x13C0)
The cluster node is up.
- 5057 (0x13C1)
The cluster IP address is already in use.
- 5058 (0x13C2)
The cluster node is not paused.
- 5059 (0x13C3)
No cluster security context is available.
- 5060 (0x13C4)
The cluster network is not configured for internal cluster communication.
- 5061 (0x13C5)
The cluster node is already up.
- 5062 (0x13C6)
The cluster node is already down.
- 5063 (0x13C7)
The cluster network is already online.
- 5064 (0x13C8)
The cluster network is already offline.
- 5065 (0x13C9)
The cluster node is already a member of the cluster.
- 5066 (0x13CA)
The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.
- 5067 (0x13CB)
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
- 5068 (0x13CC)
This operation cannot be performed on the cluster resource as it the quorum resource. You may not bring the quorum resource offline or modify its possible owners list.
- 5069 (0x13CD)
The cluster quorum resource is not allowed to have any dependencies.
- 5070 (0x13CE)
The cluster node is paused.
- 5071 (0x13CF)
The cluster resource cannot be brought online. The owner node cannot run this resource.
- 5072 (0x13D0)
The cluster node is not ready to perform the requested operation.
- 5073 (0x13D1)
The cluster node is shutting down.
- 5074 (0x13D2)
The cluster join operation was aborted.
- 5075 (0x13D3)
The cluster join operation failed due to incompatible software versions between the joining node and its sponsor.
- 5076 (0x13D4)
This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
- 5077 (0x13D5)
The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
- 5078 (0x13D6)
The specified resource type was not found.
- 5079 (0x13D7)
The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
- 5080 (0x13D8)
The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.
- 5081 (0x13D9)
No authentication package could be registered with the RPC server.
- 5082 (0x13DA)
You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.
- 5083 (0x13DB)
The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.
- 5084 (0x13DC)
The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.
- 5085 (0x13DD)
A non locker code got a request to reserve the lock for making global updates.
- 5086 (0x13DE)
The quorum disk could not be located by the cluster service.
- 5087 (0x13DF)
The backed up cluster database is possibly corrupt.
- 5088 (0x13E0)
A DFS root already exists in this cluster node.
- 5089 (0x13E1)
An attempt to modify a resource property failed because it conflicts with another existing property.
- 5890 (0x1702)
An operation was attempted that is incompatible with the current membership state of the node.
- 5891 (0x1703)
The quorum resource does not contain the quorum log.
- 5892 (0x1704)
The membership engine requested shutdown of the cluster service on this node.
- 5893 (0x1705)
The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
- 5894 (0x1706)
A matching cluster network for the specified IP address could not be found.
- 5895 (0x1707)
The actual data type of the property did not match the expected data type of the property.
- 5896 (0x1708)
The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer.
- 5897 (0x1709)
Two or more parameter values specified for a resource’s properties are in conflict.
- 5898 (0x170A)
This computer cannot be made a member of a cluster.
- 5899 (0x170B)
This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.
- 5900 (0x170C)
A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.
- 5901 (0x170D)
The cluster configuration action has already been committed.
- 5902 (0x170E)
The cluster configuration action could not be rolled back.
- 5903 (0x170F)
The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.
- 5904 (0x1710)
One or more nodes in the cluster are running a version of Windows that does not support this operation.
- 5905 (0x1711)
The name of the corresponding computer account doesn’t match the Network Name for this resource.
- 5906 (0x1712)
No network adapters are available.
- 5907 (0x1713)
The cluster node has been poisoned.
- 5908 (0x1714)
The group is unable to accept the request since it is moving to another node.
- 5909 (0x1715)
The resource type cannot accept the request since is too busy performing another operation.
- 5910 (0x1716)
The call to the cluster resource DLL timed out.
- 5911 (0x1717)
The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted.
- 5912 (0x1718)
An internal cluster error occurred. A call to an invalid function was attempted.
- 5913 (0x1719)
A parameter value is out of acceptable range.
- 5914 (0x171A)
A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required.
- 5915 (0x171B)
An invalid cluster registry operation was attempted.
- 5916 (0x171C)
An input string of characters is not properly terminated.
- 5917 (0x171D)
An input string of characters is not in a valid format for the data it represents.
- 5918 (0x171E)
An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress.
- 5919 (0x171F)
An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress.
- 5920 (0x1720)
An internal cluster error occurred. Data was not properly initialized.
- 5921 (0x1721)
An error occurred while reading from a stream of data. An unexpected number of bytes was returned.
- 5922 (0x1722)
An error occurred while writing to a stream of data. The required number of bytes could not be written.
- 5923 (0x1723)
An error occurred while deserializing a stream of cluster data.
- 5924 (0x1724)
One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s).
- 5925 (0x1725)
A quorum of cluster nodes was not present to form a cluster.
- 5926 (0x1726)
The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address.
- 5927 (0x1727)
The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends.
- 5928 (0x1728)
Quorum resource cannot reside in the Available Storage group.
- 5929 (0x1729)
The dependencies for this resource are nested too deeply.
- 5930 (0x172A)
The call into the resource DLL raised an unhandled exception.
- 5931 (0x172B)
The RHS process failed to initialize.
- 5932 (0x172C)
The Failover Clustering feature is not installed on this node.
- 5933 (0x172D)
The resources must be online on the same node for this operation.
- 5934 (0x172E)
A new node can not be added since this cluster is already at its maximum number of nodes.
- 5935 (0x172F)
This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit.
- 5936 (0x1730)
An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain.
- 5937 (0x1731)
This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed.
- 5938 (0x1732)
File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes.
- 5939 (0x1733)
Eviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown. If it is the last node in the cluster, destroy cluster command should be used.
- 5940 (0x1734)
Only one instance of this resource type is allowed in the cluster.
- 5941 (0x1735)
Only one instance of this resource type is allowed per resource group.
- 5942 (0x1736)
The resource failed to come online due to the failure of one or more provider resources.
- 5943 (0x1737)
The resource has indicated that it cannot come online on any node.
- 5944 (0x1738)
The current operation cannot be performed on this group at this time.
- 5945 (0x1739)
The directory or file is not located on a cluster shared volume.
- 5946 (0x173A)
The Security Descriptor does not meet the requirements for a cluster.
- 5947 (0x173B)
There is one or more shared volumes resources configured in the cluster. Those resources must be moved to available storage in order for operation to succeed.
- 5948 (0x173C)
This group or resource cannot be directly manipulated. Use shared volume APIs to perform desired operation.
- 5949 (0x173D)
Back up is in progress. Please wait for backup completion before trying this operation again.
- 5950 (0x173E)
The path does not belong to a cluster shared volume.
- 5951 (0x173F)
The cluster shared volume is not locally mounted on this node.
- 5952 (0x1740)
The cluster watchdog is terminating.
- 5953 (0x1741)
A resource vetoed a move between two nodes because they are incompatible.
- 5954 (0x1742)
The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements.
- 5955 (0x1743)
The resource vetoed the call.
- 5956 (0x1744)
Resource could not start or run because it could not reserve sufficient system resources.
- 5957 (0x1745)
A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation.
- 5958 (0x1746)
A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation.
- 5959 (0x1747)
The requested operation can not be completed because the group is queued for an operation.
- 5960 (0x1748)
The requested operation can not be completed because a resource has locked status.
- 5961 (0x1749)
The resource cannot move to another node because a cluster shared volume vetoed the operation.
- 5962 (0x174A)
A node drain is already in progress.
This value was also named ERROR_CLUSTER_NODE_EVACUATION_IN_PROGRESS
- 5963 (0x174B)
Clustered storage is not connected to the node.
- 5964 (0x174C)
The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS.
- 5965 (0x174D)
The resource must be part of the Available Storage group to complete this action.
- 5966 (0x174E)
CSVFS failed operation as volume is in redirected mode.
- 5967 (0x174F)
CSVFS failed operation as volume is not in redirected mode.
- 5968 (0x1750)
Cluster properties cannot be returned at this time.
- 5969 (0x1751)
The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes.
- 5970 (0x1752)
The operation cannot be completed because the resource is in maintenance mode.
- 5971 (0x1753)
The operation cannot be completed because of cluster affinity conflicts.
- 5972 (0x1754)
- The operation cannot be completed because the resource is a replica virtual machine.
Source – Microsoft
For any questions, queries please do not hesitate to leave a comment in the queries page at the bottom of the page or contact us at email@example.com
Join us on facebook