0x00000033: Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.
0x00000034: You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.
0x000000DA: The image file %1 is strong signed, unable to modify.
0x000000DC: This file is checked out or locked for editing by another user.
0x000000DD: The file must be checked out before saving changes.
0x000000DE: The file type being saved or retrieved has been blocked.
0x000000DF: The file size exceeds the limit allowed and cannot be saved.
0x000000E0: Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.
0x000000E1: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
0x000000E2: This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location.
0x00000162: Enterprise Data Protection policy does not allow access to this network resource.
0x00000163: The device hint name buffer is too small to receive the remaining name.
0x00000164: The requested operation was blocked by Enterprise Data Protection policy. For more information, contact your system administrator.
0x00000165: The requested operation cannot be performed because hardware or software configuration of the device does not comply with Enterprise Data Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator.
0x00000238: The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role.
0x00000239: The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required.
0x0000023A: The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines.
0x0000023B: The I/O permissions for the process could not be changed.
0x0000023C: The application terminated as a result of a CTRL+C.
0x0000023E: The exception %s (0x%08lx) occurred in the application at location 0x%08lx.
0x0000023F: The application was unable to start correctly (0x%lx). Click OK to close the application.
0x00000240: The creation of the paging file %hs failed (%lx). The requested size was %ld.
0x00000241: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
0x00000242: No paging file was specified in the system configuration.
0x00000243: A real-mode application issued a floating-point instruction and floating-point hardware is not present.
0x00000244: An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.
0x00000246: An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.
0x00000247: The Unicode character is not defined in the Unicode character set installed on the system.
0x00000248: The paging file cannot be created on a floppy diskette.
0x00000249: The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected.
0x0000024A: This operation is only allowed for the Primary Domain Controller of the domain.
0x0000024B: An attempt was made to acquire a mutant such that its maximum count would have been exceeded.
0x0000024C: A volume has been accessed for which a file system driver is required that has not yet been loaded.
0x00000257: The request must be handled by the stack overflow code.
0x00000258: Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream.
0x00000259: The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation.
0x0000025A: The bucket array must be grown. Retry transaction after doing so.
0x0000025B: The user/kernel marshalling buffer has overflowed.
0x0000025C: The supplied variant structure contains invalid data.
0x0000026B: The specified hardware profile configuration is invalid.
0x0000026C: The specified Plug and Play registry device path is invalid.
0x0000026D: The specified quota list is internally inconsistent with its descriptor.
0x0000026E: The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product.
0x0000026F: The relocation occurred because the DLL %hs occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL.
0x00000270: The application failed to initialize because the window station is shutting down.
0x00000271: The validation process needs to continue on to the next step.
0x00000272: There are no more matches for the current index enumeration.
0x00000273: The range could not be added to the range list because of a conflict.
0x00000274: The server process is running under a SID different than that required by client.
0x00000275: A group marked use for deny only cannot be enabled.
0x000002AD: was corrupted and it has been recovered. Some data might have been lost.
0x000002AE: The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?
0x000002AF: The application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs?
0x000002D3: The arbiter has deferred arbitration of these resources to its parent
0x000002D4: The inserted CardBus device cannot be started because of a configuration error on "%hs".
0x000002D5: The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported.
0x000003F5: The configuration registry key could not be written.
0x000003F6: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.
0x000003F7: The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.
0x000003F8: An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.
0x000003F9: The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.
0x000003FA: Illegal operation attempted on a registry key that has been marked for deletion.
0x000003FB: System could not allocate the required space in a registry log.
0x000003FC: Cannot create a symbolic link in a registry key that already has subkeys or values.
0x000003FD: Cannot create a stable subkey under a volatile parent key.
0x000003FE: A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.
0x0000041B: A stop control has been sent to a service that other running services are dependent on.
0x0000041C: The requested control is not valid for this service.
0x0000041D: The service did not respond to the start or control request in a timely fashion.
0x000004C1: The format of the specified message name is invalid.
0x000004C2: The format of the specified message destination is invalid.
0x000004C3: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
0x000004C4: An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.
0x000004C5: The workgroup or domain name is already in use by another computer on the network.
0x000004EF: The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log.
0x000004F0: The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.
0x000004F1: The system cannot contact a domain controller to service the authentication request. Please try again later.
0x000004F7: The machine is locked and cannot be shut down without the force option.
0x000004F8: You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
0x000004F9: An application-defined callback gave invalid data when called.
0x000004FA: The group policy framework should call the extension in the synchronous foreground policy refresh.
0x00000500: The current thread has already been converted to a fiber.
0x00000501: The current thread has already been converted from a fiber.
0x00000502: The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
0x00000503: Data present in one of the parameters is more than the function can operate on.
0x00000504: An attempt to do an operation on a debug object failed because the object is in the process of being deleted.
0x00000505: An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed.
0x00000506: %1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator.
0x00000507: Insufficient information exists to identify the cause of failure.
0x00000508: The parameter passed to a C runtime function is incorrect.
0x00000509: The operation occurred beyond the valid data length of the file.
0x0000050A: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service.
0x0000050B: The process hosting the driver for this device has been terminated.
0x0000050C: An operation attempted to exceed an implementation-defined limit.
0x0000050D: Either the target process, or the target thread's containing process, is a protected process.
0x0000050E: The service notification client is lagging too far behind the current state of services in the machine.
0x0000050F: To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator.
0x00000510: The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.
0x00000511: You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration.
0x00000512: A thread involved in this operation appears to be unresponsive.
0x00000513: Indicates a particular Security ID may not be assigned as the label of an object.
0x00000514: Not all privileges or groups referenced are assigned to the caller.
0x00000515: Some mapping between account names and security IDs was not done.
0x00000516: No system quota limits are specifically set for this account.
0x00000517: No encryption key is available. A well-known encryption key was returned.
0x00000518: The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.
0x00000572: There is no user session key for the specified logon session.
0x00000573: The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.
0x00000652: Another installation is already in progress. Complete that installation before proceeding with this install.
0x00000653: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.
0x00000654: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
0x00000655: There was an error starting the Windows Installer service user interface. Contact your support personnel.
0x00000656: Error opening installation log file. Verify that the specified log file location exists and that you can write to it.
0x00000657: The language of this installation package is not supported by your system.
0x00000658: Error applying transforms. Verify that the specified transform paths are valid.
0x00000659: This installation is forbidden by system policy. Contact your system administrator.
0x00000663: This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
0x00000664: This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package.
0x00000665: This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
0x00000666: Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
0x00000667: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
0x00000668: Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.
0x00000669: The requested operation completed successfully. The system will be restarted so the changes can take effect.
0x0000066A: The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
0x0000066B: The update package is not permitted by software restriction policy.
0x0000066C: One or more customizations are not permitted by software restriction policy.
0x0000066D: The Windows Installer does not permit installation from a Remote Desktop Connection.
0x0000066E: Uninstallation of the update package is not supported.
0x00000673: Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update.
0x00000674: The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state.
0x00000675: A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.
0x00000676: The app that you are trying to run is not supported on this version of Windows.
0x00000677: The operation was blocked as the process prohibits dynamic code generation.
0x000013C9: The cluster node is already a member of the cluster.
0x000013CA: 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.
0x000013CB: One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
0x000013CC: This operation cannot currently be performed on the cluster group containing the quorum resource.
0x000013CD: The cluster quorum resource is not allowed to have any dependencies.
0x000013D3: The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet.
0x000013D4: This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
0x000013D5: The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
0x000013D7: 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.
0x000013D8: 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.
0x000013D9: No authentication package could be registered with the RPC server.
0x000013DA: 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.
0x000013DB: 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.
0x000013DC: 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.
0x000013DD: A non locker code got a request to reserve the lock for making global updates.
0x000013DE: The quorum disk could not be located by the cluster service.
0x000013DF: The backed up cluster database is possibly corrupt.
0x000013E1: An attempt to modify a resource property failed because it conflicts with another existing property.
0x000013E2: This operation is not supported on a cluster without an Administrator Access Point.
0x00001702: An operation was attempted that is incompatible with the current membership state of the node.
0x00001703: The quorum resource does not contain the quorum log.
0x00001704: The membership engine requested shutdown of the cluster service on this node.
0x00001705: The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
0x00001706: A matching cluster network for the specified IP address could not be found.
0x00001707: The actual data type of the property did not match the expected data type of the property.
0x00001708: 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.
0x00001709: Two or more parameter values specified for a resource's properties are in conflict.
0x0000170A: This computer cannot be made a member of a cluster.
0x0000170B: This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.
0x0000170C: 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.
0x0000170D: The cluster configuration action has already been committed.
0x0000170E: The cluster configuration action could not be rolled back.
0x0000170F: The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.
0x00001710: One or more nodes in the cluster are running a version of Windows that does not support this operation.
0x00001711: The name of the corresponding computer account doesn't match the Network Name for this resource.
0x00001741: A resource vetoed a move between two nodes because they are incompatible.
0x00001742: 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.
0x00001A38: The requested propagation protocol was not registered as a CRM.
0x00001A39: The buffer passed in to PushTransaction or PullTransaction is not in a valid format.
0x00001A3A: The current transaction context associated with the thread is not a valid handle to a transaction object.
0x00001A3B: The specified Transaction object could not be opened, because it was not found.
0x00001A3C: The specified ResourceManager object could not be opened, because it was not found.
0x00001A3D: The specified Enlistment object could not be opened, because it was not found.
0x00001A3E: The specified TransactionManager object could not be opened, because it was not found.
0x00001A3F: The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.
0x00001A40: The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.
0x00001A41: The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior.
0x00001A42: Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.
0x00001A43: The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.
0x00001A44: The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.
0x00001A46: The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.
0x00001A47: The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file.
0x00001A48: This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.
0x00001A49: The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.
0x00001A4A: The transaction does not have a superior enlistment.
0x00001A4B: The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data.
0x00001A90: The function attempted to use a name that is reserved for use by another transaction.
0x00001A91: Transaction support within the specified resource manager is not started or was shut down due to an error.
0x00001A92: The metadata of the RM has been corrupted. The RM will not function.
0x00001A93: The specified directory does not contain a resource manager.
0x00001A95: The remote server or share does not support transacted file operations.
0x00001A97: The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.
0x00001A98: The specified file miniversion was not found for this transacted file open.
0x00001A99: The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.
0x00001A9A: A miniversion may only be opened in the context of the transaction that created it.
0x00001A9B: It is not possible to open a miniversion with modify access.
0x00001A9C: It is not possible to create any more miniversions for this stream.
0x00001A9E: The remote server sent mismatching version number or Fid for a file opened with transactions.
0x00001A9F: The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint.
0x00001AA2: The file can't be recovered because there is a handle still open on it.
0x00001AA3: The transaction outcome is unavailable because the resource manager responsible for it has disconnected.
0x00001AA4: The request was rejected because the enlistment in question is not a superior enlistment.
0x00001AA5: The transactional resource manager is already consistent. Recovery is not needed.
0x00001AA6: The transactional resource manager has already been started.
0x00001AA7: The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.
0x00001AA8: The operation cannot be performed because another transaction is depending on the fact that this property will not change.
0x00001AA9: The operation would involve a single file with two transactional resource managers and is therefore not allowed.
0x00001AAA: The $Txf directory must be empty for this operation to succeed.
0x00001AAB: The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.
0x00001AAC: The operation could not be completed because the transaction manager does not have a log.
0x00001AAD: A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.
0x00001AAE: The transactional metadata attribute on the file or directory is corrupt and unreadable.
0x00001AAF: The encryption operation could not be completed because a transaction is active.
0x00001AB0: This object is not allowed to be opened in a transaction.
0x00001AB1: An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.
0x00001AB2: Memory mapping (creating a mapped section) a remote file under a transaction is not supported.
0x00001AB3: Transaction metadata is already present on this file and cannot be superseded.
0x00001AB4: A transaction scope could not be entered because the scope handler has not been initialized.
0x00001AB5: Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.
0x00001AB6: This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.
0x00001AB7: The request to thaw frozen transactions was ignored because transactions had not previously been frozen.
0x00001AB8: Transactions cannot be frozen because a freeze is already in progress.
0x00001AB9: The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.
0x00001ABA: The savepoint operation failed because files are open on the transaction. This is not permitted.
0x00001ABB: Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.
0x00001ABC: The sparse operation could not be completed because a transaction is active on the file.
0x00001ABD: The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.
0x00001ABE: I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.
0x00001ABF: The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.
0x00001AC0: The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down.
0x00001AC1: The operation could not be completed due to bad clusters on disk.
0x00001AC2: The compression operation could not be completed because a transaction is active on the file.
0x00001AC3: The operation could not be completed because the volume is dirty. Please run chkdsk and try again.
0x00001AC4: The link tracking operation could not be completed because a transaction is active.
0x00001AC5: This operation cannot be performed in a transaction.
0x00001AC6: The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one.
0x00001AC7: The specified operation could not be performed because the resource manager is not enlisted in the transaction.
0x00001B89: The specified terminal connection driver is invalid.
0x00001B8A: This may be because the session is disconnected or does not currently have a user logged on.
0x00001B8B: The requested session is not configured to allow remote control.
0x00001B8C: Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number.
0x00001B8D: Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator.
0x00001B8E: The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.
0x00001B8F: The client you are using is not licensed to use this system. Your logon request is denied.
0x00001B90: The system license has expired. Your logon request is denied.
0x00001B91: Remote control could not be terminated because the specified session is not currently being remotely controlled.
0x00001B92: The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported.
0x00001B93: Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.
0x00002046: The search results exceed the offset range specified.
0x00002047: The directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation.
0x0000206D: The root object must be the head of a naming context. The root object cannot have an instantiated parent.
0x0000206E: The add replica operation cannot be performed. The naming context must be writeable in order to create the replica.
0x0000206F: A reference to an attribute that is not defined in the schema occurred.
0x0000210E: The replication synchronization attempt was abandoned because of a lack of updates.
0x0000210F: The replication operation was terminated because the system is shutting down.
0x00002110: Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.
0x00002111: The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.
0x00002112: The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.
0x00002113: The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.
0x00002114: Schema update failed: An attribute with the same link identifier already exists.
0x00002116: Name translation: Could not find the name or insufficient right to see name.
0x00002117: Name translation: Input name mapped to more than one output name.
0x00002118: Name translation: Input name found, but not the associated output format.
0x00002119: Name translation: Unable to resolve completely, only the domain was found.
0x0000211A: Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.
0x0000211B: Modification of a constructed attribute is not allowed.
0x0000211C: The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
0x0000211D: The replication request has been posted; waiting for reply.
0x0000211E: The requested operation requires a directory service, and none was available.
0x0000211F: The LDAP display name of the class or attribute contains non-ASCII characters.
0x00002120: The requested search operation is only supported for base searches.
0x00002121: The search failed to retrieve attributes from the database.
0x00002122: The schema update operation tried to add a backward link attribute that has no corresponding forward link.
0x00002123: Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object.
0x00002124: Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object.
0x00002125: Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.
0x00002126: Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.
0x00002127: Destination of a cross-domain move is not authoritative for the destination naming context.
0x00002128: Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.
0x00002129: Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.
0x0000212A: Another operation which requires exclusive access to the PDC FSMO is already in progress.
0x0000212B: A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.
0x0000212C: This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move.
0x0000212D: Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.
0x0000212E: A naming context head must be the immediate child of another naming context head, not of an interior node.
0x0000212F: The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)
0x0000213C: Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed.
0x0000213D: Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.
0x0000213E: An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.
0x0000213F: The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.
0x00002140: The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.
0x0000215B: The source object's SID already exists in destination forest.
0x0000215C: The source and destination object must be of the same type.
0x0000215D: Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information.
0x0000215E: Schema information could not be included in the replication request.
0x0000215F: The replication operation could not be completed due to a schema incompatibility.
0x00002160: The replication operation could not be completed due to a previous schema incompatibility.
0x00002161: The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.
0x00002162: The requested domain could not be deleted because there exist domain controllers that still host this domain.
0x00002163: The requested operation can be performed only on a global catalog server.
0x00002164: A local group can only be a member of other local groups in the same domain.
0x00002165: Foreign security principals cannot be members of universal groups.
0x00002166: The attribute is not allowed to be replicated to the GC because of security reasons.
0x00002167: The checkpoint with the PDC could not be taken because there too many modifications being processed currently.
0x00002168: The operation requires that source domain auditing be enabled.
0x00002169: Security principal objects can only be created inside domain naming contexts.
0x0000216A: A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.
0x0000216B: A Filter was passed that uses constructed attributes.
0x0000216C: The unicodePwd attribute value must be enclosed in double quotes.
0x0000216D: Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.
0x0000216E: For security reasons, the operation must be run on the destination DC.
0x0000216F: For security reasons, the source DC must be NT4SP4 or greater.
0x00002170: Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.
0x00002171: Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.
0x00002172: Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.
0x00002173: The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set.
0x00002174: The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain.
0x00002175: The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set.
0x00002176: The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain.
0x00002177: The version of the operating system installed on this server is incompatible with the functional level of the domain or forest.
0x00002178: The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level.
0x00002179: The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level.
0x0000217E: Unable to continue operation because multiple conflicting controls were used.
0x0000217F: Unable to find a valid security descriptor reference domain for this partition.
0x00002180: Schema update failed: The link identifier is reserved.
0x00002181: Schema update failed: There are no link identifiers available.
0x00002182: An account group cannot have a universal group as a member.
0x00002183: Rename or move operations on naming context heads or read-only objects are not allowed.
0x00002184: Move operations on objects in the schema naming context are not allowed.
0x00002185: A system flag has been set on the object and does not allow the object to be moved or renamed.
0x00002186: This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.
0x00002187: Unable to resolve completely, a referral to another forest is generated.
0x00002188: The requested action is not supported on standard server.
0x00002189: Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question.
0x0000218A: The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master.
0x0000218C: The Global catalog server is not in the closest site.
0x0000218D: The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute.
0x0000218E: The Directory Service failed to enter single user mode.
0x0000218F: The Directory Service cannot parse the script because of a syntax error.
0x00002190: The Directory Service cannot process the script because of an error.
0x00002191: The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress).
0x00002192: The directory service binding must be renegotiated due to a change in the server extensions information.
0x0000219D: The requested object has a non-unique identifier and cannot be retrieved.
0x0000219E: Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
0x0000219F: The group cannot be converted due to attribute restrictions on the requested group type.
0x000021A0: Cross-domain move of non-empty basic application groups is not allowed.
0x000021A1: Cross-domain move of non-empty query based application groups is not allowed.
0x000021A2: The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
0x000021A3: The target container for a redirection of a well known object container cannot already be a special container.
0x000021A4: The Directory Service cannot perform the requested operation because a domain rename operation is in progress.
0x000021A5: The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method.
0x000021A6: The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
0x000021A7: The requested operation is not allowed on an object under the system container.
0x000021A8: The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected.
0x000021A9: The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency.
0x000021AA: At this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies.
0x000021AB: The site settings object for the specified site does not exist.
0x000021AC: The local account store does not contain secret material for the specified account.
0x000021AD: Could not find a writable domain controller in the domain.
0x000021AE: The server object for the domain controller does not exist.
0x000021AF: The NTDS Settings object for the domain controller does not exist.
0x000021B0: The requested search operation is not supported for ASQ searches.
0x000021B1: A required audit event could not be generated for the operation.
0x000021B2: The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes.
0x000021B3: The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings.
0x000021B4: The address books are nested too deeply. Failed to build the hierarchy table.
0x000021BF: The replication operation failed because the target object referred by a link value is recycled.
0x000021C0: The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller.
0x000021C1: The functional level of the AD LDS configuration set cannot be lowered to the requested value.
0x000021C2: The functional level of the domain (or forest) cannot be lowered to the requested value.
0x000021C3: The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level.
0x000021C4: The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information.
0x000021C5: The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object.
0x000021C6: The system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site.
0x000021C7: The operation failed because SPN value provided for addition/modification is not unique forest-wide.
0x000021C8: The operation failed because UPN value provided for addition/modification is not unique forest-wide.
0x000021C9: The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present.
0x000021CA: The link value specified was not found, but a link value with that key was found.
0x000035FC: IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key.
0x0000361D: Failed to obtain security function table dispatch address from SSPI.
0x0000361E: Failed to query Kerberos package to obtain max token size.
0x0000361F: Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.
0x00003620: Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).
0x00003621: Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.
0x00003624: Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.
0x00003702: The activation context activation stack for the running thread of execution is corrupt.
0x00003703: The application isolation metadata for this process or thread has become corrupt.
0x00003704: The activation context being deactivated is not the most recently activated one.
0x00003705: The activation context being deactivated is not active for the current thread of execution.
0x00003706: The activation context being deactivated has already been deactivated.
0x00003707: A component used by the isolation facility has requested to terminate the process.
0x00003708: A kernel mode component is releasing a reference on an activation context.
0x00003709: The activation context of system default assembly could not be generated.
0x0000370A: The value of an attribute in an identity is not within the legal range.
0x0000370B: The name of an attribute in an identity is not within the legal range.
0x0000370C: An identity contains two definitions for the same attribute.
0x0000370D: The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.
0x0000370E: A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found.
0x0000370F: The public key token does not correspond to the public key specified.
0x00003AA3: The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query.
0x00003AA6: An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation.
0x00003AA7: Can't perform a step operation from a term that does not represent an element set.
0x00003AA8: Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants.
0x00003AA9: A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceeding node set can be evaluated.
0x00003B60: The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision 1 specification.
0x00003B61: The monitor's VCP Version (0xDF) VCP code returned an invalid version value.
0x00003B62: The monitor does not comply with the MCCS specification it claims to support.
0x00003B63: The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.
0x00003B64: The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.
0x00003B65: An internal Monitor Configuration API error occurred.
0x00003B66: The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
0x00003B67: The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
0x00003B92: The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.