Windows Errors 3

303 views

0 from 0 vots

Vote this article

4994	0x1382	Access ended
4995	0x1383	Log on to network
4996	0x1384	Logon denied
4997	0x1385	Program Message Time
4999	0x1387	Account unlocked by administrator
5000	0x1388	Log off network
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.
5055	0x13BF	Mar
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.
5090	0x13E2	Spain
5091	0x13E3	Denmark
5092	0x13E4	Sweden
5093	0x13E5	Norway
5094	0x13E6	Germany
5095	0x13E7	Australia
5096	0x13E8	Japan
5097	0x13E9	Korea
5098	0x13EA	China (PRC)
5099	0x13EB	Taiwan
5100	0x13EC	Asia
5101	0x13ED	Portugal
5102	0x13EE	Finland
5103	0x13EF	Arabic
5104	0x13F0	Hebrew
5153	0x1421	The UPS service is about to perform final shut down.
5170	0x1432	The Workstation must be started with the NET START command.
5175	0x1437	Remote IPC
5176	0x1438	Remote Admin
5177	0x1439	Default share
5178	0x143A	User Profiles
5291	0x14AB	Never
5292	0x14AC	Never
5293	0x14AD	Never
5295	0x14AF	NET.HLP
5296	0x14B0	NET.HLP
5297	0x14B1	Deny
5300	0x14B4	The network control block (NCB) request completed successfully. The NCB is the data.
5301	0x14B5	Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data.
5302	0x14B6	The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data.
5303	0x14B7	The command specified in the network control block (NCB) is illegal. The NCB is the data.
5304	0x14B8	The message correlator specified in the network control block (NCB) is invalid. The NCB is the data.
5305	0x14B9	A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data.
5306	0x14BA	An incomplete network control block (NCB) message was received. The NCB is the data.
5307	0x14BB	The buffer address specified in the network control block (NCB) is illegal. The NCB is the data.
5308	0x14BC	The session number specified in the network control block (NCB) is not active. The NCB is the data.
5309	0x14BD	No resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data.
5310	0x14BE	The session specified in the network control block (NCB) was closed. The NCB is the data.
5311	0x14BF	The network control block (NCB) command was canceled. The NCB is the data.
5312	0x14C0	The message segment specified in the network control block (NCB) is illogical. The NCB is the data.
5313	0x14C1	The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data.
5314	0x14C2	The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data.
5315	0x14C3	The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data.
5316	0x14C4	A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data.
5317	0x14C5	The local session table is full. The network control block (NCB) request was refused. The NCB is the data.
5318	0x14C6	A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data.
5319	0x14C7	The name number specified in the network control block (NCB) is illegal. The NCB is the data.
5320	0x14C8	The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data.
5321	0x14C9	The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data.
5322	0x14CA	The name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data.
5323	0x14CB	The name specified in the network control block (NCB) has been deleted. The NCB is the data.
5324	0x14CC	The session specified in the network control block (NCB) ended abnormally. The NCB is the data.
5325	0x14CD	The network protocol has detected two or more identical names on the network. The network control block (NCB) is the data.
5326	0x14CE	An unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data.
5333	0x14D5	The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data.
5334	0x14D6	There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data.
5335	0x14D7	The adapter number specified in the network control block (NCB) is illegal. The NCB is the data.
5336	0x14D8	The network control block (NCB) command completed while a cancel was occurring. The NCB is the data.
5337	0x14D9	The name specified in the network control block (NCB) is reserved. The NCB is the data.
5338	0x14DA	The network control block (NCB) command is not valid to cancel. The NCB is the data.
5351	0x14E7	There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data.
5352	0x14E8	There has been a network adapter error. The only NetBIOS command that may be issued is an NCB RESET. The network control block (NCB) is the data.
5354	0x14EA	The maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data.
5356	0x14EC	The requested resources are not available. The network control block (NCB) request was refused. The NCB is the data.
5364	0x14F4	A system error has occurred. The network control block (NCB) request was refused. The NCB is the data.
5365	0x14F5	A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5366	0x14F6	A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5367	0x14F7	A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5368	0x14F8	An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5369	0x14F9	An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data.
5370	0x14FA	An unrecognized network control block (NCB) return code was received. The NCB is the data.
5380	0x1504	A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data.
5381	0x1505	The network control block (NCB) command is still pending. The NCB is the data.
5509	0x1585	Windows could not be started as configured. A previous working configuration was used instead.
5600	0x15E0	Could not share the User or Script path.
5601	0x15E1	The password for this computer is not found in the local security database.
5602	0x15E2	An internal error occurred while accessing the computer's local or network security database.
5728	0x1660	Could not load any transport.
5739	0x166B	This domain has more global groups than can be replicated to a LanMan BDC. Either delete some of your global groups or remove the LanMan BDCs from the domain.
5742	0x166E	Service failed to retrieve messages needed to boot remote boot clients.
5743	0x166F	Service experienced a severe error and can no longer provide remote boot for 3Com 3Start remote boot clients.
5744	0x1670	Service experienced a severe system error and will shut itself down.
5760	0x1680	Service experienced error evaluating RPL configurations.
5761	0x1681	Service experienced error creating RPL profiles for all configurations.
5762	0x1682	Service experienced error accessing registry.
5763	0x1683	Service experienced error replacing possibly outdated RPLDISK.SYS.
5764	0x1684	Service experienced error adding security accounts or setting file permissions. These accounts are the RPLUSER local group and the user accounts for the individual RPL workstations.
5765	0x1685	Service failed to back up its database.
5766	0x1686	Service failed to initialize from its database. The database may be missing or corrupted. Service will attempt restoring the database from the backup.
5767	0x1687	Service failed to restore its database from the backup. Service will not start.
5768	0x1688	Service successfully restored its database from the backup.
5769	0x1689	Service failed to initialize from its restored database. Service will not start.
5771	0x168B	The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is attempting to convert it to NT 4.0 format. The JETCONV converter will write to the Application event log when it is finished.
5806	0x16AE	Dynamic DNS updates have been manually disabled on this domain controller. USER ACTION Reconfigure this domain controller to use dynamic DNS updates or manually add the DNS records from the file 'SystemRoot\System32\Config\Netlogon.dns' to the DNS database.
5808	0x16B0	The deregistration of some DNS domain controller locator records was aborted at the time of this domain controller demotion because the DNS deregistrations took too long. USER ACTION Manually delete the DNS records listed in the file 'SystemRoot\System32\Config\Netlogon.dns' from the DNS database.
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
6000	0x1770	The specified file could not be encrypted.
6001	0x1771	The specified file could not be decrypted.
6002	0x1772	The specified file is encrypted and the user does not have the ability to decrypt it.
6003	0x1773	There is no valid encryption recovery policy configured for this system.
6004	0x1774	The required encryption driver is not loaded for this system.
6005	0x1775	The file was encrypted with a different encryption driver than is currently loaded.
6006	0x1776	There are no EFS keys defined for the user.
6007	0x1777	The specified file is not encrypted.
6008	0x1778	The specified file is not in the defined EFS export format.
6009	0x1779	The specified file is read only.
6010	0x177A	The directory has been disabled for encryption.
6011	0x177B	The server is not trusted for remote encryption operation.
6012	0x177C	Recovery policy configured for this system contains invalid recovery certificate.
6013	0x177D	The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file.
6014	0x177E	The disk partition does not support file encryption.
6015	0x177F	This machine is disabled for file encryption.
6016	0x1780	A newer system is required to decrypt this encrypted file.
6017	0x1781	The remote server sent an invalid response for a file being opened with Client Side Encryption.
6018	0x1782	Client Side Encryption is not supported by the remote server even though it claims to support it.
6019	0x1783	File is encrypted and should be opened in Client Side Encryption mode.
6020	0x1784	A new encrypted file is being created and a $EFS needs to be provided.
6021	0x1785	The SMB client requested a CSE FSCTL on a non-CSE file.
6118	0x17E6	The list of servers for this workgroup is not currently available
6200	0x1838	The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts.
6600	0x19C8	Log service encountered an invalid log sector.
6601	0x19C9	Log service encountered a log sector with invalid block parity.
6602	0x19CA	Log service encountered a remapped log sector.
6603	0x19CB	Log service encountered a partial or incomplete log block.
6604	0x19CC	Log service encountered an attempt access data outside the active log range.
6605	0x19CD	Log service user marshalling buffers are exhausted.
6606	0x19CE	Log service encountered an attempt read from a marshalling area with an invalid read context.
6607	0x19CF	Log service encountered an invalid log restart area.
6608	0x19D0	Log service encountered an invalid log block version.
6609	0x19D1	Log service encountered an invalid log block.
6610	0x19D2	Log service encountered an attempt to read the log with an invalid read mode.
6611	0x19D3	Log service encountered a log stream with no restart area.
6612	0x19D4	Log service encountered a corrupted metadata file.
6613	0x19D5	Log service encountered a metadata file that could not be created by the log file system.
6614	0x19D6	Log service encountered a metadata file with inconsistent data.
6615	0x19D7	Log service encountered an attempt to erroneous allocate or dispose reservation space.
6616	0x19D8	Log service cannot delete log file or file system container.
6617	0x19D9	Log service has reached the maximum allowable containers allocated to a log file.
6618	0x19DA	Log service has attempted to read or write backward past the start of the log.
6619	0x19DB	Log policy could not be installed because a policy of the same type is already present.
6620	0x19DC	Log policy in question was not installed at the time of the request.
6621	0x19DD	The installed set of policies on the log is invalid.
6622	0x19DE	A policy on the log in question prevented the operation from completing.
6623	0x19DF	Log space cannot be reclaimed because the log is pinned by the archive tail.
6624	0x19E0	Log record is not a record in the log file.
6625	0x19E1	Number of reserved log records or the adjustment of the number of reserved log records is invalid.
6626	0x19E2	Reserved log space or the adjustment of the log space is invalid.
6627	0x19E3	An new or existing archive tail or base of the active log is invalid.
6628	0x19E4	Log space is exhausted.
6629	0x19E5	The log could not be set to the requested size.
6630	0x19E6	Log is multiplexed, no direct writes to the physical log is allowed.
6631	0x19E7	The operation failed because the log is a dedicated log.
6632	0x19E8	The operation requires an archive context.
6633	0x19E9	Log archival is in progress.
6634	0x19EA	The operation requires a non-ephemeral log, but the log is ephemeral.
6635	0x19EB	The log must have at least two containers before it can be read from or written to.
6636	0x19EC	A log client has already registered on the stream.
6637	0x19ED	A log client has not been registered on the stream.
6638	0x19EE	A request has already been made to handle the log full condition.
6639	0x19EF	Log service enountered an error when attempting to read from a log container.
6640	0x19F0	Log service enountered an error when attempting to write to a log container.
6641	0x19F1	Log service enountered an error when attempting open a log container.
6642	0x19F2	Log service enountered an invalid container state when attempting a requested action.
6643	0x19F3	Log service is not in the correct state to perform a requested action.
6644	0x19F4	Log space cannot be reclaimed because the log is pinned.
6645	0x19F5	Log metadata flush failed.
6646	0x19F6	Security on the log and its containers is inconsistent.
6647	0x19F7	Records were appended to the log or reservation changes were made, but the log could not be flushed.
6648	0x19F8	The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.
6700	0x1A2C	The transaction handle associated with this operation is not valid.
6701	0x1A2D	The requested operation was made in the context of a transaction that is no longer active.
6702	0x1A2E	The requested operation is not valid on the Transaction object in its current state.
6703	0x1A2F	The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.
6704	0x1A30	It is too late to perform the requested operation, since the Transaction has already been aborted.
6705	0x1A31	It is too late to perform the requested operation, since the Transaction has already been committed.
6706	0x1A32	The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.
6707	0x1A33	The specified ResourceManager made no changes or updates to the resource under this transaction.
6708	0x1A34	The resource manager has attempted to prepare a transaction that it has not successfully joined.
6709	0x1A35	The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow.
6710	0x1A36	The RM tried to register a protocol that already exists.
6711	0x1A37	The attempt to propagate the Transaction failed.
6712	0x1A38	The requested propagation protocol was not registered as a CRM.
6713	0x1A39	The buffer passed in to PushTransaction or PullTransaction is not in a valid format.
6714	0x1A3A	The current transaction context associated with the thread is not a valid handle to a transaction object.
6715	0x1A3B	The specified Transaction object could not be opened, because it was not found.
6716	0x1A3C	The specified ResourceManager object could not be opened, because it was not found.
6717	0x1A3D	The specified Enlistment object could not be opened, because it was not found.
6718	0x1A3E	The specified TransactionManager object could not be opened, because it was not found.
6719	0x1A3F	The specified ResourceManager was unable to create an enlistment, because its associated TransactionManager is not online.
6720	0x1A40	The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.
6721	0x1A41	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 Transactoin can be enlisted on as a superior.
6722	0x1A42	Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.
6723	0x1A43	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.
6724	0x1A44	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.
6725	0x1A45	Implicit transaction are not supported.
6726	0x1A46	The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.
6800	0x1A90	The function attempted to use a name that is reserved for use by another transaction.
6801	0x1A91	Transaction support within the specified file system resource manager is not started or was shutdown due to an error.
6802	0x1A92	The metadata of the RM has been corrupted. The RM will not function.
6803	0x1A93	The specified directory does not contain a resource manager.
6805	0x1A95	The remote server or share does not support transacted file operations.
6806	0x1A96	The requested log size is invalid.
6807	0x1A97	The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.
6808	0x1A98	The specified file miniversion was not found for this transacted file open.
6809	0x1A99	The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.
6810	0x1A9A	A miniversion may only be opened in the context of the transaction that created it.
6811	0x1A9B	It is not possible to open a miniversion with modify access.
6812	0x1A9C	It is not possible to create any more miniversions for this stream.
6814	0x1A9E	The remote server sent mismatching version number or Fid for a file opened with transactions.
6815	0x1A9F	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.
6816	0x1AA0	There is no transaction metadata on the file.
6817	0x1AA1	The log data is corrupt.
6818	0x1AA2	The file can't be recovered because there is a handle still open on it.
6819	0x1AA3	The transaction outcome is unavailable because the resource manager responsible for it has disconnected.
6820	0x1AA4	The request was rejected because the enlistment in question is not a superior enlistment.
6821	0x1AA5	The transactional resource manager is already consistent. Recovery is not needed.
6822	0x1AA6	The transactional resource manager has already been started.
6823	0x1AA7	The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.
6824	0x1AA8	The operation cannot be performed because another transaction is depending on the fact that this property will not change.
6825	0x1AA9	The operation would involve a single file with two transactional resource managers and is therefore not allowed.
6826	0x1AAA	The $Txf directory must be empty for this operation to succeed.
6827	0x1AAB	The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.
6828	0x1AAC	The operation could not be completed because the transaction manager does not have a log.
6829	0x1AAD	A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.
6830	0x1AAE	The transactional metadata attribute on the file or directory is corrupt and unreadable.
6831	0x1AAF	The encryption operation could not be completed because a transaction is active.
6832	0x1AB0	This object is not allowed to be opened in a transaction.
6833	0x1AB1	An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.
6834	0x1AB2	Memory mapping (creating a mapped section) a remote file under a transaction is not supported.
6835	0x1AB3	Transaction metadata is already present on this file and cannot be superseded.
6836	0x1AB4	A transaction scope could not be entered because the scope handler has not been initialized.
6837	0x1AB5	Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.
6838	0x1AB6	This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.
6839	0x1AB7	The request to thaw frozen transactions was ignored because transactions had not previously been frozen.
6840	0x1AB8	Transactions cannot be frozen because a freeze is already in progress.
6841	0x1AB9	The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.
6842	0x1ABA	The savepoint operation failed because files are open on the transaction. This is not permitted.
6843	0x1ABB	Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.
6844	0x1ABC	The sparse operation could not be completed because a transaction is active on the file.
6845	0x1ABD	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.
6846	0x1ABE	I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.
6847	0x1ABF	The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.
6848	0x1AC0	The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down.
6849	0x1AC1	The operation could not be completed due to bad clusters on disk.
6850	0x1AC2	The compression operation could not be completed because a transaction is active on the file.
6851	0x1AC3	The operation could not be completed because the volume is dirty. Please run chkdsk and try again.
6852	0x1AC4	The link tracking operation could not be completed because a transaction is active.
6853	0x1AC5	This operation cannot be performed in a transaction.
7001	0x1B59	The specified session name is invalid.
7002	0x1B5A	The specified protocol driver is invalid.
7003	0x1B5B	The specified protocol driver was not found in the system path.
7004	0x1B5C	The specified terminal connection driver was not found in the system path.
7005	0x1B5D	A registry key for event logging could not be created for this session.
7006	0x1B5E	A service with the same name already exists on the system.
7007	0x1B5F	A close operation is pending on the session.
7008	0x1B60	There are no free output buffers available.
7009	0x1B61	The MODEM.INF file was not found.
7010	0x1B62	The modem name was not found in MODEM.INF.
7011	0x1B63	The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.
7012	0x1B64	The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.
7013	0x1B65	Carrier detect has failed or carrier has been dropped due to disconnect.
7014	0x1B66	Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.
7015	0x1B67	Busy signal detected at remote site on callback.
7016	0x1B68	Voice detected at remote site on callback.
7017	0x1B69	Transport driver error
7022	0x1B6E	The specified session cannot be found.
7023	0x1B6F	The specified session name is already in use.
7024	0x1B70	The requested operation cannot be completed because the terminal connection is currently busy processing a connect, disconnect, reset, or delete operation.
7025	0x1B71	An attempt has been made to connect to a session whose video mode is not supported by the current client.
7035	0x1B7B	The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.
7037	0x1B7D	Your interactive logon privilege has been disabled. Please contact your administrator.
7038	0x1B7E	The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access.
7040	0x1B80	The client failed to respond to the server connect message.
7041	0x1B81	Disconnecting the console session is not supported.
7042	0x1B82	Reconnecting a disconnected session to the console is not supported.
7044	0x1B84	The request to control another session remotely was denied.
7045	0x1B85	The requested session access is denied.
7049	0x1B89	The specified terminal connection driver is invalid.
7050	0x1B8A	The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on.
7051	0x1B8B	The requested session is not configured to allow remote control.
7052	0x1B8C	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.
7053	0x1B8D	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.
7054	0x1B8E	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.
7055	0x1B8F	The client you are using is not licensed to use this system. Your logon request is denied.
7056	0x1B90	The system license has expired. Your logon request is denied.
7057	0x1B91	Remote control could not be terminated because the specified session is not currently being remotely controlled.
7058	0x1B92	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.
7059	0x1B93	Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.
7060	0x1B94	Remote logins are currently disabled.
7061	0x1B95	You do not have the proper encryption level to access this Session.
7062	0x1B96	The user s\\s is currently logged on to this computer. Only the current user or an administrator can log on to this computer.
7063	0x1B97	The user s\\s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact s\\s and have them log off.
7064	0x1B98	Unable to log you on because of an account restriction.
7066	0x1B9A	The Client Drive Mapping Service Has Connected on Terminal Connection.
7067	0x1B9B	The Client Drive Mapping Service Has Disconnected on Terminal Connection.
7068	0x1B9C	The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.
7069	0x1B9D	The target session is incompatible with the current session.
8001	0x1F41	The file replication service API was called incorrectly.
8002	0x1F42	The file replication service cannot be started.
8003	0x1F43	The file replication service cannot be stopped.
8004	0x1F44	The file replication service API terminated the request. The event log may have more information.
8005	0x1F45	The file replication service terminated the request. The event log may have more information.
8006	0x1F46	The file replication service cannot be contacted. The event log may have more information.
8007	0x1F47	The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.
8008	0x1F48	The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
8009	0x1F49	The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information.
8010	0x1F4A	The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information.
8011	0x1F4B	The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.
8012	0x1F4C	The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information.
8013	0x1F4D	The file replication service cannot populate the system volume because of an internal error. The event log may have more information.
8014	0x1F4E	The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.
8015	0x1F4F	The file replication service cannot process the request. The system volume is busy with a previous request.
8016	0x1F50	The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.
8017	0x1F51	The file replication service detected an invalid parameter.
8200	0x2008	An error occurred while installing the directory service. For more information, see the event log.
8201	0x2009	The directory service evaluated group memberships locally.
8202	0x200A	The specified directory service attribute or value does not exist.
8203	0x200B	The attribute syntax specified to the directory service is invalid.
8204	0x200C	The attribute type specified to the directory service is not defined.
8205	0x200D	The specified directory service attribute or value already exists.
8206	0x200E	The directory service is busy.
8207	0x200F	The directory service is unavailable.
8208	0x2010	The directory service was unable to allocate a relative identifier.
8209	0x2011	The directory service has exhausted the pool of relative identifiers.
8210	0x2012	The requested operation could not be performed because the directory service is not the master for that type of operation.
8211	0x2013	The directory service was unable to initialize the subsystem that allocates relative identifiers.
8212	0x2014	The requested operation did not satisfy one or more constraints associated with the class of the object.
8213	0x2015	The directory service can perform the requested operation only on a leaf object.
8214	0x2016	The directory service cannot perform the requested operation on the RDN attribute of an object.
8215	0x2017	The directory service detected an attempt to modify the object class of an object.
8216	0x2018	The requested cross-domain move operation could not be performed.
8217	0x2019	Unable to contact the global catalog server.
8218	0x201A	The policy object is shared and can only be modified at the root.
8219	0x201B	The policy object does not exist.
8220	0x201C	The requested policy information is only in the directory service.
8221	0x201D	A domain controller promotion is currently active.
8222	0x201E	A domain controller promotion is not currently active
8224	0x2020	An operations error occurred.
8225	0x2021	A protocol error occurred.
8226	0x2022	The time limit for this request was exceeded.
8227	0x2023	The size limit for this request was exceeded.
8228	0x2024	The administrative limit for this request was exceeded.
8229	0x2025	The compare response was false.
8230	0x2026	The compare response was true.
8231	0x2027	The requested authentication method is not supported by the server.
8232	0x2028	A more secure authentication method is required for this server.
8233	0x2029	Inappropriate authentication.
8234	0x202A	The authentication mechanism is unknown.
8235	0x202B	A referral was returned from the server.
8236	0x202C	The server does not support the requested critical extension.
8237	0x202D	This request requires a secure connection.
8238	0x202E	Inappropriate matching.
8239	0x202F	A constraint violation occurred.
8240	0x2030	There is no such object on the server.
8241	0x2031	There is an alias problem.
8242	0x2032	An invalid dn syntax has been specified.
8243	0x2033	The object is a leaf object.
8244	0x2034	There is an alias dereferencing problem.
8245	0x2035	The server is unwilling to process the request.
8246	0x2036	A loop has been detected.
8247	0x2037	There is a naming violation.
8248	0x2038	The result set is too large.
8249	0x2039	The operation affects multiple DSAs
8250	0x203A	The server is not operational.
8251	0x203B	A local error has occurred.
8252	0x203C	An encoding error has occurred.
8253	0x203D	A decoding error has occurred.
8254	0x203E	The search filter cannot be recognized.
8255	0x203F	One or more parameters are illegal.
8256	0x2040	The specified method is not supported.
8257	0x2041	No results were returned.
8258	0x2042	The specified control is not supported by the server.
8259	0x2043	A referral loop was detected by the client.
8260	0x2044	The preset referral limit was exceeded.
8261	0x2045	The search requires a SORT control.
8262	0x2046	The search results exceed the offset range specified.
8301	0x206D	The root object must be the head of a naming context. The root object cannot have an instantiated parent.
8302	0x206E	The add replica operation cannot be performed. The naming context must be writeable in order to create the replica.
8303	0x206F	A reference to an attribute that is not defined in the schema occurred.
8304	0x2070	The maximum size of an object has been exceeded.
8305	0x2071	An attempt was made to add an object to the directory with a name that is already in use.
8306	0x2072	An attempt was made to add an object of a class that does not have an RDN defined in the schema.
8307	0x2073	An attempt was made to add an object using an RDN that is not the RDN defined in the schema.
8308	0x2074	None of the requested attributes were found on the objects.
8309	0x2075	The user buffer is too small.
8310	0x2076	The attribute specified in the operation is not present on the object.
8311	0x2077	Illegal modify operation. Some aspect of the modification is not permitted.
8312	0x2078	The specified object is too large.
8313	0x2079	The specified instance type is not valid.
8314	0x207A	The operation must be performed at a master DSA.
8315	0x207B	The object class attribute must be specified.
8316	0x207C	A required attribute is missing.
8317	0x207D	An attempt was made to modify an object to include an attribute that is not legal for its class.
8318	0x207E	The specified attribute is already present on the object.
8320	0x2080	The specified attribute is not present, or has no values.
8321	0x2081	Multiple values were specified for an attribute that can have only one value.
8322	0x2082	A value for the attribute was not in the acceptable range of values.
8323	0x2083	The specified value already exists.
8324	0x2084	The attribute cannot be removed because it is not present on the object.
8325	0x2085	The attribute value cannot be removed because it is not present on the object.
8326	0x2086	The specified root object cannot be a subref.
8327	0x2087	Chaining is not permitted.
8328	0x2088	Chained evaluation is not permitted.
8329	0x2089	The operation could not be performed because the object's parent is either uninstantiated or deleted.
8330	0x208A	Having a parent that is an alias is not permitted. Aliases are leaf objects.
8331	0x208B	The object and parent must be of the same type, either both masters or both replicas.
8332	0x208C	The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object.
8333	0x208D	Directory object not found.
8334	0x208E	The aliased object is missing.
8335	0x208F	The object name has bad syntax.
8336	0x2090	It is not permitted for an alias to refer to another alias.
8337	0x2091	The alias cannot be dereferenced.
8338	0x2092	The operation is out of scope.
8339	0x2093	The operation cannot continue because the object is in the process of being removed.
8340	0x2094	The DSA object cannot be deleted.
8341	0x2095	A directory service error has occurred.
8342	0x2096	The operation can only be performed on an internal master DSA object.
8343	0x2097	The object must be of class DSA.
8344	0x2098	Insufficient access rights to perform the operation.
8345	0x2099	The object cannot be added because the parent is not on the list of possible superiors.
8346	0x209A	Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM).
8347	0x209B	The name has too many parts.
8348	0x209C	The name is too long.
8349	0x209D	The name value is too long.
8350	0x209E	The directory service encountered an error parsing a name.
8351	0x209F	The directory service cannot get the attribute type for a name.
8352	0x20A0	The name does not identify an object; the name identifies a phantom.
8353	0x20A1	The security descriptor is too short.
8354	0x20A2	The security descriptor is invalid.
8355	0x20A3	Failed to create name for deleted object.
8356	0x20A4	The parent of a new subref must exist.
8357	0x20A5	The object must be a naming context.
8358	0x20A6	It is not permitted to add an attribute which is owned by the system.
8359	0x20A7	The class of the object must be structural; you cannot instantiate an abstract class.
8360	0x20A8	The schema object could not be found.
8361	0x20A9	A local object with this GUID (dead or alive) already exists.
8362	0x20AA	The operation cannot be performed on a back link.
8363	0x20AB	The cross reference for the specified naming context could not be found.
8364	0x20AC	The operation could not be performed because the directory service is shutting down.
8365	0x20AD	The directory service request is invalid.
8366	0x20AE	The role owner attribute could not be read.
8367	0x20AF	The requested FSMO operation failed. The current FSMO holder could not be contacted.
8368	0x20B0	Modification of a DN across a naming context is not permitted.
8369	0x20B1	The attribute cannot be modified because it is owned by the system.
8370	0x20B2	Only the replicator can perform this function.
8371	0x20B3	The specified class is not defined.
8372	0x20B4	The specified class is not a subclass.
8373	0x20B5	The name reference is invalid.
8374	0x20B6	A cross reference already exists.
8375	0x20B7	It is not permitted to delete a master cross reference.
8376	0x20B8	Subtree notifications are only supported on NC heads.
8377	0x20B9	Notification filter is too complex.
8378	0x20BA	Schema update failed: duplicate RDN.
8379	0x20BB	Schema update failed: duplicate OID.
8380	0x20BC	Schema update failed: duplicate MAPI identifier.
8381	0x20BD	Schema update failed: duplicate schema-id GUID.
8382	0x20BE	Schema update failed: duplicate LDAP display name.
8383	0x20BF	Schema update failed: range-lower less than range upper.
8384	0x20C0	Schema update failed: syntax mismatch.
8385	0x20C1	Schema deletion failed: attribute is used in must-contain.
8386	0x20C2	Schema deletion failed: attribute is used in may-contain.
8387	0x20C3	Schema update failed: attribute in may-contain does not exist.
8388	0x20C4	Schema update failed: attribute in must-contain does not exist.
8389	0x20C5	Schema update failed: class in aux-class list does not exist or is not an auxiliary class.
8390	0x20C6	Schema update failed: class in poss-superiors does not exist.
8391	0x20C7	Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules.
8392	0x20C8	Schema update failed: Rdn-Att-Id has wrong syntax.
8393	0x20C9	Schema deletion failed: class is used as auxiliary class.
8394	0x20CA	Schema deletion failed: class is used as sub class.
8395	0x20CB	Schema deletion failed: class is used as poss superior.
8396	0x20CC	Schema update failed in recalculating validation cache.
8397	0x20CD	The tree deletion is not finished. The request must be made again to continue deleting the tree.
8398	0x20CE	The requested delete operation could not be performed.
8399	0x20CF	Cannot read the governs class identifier for the schema record.
8400	0x20D0	The attribute schema has bad syntax.
8401	0x20D1	The attribute could not be cached.
8402	0x20D2	The class could not be cached.
8403	0x20D3	The attribute could not be removed from the cache.
8404	0x20D4	The class could not be removed from the cache.
8405	0x20D5	The distinguished name attribute could not be read.
8406	0x20D6	No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest.
8407	0x20D7	The instance type attribute could not be retrieved.
8408	0x20D8	An internal error has occurred.
8409	0x20D9	A database error has occurred.
8410	0x20DA	The attribute GOVERNSID is missing.
8411	0x20DB	An expected attribute is missing.
8412	0x20DC	The specified naming context is missing a cross reference.
8413	0x20DD	A security checking error has occurred.
8414	0x20DE	The schema is not loaded.
8415	0x20DF	Schema allocation failed. Please check if the machine is running low on memory.
8416	0x20E0	Failed to obtain the required syntax for the attribute schema.
8417	0x20E1	The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.
8418	0x20E2	The replication operation failed because of a schema mismatch between the servers involved.
8419	0x20E3	The DSA object could not be found.
8420	0x20E4	The naming context could not be found.
8421	0x20E5	The naming context could not be found in the cache.
8422	0x20E6	The child object could not be retrieved.
8423	0x20E7	The modification was not permitted for security reasons.
8424	0x20E8	The operation cannot replace the hidden record.
8425	0x20E9	The hierarchy file is invalid.
8426	0x20EA	The attempt to build the hierarchy table failed.
8427	0x20EB	The directory configuration parameter is missing from the registry.
8428	0x20EC	The attempt to count the address book indices failed.
8429	0x20ED	The allocation of the hierarchy table failed.
8430	0x20EE	The directory service encountered an internal failure.
8431	0x20EF	The directory service encountered an unknown failure.
8432	0x20F0	A root object requires a class of 'top'.
8433	0x20F1	This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.
8434	0x20F2	The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.
8435	0x20F3	The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.
8436	0x20F4	The replication operation failed.
8437	0x20F5	An invalid parameter was specified for this replication operation.
8438	0x20F6	The directory service is too busy to complete the replication operation at this time.
8439	0x20F7	The distinguished name specified for this replication operation is invalid.
8440	0x20F8	The naming context specified for this replication operation is invalid.
8441	0x20F9	The distinguished name specified for this replication operation already exists.
8442	0x20FA	The replication system encountered an internal error.
8443	0x20FB	The replication operation encountered a database inconsistency.
8444	0x20FC	The server specified for this replication operation could not be contacted.
8445	0x20FD	The replication operation encountered an object with an invalid instance type.
8446	0x20FE	The replication operation failed to allocate memory.
8447	0x20FF	The replication operation encountered an error with the mail system.
8448	0x2100	The replication reference information for the target server already exists.
8449	0x2101	The replication reference information for the target server does not exist.
8450	0x2102	The naming context cannot be removed because it is replicated to another server.
8451	0x2103	The replication operation encountered a database error.
8452	0x2104	The naming context is in the process of being removed or is not replicated from the specified server.
8453	0x2105	Replication access was denied.
8454	0x2106	The requested operation is not supported by this version of the directory service.
8455	0x2107	The replication remote procedure call was cancelled.
8456	0x2108	The source server is currently rejecting replication requests.
8457	0x2109	The destination server is currently rejecting replication requests.
8458	0x210A	The replication operation failed due to a collision of object names.
8459	0x210B	The replication source has been reinstalled.
8460	0x210C	The replication operation failed because a required parent object is missing.
8461	0x210D	The replication operation was preempted.
8462	0x210E	The replication synchronization attempt was abandoned because of a lack of updates.
8463	0x210F	The replication operation was terminated because the system is shutting down.
8464	0x2110	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.
8465	0x2111	The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.
8466	0x2112	The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.
8467	0x2113	The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.
8468	0x2114	Schema update failed: An attribute with the same link identifier already exists.
8469	0x2115	Name translation: Generic processing error.
8470	0x2116	Name translation: Could not find the name or insufficient right to see name.
8471	0x2117	Name translation: Input name mapped to more than one output name.
8472	0x2118	Name translation: Input name found, but not the associated output format.
8473	0x2119	Name translation: Unable to resolve completely, only the domain was found.
8474	0x211A	Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.
8475	0x211B	Modification of a constructed attribute is not allowed.
8476	0x211C	The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
8477	0x211D	The replication request has been posted; waiting for reply.
8478	0x211E	The requested operation requires a directory service, and none was available.
8479	0x211F	The LDAP display name of the class or attribute contains non-ASCII characters.
8480	0x2120	The requested search operation is only supported for base searches.
8481	0x2121	The search failed to retrieve attributes from the database.
8482	0x2122	The schema update operation tried to add a backward link attribute that has no corresponding forward link.
8483	0x2123	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.
8484	0x2124	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.
8485	0x2125	Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.
8486	0x2126	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.
8487	0x2127	Destination of a cross-domain move is not authoritative for the destination naming context.
8488	0x2128	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.
8489	0x2129	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.
8490	0x212A	Another operation which requires exclusive access to the PDC FSMO is already in progress.
8491	0x212B	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.
8492	0x212C	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.
8493	0x212D	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.
8494	0x212E	A naming context head must be the immediate child of another naming context head, not of an interior node.
8495	0x212F	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)
8496	0x2130	Destination domain must be in native mode.
8497	0x2131	The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.
8498	0x2132	Cross-domain move of non-empty account groups is not allowed.
8499	0x2133	Cross-domain move of non-empty resource groups is not allowed.
8500	0x2134	The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.
8501	0x2135	Tree deletions starting at an object which has an NC head as a descendant are not allowed.
8502	0x2136	The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.
8503	0x2137	The directory service failed to identify the list of objects to delete while attempting a tree deletion.
8505	0x2139	Only an administrator can modify the membership list of an administrative group.
8506	0x213A	Cannot change the primary group ID of a domain controller account.
8507	0x213B	An attempt is made to modify the base schema.
8508	0x213C	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.
8509	0x213D	Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.
8510	0x213E	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.
8511	0x213F	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.
8512	0x2140	The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.
8513	0x2141	The specified group type is invalid.
8514	0x2142	You cannot nest global groups in a mixed domain if the group is security-enabled.
8515	0x2143	You cannot nest local groups in a mixed domain if the group is security-enabled.
8516	0x2144	A global group cannot have a local group as a member.
8517	0x2145	A global group cannot have a universal group as a member.
8518	0x2146	A universal group cannot have a local group as a member.
8519	0x2147	A global group cannot have a cross-domain member.
8520	0x2148	A local group cannot have another cross domain local group as a member.
8521	0x2149	A group with primary members cannot change to a security-disabled group.
8522	0x214A	The schema cache load failed to convert the string default SD on a class-schema object.
8523	0x214B	Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)
8524	0x214C	The DSA operation is unable to proceed because of a DNS lookup failure.
8525	0x214D	While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.
8526	0x214E	The Security Descriptor attribute could not be read.
8527	0x214F	The object requested was not found, but an object with that key was found.
8528	0x2150	The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1
8529	0x2151	Security Account Manager needs to get the boot password.
8530	0x2152	Security Account Manager needs to get the boot key from floppy disk.
8531	0x2153	Directory Service cannot start.
8532	0x2154	Directory Services could not start.
8533	0x2155	The connection between client and server requires packet privacy or better.
8534	0x2156	The source domain may not be in the same forest as destination.
8535	0x2157	The destination domain must be in the forest.
8536	0x2158	The operation requires that destination domain auditing be enabled.
8537	0x2159	The operation couldn't locate a DC for the source domain.
8538	0x215A	The source object must be a group or user.
8539	0x215B	The source object's SID already exists in destination forest.
8540	0x215C	The source and destination object must be of the same type.
8542	0x215E	Schema information could not be included in the replication request.
8543	0x215F	The replication operation could not be completed due to a schema incompatibility.
8544	0x2160	The replication operation could not be completed due to a previous schema incompatibility.
8545	0x2161	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.
8546	0x2162	The requested domain could not be deleted because there exist domain controllers that still host this domain.
8547	0x2163	The requested operation can be performed only on a global catalog server.
8548	0x2164	A local group can only be a member of other local groups in the same domain.
8549	0x2165	Foreign security principals cannot be members of universal groups.
8550	0x2166	The attribute is not allowed to be replicated to the GC because of security reasons.
8551	0x2167	The checkpoint with the PDC could not be taken because there too many modifications being processed currently.
8552	0x2168	The operation requires that source domain auditing be enabled.
8553	0x2169	Security principal objects can only be created inside domain naming contexts.
8554	0x216A	A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.
8555	0x216B	A Filter was passed that uses constructed attributes.
8556	0x216C	The unicodePwd attribute value must be enclosed in double quotes.
8557	0x216D	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.
8558	0x216E	For security reasons, the operation must be run on the destination DC.
8559	0x216F	For security reasons, the source DC must be NT4SP4 or greater.
8560	0x2170	Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.
8563	0x2173	The version of the operating system installed is incompatible with the current forest functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this forest.
8564	0x2174	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.
8565	0x2175	The version of the operating system installed on this server no longer supports the current forest functional level. You must raise the forest functional level before this server can become a domain controller in this forest.
8566	0x2176	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.
8567	0x2177	The version of the operating system installed on this server is incompatible with the functional level of the domain or forest.
8568	0x2178	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.
8569	0x2179	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.
8570	0x217A	The sort order requested is not supported.
8571	0x217B	The requested name already exists as a unique identifier.
8572	0x217C	The machine account was created pre-NT4. The account needs to be recreated.
8573	0x217D	The database is out of version store.
8574	0x217E	Unable to continue operation because multiple conflicting controls were used.
8575	0x217F	Unable to find a valid security descriptor reference domain for this partition.
8576	0x2180	Schema update failed: The link identifier is reserved.
8577	0x2181	Schema update failed: There are no link identifiers available.
8578	0x2182	An account group cannot have a universal group as a member.
8579	0x2183	Rename or move operations on naming context heads or read-only objects are not allowed.
8580	0x2184	Move operations on objects in the schema naming context are not allowed.
8581	0x2185	A system flag has been set on the object and does not allow the object to be moved or renamed.
8582	0x2186	This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.
8583	0x2187	Unable to resolve completely, a referral to another forest is generated.
8584	0x2188	The requested action is not supported on standard server.
8585	0x2189	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.
8586	0x218A	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.
8587	0x218B	The thread limit for this request was exceeded.
8588	0x218C	The Global catalog server is not in the closest site.
8589	0x218D	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.
8590	0x218E	The Directory Service failed to enter single user mode.
8591	0x218F	The Directory Service cannot parse the script because of a syntax error.
8592	0x2190	The Directory Service cannot process the script because of an error.
8593	0x2191	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).
8594	0x2192	The directory service binding must be renegotiated due to a change in the server extensions information.
8595	0x2193	Operation not allowed on a disabled cross ref.
8596	0x2194	Schema update failed: No values for msDS-IntId are available.
8597	0x2195	Schema update failed: Duplicate msDS-INtId. Retry the operation.
8598	0x2196	Schema deletion failed: attribute is used in rDNAttID.
8599	0x2197	The directory service failed to authorize the request.
8600	0x2198	The Directory Service cannot process the script because it is invalid.
8601	0x2199	The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data.
8602	0x219A	A cross reference is in use locally with the same name.
8603	0x219B	The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest.
8604	0x219C	Writeable NCs prevent this DC from demoting.
8605	0x219D	The requested object has a non-unique identifier and cannot be retrieved.
8606	0x219E	Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
8607	0x219F	The group cannot be converted due to attribute restrictions on the requested group type.
8608	0x21A0	Cross-domain move of non-empty basic application groups is not allowed.
8609	0x21A1	Cross-domain move of non-empty query based application groups is not allowed.
8610	0x21A2	The FSMO role ownership could not be verified because its directory partition has not replicated successfully with atleast one replication partner.
8611	0x21A3	The target container for a redirection of a well known object container cannot already be a special container.
8612	0x21A4	The Directory Service cannot perform the requested operation because a domain rename operation is in progress.
8613	0x21A5	The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method.
8614	0x21A6	The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
8615	0x21A7	The requested operation is not allowed on an object under the system container.
8616	0x21A8	The LDAP servers network send queue has filled up because the client is not processing the results of it's 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.
8617	0x21A9	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.
8618	0x21AA	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.
8619	0x21AB	The site settings object for the specified site does not exist.
8620	0x21AC	The local account store does not contain secret material for the specified account.
8621	0x21AD	Could not find a writable domain controller in the domain.
8622	0x21AE	The server object for the domain controller does not exist.
8623	0x21AF	The NTDS Settings object for the domain controller does not exist.
8624	0x21B0	The requested search operation is not supported for ASQ searches.
8625	0x21B1	A required audit event could not be generated for the operation.
8626	0x21B2	The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes.
8627	0x21B3	The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings.
8628	0x21B4	The address books are nested too deeply. Failed to build the hierarchy table.
9001	0x2329	DNS server unable to interpret format.
9002	0x232A	DNS server failure.
9003	0x232B	DNS name does not exist.
9004	0x232C	DNS request not supported by name server.
9005	0x232D	DNS operation refused.
9006	0x232E	DNS name that ought not exist, does exist.
9007	0x232F	DNS RR set that ought not exist, does exist.
9008	0x2330	DNS RR set that ought to exist, does not exist.
9009	0x2331	DNS server not authoritative for zone.
9010	0x2332	DNS name in update or prereq is not in zone.
9016	0x2338	DNS signature failed to verify.
9017	0x2339	DNS bad key.
9018	0x233A	DNS signature validity expired.
9501	0x251D	No records found for given DNS query.
9502	0x251E	Bad DNS packet.
9503	0x251F	No DNS packet.
9504	0x2520	DNS error, check rcode.
9505	0x2521	Unsecured DNS packet.
9551	0x254F	Invalid DNS type.
9552	0x2550	Invalid IP address.
9553	0x2551	Invalid property.
9554	0x2552	Try DNS operation again later.
9555	0x2553	Record for given name and type is not unique.
9556	0x2554	DNS name does not comply with RFC specifications.
9557	0x2555	DNS name is a fully-qualified DNS name.
9558	0x2556	DNS name is dotted (multi-label).
9559	0x2557	DNS name is a single-part name.
9560	0x2558	DNS name contains an invalid character.
9561	0x2559	DNS name is entirely numeric.
9562	0x255A	The operation requested is not permitted on a DNS root server.
9563	0x255B	The record could not be created because this part of the DNS namespace has been delegated to another server.
9564	0x255C	The DNS server could not find a set of root hints.
9565	0x255D	The DNS server found root hints but they were not consistent across all adapters.
9566	0x255E	The specified value is too small for this parameter.
9567	0x255F	The specified value is too large for this parameter.
9568	0x2560	This operation is not allowed while the DNS server is loading zones in the background. Please try again later.
9569	0x2561	The operation requested is not permitted on against a DNS server running on a read-only DC.
9570	0x2562	No data is allowed to exist underneath a DNAME record.
9601	0x2581	DNS zone does not exist.
9602	0x2582	DNS zone information not available.
9603	0x2583	Invalid operation for DNS zone.
9604	0x2584	Invalid DNS zone configuration.
9605	0x2585	DNS zone has no start of authority (SOA) record.
9606	0x2586	DNS zone has no Name Server (NS) record.
9607	0x2587	DNS zone is locked.
9608	0x2588	DNS zone creation failed.
9609	0x2589	DNS zone already exists.
9610	0x258A	DNS automatic zone already exists.
9611	0x258B	Invalid DNS zone type.
9612	0x258C	Secondary DNS zone requires master IP address.
9613	0x258D	DNS zone not secondary.
9614	0x258E	Need secondary IP address.
9615	0x258F	WINS initialization failed.
9616	0x2590	Need WINS servers.
9617	0x2591	NBTSTAT initialization call failed.
9618	0x2592	Invalid delete of start of authority (SOA)
9619	0x2593	A conditional forwarding zone already exists for that name.
9620	0x2594	This zone must be configured with one or more master DNS server IP addresses.
9621	0x2595	The operation cannot be performed because this zone is shutdown.
9651	0x25B3	Primary DNS zone requires datafile.
9652	0x25B4	Invalid datafile name for DNS zone.
9653	0x25B5	Failed to open datafile for DNS zone.
9654	0x25B6	Failed to write datafile for DNS zone.
9655	0x25B7	Failure while reading datafile for DNS zone.
9701	0x25E5	DNS record does not exist.
9702	0x25E6	DNS record format error.
9703	0x25E7	Node creation failure in DNS.
9704	0x25E8	Unknown DNS record type.
9705	0x25E9	DNS record timed out.
9706	0x25EA	Name not in DNS zone.
9707	0x25EB	CNAME loop detected.
9708	0x25EC	Node is a CNAME DNS record.
9709	0x25ED	A CNAME record already exists for given name.
9710	0x25EE	Record only at DNS zone root.
9711	0x25EF	DNS record already exists.
9712	0x25F0	Secondary DNS zone data error.
9713	0x25F1	Could not create DNS cache data.
9714	0x25F2	DNS name does not exist.
9715	0x25F3	Could not create pointer (PTR) record.
9716	0x25F4	DNS domain was undeleted.
9717	0x25F5	The directory service is unavailable.
9718	0x25F6	DNS zone already exists in the directory service.
9719	0x25F7	DNS server not creating or reading the boot file for the directory service integrated DNS zone.
9720	0x25F8	Node is a DNAME DNS record.
9721	0x25F9	A DNAME record already exists for given name.
9722	0x25FA	An alias loop has been detected with either CNAME or DNAME records.
9751	0x2617	DNS AXFR (zone transfer) complete.
9752	0x2618	DNS zone transfer failed.
9753	0x2619	Added local WINS server.
9801	0x2649	Secure update call needs to continue update request.
9851	0x267B	TCP/IP network protocol not installed.
9852	0x267C	No DNS servers configured for local system.
9901	0x26AD	The specified directory partition does not exist.
9902	0x26AE	The specified directory partition already exists.
9903	0x26AF	This DNS server is not enlisted in the specified directory partition.
9904	0x26B0	This DNS server is already enlisted in the specified directory partition.
9905	0x26B1	The directory partition is not available at this time. Please wait a few minutes and try again.
9906	0x26B2	The application directory partition operation failed. The domain controller holding the domain naming master role is down or unable to service the request or is not running Windows Server 2003.
197120	0x30200	The underlying file was converted to compound file format.
197121	0x30201	The storage operation should block until more data is available.
197122	0x30202	The storage operation should retry immediately.
197123	0x30203	The notified event sink will not influence the storage operation.
197124	0x30204	Multiple opens prevent consolidated. (commit succeeded).
197125	0x30205	Consolidation of the storage file failed. (commit succeeded).
197126	0x30206	Consolidation of the storage file is inappropriate. (commit succeeded).
262144	0x40000	Use the registry database to provide the requested information
262145	0x40001	Success, but static
262146	0x40002	Macintosh clipboard format
262400	0x40100	Successful drop took place
262401	0x40101	Drag-drop operation canceled
262402	0x40102	Use the default cursor
262448	0x40130	Data has same FORMATETC
262464	0x40140	View is already frozen
262512	0x40170	FORMATETC not supported
262513	0x40171	Same cache
262514	0x40172	Some cache(s) not updated
262528	0x40180	Invalid verb for OLE object
262529	0x40181	Verb number is valid but verb cannot be done now
262530	0x40182	Invalid window handle passed
262560	0x401A0	Message is too long; some of it had to be truncated before displaying
262592	0x401C0	Unable to convert OLESTREAM to IStorage
262626	0x401E2	Moniker reduced to itself
262628	0x401E4	Common prefix is this moniker
262629	0x401E5	Common prefix is input moniker
262630	0x401E6	Common prefix is both monikers
262631	0x401E7	Moniker is already registered in running object table
524306	0x80012	Not all the requested interfaces were available
524307	0x80013	The specified machine name was not found in the cache.

+ post a comment