WRITTEN BY: supportmymoto.com STAFF
System Error Codes (4000-5999)
The System Error Codes are very broad. Each can happen in one in all many lots of of places within the system. Consequently the descriptions of those codes can’t be very particular. Use of those codes requires some quantity of investigation and evaluation. That you must word each the programmatic and the run-time context during which these errors happen. As a result of these codes are outlined in WinError.h for anybody to make use of, typically the codes are returned by non-system software program. Generally the code is returned by a perform deep within the stack and much eliminated out of your code that’s dealing with the error.
The next checklist describes system error codes (errors 4000 to 5999). They’re returned by the GetLastError perform when many features fail. To retrieve the outline textual content for the error in your utility, use the FormatMessage perform with the FORMAT_MESSAGE_FROM_SYSTEM flag.
4000 (0xFA0) – WINS encountered an error whereas processing the command.
4001 (0xFA1) – The native WINS can’t be deleted.
4002 (0xFA2) – The importation from the file failed.
4003 (0xFA3) – The backup failed. Was a full backup achieved earlier than?
4004 (0xFA4) – The backup failed. Test the listing to which you might be backing the database.
4005 (0xFA5) – The identify doesn’t exist within the WINS database.
4006 (0xFA6) – Replication with a nonconfigured companion isn’t allowed.
4050 (0xFD2) – The model of the provided content material info isn’t supported.
4051 (0xFD3) – The provided content material info is malformed.
4052 (0xFD4) – The requested knowledge can’t be present in native or peer caches.
4053 (0xFD5) – No extra knowledge is accessible or required.
4054 (0xFD6) – The provided object has not been initialized.
4055 (0xFD7) – The provided object has already been initialized.
4056 (0xFD8) – A shutdown operation is already in progress.
4057 (0xFD9) – The provided object has already been invalidated.
4058 (0xFDA) – A component already exists and was not changed.
4059 (0xFDB) – Cannot cancel the requested operation because it has already been accomplished.
4060 (0xFDC) – Cannot carry out the reqested operation as a result of it has already been carried out.
4061 (0xFDD) – An operation accessed knowledge past the bounds of legitimate knowledge.
4062 (0xFDE) – The requested model isn’t supported.
4063 (0xFDF) – A configuration worth is invalid.
4064 (0xFE0) – The SKU isn’t licensed.
4065 (0xFE1) – PeerDist Service remains to be initializing and shall be accessible shortly.
4066 (0xFE2) – Communication with a number of computer systems shall be briefly blocked as a result of current errors.
4100 (0x1004) – The DHCP shopper has obtained an IP handle that’s already in use on the community. The native interface shall be disabled till the DHCP shopper can get hold of a brand new handle.
4200 (0x1068) – The GUID handed was not acknowledged as legitimate by a WMI knowledge supplier.
4201 (0x1069) – The occasion identify handed was not acknowledged as legitimate by a WMI knowledge supplier.
4202 (0x106A) – The information merchandise ID handed was not acknowledged as legitimate by a WMI knowledge supplier.
4203 (0x106B) – The WMI request couldn’t be accomplished and must be retried.
4204 (0x106C) – The WMI knowledge supplier couldn’t be positioned.
4205 (0x106D) – The WMI knowledge supplier references an occasion set that has not been registered.
4206 (0x106E) – The WMI knowledge block or occasion notification has already been enabled.
4207 (0x106F) – The WMI knowledge block is not accessible.
4208 (0x1070) – The WMI knowledge service isn’t accessible.
4209 (0x1071) – The WMI knowledge supplier failed to hold out the request.
4210 (0x1072) – The WMI MOF info isn’t legitimate.
4211 (0x1073) – The WMI registration info isn’t legitimate.
4212 (0x1074) – The WMI knowledge block or occasion notification has already been disabled.
4213 (0x1075) – The WMI knowledge merchandise or knowledge block is learn solely.
4214 (0x1076) – The WMI knowledge merchandise or knowledge block couldn’t be modified.
4250 (0x109A) – This operation is simply legitimate within the context of an app container.
4251 (0x109B) – This utility can solely run within the context of an app container.
4252 (0x109C) – This performance isn’t supported within the context of an app container.
4253 (0x109D) – The size of the SID provided isn’t a legitimate size for app container SIDs.
4300 (0x10CC) – The media identifier doesn’t symbolize a legitimate medium.
4301 (0x10CD) – The library identifier doesn’t symbolize a legitimate library.
4302 (0x10CE) – The media pool identifier doesn’t symbolize a legitimate media pool.
4303 (0x10CF) – The drive and medium are usually not appropriate or exist in several libraries.
4304 (0x10D0) – The medium at present exists in an offline library and should be on-line to carry out this operation.
4305 (0x10D1) – The operation can’t be carried out on an offline library.
4306 (0x10D2) – The library, drive, or media pool is empty.
4307 (0x10D3) – The library, drive, or media pool should be empty to carry out this operation.
4308 (0x10D4) – No media is at present accessible on this media pool or library.
4309 (0x10D5) – A useful resource required for this operation is disabled.
4310 (0x10D6) – The media identifier doesn’t symbolize a legitimate cleaner.
4311 (0x10D7) – The drive can’t be cleaned or doesn’t help cleansing.
4312 (0x10D8) – The article identifier doesn’t symbolize a legitimate object.
4313 (0x10D9) – Unable to learn from or write to the database.
4314 (0x10DA) – The database is full.
4315 (0x10DB) – The medium isn’t appropriate with the system or media pool.
4316 (0x10DC) – The useful resource required for this operation doesn’t exist.
4317 (0x10DD) – The operation identifier isn’t legitimate.
4318 (0x10DE) – The media isn’t mounted or prepared to be used.
4319 (0x10DF) – The system isn’t prepared to be used.
4320 (0x10E0) – The operator or administrator has refused the request.
4321 (0x10E1) – The drive identifier doesn’t symbolize a legitimate drive.
4322 (0x10E2) – Library is full. No slot is accessible to be used.
4323 (0x10E3) – The transport can’t entry the medium.
4324 (0x10E4) – Unable to load the medium into the drive.
4325 (0x10E5) – Unable to retrieve the drive standing.
4326 (0x10E6) – Unable to retrieve the slot standing.
4327 (0x10E7) – Unable to retrieve standing concerning the transport.
4328 (0x10E8) – Can not use the transport as a result of it’s already in use.
4329 (0x10E9) – Unable to open or shut the inject/eject port.
4330 (0x10EA) – Unable to eject the medium as a result of it’s in a drive.
4331 (0x10EB) – A cleaner slot is already reserved.
4332 (0x10EC) – A cleaner slot isn’t reserved.
4333 (0x10ED) – The cleaner cartridge has carried out the utmost variety of drive cleanings.
4334 (0x10EE) – Sudden on-medium identifier.
4335 (0x10EF) – The final remaining merchandise on this group or useful resource can’t be deleted.
4336 (0x10F0) – The message supplied exceeds the utmost measurement allowed for this parameter.
4337 (0x10F1) – The amount accommodates system or paging information.
4338 (0x10F2) – The media sort can’t be faraway from this library since at the least one drive within the library reviews it might help this media sort.
4339 (0x10F3) – This offline media can’t be mounted on this technique since no enabled drives are current which can be utilized.
4340 (0x10F4) – A cleaner cartridge is current within the tape library.
4341 (0x10F5) – Can not use the inject/eject port as a result of it isn’t empty.
4350 (0x10FE) – This file is at present not accessible to be used on this pc.
4351 (0x10FF) – The distant storage service isn’t operational presently.
4352 (0x1100) – The distant storage service encountered a media error.
4390 (0x1126) – The file or listing isn’t a reparse level.
4391 (0x1127) – The reparse level attribute can’t be set as a result of it conflicts with an present attribute.
4392 (0x1128) – The information current within the reparse level buffer is invalid.
4393 (0x1129) – The tag current within the reparse level buffer is invalid.
4394 (0x112A) – There’s a mismatch between the tag specified within the request and the tag current within the reparse level.
4400 (0x1130) – Quick Cache knowledge not discovered.
4401 (0x1131) – Quick Cache knowledge expired.
4402 (0x1132) – Quick Cache knowledge corrupt.
4403 (0x1133) – Quick Cache knowledge has exceeded its max measurement and can’t be up to date.
4404 (0x1134) – Quick Cache has been ReArmed and requires a reboot till it may be up to date.
4420 (0x1144) – Safe Boot detected that rollback of protected knowledge has been tried.
4421 (0x1145) – The worth is protected by Safe Boot coverage and can’t be modified or deleted.
4422 (0x1146) – The Safe Boot coverage is invalid.
4423 (0x1147) – A brand new Safe Boot coverage didn’t include the present writer on its replace checklist.
4424 (0x1148) – The Safe Boot coverage is both not signed or is signed by a non-trusted signer.
4425 (0x1149) – Safe Boot isn’t enabled on this machine.
4426 (0x114A) – Safe Boot requires that sure information and drivers are usually not changed by different information or drivers.
4440 (0x1158) – The copy offload learn operation isn’t supported by a filter.
4441 (0x1159) – The copy offload write operation isn’t supported by a filter.
4442 (0x115A) – The copy offload learn operation isn’t supported for the file.
4443 (0x115B) – The copy offload write operation isn’t supported for the file.
4500 (0x1194) – Single Occasion Storage isn’t accessible on this quantity.
5001 (0x1389) – The operation can’t be accomplished as a result of different sources are depending on this useful resource.
5002 (0x138A) – The cluster useful resource dependency can’t be discovered.
5003 (0x138B) – The cluster useful resource can’t be made depending on the desired useful resource as a result of it’s already dependent.
5004 (0x138C) – The cluster useful resource isn’t on-line.
5005 (0x138D) – A cluster node isn’t accessible for this operation.
5006 (0x138E) – The cluster useful resource isn’t accessible.
5007 (0x138F) – The cluster useful resource couldn’t be discovered.
5008 (0x1390) – The cluster is being shut down.
5009 (0x1391) – A cluster node can’t be evicted from the cluster until the node is down or it’s the final node.
5010 (0x1392) – The article already exists.
5011 (0x1393) – The article is already within the checklist.
5012 (0x1394) – The cluster group isn’t accessible for any new requests.
5013 (0x1395) – The cluster group couldn’t be discovered.
5014 (0x1396) – The operation couldn’t be accomplished as a result of the cluster group isn’t on-line.
5015 (0x1397) – The operation failed as a result of both the desired cluster node isn’t the proprietor of the useful resource, or the node isn’t a potential proprietor of the useful resource.
5016 (0x1398) – The operation failed as a result of both the desired cluster node isn’t the proprietor of the group, or the node isn’t a potential proprietor of the group.
5017 (0x1399) – The cluster useful resource couldn’t be created within the specified useful resource monitor.
5018 (0x139A) – The cluster useful resource couldn’t be introduced on-line by the useful resource monitor.
5019 (0x139B) – The operation couldn’t be accomplished as a result of the cluster useful resource is on-line.
5020 (0x139C) – The cluster useful resource couldn’t be deleted or introduced offline as a result of it’s the quorum useful resource.
5021 (0x139D) – The cluster couldn’t make the desired useful resource a quorum useful resource as a result of it isn’t able to being a quorum useful resource.
5022 (0x139E) – The cluster software program is shutting down.
5023 (0x139F) – The group or useful resource isn’t within the appropriate state to carry out the requested operation.
5024 (0x13A0) – The properties had been saved however not all modifications will take impact till the subsequent time the useful resource is introduced on-line.
5025 (0x13A1) – The cluster couldn’t make the desired useful resource a quorum useful resource as a result of it doesn’t belong to a shared storage class.
5026 (0x13A2) – The cluster useful resource couldn’t be deleted since it’s a core useful resource.
5027 (0x13A3) – The quorum useful resource failed to come back on-line.
5028 (0x13A4) – The quorum log couldn’t be created or mounted efficiently.
5029 (0x13A5) – The cluster log is corrupt.
5030 (0x13A6) – The file couldn’t be written to the cluster log because it exceeds the utmost measurement.
5031 (0x13A7) – The cluster log exceeds its most measurement.
5032 (0x13A8) – No checkpoint file was discovered within the cluster log.
5033 (0x13A9) – The minimal required disk house wanted for logging isn’t accessible.
5034 (0x13AA) – The cluster node didn’t take management of the quorum useful resource as a result of the useful resource is owned by one other lively node.
5035 (0x13AB) – A cluster community isn’t accessible for this operation.
5036 (0x13AC) – A cluster node isn’t accessible for this operation.
5037 (0x13AD) – All cluster nodes should be operating to carry out this operation.
5038 (0x13AE) – A cluster useful resource failed.
5039 (0x13AF) – The cluster node isn’t legitimate.
5040 (0x13B0) – The cluster node already exists.
5041 (0x13B1) – A node is within the strategy of becoming a member of the cluster.
5042 (0x13B2) – The cluster node was not discovered.
5043 (0x13B3) – The cluster native node info was not discovered.
5044 (0x13B4) – The cluster community already exists.
5045 (0x13B5) – The cluster community was not discovered.
5046 (0x13B6) – The cluster community interface already exists.
5047 (0x13B7) – The cluster community interface was not discovered.
5048 (0x13B8) – The cluster request isn’t legitimate for this object.
5049 (0x13B9) – The cluster community supplier isn’t legitimate.
5050 (0x13BA) – The cluster node is down.
5051 (0x13BB) – The cluster node isn’t reachable.
5052 (0x13BC) – The cluster node isn’t a member of the cluster.
5053 (0x13BD) – A cluster be a part of operation isn’t in progress.
5054 (0x13BE) – The cluster community isn’t legitimate.
5056 (0x13C0) – The cluster node is up.
5057 (0x13C1) – The cluster IP handle is already in use.
5058 (0x13C2) – The cluster node isn’t paused.
5059 (0x13C3) – No cluster safety context is accessible.
5060 (0x13C4) – The cluster community isn’t configured for inside cluster communication.
5061 (0x13C5) – The cluster node is already up.
5062 (0x13C6) – The cluster node is already down.
5063 (0x13C7) – The cluster community is already on-line.
5064 (0x13C8) – The cluster community is already offline.
5065 (0x13C9) – The cluster node is already a member of the cluster.
5066 (0x13CA) – The cluster community is the one one configured for inside cluster communication between two or extra lively cluster nodes. The interior communication functionality can’t be faraway from the community.
5067 (0x13CB) – A number of cluster sources rely on the community to supply service to shoppers. The shopper entry functionality can’t be faraway from the community.
5068 (0x13CC) – This operation can’t be carried out on the cluster useful resource because it the quorum useful resource. You might not carry the quorum useful resource offline or modify its potential house owners checklist.
5069 (0x13CD) – The cluster quorum useful resource isn’t allowed to have any dependencies.
5070 (0x13CE) – The cluster node is paused.
5071 (0x13CF) – The cluster useful resource can’t be introduced on-line. The proprietor node can’t run this useful resource.
5072 (0x13D0) – The cluster node isn’t able to carry out the requested operation.
5073 (0x13D1) – The cluster node is shutting down.
5074 (0x13D2) – The cluster be a part of operation was aborted.
5075 (0x13D3) – The cluster be a part of operation failed as a result of incompatible software program variations between the becoming a member of node and its sponsor.
5076 (0x13D4) – This useful resource can’t be created as a result of the cluster has reached the restrict on the variety of sources it might monitor.
5077 (0x13D5) – The system configuration modified through the cluster be a part of or kind operation. The be a part of or kind operation was aborted.
5078 (0x13D6) – The required useful resource sort was not discovered.
5079 (0x13D7) – The required node doesn’t help a useful resource of this sort. This can be as a result of model inconsistencies or because of the absence of the useful resource DLL on this node.
5080 (0x13D8) – The required useful resource identify isn’t supported by this useful resource DLL. This can be as a result of a nasty (or modified) identify provided to the useful resource DLL.
5081 (0x13D9) – No authentication bundle may very well be registered with the RPC server.
5082 (0x13DA) – You can not carry the group on-line as a result of the proprietor of the group isn’t in the popular checklist for the group. To alter the proprietor node for the group, transfer the group.
5083 (0x13DB) – The be a part of operation failed as a result of the cluster database sequence quantity has modified or is incompatible with the locker node. This may occasionally occur throughout a be a part of operation if the cluster database was altering through the be a part of.
5084 (0x13DC) – The useful resource monitor won’t enable the fail operation to be carried out whereas the useful resource is in its present state. This may occasionally occur if the useful resource is in a pending state.
5085 (0x13DD) – A non locker code acquired a request to order the lock for making world updates.
5086 (0x13DE) – The quorum disk couldn’t be positioned by the cluster service.
5087 (0x13DF) – The backed up cluster database is presumably corrupt.
5088 (0x13E0) – A DFS root already exists on this cluster node.
5089 (0x13E1) – An try to change a useful resource property failed as a result of it conflicts with one other present property.
5890 (0x1702) – An operation was tried that’s incompatible with the present membership state of the node.
5891 (0x1703) – The quorum useful resource doesn’t include the quorum log.
5892 (0x1704) – The membership engine requested shutdown of the cluster service on this node.
5893 (0x1705) – The be a part of operation failed as a result of the cluster occasion ID of the becoming a member of node doesn’t match the cluster occasion ID of the sponsor node.
5894 (0x1706) – An identical cluster community for the desired IP handle couldn’t be discovered.
5895 (0x1707) – The precise knowledge sort of the property didn’t match the anticipated knowledge sort of the property.
5896 (0x1708) – The cluster node was evicted from the cluster efficiently, however the node was not cleaned up. To find out what cleanup steps failed and how you can recuperate, see the Failover Clustering utility occasion log utilizing Occasion Viewer.
5897 (0x1709) – Two or extra parameter values specified for a useful resource’s properties are in battle.
5898 (0x170A) – This pc can’t be made a member of a cluster.
5899 (0x170B) – This pc can’t be made a member of a cluster as a result of it doesn’t have the right model of Home windows put in.
5900 (0x170C) – A cluster can’t be created with the desired cluster identify as a result of that cluster identify is already in use. Specify a distinct identify for the cluster.
5901 (0x170D) – The cluster configuration motion has already been dedicated.
5902 (0x170E) – The cluster configuration motion couldn’t be rolled again.
5903 (0x170F) – The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on one other node.
5904 (0x1710) – A number of nodes within the cluster are operating a model of Home windows that doesn’t help this operation.
5905 (0x1711) – The identify of the corresponding pc account does not match the Community Identify for this useful resource.
5906 (0x1712) – No community adapters can be found.
5907 (0x1713) – The cluster node has been poisoned.
5908 (0x1714) – The group is unable to simply accept the request since it’s transferring to a different node.
5909 (0x1715) – The useful resource sort can’t settle for the request since is just too busy performing one other operation.
5910 (0x1716) – The decision to the cluster useful resource DLL timed out.
5911 (0x1717) – The handle isn’t legitimate for an IPv6 Handle useful resource. A world IPv6 handle is required, and it should match a cluster community. Compatibility addresses are usually not permitted.
5912 (0x1718) – An inside cluster error occurred. A name to an invalid perform was tried.
5913 (0x1719) – A parameter worth is out of acceptable vary.
5914 (0x171A) – A community error occurred whereas sending knowledge to a different node within the cluster. The variety of bytes transmitted was lower than required.
5915 (0x171B) – An invalid cluster registry operation was tried.
5916 (0x171C) – An enter string of characters isn’t correctly terminated.
5917 (0x171D) – An enter string of characters isn’t in a legitimate format for the information it represents.
5918 (0x171E) – An inside cluster error occurred. A cluster database transaction was tried whereas a transaction was already in progress.
5919 (0x171F) – An inside cluster error occurred. There was an try and commit a cluster database transaction whereas no transaction was in progress.
5920 (0x1720) – An inside cluster error occurred. Knowledge was not correctly initialized.
5921 (0x1721) – An error occurred whereas studying from a stream of information. An surprising variety of bytes was returned.
5922 (0x1722) – An error occurred whereas writing to a stream of information. The required variety of bytes couldn’t be written.
5923 (0x1723) – An error occurred whereas deserializing a stream of cluster knowledge.
5924 (0x1724) – A number of property values for this useful resource are in battle with a number of property values related to its dependent useful resource(s).
5925 (0x1725) – A quorum of cluster nodes was not current to kind a cluster.
5926 (0x1726) – The cluster community isn’t legitimate for an IPv6 Handle useful resource, or it doesn’t match the configured handle.
5927 (0x1727) – The cluster community isn’t legitimate for an IPv6 Tunnel useful resource. Test the configuration of the IP Handle useful resource on which the IPv6 Tunnel useful resource relies upon.
5928 (0x1728) – Quorum useful resource can’t reside within the Accessible Storage group.
5929 (0x1729) – The dependencies for this useful resource are nested too deeply.
5930 (0x172A) – The decision into the useful resource DLL raised an unhandled exception.
5931 (0x172B) – The RHS course of didn’t initialize.
5932 (0x172C) – The Failover Clustering characteristic isn’t put in on this node.
5933 (0x172D) – The sources should be on-line on the identical node for this operation.
5934 (0x172E) – A brand new node can’t be added since this cluster is already at its most variety of nodes.
5935 (0x172F) – This cluster can’t be created for the reason that specified variety of nodes exceeds the utmost allowed restrict.
5936 (0x1730) – An try to make use of the desired cluster identify failed as a result of an enabled pc object with the given identify already exists within the area.
5937 (0x1731) – This cluster can’t be destroyed. It has non-core utility teams which should be deleted earlier than the cluster might be destroyed.
5938 (0x1732) – File share related to file share witness useful resource can’t be hosted by this cluster or any of its nodes.
5939 (0x1733) – Eviction of this node is invalid presently. As a result of quorum necessities node eviction will lead to cluster shutdown. If it’s the final node within the cluster, destroy cluster command must be used.
5940 (0x1734) – Just one occasion of this useful resource sort is allowed within the cluster.
5941 (0x1735) – Just one occasion of this useful resource sort is allowed per useful resource group.
5942 (0x1736) – The useful resource failed to come back on-line because of the failure of a number of supplier sources.
5943 (0x1737) – The useful resource has indicated that it can’t come on-line on any node.
5944 (0x1738) – The present operation can’t be carried out on this group presently.
5945 (0x1739) – The listing or file isn’t positioned on a cluster shared quantity.
5946 (0x173A) – The Safety Descriptor doesn’t meet the necessities for a cluster.
5947 (0x173B) – There’s a number of shared volumes sources configured within the cluster. These sources should be moved to accessible storage to ensure that operation to succeed.
5948 (0x173C) – This group or useful resource can’t be immediately manipulated. Use shared quantity APIs to carry out desired operation.
5949 (0x173D) – Again up is in progress. Please look ahead to backup completion earlier than attempting this operation once more.
5950 (0x173E) – The trail doesn’t belong to a cluster shared quantity.
5951 (0x173F) – The cluster shared quantity isn’t regionally mounted on this node.
5952 (0x1740) – The cluster watchdog is terminating.
5953 (0x1741) – A useful resource vetoed a transfer between two nodes as a result of they’re incompatible.
5954 (0x1742) – The request is invalid both as a result of node weight can’t be modified whereas the cluster is in disk-only quorum mode, or as a result of altering the node weight would violate the minimal cluster quorum necessities.
5955 (0x1743) – The useful resource vetoed the decision.
5956 (0x1744) – Useful resource couldn’t begin or run as a result of it couldn’t reserve ample system sources.
5957 (0x1745) – A useful resource vetoed a transfer between two nodes as a result of the vacation spot at present doesn’t have sufficient sources to finish the operation.
5958 (0x1746) – A useful resource vetoed a transfer between two nodes as a result of the supply at present doesn’t have sufficient sources to finish the operation.
5959 (0x1747) – The requested operation can’t be accomplished as a result of the group is queued for an operation.
5960 (0x1748) – The requested operation can’t be accomplished as a result of a useful resource has locked standing.
5961 (0x1749) – The useful resource can’t transfer to a different node as a result of a cluster shared quantity vetoed the operation.
5962 (0x174A) – A node drain is already in progress. This worth was additionally named ERROR_CLUSTER_NODE_EVACUATION_IN_PROGRESS
5963 (0x174B) – Clustered storage isn’t related to the node.
5964 (0x174C) – The disk isn’t configured in a approach for use with CSV. CSV disks should have at the least one partition that’s formatted with NTFS.
5965 (0x174D) – The useful resource should be a part of the Accessible Storage group to finish this motion.
5966 (0x174E) – CSVFS failed operation as quantity is in redirected mode.
5967 (0x174F) – CSVFS failed operation as quantity isn’t in redirected mode.
5968 (0x1750) – Cluster properties can’t be returned presently.
5969 (0x1751) – The clustered disk useful resource accommodates software program snapshot diff space that aren’t supported for Cluster Shared Volumes.
5970 (0x1752) – The operation can’t be accomplished as a result of the useful resource is in upkeep mode.
5971 (0x1753) – The operation can’t be accomplished due to cluster affinity conflicts.
5972 (0x1754) – The operation can’t be accomplished as a result of the useful resource is a duplicate digital machine.