netevent.dll

Network Events API

Associated Error Codes

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

Code	Description
0x00001F59	The browser has retrieved a list of servers from remote computer %1 on transport %2. There were %3 entries read, and %4 total entries.
0x00001F5A	The browser has retrieved a list of domains from remote computer %1 on transport %2. There were %3 entries read, and %4 total entries.
0x00007858	nts API 0x00001f4c The browser driver has received an election packet from computer %2 on network %3. The data is the packet received.
0x10000038	Classic
0x40000C1C	The Microsoft TCP/IP version 6 driver was started.
0x40001069	The system detected that network adapter %2 was connected to the network, and has initiated normal operation.
0x4000106A	The system detected that network adapter %2 was disconnected from the network and its network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Try updating the driver for the network adapter.
0x4000106B	The system detected that IPv4 is not installed. This may cause some networking services to fail to start, or to malfunction. To install IPv4, use "netsh interface ipv4 install".
0x40001395	%2 : The adapter is configured such that the receive space is smaller than the maximum packet size. Some packets may be lost.
0x400013A6	%2 : The network adapter has successfully reinserted into the ring.
0x40001B7B	The %1 service was successfully sent a %2 control.
0x40001B7C	The %1 service entered the %2 state.
0x40001B80	The start type of the %1 service was changed from %2 to %3.
0x40001B82	The %1 service was successfully sent a %2 control. The reason specified was: %3 [%4] Comment: %5
0x40001F4D	The browser driver has forced an election on network %2 because it was unable to find a master browser to retrieve a backup list on that network.
0x40001F4E	The browser driver has forced an election on network %2 because it was unable to find a master browser for that network.
0x40001F4F	The browser has forced an election on network %1 because a Windows Server (or domain master) browser is started.
0x40001F58	The backup browser server %2 is out-of-date. Consider upgrading this computer.
0x40001F5B	The browser running on the Domain Controller has lost an election. The computer that won the election is %2, on the transport %3. The data contains the election version, election criteria, and remote computer time up, and the same information for the current computer.
0x40001F5C	The browser running on this computer has won a browser election on network %2. This computer is a member of a domain, so the Domain Controller should become the master browser.
0x40001F5D	The browser driver was unable to initialize variables from the Registry.
0x40001F5E	The browser driver has discarded too many mailslot messages.
0x40001F5F	The browser driver has discarded too many GetBrowserServerList requests.
0x40001F61	The browser has forced an election on network %1 because a master browser was stopped.
0x40001F63	The browser has forced an election on network %1 because the Domain Controller (or Server) has changed its role.
0x40002331	%2 could not transfer a packet from the network adapter. The packet was dropped.
0x40002332	%2 could not create a link to a remote computer. Your computer has exceeded the number of connections it can make to that remote computer.
0x40002333	%2 received an unexpected %3 packet from a remote computer.
0x4000251D	The default frame type for auto-detection on %2 was changed to %3. This type is now the default if no frame type can be detected.
0x40002BC0	The system registered network adapter with settings : Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6
0x40002BC1	The system registered pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 Primary Domain Suffix : %4 DNS server list : %5 Sent update to server : %6 IP Address : %7
0x40002BC2	The system registered host (A or AAAA) resource records (RRs) for network adapter with settings : Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6
0x400030D5	Service started successfully
0x400030D9	A new volume ID has been assigned for %1: %2 This ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. If there previously were links to files on this volume that are broken, they might not be automatically repairable.
0x400030DA	Ownership of the volume ID for %1: has been successfully claimed. This volume ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.
0x400030DB	The volume ID for %1: has been reset, since it was a duplicate of that on %2:. This volume ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.
0x400034BD	The File Replication Service is starting.
0x400034BE	The File Replication Service is stopping.
0x400034BF	The File Replication Service has stopped.
0x400034CC	The File Replication Service is no longer preventing the computer %1 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. Type "net share" to check for the SYSVOL share.
0x400034F1	The File Replication Service successfully added this computer to the following replica set: "%1" Information related to this event is shown below: Computer DNS name is "%2" Replica set member name is "%3" Replica set root path is "%4" Replica staging directory path is "%5" Replica working directory path is "%6"
0x400034F2	The File Replication Service successfully added the connections shown below to the replica set: "%1" %2 %3 %4 %5 %6 %7 %8 %9 More information may appear in subsequent event log messages.
0x400037EE	Dfs received a referral request for "%2". The return code is in the data.
0x40003840	The path "%2" is not a dfs path
0x40003841	Dfs was unable to open the Lan Redir
0x40003842	Dfs was unable to open a connection to server %2. The error returned is in the record data.
0x40003843	Dfs was unable to obtain a referral for "%2" from %3. The error returned is in the record data.
0x40003844	Dfs obtained a referral for "%2" from %3
0x40003845	Dfs reached its limit of attempts of resolution of "%2".
0x40003846	Dfs was unable to obtain the special referral table from %2. The error returned is in the record data.
0x40003847	Dfs failed on open of %2 directed to %3. The error returned is in the record data.
0x400038A4	NetrDfsEnum received an enumeration. The return code is in the record data.
0x400038A5	NetrDfsEnumEx received an enumeration. The return code is in the record data.
0x400038AC	DFS re-established a connection to the PDC to initiate Domain DFS operations.
0x400038C1	DFS has connected to the %1 Active Directory.
0x400038C3	DFS server has finished initializing.
0x400038C4	DFS has recovered from an error and is able to read its private data from the Active Directory. Root %1 is now able to read information from the Active Directory.
0x400038C5	DFS has finished building all namespaces.
0x400038C9	DFS is requesting the client for a larger buffer for trusted domain information. Some Win98 clients may not be able to access DFS namespaces.
0x400038D2	Dfs successfully created the reparse point for directory %1 under directory %2. This operation had previously failed.
0x400038D5	The DFS Namespace service successfully initialized the trusted domain information on this domain controller.
0x400038D7	The DFS Namespace service successfully initialized cross forest trust information on this domain controller.
0x400038D8	The DFS Namespaces service has successfully initialized the following namespace: %1
0x400038DA	The DFS Namespaces service has successfully initialized the shared folder that hosts the namespace root. Shared folder: %1
0x40004074	Computer QoS policies successfully refreshed. No changes detected.
0x40004075	Computer QoS policies successfully refreshed. Policy changes detected.
0x40004076	User QoS policies successfully refreshed. No changes detected.
0x40004077	User QoS policies successfully refreshed. Policy changes detected.
0x40004078	The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is not specified by any QoS policy. Local computer default will be applied.
0x40004079	The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 0 (minimum throughput).
0x4000407A	The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 1.
0x4000407B	The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 2.
0x4000407C	The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. Setting value is Level 3 (maximum throughput).
0x4000407D	The Advanced QoS Setting for DSCP marking overrides successfully refreshed. Setting value is not specified by any QoS policy. Local computer default will be applied. By default, applications can set DSCP values independently of QoS policies.
0x4000407E	The Advanced QoS Setting for DSCP marking overrides successfully refreshed. Application DSCP marking requests will be ignored. Only QoS policies can set DSCP values.
0x4000407F	The Advanced QoS Setting for DSCP marking overrides successfully refreshed. Applications can set DSCP values independently of QoS policies.
0x40004080	Selective application of QoS policies based on domain or non-domain network category has been disabled on this machine. QoS policies will be applied to all network interfaces.
0x40004081	In the past %1 hour(s) and %2 minute(s), %3 HTTP.SYS responses have had their application requested QoS conflict with URL QoS policies.
0x800007D9	The server could not expand a table because the table reached the maximum size.
0x800007DC	While transmitting or receiving data, the server encountered a network error. Occasional errors are expected, but large amounts of these indicate a possible error in your network configuration. The error status code is contained within the returned data (formatted as Words) and may point you towards the problem.
0x800007DD	The %2 disk is at or near capacity. You may need to delete some files.
0x800007E5	The server was unable to allocate a work item %2 times in the last %3 seconds.
0x800007E6	The server was unable to find a free connection %2 times in the last %3 seconds. This indicates a spike in network traffic. If this is happening frequently, you should consider increasing the minimum number of free connections to add headroom. To do that, modify the MinFreeConnections and MaxFreeConnections for the LanmanServer in the registry.
0x800007E7	The server was unable to find a free raw work item %2 times in the last %3 seconds.
0x800007E8	The server was unable to allocate resources for blocking I/O %2 times in the last %3 seconds.
0x800007E9	The server has detected an attempted Denial-Of-Service attack from client %2, and has disconnected the connection.
0x800007EA	The server has detected too many Denial-Of-Service attacks and will stop logging events for any more of them. Be advised it is likely someone is actively attacking your machine.
0x800007EB	The server has detected a potential Denial-of-Service attack caused by consuming all the work-items. Some connections were disconnected to protect against this. If this is not the case, please raise the MaxWorkItems for the server or disable DoS detection. This event will not be logged again for 24 hours.
0x800009C8	The server could not bind to the transport %1.
0x800009CA	The value named %1 in the server's registry key %2 was not valid, and was ignored. If you want to change the value, change it to one that is the correct type and is within the acceptable range, or delete the value to use the default. This value might have been set up by an older program that did not use the correct boundaries.
0x800009CB	The security descriptor stored in the Registry for the share %1 was invalid. The share was not automatically recreated.
0x800009CC	The server service was unable to load the server driver.
0x800009CD	The server service was unable to unload the server driver.
0x800009CE	The server service was unable to map error code %1.
0x800009CF	The server service was unable to recreate the share %1 because the directory %2 no longer exists. Please run "net share %1 /delete" to delete the share, or recreate the directory %2.
0x800009D0	The server service was unable to change the domain name from %1 to %2.
0x800009D1	The server service was unable to register to the transaction resource manager. Remote transactions will be unavailable.
0x80000BB9	The redirector was unable to allocate memory.
0x80000BBA	The redirector could not create its device. The redirector could not be started.
0x80000BBB	The redirector could not create a system thread.
0x80000BBC	The redirector could not set the priority for a system thread.
0x80000BBD	The redirector received an incorrectly formatted response from %2.
0x80000BBE	The redirector received an SMB that was too short.
0x80000BBF	The redirector received an incorrect response from %2 to a lock request.
0x80000BC1	The redirector failed to unlock part of a file on server %2.
0x80000BC3	The redirector failed to write data to server %2 after the file was closed.
0x80000BC4	An unexpected network error has occurred on the virtual circuit to %2.
0x80000BC5	The redirector has timed out a request to %2.
0x80000BC6	The redirector received an invalid oplock level from %2.
0x80000BC7	The redirector dereferenced a connection through zero.
0x80000BC8	The redirector dereferenced a server through zero.
0x80000BC9	The redirector dereferenced the allocated SMB count through zero.
0x80000BCA	The redirector accessed a share-level server that indicates it encrypts passwords. This combination is not supported.
0x80000BCB	The redirector failed to determine the connection type.
0x80000BCD	The redirector failed to allocate a multiplex table entry. This indicates that the MAXCMDS parameter to the redirector is insufficient for the users needs.
0x80000BCE	The redirector failed to allocate a buffer for an oplock break.
0x80000BCF	The redirector failed to map the requested file disposition (for NtCreateFile).
0x80000BD0	The redirector is allocating additional resources for input/output request packet contexts. This is probably caused by a resource leak in the redirector.
0x80000BD1	A write-behind operation has failed to the remote server %2. The data contains the amount requested to write and the amount actually written.
0x80000BD2	The redirector was unable to create a worker thread because it has already created the maximum number of configured work threads.
0x80000BD3	The redirector was unable to initialize variables from the Registry.
0x80000BD4	The time zone bias calculated between %2 and the current workstation is too large. The data specifies the number of 100ns units between the workstation and server. Make sure that the time of day on the workstation and server are correct.
0x80000BD5	The redirector has failed to connect to the server %2 on the primary transport. The data contains the error.
0x80000BD6	The redirector was unable to update the file attributes on a file located on server %2. The data contains the name of the file.
0x80000BD7	The redirector was unable to delete the file specified on server %2 when it was closed by the application. The data contains the name of the file.
0x80000BD8	The redirector was unable to register the domain %2 on to transport %3 for the following reason: %4. Transport has been taken offline.
0x80000BD9	The redirector was unable to register the address for transport %3 for the following reason: %4. Transport has been taken offline.
0x80000BDA	The redirector was unable to initialize security context or query context attributes.
0x80000BDB	The redirector was unable to build SMB header.
0x80000BDC	The redirector detected a security signature mismatch. The connection has been disconnected.
0x80000FA1	Unable to allocate a %2 byte message.
0x80000FA2	%2 message allocations have failed since initialization.
0x80000FA3	Unable to allocate a %2 byte external message.
0x80000FA4	%2 external message allocations have failed since initialization.
0x8000105E	IP was unable to initialize network adapter %2 for configuration by DHCP. If DHCP is enabled on this network adapter, the primary interface may not be configured properly. Interfaces on this network adapter not configured by DHCP will be unaffected.
0x80001060	Invalid default gateway address %2 was specified for network adapter %3. Some remote networks may not be reachable as a result.
0x80001065	More than the maximum number of default gateways were specified for network adapter %2. Some remote networks may not be reachable as a result.
0x8000106C	Autoconfigured address limit has been reached. No further autoconfigured addresses will be added until the interface is reconnected.
0x8000106D	Autoconfigured route limit has been reached. No further autoconfigured routes will be added until the interface is reconnected.
0x8000106E	More than the supported number of out of order IP fragments were received. One or more fragmented IP packets were dropped as a result.
0x80001082	TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
0x80001083	TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.
0x80001084	TCP/IP has chosen to restrict the scale factor due to a network condition. This could be related to a problem in a network device and will cause degraded throughput.
0x80001085	TCP/IP has detected high memory utilization and has terminated some existing connections to maintain system stability.
0x80001086	TCP/IP has chosen to restrict the congestion window for several connections due to a network condition. This could be related to a problem in the TCP global or supplemental configuration and will cause degraded throughput.
0x80001087	A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use.
0x800010A9	Backlog of pending datagram sends reached. Please increase the value of Tcpip\Parameters\DGMaxSendFree in the registry.
0x800010AA	A request to allocate an ephemeral port number from the global UDP port space has failed due to all such ports being in use.
0x800010C2	Multicast address list could not be set on the network adapter with hardware address %2 (%3 %4 %5 %6).
0x800010C3	The network adapter with hardware address %2 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (%3 %4).
0x800010C4	An attempt to set a packet coalescing filter on the network adapter with hardware address %2 has failed (%3 %4 %5).
0x800010C5	The ARP packet coalescing filter on the network adapter with hardware address %2 is not set since more than one IPv4 address is currently assigned to the adapter. An ARP packet coalescing filter may be set later when only one IPv4 address is assigned to this adapter (%3 %4).
0x800010CE	The backup WINS server address is not configured in the registry.
0x800010CF	The primary WINS server address is not configured in the registry.
0x800010D0	The backup WINS server address is not formated correctly in the registry.
0x800010D1	The primary WINS server address is not formatted correctly in the registry.
0x800010D8	There are no network adapters configured for this protocol stack.
0x800010DC	Unable to open the registry to read the WINS server addresses.
0x800010DD	The Netbios Name Scope has a component longer than 63 characters. Each label in the Scope cannot be longer than 63 bytes.
0x800010DE	The Netbios Name Scope is too long. The scope cannot be longer than 255 bytes.
0x8000138F	%2 : Timed out during an operation.
0x80001396	%2 : The driver cannot function because the network adapter is disabled.
0x80001397	%2 : There is an I/O port conflict.
0x80001398	%2 : There is an I/O port or DMA channel conflict.
0x80001399	%2 : There is a memory conflict at address 0x%3.
0x8000139A	%2 : There is a interrupt conflict at Interrupt %3.
0x8000139B	%2 : There is a resource conflict at DMA channel %3.
0x8000139D	%2 : The specified registry entry MaxReceives is out of range. Using default value.
0x8000139E	%2 : The specified registry entry MaxTransmits is out of range. Using default value
0x8000139F	%2 : The specified registry entry MaxFrameSize is out of range. Using default value.
0x800013A0	%2 : The specified registry entry MaxInternalBufs is out of range. Using default value.
0x800013A1	%2 : The specified registry entry MaxMulticast is out of range. Using default value.
0x800013A2	%2 : The specified registry entry ProductId is out of range. Using default value.
0x800013A3	%2 : A Token Ring Lobe Wire Fault has occurred. Verify cable connections. The network adapter will continue to try to reinsert into the ring.
0x800013A4	%2 : The adapter had detected a loss of signal on the ring. The adapter will continue to try to reinsert back into the ring.
0x800013A5	%2 : The adapter has received a request to deinsert from the ring. The adapter will continue to try to reinsert back into the ring.
0x800013A8	%2 : The network adapter failed to reset within a specified time, which could be caused by a hardware failure. The network adapter will continue to try to reset.
0x800013A9	%2 : The network adapter has detected that the token ring cable is disconnected from the network adapter. Please reconnect the cable.
0x800013AA	%2 : The network adapter has successfully completed a previously failed reset.
0x80001775	The Event log service was started.
0x80001776	The Event log service was stopped.
0x80001778	The previous system shutdown at %1 on %2 was unexpected.
0x80001779	Microsoft (R) Windows (R) %1 %2 %3 %4.
0x8000177B	The NetBIOS name and DNS host name of this machine have been changed from %1 to %2.
0x8000177C	The DNS domain assigned to this computer has been changed from %1 to %2.
0x8000177D	The system uptime is %5 seconds.
0x80001B7F	A service process other than the one launched by the Service Control Manager connected when starting the %1 service. The Service Control Manager launched process %2 and process %3 connected instead. Note that if this service is configured to start under a debugger, this behavior is expected.
0x80001F44	A request has been submitted to promote the computer to backup when it is already a master browser.
0x80001F45	The browser has received a server announcement indicating that the computer %2 is a master browser, but this computer is not a master browser.
0x80001F46	The browser has received an illegal datagram from the remote computer %2 to name %3 on transport %4. The data is the datagram.
0x80001F55	The browser service was unable to retrieve a list of servers from the browser master %1 on the network %2. Browser master: %1 Network: %2 This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.
0x80001F56	The browser service was unable to retrieve a list of domains from the browser master %1 on the network %2. Browser master: %1 Network: %2 This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.
0x80001F57	The value for the parameter %1 to the browser service was illegal.
0x8000214D	Name too long in key %1: Name = %s. The Sap Agent cannot continue.
0x80002329	%2 could not allocate a resource of type %3 due to system resource problems.
0x8000232A	%2 could not allocate a resource of type %3 due to its configured size of %4.
0x8000232B	%2 could not allocate a resource of type %3 due to a specifically configured limit of %4.
0x8000251E	A SAP announcement was sent over %2 which is configured for multiple networks, but no internal network is configured. This may prevent machines on some networks from locating the advertised service.
0x8000251F	The value for the %2 parameter %3 was illegal.
0x80002B2A	The DNS Client service could not contact any DNS servers for a repeated number of attempts. For the next %3 seconds the DNS Client service will not use the network to avoid further network performance problems. It will resume its normal behavior after that. If this problem persists, verify your TCP/IP configuration, specifically check that you have a preferred (and possibly an alternate) DNS server configured. If the problem continues, verify network conditions to these DNS servers or contact your network administrator.
0x80002B2B	The DNS Client service failed to reach DNS server at address %1. It will not use this DNS server for %2 seconds.
0x80002B8E	The system failed to register network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS Server list : %4 Sent update to server : %5 IP Address(es) : %6 The cause of this DNS registration failure was because the DNS update request timed out after being sent to the specified DNS Server. This is probably because the authoritative DNS server for the name being updated is not running. You can manually retry registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.
0x80002B8F	The system failed to register network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with. (The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.
0x80002B90	The system failed to register network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason it could not register was because either: (a) the DNS server does not support the DNS dynamic update protocol, or (b) the primary zone authoritative for the registering names does not currently accept dynamic updates. To add or register a DNS host (A or AAAA) resource record using the specific DNS name for this adapter, contact your DNS server or network systems administrator.
0x80002B91	The system failed to register network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason it could not register was because the DNS server refused the dynamic update request. This could happen for the following reasons: (a) current DNS update policies do not allow this computer to update the DNS domain name configured for this adapter, or (b) the authoritative DNS server for this DNS domain name does not support the DNS dynamic update protocol. To register a DNS host (A or AAAA) resource record using the specific DNS domain name for this adapter, contact your DNS server or network systems administrator.
0x80002B92	The system failed to register network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The system could not register the DNS update request because of a security related problem. This could happen for the following reasons: (a) the DNS domain name that your computer is trying to register could not be updated because your computer does not have the right permissions, or (b) there might have been a problem negotiating valid credentials with the DNS server to update. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002B93	The system failed to register network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the DNS update request could not be completed was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002B94	The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The reason that the system could not register these RRs was because the update request that was sent to the specified DNS server timed out. This is probably because the authoritative DNS server for the name being registered is not running. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002B95	The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The cause was DNS server failure. This may because the reverse lookup zone is busy or missing on the DNS server that your computer needs to update. In most cases, this is a minor problem because it does not affect normal (forward) name resolution. If reverse (address-to-name) resolution is required for your computer, you can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002B96	The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The reason that the system could not register these RRs was because (a) either the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone where these records are to be registered does not allow dynamic updates. To register DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
0x80002B97	The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The reason that the system could not register these RRs was because the DNS server refused the update request. The cause of this could be (a) your computer is not allowed to update the adapter-specified DNS domain name, or (b) because the DNS server authoritative for the specified name does not support the DNS dynamic update protocol. To register the DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
0x80002B98	The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
0x80002B99	The system failed to register pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002B9A	The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at this time. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
0x80002B9B	The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
0x80002B9C	The system failed to register host (A or AAAA) resource records for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 Either the DNS server does not support the DNS dynamic update protocol or the authoritative zone for the specified DNS domain name does not accept dynamic updates. To register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
0x80002B9D	The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol. To register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
0x80002B9E	The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002B9F	The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not register these RRs during the update request was because of a system problem. You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.
0x80002BAC	The system failed to update and remove registration for the network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time.
0x80002BAD	The system failed to update and remove registration for the network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason for this failure is because the DNS server it sent the update to failed the update request. A possible cause of this failure is that the DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.
0x80002BAE	The system failed to update and remove registration for the network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not currently accept DNS dynamic updates.
0x80002BAF	The system failed to update and remove registration for the network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not perform the update request was the DNS server contacted refused update request. The cause of this is (a) this computer is not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for the zone that requires updating does not support the DNS dynamic update protocol.
0x80002BB0	The system failed to update and remove registration for the network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the system could not perform the update request was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information.
0x80002BB1	The system failed to update and remove the DNS registration for the network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The system could not update to remove this DNS registration because of a system problem. See event details for specific error code information.
0x80002BB2	The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The system could not remove these PTR RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone that requires update is not running.
0x80002BB3	The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The system could not remove these PTR RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs.
0x80002BB4	The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The system could not remove these PTR RRs because either the DNS server does not support the DNS dynamic update protocol or the authoritative zone that contains these RRs does not accept dynamic updates.
0x80002BB5	The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The system could not remove these PTR RRs because the DNS server refused the update request. The cause of this might be (a) this computer is not allowed to update the specified DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol.
0x80002BB6	The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The system could not remove these PTR RRs because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information.
0x80002BB7	The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Adapter-specific Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address : %6 The system could not remove these PTR RRs because because of a system problem. See event details for specific error code information.
0x80002BB8	The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The system could not remove these host (A or AAAA) RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone where these RRs need to be updated is either not currently running or reachable on the network.
0x80002BB9	The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The system could not remove these host (A or AAAA) RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs.
0x80002BBA	The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the DNS domain name specified in these host (A or AAAA) RRs does not currently accept DNS dynamic updates.
0x80002BBB	The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The request to remove these records failed because the DNS server refused the update request. The cause of this might be that either (a) this computer is not allowed to update the DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol.
0x80002BBC	The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason for this failure was because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information.
0x80002BBD	The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : %1 Host Name : %2 Primary Domain Suffix : %3 DNS server list : %4 Sent update to server : %5 IP Address(es) : %6 The reason the update request failed was because of a system problem. See event details for specific error code information
0x800030D8	The Distributed Link Tracking volume ID quota on this machine has been exceeded. As a result, it is not possible to create new volume IDs. Distributed Link Tracking normally uses these volume IDs to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.
0x800030DC	The move table quota for Distributed Link Tracking in this domain has been exceeded. This table is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken. While this quota is exceeded, it may not be possible to automatically repair some such broken links.
0x800034C4	The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name %4 from this computer. [2] FRS is not running on %4. [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
0x800034C5	The File Replication Service has enabled replication from %1 to %2 for %3 after repeated retries.
0x800034C8	The File Replication Service has detected an enabled disk write cache on the drive containing the directory %2 on the computer %1. The File Replication Service might not recover when power to the drive is interrupted and critical updates are lost.
0x800034CA	The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume is being initialized with data from another domain controller and then shared as SYSVOL. Type "net share" to check for the SYSVOL share. The File Replication Service has stopped preventing the computer from becoming a domain controller once the SYSVOL share appears. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
0x800034CB	The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume is being initialized and then shared as SYSVOL. Type "net share" to check for the SYSVOL share. The File Replication Service has stopped preventing the computer from becoming a domain controller once the SYSVOL share appears. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume. The initialization of the system volume can be bypassed by first typing regedt32 and setting the value of SysvolReady to 1 and then restarting the Netlogon service. WARNING - BYPASSING THE SYSTEM VOLUME INITIALIZATION IS NOT RECOMMENDED. Applications may fail in unexpected ways. The value SysvolReady is located by clicking on HKEY_LOCAL_MACHINE and then clicking on System, CurrentControlSet, Services, Netlogon, and Parameters. The Netlogon service can be restarted by typing "net stop netlogon" followed by "net start netlogon".
0x800034CD	The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedt32. Click on Start, Run, and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Access Checks, "%1", and "%2". Change the string to Enabled. Permissions can be changed by highlighting "%1" and then clicking on the toolbar option Security and then Permissions...
0x800034CE	The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running regedt32. Click on Start, Run, and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Access Checks, and highlight "%1". Click on the toolbar option Security and then Permissions... Access checks can be disabled for "%1". Double click on "%2" and change the string to Disabled.
0x800034D0	The File Replication Service moved the preexisting files in %1 to %2. The File Replication Service may delete the files in %2 at any time. Files can be saved from deletion by copying them out of %2. Copying the files into %1 may lead to name conflicts if the files already exist on some other replicating partner. In some cases, the File Replication Service may copy a file from %2 into %1 instead of replicating the file from some other replicating partner. Space can be recovered at any time by deleting the files in %2.
0x800034D2	The File Replication Service paused because the staging area is full. Replication will resume if staging space becomes available or if the staging space limit is increased. The current value of the staging space limit is %1 KB. To change the staging space limit, run regedt32. Click on Start, Run and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space Limit in KB".
0x800034D3	The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only if the staging space limit is increased. The staging space limit is %1 KB and the file size is %2 KB. To change the staging space limit, run regedt32. Click on Start, Run and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space Limit in KB".
0x800034D5	The File Replication Service cannot find the DNS name for the computer %1 because the "%2" attribute could not be read from the distinguished name "%3". The File Replication Service will try using the name "%1" until the computer's DNS name appears.
0x800034EB	The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". The expected value name is "%3". The expected registry data type is %4. The allowed range for this parameter is %5 The data units for this parameter value are %6. The File Replication Service is using a default value of "%7". To change this parameter, run regedt32. Click on Start, Run and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Click down the key path: "%8" Double click on the value name - "%9" and update the value. If the value name is not present you may add it with the Add Value function under the Edit Menu item. Type the value name exactly as shown above using the above registry data type. Make sure you observe the data units and allowed range when entering the value.
0x800034F8	The File Replication Service is deleting this computer from the replica set "%1" as an attempt to recover from the error state, Error status = %2 At the next poll, which will occur in %3 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
0x800034FA	Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller %1 for FRS replica set configuration information. %2
0x80003714	QoS [Adapter %2]: The BestEffortLimit value set in the registry exceeds the LinkSpeed. Defaulting to Unlimited BestEffort.
0x8000371D	QoS [Adapter %2]: The registry entry for BestEffortLimit is not supported over WAN links. Defaulting to Unlimited BestEffort mode.
0x8000371F	QoS [Adapter %2]: Total bandwidth allocated to flows exceeds the NonBestEffortLimit. This is because of a reduction in the LinkSpeed or because of a change to the NonBestEffortLimit registry key.
0x800038BE	DFS could not contact the %1 Active Directory. DFS will be using cached data. The return code is in the record data.
0x800038C6	DFS Root %1 failed during initialization. The root will not be available.
0x800038C8	DFS is unable to return the entire list of trusted domains to the client. There are too many trusted domains.
0x800038CA	DFS was unable to move all matching links of root: %1 for path %2 to new path %3
0x800038CD	DFS link %1 was marked incorrectly as a DFS root. The DFS namespace is operational on this server. If this namespace is hosted on servers running Windows Server 2003 prior to Service Pack 2 (SP2), or if the server is running Windows 2000 Server, the namespace might not be fully functional on those servers. Please consult the Microsoft Knowledge Base for more information on correcting this issue.
0x800038CE	DFS metadata object %1 is empty in the metadata for DFS root %2. The DFS namespace is operational on this server. If this namespace is hosted on servers running Windows Server 2003 prior to Service Pack 2 (SP2), or if the server is running Windows 2000 Server, the namespace might not be fully functional on those servers. Please consult the Microsoft Knowledge Base for more information on correcting this issue.
0x800038D9	The DFS Namespaces service failed to initialize the shared folder that hosts the namespace root. Shared folder: %1
0x800039D0	Windows was unable to save data for file %2. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
0x80003A35	PUT failed for file %1 on Close. ErrorStatus: %2.
0x80003A36	DELETE failed for file %1 on Close. ErrorStatus: %2.
0x80003A37	PROPPATCH failed for file %1 on Close. ErrorStatus: %2.
0x80003A38	PROPPATCH failed for file %1 on SetFileInfo. ErrorStatus: %2.
0x80003E81	A TDI filter (%2) was detected. This filter has not been certified by Microsoft and may cause system instability.
0x80003E82	Closing a %2 socket with local port number %3 in process %4 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
0x800040D8	EQOS: *Testing*, with one string %2.
0x800040D9	EQOS: *Testing*, with two strings, string1 is %2, string2 is %3.
0x800040DA	A computer QoS policy "%2" has an invalid version number. This policy will not be applied.
0x800040DB	A user QoS policy "%2" has an invalid version number. This policy will not be applied.
0x800040DC	A computer QoS policy "%2" does not specify a DSCP value or throttle rate. This policy will not be applied.
0x800040DD	A user QoS policy "%2" does not specify a DSCP value or throttle rate. This policy will not be applied.
0x800040DE	Exceeded the maximum number of computer QoS policies. The computer QoS policy "%2" and subsequent computer QoS policies will not be applied.
0x800040DF	Exceeded the maximum number of user QoS policies. The user QoS policy "%2" and subsequent user QoS policies will not be applied.
0x800040E0	A computer QoS policy "%2" potentially conflicts with other QoS policies. See documentation for rules about which policy will be applied at packet send time.
0x800040E1	A user QoS policy "%2" potentially conflicts with other QoS policies. See documentation for rules about which policy will be applied at packet send time.
0x800040E2	A computer QoS policy "%2" was ignored because the application path cannot be processed. The application path may be totally invalid, or has an invalid drive letter, or contains network-mapped drive letter.
0x800040E3	A user QoS policy "%2" was ignored because the application path cannot be processed. The application path may be totally invalid, or has an invalid drive letter, or contains network-mapped drive letter.
0x80004268	WinNat session limit has been reached.
0x90000001	Microsoft-Windows-DfsSvc
0x90000002	System
0xC00007D0	The server's call to a system service failed unexpectedly.
0xC00007D1	The server was unable to perform an operation due to a shortage of available resources.
0xC00007D2	The server could not create its device. The server could not be started.
0xC00007D3	The server could not create a process. The server could not be started.
0xC00007D4	The server could not create a startup thread. The server could not be started.
0xC00007D5	The server received an unexpected disconnection from a client.
0xC00007D6	The server received an incorrectly formatted request from %2.
0xC00007D7	The server could not open the named pipe file system. Remote named pipes are disabled.
0xC00007DA	The server could not start the scavenger thread. The server could not be started.
0xC00007DB	The server's configuration parameter "irpstacksize" is too small for the server to use a local device. Please increase the value of this parameter.
0xC00007E0	The server was unable to allocate virtual memory.
0xC00007E1	The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.
0xC00007E2	The server was unable to allocate from the system paged pool because the server reached the configured limit for paged pool allocations.
0xC00007E3	The server was unable to allocate from the system nonpaged pool because the pool was empty.
0xC00007E4	The server was unable to allocate from the system paged pool because the pool was empty.
0xC00009C5	The server's Registry key %1 was not present. The server could not start.
0xC00009C6	The server's Registry key %1 was not present and could not be created. The server could not start.
0xC00009C7	The server did not bind to any transports. The server could not start.
0xC00009C9	The server could not bind to the transport %1 because another computer on the network has the same name. The server could not start.
0xC0000FA0	%2
0xC0001004	Unable to create device object %2. Initialization failed.
0xC0001005	Unable to allocate required resources. Initialization failed.
0xC0001059	IP has been bound to more than the maximum number of supported interfaces. Some interfaces on network adapter %2 will not be initialized.
0xC000105A	No subnet mask was specified for interface %2. This interface and all subsequent interfaces on network adapter %3 cannot be initialized.
0xC000105B	An invalid address %2 was specified for network adapter %3. This interface cannot be initialized.
0xC000105C	An invalid subnet mask %2 was specified for address %3 on network adapter %4. This interface cannot be initialized.
0xC000105D	IP could not allocate some resources required to configure network adapter %2. Some interfaces on this network adapter will not be initialized.
0xC000105F	IP could not open the registry key for network adapter %2. Interfaces on this network adapter will not be initialized.
0xC0001061	Unable to read the configured IP addresses for network adapter %2. IP interfaces will not be initialized on this network adapter.
0xC0001062	Unable to read the configured subnet masks for network adapter %2. IP interfaces will not be initialized on this network adapter.
0xC0001063	IP was unable to read its bindings from the registry. No network interfaces were configured.
0xC0001064	Initialization of IP failed.
0xC0001066	The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled.
0xC0001067	The system detected an address conflict for IP address %2 with the system having network hardware address %3. Network operations on this system may be disrupted as a result.
0xC0001068	Unable to read or write the NTE Context list for network adapter %2. IP interfaces on this network adapter may not be initialized completely.
0xC000106F	The %2 TCP/IP interface with index %3 failed to bind to its provider.
0xC0001081	Initialization of TCP/UDP failed.
0xC00010C6	An attempt to clear a packet coalescing filter on the network adapter with hardware address %2 has failed (%3 %4 %5).
0xC00010CC	The driver could not be created.
0xC00010CD	Unable to open the Registry Parameters to read configuration information.
0xC00010D2	Unable to configure the addresses of the WINS servers.
0xC00010D3	Initialization failed because the transport refused to open initial addresses.
0xC00010D4	Initialization failed because the transport refused to open initial connections.
0xC00010D5	Data structure initialization failed.
0xC00010D6	Initialization failed because the timers could not be started.
0xC00010D7	Initialization failed because the driver device could not be created. Use the string "%2" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name.
0xC00010D9	Unable to open the Registry Linkage to read configuration information.
0xC00010DA	Unable to read the driver's bindings to the transport from the registry.
0xC00010DB	Unable to read the driver's exported linkage configuration information.
0xC00010DF	A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
0xC00010E0	Another computer has sent a name release message to this computer, probably because a duplicate name has been detected on the TCP network. The IP address of the node that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
0xC00010E1	The name "%2" could not be registered on the interface with IP address %3. The computer with the IP address %4 did not allow the name to be claimed by this computer.
0xC00010E2	NetBT failed to process a request because it encountered OutOfResources exception(s) in the last 1 hour.
0xC0001388	%2 : Has encountered a conflict in resources and could not load.
0xC0001389	%2 : Could not allocate the resources necessary for operation.
0xC000138A	%2 : Has determined that the network adapter is not functioning properly.
0xC000138B	%2 : Could not find a network adapter.
0xC000138C	%2 : Could not connect to the interrupt number supplied.
0xC000138D	%2 : Has encountered an internal error and has failed.
0xC000138E	%2 : The version number is incorrect for this driver.
0xC0001390	%2 : Has encountered an invalid network address.
0xC0001391	%2 : Does not support the configuration supplied.
0xC0001392	%2 : The network adapter has returned an invalid value to the driver.
0xC0001393	%2 : A required parameter is missing from the registry.
0xC0001394	%2 : The I/O base address supplied does not match the jumpers on the adapter.
0xC000139C	%2 : The download file is invalid. The driver is unable to load.
0xC00013A7	%2 : The network adapter has detected an Adapter Check as a result of an unrecoverable hardware or software error.
0xC00017D4	A uniprocessor-specific driver was loaded on a multiprocessor system. The driver could not load.
0xC0001B58	The %1 service failed to start due to the following error: %2
0xC0001B59	The %1 service depends on the %2 service which failed to start because of the following error: %3
0xC0001B5A	The %1 service depends on the %2 group and no member of this group started.
0xC0001B5B	The %1 service depends on the following nonexistent service: %2
0xC0001B5D	The %1 call failed with the following error: %2
0xC0001B5E	The %1 call failed for %2 with the following error: %3
0xC0001B5F	The system reverted to its last known good configuration. The system is restarting....
0xC0001B60	No backslash is in the account name.
0xC0001B61	Timeout (%1 milliseconds) waiting for the %2 service to connect.
0xC0001B62	Timeout (%1 milliseconds) waiting for ReadFile.
0xC0001B63	Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.
0xC0001B64	Message returned in transaction has incorrect size.
0xC0001B65	Logon attempt with current password failed with the following error: %1
0xC0001B66	Second logon attempt with old password also failed with the following error: %1
0xC0001B67	Boot-start or system-start driver (%1) must not depend on a service.
0xC0001B68	The %1 service has reported an invalid current state %2.
0xC0001B69	Detected circular dependencies demand starting %1.
0xC0001B6A	Detected circular dependencies auto-starting services.
0xC0001B6B	Circular dependency: The %1 service depends on a service in a group which starts later.
0xC0001B6C	Circular dependency: The %1 service depends on a group which starts later.
0xC0001B6D	About to revert to the last known good configuration because the %1 service failed to start.
0xC0001B6E	The %1 service hung on starting.
0xC0001B6F	The %1 service terminated with the following error: %2
0xC0001B70	The %1 service terminated with service-specific error %2.
0xC0001B71	At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
0xC0001B72	The following boot-start or system-start driver(s) failed to load: %1
0xC0001B73	Windows could not be started as configured. A previous working configuration was used instead.
0xC0001B74	The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key.
0xC0001B75	Service Control Manager %0
0xC0001B76	The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
0xC0001B77	The %1 service terminated unexpectedly. It has done this %2 time(s). The following corrective action will be taken in %3 milliseconds: %5.
0xC0001B78	The Service Control Manager tried to take a corrective action (%2) after the unexpected termination of the %3 service, but this action failed with the following error: %4
0xC0001B79	The Service Control Manager did not initialize successfully. The security configuration server (scesrv.dll) failed to initialize with error %1. The system is restarting...
0xC0001B7A	The %1 service terminated unexpectedly. It has done this %2 time(s).
0xC0001B7D	The Service Control Manager encountered an error undoing a configuration change to the %1 service. The service's %2 is currently in an unpredictable state. If you do not correct this configuration, you may not be able to restart the %1 service or may encounter other errors. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).
0xC0001B7E	The %1 service was unable to log on as %2 with the currently configured password due to the following error: %3 To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).
0xC0001B81	The %1 service was unable to log on as %2 with the currently configured password due to the following error: Logon failure: the user has not been granted the requested logon type at this computer. Service: %1 Domain and account: %2 This service account does not have the necessary user right "Log on as a service." User Action Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster. If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.
0xC0001B83	The %1 service did not shutdown properly after receiving a preshutdown control.
0xC0001EDC	The %1 command is marked as an interactive command. However, the system is configured to not allow interactive command execution. This command may not function properly.
0xC0001EDD	The %1 command failed to start due to the following error: %2
0xC0001F43	The master browser has received a server announcement from the computer %2 that believes that it is the master browser for the domain on transport %3. The master browser is stopping or an election is being forced.
0xC0001F47	The browser was unable to update the service status bits. The data is the error.
0xC0001F48	The browser was unable to update its role. The data is the error.
0xC0001F49	The browser was unable to promote itself to master browser. The computer that currently believes it is the master browser is %1.
0xC0001F4A	The browser driver was unable to convert a character string to a unicode string.
0xC0001F4B	The browser was unable to add the configuration parameter %1.
0xC0001F50	The browser driver has received too many illegal datagrams from the remote computer %2 to name %3 on transport %4. The data is the datagram. No more events will be generated until the reset frequency has expired.
0xC0001F51	The browser has failed to start because the dependent service %1 had invalid service status %2. Status Meaning 1 Service Stopped 2 Start Pending 3 Stop Pending 4 Running 5 Continue Pending 6 Pause Pending 7 Paused
0xC0001F53	The browser was unable to promote itself to master browser. The browser will continue to attempt to promote itself to the master browser, but will no longer log any events in the event log in Event Viewer.
0xC0001F54	The browser was unable to promote itself to master browser. The computer that currently believes it is the master browser is unknown.
0xC0001F60	The browser service has failed to retrieve the backup list too many times on transport %1. The backup browser is stopping.
0xC0001F62	The browser has received a GetBrowserServerList request when it is not the master browser.
0xC0001F64	The browser has failed to start because of an error in the DirectHostBinding parameter to the browser.
0xC0002134	The Registry Key %1 was not present. The Sap Agent could not start.
0xC0002135	Winsock startup routine failed. The Sap Agent cannot continue.
0xC0002136	Socket create call failed for main socket. The Sap Agent cannot continue.
0xC0002137	Setting broadcast option on socket failed. The Sap Agent cannot continue.
0xC0002138	Binding to SAP Socket failed. The Sap Agent cannot continue.
0xC0002139	Getting bound address of socket failed. The Sap Agent cannot continue.
0xC000213A	Setting option EXTENDED_ADDRESS failed. The Sap Agent cannot continue.
0xC000213B	Setting NWLink option BCASTINTADDR failed. The Sap Agent cannot continue.
0xC000213C	Error allocating memory to hold a card structure. The Sap Agent cannot continue.
0xC000213D	Enumeration of cards returned 0 cards.
0xC000213E	Error creating thread counting event. The Sap Agent cannot continue.
0xC000213F	Error creating receive semaphore. The Sap Agent cannot continue.
0xC0002140	Error creating send event. The Sap Agent cannot continue.
0xC0002141	Error starting receive thread. The Sap Agent cannot continue.
0xC0002142	Error starting worker thread. The Sap Agent cannot continue.
0xC0002143	Error allocating database array. The Sap Agent cannot continue.
0xC0002144	Error allocating hash table. The Sap Agent cannot continue.
0xC0002145	Error starting LPC worker thread. The Sap Agent cannot continue.
0xC0002146	Error creating the LPC port. The Sap Agent cannot continue.
0xC0002147	Error creating the LPC thread event. The Sap Agent cannot continue.
0xC0002148	Error allocating memory for an LPC Client structure. The Sap Agent cannot continue.
0xC0002149	Error allocating buffer to hold LPC worker thread handles. The Sap Agent cannot continue.
0xC000214A	The value for WANFilter in the registry must be 0-2. The Sap Agent cannot continue.
0xC000214B	Error creating event for card list access synchronization. The Sap Agent cannot continue.
0xC000214C	Error creating event for database access synchronization. The Sap Agent cannot continue.
0xC000214E	Error creating WAN control semaphore. The Sap Agent cannot continue.
0xC000214F	Socket create call failed for WAN socket. The Sap Agent cannot continue.
0xC0002150	Binding to WAN socket failed. The Sap Agent cannot continue.
0xC0002151	Error starting WAN worker thread. The Sap Agent cannot continue.
0xC0002152	Error starting WAN check thread. The Sap Agent cannot continue.
0xC0002153	Error on getsockopt IPX_MAX_ADAPTER_NUM. Data is the error code. The Sap Agent cannot continue.
0xC0002154	Error allocating buffer to hold WAN notify thread handles. The Sap Agent cannot continue.
0xC0002155	Error creating the WAN thread event. The Sap Agent cannot continue.
0xC000232C	%2 failed to register itself with the NDIS wrapper.
0xC000232D	%2 failed to bind to network adapter %3.
0xC000232E	%2 could not find network adapter %3.
0xC000232F	%2 failed while setting object identifier %3 on network adapter %4.
0xC0002330	%2 failed while querying object identifier %3 on network adapter %4.
0xC0002520	%2 was configured with an internal network number of %3. This network number conflicts with one of the attached networks. The configured internal network number will be ignored.
0xC0002521	%2 had no frame types configured for the binding to adapter %3.
0xC0002522	%2 failed to initialize because the driver device could not be created.
0xC0002523	%2 could not bind to any adapters. The transport could not start.
0xC0002710	Unable to start a DCOM Server: %3. The error: "%%%2" Happened while starting this command: %1
0xC0002711	Unable to start a DCOM Server: %3 as %4/%5. The error: "%%%2" Happened while starting this command: %1
0xC0002712	Access denied attempting to launch a DCOM Server. The server is: %1 The user is %2/%3, SID=%4.
0xC0002713	Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion. The server is: %1 The user is %2/%3, SID=%4.
0xC0002714	DCOM got error "%%%1" and was unable to logon %2\%3 in order to run the server: %4
0xC0002715	DCOM got error "%%%1" attempting to start the service %2 with arguments "%3" in order to run the server: %4
0xC0002716	DCOM got error "%%%1" from the computer %2 when attempting to activate the server: %3
0xC0002717	DCOM got error "%%%1" when attempting to activate the server: %2
0xC0002718	DCOM got error "%%%1" from the computer %2 when attempting to the server: %3 with file %4.
0xC0002719	DCOM was unable to communicate with the computer %1 using any of the configured protocols.
0xC000271A	The server %1 did not register with DCOM within the required timeout.
0xC000271B	The server %1 could not be contacted to establish the connection to the client
0xC000271C	There is an assertion failure in DCOM. Context follows: %1 %2 %3
0xC000271D	DCOM server attempted to listen on an invalid endpoint. Protseq: %1 Endpoint: %2 Flags: %3
0xC000271E	The activation for CLSID %1 failed because remote activations for COM+ are disabled. To enable this functionality use the Configure Your Server wizard and select the Web Application Server role.
0xC000272D	The activation of the CLSID %1 timed out waiting for the service %2 to stop.
0xC000272E	Unable to start a COM Server for debugging: %3. The error: "%%%2" Happened while starting this command: %1
0xC0002AF8	Unable to start DNS Client Service. Failed to load DLL %2, Error: %1. Please reinstall this DLL from installation CD.
0xC0002AF9	Unable to start DNS Client service. Can not find entry %3 in DLL %2. Please reinstall this DLL from installation CD. See event details for specific error code information.
0xC0002AFA	Unable to start the DNS Client service. The system could not register a service control handler and could be out of resources. Close any applications not in use or reboot the computer. See event details for specific error code information.
0xC0002AFB	Unable to start DNS Client service. The system could not create a termination event for this service and could be out of resources. Close any applications not in use or reboot the computer. See event details for specific error code information.
0xC0002AFC	Unable to start DNS Client service. Could not start the Remote Procedure Call (RPC) interface for this service. To correct the problem, you may restart the RPC and DNS Client services. To do so, use the following commands at a command prompt: (1) type "net start rpc" to start the RPC service, and (2) type "net start dnscache" to start the DNS Client service. See event details for specific error code information.
0xC0002AFD	Unable to start DNS Client service. The system could not register shutdown notification for this service and could be out of resources. Try closing any applications not in use or reboot the computer.
0xC0002AFE	Unable to start DNS Client service. Could not update status with Service Control Manager. To correct the problem, you may restart the RPC and DNS Client services. To do so, use the following commands at a command prompt: (1) type "net start rpc" to start the RPC service, and (2) type "net start dnscache" to start the DNS Client service. See event details for specific error code information.
0xC0002AFF	Unable to start DNS Client service because the system failed to allocate memory and may be out of available memory. Try closing any applications not in use or reboot the computer. See event details for specific error code information.
0xC00030D4	An internal error occured in Distributed Link Tracking. The error code was %1.
0xC00030D6	Service failed to start. Error = %1
0xC00030D7	The Distributed Link Tracking log was corrupt on volume %1: and has been re-created. This log is used to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.
0xC00034BC	File Replication Service
0xC00034C0	The File Replication Service stopped without cleaning up.
0xC00034C1	The File Replication Service has stopped after taking an assertion failure.
0xC00034C2	The File Replication Service failed a consistency check (%3) in "%1" at line %2. The File Replication Service will restart automatically at a later time. If this problem persists a subsequent entry in this event log describes the recovery procedure. For more information about the automatic restart right click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery.
0xC00034C3	The File Replication Service cannot start replica set %1 on computer %2 for directory %3 because the type of volume %4 is not NTFS 5.0 or later. The volume's type can be found by typing "chkdsk %4". The volume can be upgraded to NTFS 5.0 or later by typing "chkntfs /E %4".
0xC00034C6	The File Replication Service on the computer %1 cannot communicate with the File Replication Service on the computer %2. Verify that the computer %2 is up and running. Verify that the File Replication Service is running on %2 by typing "net start ntfrs" on %2. Verify that the network is functioning between %1 and %2 by typing "ping %1" on %2 and "ping %2" on %1. If the pings succeed then retry the failed operation. If the pings fail then there may be problems with the DNS server. The DNS server is responsible for mapping computer names to IP addresses. The commands "ipconfig" and "nslookup" help diagnose problems with the DNS server. Typing "ipconfig /all" will list the computer's IP address and the IP address of the computer's DNS servers. Type "ping " to verify that a DNS server is available. The DNS mapping for %2 or %1 can be verified by typing "nslookup" and then typing "%2" and then "%1" on %1 and %2. Be sure to check out the DNS server on both %1 and %2; a DNS problem on either computer will prevent proper communication. Some network problems between %1 and %2 can be cleared up by flushing the DNS Resolver Cache. Type "ipconfig /flushdns". Some network problems between %1 and %2 can be cleared up by renewing the IP address. Type "ipconfig /release" followed by "ipconfig /renew". Some network problems between %1 and %2 can be cleared up by resetting the computer's DNS entry. Type "net stop NetLogon" followed by "net start NetLogon". Some problems between %1 and %2 can be cleared up by restarting the File Replication Service. Type "net stop ntfrs" followed by "net start ntfrs". Some problems between %1 and %2 can be cleared up by restarting the computers %1 and %2 AFTER CLOSING RUNNING APPLIATIONS, especially dcpromo. Click on Start, Shutdown, select Restart, and click on OK. Other network and computer problems are beyond the scope of this event log message.
0xC00034C7	The File Replication Service is stopping on computer %1 because there is no free space on the volume containing %2. The available space on the volume can be found by typing "dir %2". Once free space is made available on the volume containing %2, the File Replication Service can be restarted immediately by typing "net start ntfrs". Otherwise, the File Replication Service will restart automatically at a later time. For more information about the automatic restart right click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery. For more information about managing space on a volume type "copy /?", "rename /?", "del /?", "rmdir /?", and "dir /?".
0xC00034C9	The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered by typing "esentutl /d %2 /l%3 /s%4". Once the database has been successfully recovered the File Replication Service can be restarted by typing "net start ntfrs".
0xC00034CF	The File Replication Service could not grant an unknown user access to the API "%1". Access checks can be disabled for "%1" by running regedt32. Click on Start, Run, and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Access Checks, "%1", and "%2". Change the string to Disabled. Permissions can be changed by highlighting "%1" and then clicking on the toolbar option Security and then Permissions...
0xC00034D1	The File Replication Service cannot enable replication on the comptuer %1 until a backup/restore application completes. A backup/restore application has set a registry key that prevents the File Replication Service from starting until the registry key is deleted or the system is rebooted. The backup/restore application may still be running. Check with your local administrator before proceeding further. The computer can be rebooted by clicking on Start, Shutdown, and selecting Restart. WARNING - DELETING THE REGISTRY KEY IS NOT RECOMMENDED! Applications may fail in unexpected ways. The registry key can be deleted by running regedt32. Click on Start, Run, and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Backup/Restore, "Stop NtFrs from Starting". On the toolbar, click on Edit and select Delete. Be careful! Deleting a key other than "Stop NtFrs From Starting" can have unexpected sideeffects.
0xC00034D4	The File Replication Service is stopping on the computer %1 because a universally unique ID (UUID) cannot be created. The SDK function UuidCreate() returned the error "%2". The problem may be the lack of an Ethernet address, token ring address, or network address. The lack of a network address implies an unsupported netcard. The File Replication Service will restart automatically at a later time. For more information about the automatic restart right click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery.
0xC00034D6	The File Replication Service cannot replicate %1 with the computer %2 because the computer's SID cannot be determined from the distinguished name "%3". The File Replication Service will retry later.
0xC00034D7	The RPC binding failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
0xC00034D8	The RPC binding failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service.
0xC00034D9	The RPC call failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
0xC00034DA	The RPC call failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service.
0xC00034DB	The RPC binding failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be available till the binding succeeds. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
0xC00034DC	The RPC binding failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be available till the binding succeeds. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service.
0xC00034DD	The RPC call failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be available till the call succeeds. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
0xC00034DE	The RPC call failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be available till the call succeeds. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service.
0xC00034DF	The call to VirtualAlloc failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
0xC00034E0	The call to VirtualAlloc failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service.
0xC00034E1	The call to the Registry failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.
0xC00034E2	The call to the Registry failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service.
0xC00034E3	The File Replication Service cannot replicate %1 because the pathname of the replicated directory is not the fully qualified pathname of an existing, accessible local directory.
0xC00034E4	The File Replication Service cannot replicate %1 because the pathname of the customer designated staging directory: %2 is not the fully qualified pathname of an existing, accessible local directory.
0xC00034E5	The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's logging pathname %2.
0xC00034E6	The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's working directory %2.
0xC00034E7	The File Replication Service cannot replicate %1 because it overlaps the staging directory %2.
0xC00034E8	The File Replication Service cannot replicate %1 because it overlaps the replicating directory %2.
0xC00034E9	The File Replication Service cannot replicate %1 because it overlaps the staging directory %2 of the replicating directory %3.
0xC00034EA	The File Replication Service could not prepare the root directory %1 for replication. This is likely due to a problem creating the root directory or a problem removing preexisting files in the root directory. Check that the path leading up to the root directory exists and is accessible.
0xC00034EC	The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside the range of plus or minus %1 minutes. The connection to the partner computer is: "%2" The detected time difference is: %3 minutes. Note: If this time difference is close to a multiple of 60 minutes then it is likely that either this computer or its partner computer was set to the incorrect time zone when the computer time was initially set. Check that the time zone and the system time are correctly set on both computers. If necessary, the default value used to test for computer time consistency may be changed in the registry on this computer. (Note: This is not recommended.) To change this parameter, run regedt32. Click on Start, Run and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Click down the key path: "System\CurrentControlSet\Services\NtFrs\Parameters" Double click on the value name "Partner Clock Skew In Minutes" and update the value. If the value name is not present you may add it with the Add Value function under the Edit Menu item. Type the value name exactly as shown above using the the registry data type REG_DWORD.
0xC00034ED	The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is %1 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further. The file name is: "%2" The connection to the partner computer is: "%3" Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.
0xC00034EE	The File Replication Service is unable to open the customer designated staging directory for replica set %1. The path used for the staging directory is, "%2" The customer designated root path for this replica set is: "%3" The service is unable to start replication on this replica set. Among the possible errors to check are: -- an invalid staging path, -- a missing directory, -- a missing disk volume, -- a file system on the volume that does not support ACLs, -- a sharing conflict on the staging directory with some other application. Correct the problem and the service will attempt to restart replication automatically at a later time.
0xC00034EF	The File Replication Service is unable to open (or create) the pre-install directory under the customer designated replica tree directory for replica set %1. The path used for the pre-install directory is, "%2" The customer designated root path for this replica set is: "%3" The service is unable to start replication on this replica set. Among the possible errors to check are: -- an invalid root path, -- a missing directory, -- a missing disk volume, -- a file system on the volume that does not support NTFS 5.0 -- a sharing conflict on the pre-install directory with some other application. Correct the problem and the service will attempt to restart replication automatically at a later time.
0xC00034F0	The File Replication Service is unable to add this computer to the following replica set: "%1" This could be caused by a number of problems such as: -- an invalid root path, -- a missing directory, -- a missing disk volume, -- a file system on the volume that does not support NTFS 5.0 The information below may help to resolve the problem: Computer DNS name is "%2" Replica set member name is "%3" Replica set root path is "%4" Replica staging directory path is "%5" Replica working directory path is "%6" Windows error status code is %7 FRS error status code is %8 Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time.
0xC00034F3	The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on his computer until the following recovery steps are performed: Recovery Steps: [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window: net stop ntfrs net start ntfrs If this fails to clear up the problem then proceed as follows. [2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled: If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary. If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative. [3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled: (3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location. (3-b) If this server is the only Active Directory Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS. (3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. (3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published. [4] For other Windows 2000 servers: (4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location. (4-b) net stop ntfrs (4-c) rd /s /q %1 (4-d) net start ntfrs (4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time). Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members.
0xC00034F4	The File Replication Service has detected what appears to be an attempt to change the root path for the following replica set: "%1" This is not allowed. To perform this operation you must remove this member from the replica set and add the member back with the new root path. It is possible that this is a transient error due to Active Directory replication delays associated with updating FRS configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory replication is required, you must delete and re-add this member to the replica set. Information related to this event is shown below: Computer DNS name is "%2" Replica set member name is "%3" The current Replica set root path is "%4" The desired new Replica set root path is "%5" Replica staging directory path is "%6"
0xC00034F5	The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". This was detected for the following replica set: "%2" This is not allowed and replication will not occur between these two computers until the duplicate connection objects are removed. It is possible that this is a transient error due to Active Directory replication delays associated with updating FRS configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory replication is required, you must manually delete the duplicate connection objects by following the steps below: [1] Start the Active Directory Sites and Services Snapin. [2] Click on "%3, %4, %5, %6, %7". [3] Look for duplicate connections from "%1" in site "%8". [4] Delete all but one of the connections.
0xC00034F6	The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". This was detected for the following replica set: "%2" This is not allowed and replication will not occur between these two computers until the duplicate connection objects are removed. It is possible that this is a transient error due to Active Directory replication delays associated with updating FRS configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory replication is required, you must manually delete the duplicate connection objects by following the steps below: [1] Start the Active Directory Users and Computers Snapin. [2] Click the view button and advanced features to display the system node. [3] Click on "%3, %4, %5". [4] Under "%5" you will see one or more DFS related replica set objects. Look for the FRS member object "%6" under the subtree for replica set "%2". [5] Under "%6" look for duplicate connections from "%1". [6] Delete all but one of the connections.
0xC00034F7	The File Replication Service has detected that the replica root path has changed from "%2" to "%3". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. This was detected for the following replica set: "%1" Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. [1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set. [2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not.
0xC00034F9	The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica root path is : "%2" Replica root volume is : "%3" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "%3" has been formatted. [2] The NTFS USN journal on volume "%3" has been deleted. [3] The NTFS USN journal on volume "%3" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "%3". Following recovery steps will be taken to automatically recover from this error state. [1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
0xC00036B0	QoS: The Packet Scheduler failed to register with the Generic Packet Classifier (msgpc.sys).
0xC00036B1	QoS: The Packet Scheduler was unable to allocate required resources for initialization.
0xC00036B2	QoS: The Packet Scheduler failed to register as a protocol with NDIS.
0xC00036B3	QoS: The Packet Scheduler failed to register as a miniport with NDIS.
0xC0003715	QoS [Adapter %2]: The network adapter driver failed the query for OID_GEN_MAXIMUM_FRAME_SIZE.
0xC0003716	QoS [Adapter %2]: The network adapter driver failed the query for OID_GEN_MAXIMUM_TOTAL_SIZE.
0xC0003717	QoS [Adapter %2]: The network adapter driver failed the query for OID_GEN_LINK_SPEED.
0xC0003718	QoS [Adapter %2]: The Packet Scheduler failed to bind to the network adapter's miniport driver.
0xC0003719	QoS [Adapter %2]: The UpperBindings key is missing from the registry.
0xC000371A	QoS [Adapter %2]: The Packet Scheduler was unable to register with the NDISWAN Call Manager.
0xC000371B	QoS [Adapter %2]: The Packet Scheduler could not initialize the virtual miniport with NDIS.
0xC000371C	QoS [Adapter %2]: The Packet Scheduler could not obtain the network adapter's friendly name from NDIS.
0xC000371E	QoS [Adapter %2]: Could not initialize due to insufficient nonpaged pool memory.
0xC0003720	QoS [Adapter %2]: Could not allocate non-paged pool memory for storing network addresses.
0xC00037DC	An extra ExitPoint %2 was found at server %3
0xC00037DD	The ExitPoint %2 was missing at server %3
0xC00037DE	The Volume %2 was missing at server %3
0xC00037DF	The extra Volume %2 was found at server %3
0xC00037E0	The extra ExitPoint %2 was deleted successfully from the server %3
0xC00037E1	Unable to delete the extra ExitPoint %2 at the server %3
0xC00037E2	The missing ExitPoint %2 was created at the server %3 successfully
0xC00037E3	Unable to create the missing Exit Point %2 at the server %3
0xC00037E4	Successfully created the missing volume %2 knowledge at the server %3
0xC00037E5	Unable to create the missing Volume %2 info at server %3
0xC00037E6	The extra Volume %2 info was deleted at server %3
0xC00037E7	The extra Volume %2 info was not deleted at server %3
0xC00037E8	Since the DC %2 was unavailable could not verify volumes knowledge.
0xC00037E9	Detected Knowledge inconsistency with the volume %2 at server %3
0xC00037EA	The local Prefix %2 was represented as %3 at remote server %4
0xC00037EB	The remote Prefix %3 was corrected to %2 at remote server %4
0xC00037EC	The remote Prefix %3 was NOT corrected to %2 at remote server %4
0xC00037ED	The machine %2 has become unlinked from the domain. Re-join the machine the machine to this domain.
0xC00038A7	Dfs could not create reparse point for directory %1 under directory %2. The return code is in the record data.
0xC00038A8	Share %1 mapped to %2 does not support reparse points. Upgrade Filesystem and retry.
0xC00038A9	Share %1 mapped to %2 directory overlaps an existing root. The DFS Root will not be created.
0xC00038AD	Root %1 has too many errors. No further eventlogs will be logged on this root.
0xC00038AE	DFS could not initialize winsock library. The return code is in the record data.
0xC00038AF	DFS could not initialize security library. The return code is in the record data.
0xC00038B0	DFS could not create DFS support thread. The return code is in the record data.
0xC00038B1	DFS could not initialize IP site cache. The return code is in the record data.
0xC00038B2	DFS could not synchronize all DFS roots. The return code is in the record data.
0xC00038B3	DFS could not create event handle. The return code is in the record data.
0xC00038B4	DFS could not get required computer information. The return code is in the record data.
0xC00038B5	DFS could not get required cluster information. The return code is in the record data.
0xC00038B6	DFS could not get required DC information. The return code is in the record data.
0xC00038B7	DFS could not initialize prefix table. The return code is in the record data.
0xC00038B8	DFS could not initialize DFS namespace.The return code is in the record data.
0xC00038B9	DFS could not Register DFS Namespaces. The return code is in the record data.
0xC00038BA	DFS could not initialize User/kernel communication package. The return code is in the record data.
0xC00038BB	DFS could not contact any DC for Domain DFS operations. This operation will be retried periodically.
0xC00038BC	DFS could not initialize site support table. The return code is in the record data.
0xC00038C2	DFS could not access its private data from the Active Directory. Please manually check network connectivity, security access, and/or consistency of DFS information in the Active Directory. This error occurred on root %1.
0xC00038C7	DFS does not support multiple roots on Standard server SKU. Please cleanup the roots or upgrade.
0xC00038CB	DFS was unable to resynchronize this root target for root: %1. This may lead to inaccessability of portions of the DFS namespace. Please verify the share %1 has all the link directories created for the DFS links. This error may occur if there are directories on this share that may be preventing creation of links.
0xC00038CC	DFS was unable to delete link: %2 for root: %1 during a link move operation.
0xC00038CF	The list of folder targets for the following Distributed File System (DFS) folder is corrupt. DFS folder: %1
0xC00038D0	A Distributed File System (DFS) folder with folder targets was created that contains other DFS folders. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder 1: %2 DFS folder 2: %3
0xC00038D1	A Distributed File System (DFS) folder with folder targets was created that contains other DFS folders. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder: %2
0xC00038D3	A Distributed File System (DFS) folder was created with conflicting descriptions. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder path: %2 DFS folder 1: %3 DFS folder 2: %4
0xC00038D4	The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
0xC00038D6	The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
0xC0003908	Bridge: The bridge could not be initialized because the bridge failed to register as a protocol with NDIS.
0xC0003909	Bridge: The bridge could not be initialized because the bridge's miniport device name is missing from the registry.
0xC000390A	Bridge: The bridge could not be initialized because the bridge failed to register as a miniport with NDIS.
0xC000390B	Bridge: The bridge could not be initialized because the bridge failed to create a device object.
0xC000390C	Bridge: The bridge could not be initialized because the bridge failed to determine a MAC address for itself.
0xC000390D	Bridge: The bridge failed to create its virtual miniport.
0xC000390E	Bridge: The bridge could not initialize its miniport because Ethernet was not offered as a supported medium.
0xC000390F	Bridge: The bridge could not initialize because it failed to create a system thread.
0xC0003910	Bridge: The bridge could not initialize because it failed to reference its system thread.
0xC0003911	Bridge: The bridge could not initialize because it failed to create a packet pool.
0xC0003912	Bridge: The bridge could not initialize because it failed to create a buffer pool.
0xC0003913	Bridge: The bridge could not initialize because it failed to allocate memory.
0xC000396C	Bridge [Adapter %2]: The bridge could not determine the network adapter's link speed. The network adapter will not be used.
0xC000396D	Bridge [Adapter %2]: The bridge could not determine the network adapter's MAC address. The network adapter will not be used.
0xC000396E	Bridge [Adapter %2]: The bridge could not modify the network adapter's packet filter. The network adapter will not function correctly.
0xC000396F	Bridge [Adapter %2]: The bridge could not retrieve the network adapter's description string. The network adapter will not be used.
0xC0003970	Bridge [Adapter %2]: The bridge failed to bind to the network adapter. The network adapter will not be used.
0xC0003E80	WSK provider has ignored the OwningThread parameter passed to a WSK socket creation request. This happens when the socket needs to be created over a TDI transport provider either because a TDI filter driver is installed or because a client-specified TDI mapping exists that matches the AddressFamily, socketType, and Protocol specified in the socket creation request.
0xC000413C	Computer QoS policies failed to refresh. Error code: %2.
0xC000413D	User QoS policies failed to refresh. Error code: %2.
0xC000413E	QoS failed to open the computer-level root key for QoS policies. Error code: %2.
0xC000413F	QoS failed to open the user-level root key for QoS policies. Error code: %2.
0xC0004140	A computer QoS policy exceeds the maximum allowed name length. The offending policy is listed under the computer-level QoS policy root key, with index %2.
0xC0004141	A user QoS policy exceeds the maximum allowed name length. The offending policy is listed under the user-level QoS policy root key, with index %2.
0xC0004142	A computer QoS policy has a zero length name. The offending policy is listed under the computer-level QoS policy root key, with index %2.
0xC0004143	A user QoS policy has a zero length name. The offending policy is listed under the user-level QoS policy root key, with index %2.
0xC0004144	QoS failed to open the registry subkey for a computer QoS policy. The policy is listed under the computer-level QoS policy root key, with index %2.
0xC0004145	QoS failed to open the registry subkey for a user QoS policy. The policy is listed under the user-level QoS policy root key, with index %2.
0xC0004146	QoS failed to read or validate the "%2" field for the computer QoS policy "%3".
0xC0004147	QoS failed to read or validate the "%2" field for the user QoS policy "%3".
0xC0004148	QoS failed to read or set inbound TCP throughput level, error code: "%2".
0xC0004149	QoS failed to read or set the DSCP marking override setting, error code: "%2".
612 entries