DonatShell
Server IP : 180.180.241.3  /  Your IP : 216.73.216.252
Web Server : Microsoft-IIS/7.5
System : Windows NT NETWORK-NHRC 6.1 build 7601 (Windows Server 2008 R2 Standard Edition Service Pack 1) i586
User : IUSR ( 0)
PHP Version : 5.3.28
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /Windows/System32/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME SHELL ]     

Current File : /Windows/System32/en-US//netevent.dll.mui
MZ@	!L!This program cannot be run in DOS mode.

$uEEELlDLl
DRichEPELb\!	S@.rsrc@@(@Xp			HMUI/p<YuFvϷ|8W՟+~ٛMUIen-US88LL,YZ 	@@Xi@k@@@H@@P{@|@@@@@$M@O@X@X@[@_@a@a@c@c@1#@3#@%@%@!+@+@"0@0@(0@0@(4@4@h/4@4@|04@4@37@7@7@8@G8@l88@8@<8@8@D>8@8@>8@8@L?8@8@LA8@8@pB8@8@dC8@8@HDt@@@@,ESXTxW		<a		aiTmmrh^^,``0ee<lndԔ̕$0ܝduvtxy{}DFUWM!M!)#+#%%*+++++++.D/I/0000D44444444444H44444444̼44\7777778888x888888995:8:@@x				Y]__adfh,dxlX[8]z}~',3|4CCh6GK 8PQ;ST @``BbbCddD4!L!xEN!U!,T,#0#Y %#%\[''x^**j..z00{00X|44x~44~444404444444444H44 44/66877p;77|A 7 7(B77B88K88LN88<Y88[88[88_88Td88 h99il9p9r>>w<AIAzClassic

<Microsoft-Windows-DfsSvc

System

The browser driver has received an election packet from computer %2 on network %3.  The data is the packet received.

The browser has retrieved a list of servers from remote computer %1 on transport %2.%n

There were %3 entries read, and %4 total entries.

The browser has retrieved a list of domains from remote computer %1 on transport %2.%n

There were %3 entries read, and %4 total entries.

pThe Microsoft TCP/IP version 6 driver was started.

The system detected that network adapter %2 was connected to the network,

and has initiated normal operation.

$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.

tThe 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".

%2 : The adapter is configured such that the receive space is smaller than

the maximum packet size.  Some packets may be lost.

%2 : The network adapter has successfully reinserted into the ring.

pThe %1 service was successfully sent a %2 control.

TThe %1 service entered the %2 state.

The start type of the %1 service was changed from %2 to %3.

The %1 service was successfully sent a %2 control.%n%n

The reason specified was: %3 [%4]%n%n

Comment: %5

,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.

The browser driver has forced an election on network %2 because it was unable to find a master browser for that network.

The browser has forced an election on network %1 because a Windows Server (or domain master) browser is started.

The backup browser server %2 is out-of-date.  Consider upgrading this computer.

,The browser running on the Domain Controller has lost an election.  The computer that won the election is %2, on the transport %3.%n

The data contains the election version, election criteria, and remote computer time up, and the same information for

the current computer.

pThe 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.

The browser driver was unable to initialize variables from the Registry.

The browser driver has discarded too many mailslot messages.

The browser driver has discarded too many GetBrowserServerList requests.

The browser has forced an election on network %1 because a master browser was stopped.

The browser has forced an election on network %1 because the Domain Controller (or Server) has changed its role.

%2 could not transfer a packet from the network adapter.  The packet was dropped.

 %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.

%2 received an unexpected %3 packet from a remote computer.

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.

The system registered network adapter with settings :%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6

`The system registered pointer (PTR) resource records (RRs) for network

adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  Primary Domain Suffix : %4%n

  DNS server list :%n

    %5%n

  Sent update to server : %6%n

  IP Address : %7

,The system registered host (A or AAAA) resource records (RRs) for network

adapter%nwith settings :%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6

DService started successfully

A new volume ID has been assigned for %1:%n%2%n%n

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.

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.

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.

\The File Replication Service is starting.

\The File Replication Service is stopping.

\The File Replication Service has stopped.

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.

%n

%nType "net share" to check for the SYSVOL share.

The File Replication Service successfully added this computer to the following

replica set:

%n    "%1"

%n

%nInformation related to this event is shown below:

%nComputer DNS name is "%2"

%nReplica set member name is "%3"

%nReplica set root path is "%4"

%nReplica staging directory path is "%5"

%nReplica working directory path is "%6"

The File Replication Service successfully added the connections shown below

to the replica set:

%n    "%1"

%n

%n    %2

%n    %3

%n    %4

%n    %5

%n    %6

%n    %7

%n    %8

%n    %9

%n

%nMore information may appear in subsequent event log messages.

Dfs received a referral request for "%2".  The return code is in the data.

HThe path "%2" is not a dfs path

TDfs was unable to open the Lan Redir

Dfs was unable to open a connection to server %2.  The error returned is in the record data.

Dfs was unable to obtain a referral for "%2" from %3.  The error returned is in the record data.

\Dfs obtained a referral for "%2" from %3

|Dfs reached its limit of attempts of resolution of "%2".

Dfs was unable to obtain the special referral table from %2.  The error returned is in the record data.

Dfs failed on open of %2 directed to %3.  The error returned is in the record data.

NetrDfsEnum received an enumeration.  The return code is in the record data.

NetrDfsEnumEx received an enumeration.  The return code is in the record data.

DFS re-established a connection to the PDC to initiate Domain DFS operations.

dDFS has connected to the %1 Active Directory.

TDFS server has finished initializing.

PDFS 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.

\DFS has finished building all namespaces.

$DFS is requesting the client for a larger buffer for trusted domain information. Some Win98 clients may not be able to access DFS namespaces.

Dfs successfully created the reparse point for directory %1 under directory %2. This operation had previously failed.

The DFS Namespace service successfully initialized the trusted domain information on this domain controller.

The DFS Namespace service successfully initialized cross forest trust information on this domain controller.

Computer QoS policies successfully refreshed. No changes detected.

Computer QoS policies successfully refreshed. Policy changes detected.

User QoS policies successfully refreshed. No changes detected.

User QoS policies successfully refreshed. Policy changes detected.

dThe 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.

The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. 

Setting value is Level 0 (minimum throughput).

The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. 

Setting value is Level 1.

The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. 

Setting value is Level 2.

The Advanced QoS Setting for inbound TCP throughput level successfully refreshed. 

Setting value is Level 3 (maximum throughput).

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.

XThe Advanced QoS Setting for DSCP marking overrides successfully refreshed. 

Application DSCP marking requests will be ignored. Only QoS policies can set DSCP values.

$The Advanced QoS Setting for DSCP marking overrides successfully refreshed. 

Applications can set DSCP values independently of QoS policies.

tSelective 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.    

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.

The server could not expand a table because the table reached the maximum size.

While transmitting or receiving data, the server encountered a network error.

Occassional 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.

The %2 disk is at or near capacity.  You may need to delete some files.

The server was unable to allocate a work item %2 times in the last %3 seconds.

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.

The server was unable to find a free raw work item %2 times in the last %3 seconds.

The server was unable to allocate resources for blocking I/O %2 times in the last %3 seconds.

The server has detected an attempted Denial-Of-Service attack from client %2, and has disconnected the connection.

tThe 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.

xThe 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.

hThe server could not bind to the transport %1.

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.

The security descriptor stored in the Registry for the share %1 was invalid.  The share was not automatically recreated.

|The server service was unable to load the server driver.

The server service was unable to unload the server driver.

pThe server service was unable to map error code %1.

xThe 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.

The server service was unable to change the domain name from %1 to %2.

The server service was unable to register to the transaction resource manager. Remote transactions will be unavailable.

dThe redirector was unable to allocate memory.

The redirector could not create its device.  The redirector could not be started.

lThe redirector could not create a system thread.

The redirector could not set the priority for a system thread.

The redirector received an incorrectly formatted response from %2.

pThe redirector received an SMB that was too short.

The redirector received an incorrect response from %2 to a lock request.

The redirector failed to unlock part of a file on server %2.

The redirector failed to write data to server %2 after the file was closed.

An unexpected network error has occurred on the virtual circuit to %2.

dThe redirector has timed out a request to %2.

|The redirector received an invalid oplock level from %2.

xThe redirector dereferenced a connection through zero.

pThe redirector dereferenced a server through zero.

The redirector dereferenced the allocated SMB count through zero.

The redirector accessed a share-level server that indicates it encrypts passwords.

This combination is not supported.

xThe redirector failed to determine the connection type.

DThe redirector failed to allocate a multiplex table entry.  This indicates that

the MAXCMDS parameter to the redirector is insufficient for the users needs.

The redirector failed to allocate a buffer for an oplock break.

The redirector failed to map the requested file disposition (for NtCreateFile).

@The redirector is allocating additional resources for input/output request packet contexts.  This is

probably caused by a resource leak in the redirector.

(A write-behind operation has failed to the remote server %2.  The data contains the amount requested to write and the amount actually written.

The redirector was unable to create a worker thread because it has already created the maximum number of configured work threads.

The redirector was unable to initialize variables from the Registry.

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.

The redirector has failed to connect to the server %2 on the primary transport.  The data contains the error.

The redirector was unable to update the file attributes on a file located on server %2.

The data contains the name of the file.

0The 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.

The redirector was unable to register the domain %2 on to transport %3 for the following reason: %4. Transport has been taken offline.

The redirector was unable to register the address for transport %3 for the following reason: %4. Transport has been taken offline.

The redirector was unable to initialize security context or query context attributes.

hThe redirector was unable to build SMB header.

The redirector detected a security signature mismatch. The connection has been disconnected.

TUnable to allocate a %2 byte message.

|%2 message allocations have failed since initialization.

hUnable to allocate a %2 byte external message.

%2 external message allocations have failed since initialization.

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.

Invalid default gateway address %2 was specified for network adapter %3.

Some remote networks may not be reachable as a result.

(More than the maximum number of default gateways were specified for

network adapter %2. Some remote networks may not be reachable as a result.

Autoconfigured address limit has been reached. No further autoconfigured addresses will be added until the interface is reconnected.

Autoconfigured route limit has been reached. No further autoconfigured routes will be added until the interface is reconnected.

More than the supported number of out of order IP fragments were received. One or

more fragmented IP packets were dropped as a result.

TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

HTCP/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.

\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.

TCP/IP has detected high memory utilization and has terminated some existing connections to 

maintain system stability.  

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. 

Backlog of pending datagram sends reached. Please increase the value of Tcpip\Parameters\DGMaxSendFree in the registry.

The backup WINS server address is not configured in the registry.

The primary WINS server address is not configured in the registry.

The backup WINS server address is not formated correctly in the registry.

The primary WINS server address is not formatted correctly in the registry.

There are no network adapters configured for this protocol stack.

Unable to open the registry to read the WINS server addresses.

The Netbios Name Scope has a component longer than 63 characters. Each label

in the Scope cannot be longer than 63 bytes.

The Netbios Name Scope is too long. The scope cannot be longer than

255 bytes.

P%2 : Timed out during an operation.

%2 : The driver cannot function because the network adapter is disabled.

P%2 : There is an I/O port conflict.

p%2 : There is an I/O port or DMA channel conflict.

l%2 : There is a memory conflict at address 0x%3.

p%2 : There is a interrupt conflict at Interrupt %3.

t%2 : There is a resource conflict at DMA channel %3.

%2 : The specified registry entry MaxReceives is out of range. Using 

default value.

%2 : The specified registry entry MaxTransmits is out of range. Using 

default value

%2 : The specified registry entry MaxFrameSize is out of range. Using 

default value.

%2 : The specified registry entry MaxInternalBufs is out of range. Using 

default value.

%2 : The specified registry entry MaxMulticast is out of range. Using 

default value.

%2 : The specified registry entry ProductId is out of range. Using 

default value.

(%2 : A Token Ring Lobe Wire Fault has occurred. Verify cable connections. 

The network adapter will continue to try to reinsert into the ring.

%2 : The adapter had detected a loss of signal on the ring.  The adapter

will continue to try to reinsert back into the ring.

%2 : The adapter has received a request to deinsert from the

ring.  The adapter will continue to try to reinsert back into the ring.

P%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.

%2 : The network adapter has detected that the token ring cable is disconnected 

from the network adapter. Please reconnect the cable.

%2 : The network adapter has successfully completed a previously failed reset.

PThe Event log service was started.

PThe Event log service was stopped.

|The previous system shutdown at %1 on %2 was unexpected.

XMicrosoft (R) Windows (R) %1 %2 %3 %4.

The NetBIOS name and DNS host name of this machine have been changed from %1 to %2.

The DNS domain assigned to this computer has been changed from %1 to %2.

LThe system uptime is %5 seconds.

hA 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.%n%n



Note that if this service is configured to start under a debugger, this behavior

is expected.

A request has been submitted to promote the computer to backup when it is already a

master browser.

(The browser has received a server announcement indicating that the computer %2

is a master browser, but this computer is not a master browser.

The browser has received an illegal datagram from the remote computer %2 to name %3 on transport %4.  The data is the datagram.

The browser service was unable to retrieve a list of servers from the browser master %1 on the network %2.%n

%n

Browser master: %1%n

Network: %2%n

%n

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.

The browser service was unable to retrieve a list of domains from the browser master %1 on the network %2.%n

%n

Browser master: %1%n

Network: %2%n

%n

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.

The value for the parameter %1 to the browser service was illegal.

Name too long in key %1: Name = %s.  The Sap Agent cannot continue.

%2 could not allocate a resource of type %3 due to system resource problems.

%2 could not allocate a resource of type %3 due to its configured size of %4.

%2 could not allocate a resource of type %3 due to a specifically configured limit of %4.

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.

hThe value for the %2 parameter %3 was illegal.

4The 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.

The DNS Client service failed to reach DNS server at address %1. It will

not use this DNS server for %2 seconds.

The system failed to register network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS Server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n 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.

|The system failed to register network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

(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.

The system failed to register network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n 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.

<The system failed to register network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

<The system failed to register network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

The system failed to register network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

\The system failed to register pointer (PTR) resource records (RRs) for

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.%n%n 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.

The system failed to register pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.%n%n 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.

The system failed to register pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.%n%n

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.

XThe system failed to register pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.%n%n

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.

The system failed to register pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.%n%n

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.

LThe system failed to register pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.

0The system failed to register host (A or AAAA) resource records (RRs) for

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

dThe system failed to register host (A or AAAA) resource records (RRs) for

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

The system failed to register host (A or AAAA) resource records for 

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

DThe system failed to register host (A or AAAA) resource records (RRs) for

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

tThe system failed to register host (A or AAAA) resource records (RRs) for

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

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.

TThe system failed to register host (A or AAAA) resource records (RRs) for

network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

The system failed to update and remove registration for the

network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

xThe system failed to update and remove registration for the

network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

$The system failed to update and remove registration for the network

adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

The system failed to update and remove registration for the network

adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

The system failed to update and remove registration for the network

adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.%n%n

See event details for specific error code information.

lThe system failed to update and remove the DNS registration for the

network adapter with settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

The system could not update to remove this DNS registration because of

a system problem. See event details for specific error code information.

 The system failed to update and remove pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.

<The system failed to update and remove pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.

The system failed to update and remove pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.

8The system failed to update and remove pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.

The system failed to update and remove pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

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.

\The system failed to update and remove pointer (PTR) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Adapter-specific Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address : %6%n%n

The system could not remove these PTR RRs because because of a system

problem. See event details for specific error code information.

The system failed to update and remove host (A or AAAA) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

`The system failed to update and remove host (A or AAAA) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

|The system failed to update and remove host (A or AAAA) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

HThe system failed to update and remove host (A or AAAA) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

The system failed to update and remove host (A or AAAA) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

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.

PThe system failed to update and remove host (A or AAAA) resource records (RRs)

for network adapter%nwith settings:%n%n

  Adapter Name : %1%n

  Host Name : %2%n

  Primary Domain Suffix : %3%n

  DNS server list :%n

    %4%n

  Sent update to server : %5%n

  IP Address(es) :%n

    %6%n%n

The reason the update request failed was because of a system problem.

See event details for specific error code information

The binary MOF in the resource named %1 in the image file %2 is not valid.

The binary MOF in the resource named %1 in the image file %2 could not be loaded.

The registration information for the image file %1 is not valid.

The registry path (%1) passed by a kernel mode driver is invalid. The driver device object is in the additional data.

An event was fired specifying a static instance name that could not be resolved.

An error occured while attempting to query for the event data referenced by a fired event.

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.

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.

The File Replication Service is having trouble enabling replication

from %1 to %2 for %3 using the DNS name %4. FRS will keep retrying.

%n Following are some of the reasons you would see this warning.

%n

%n [1] FRS can not correctly resolve the DNS name %4 from this computer.

%n [2] FRS is not running on %4.

%n [3] The topology information in the Active Directory for this replica has not

yet replicated to all the Domain Controllers.

%n

%n 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.

The File Replication Service has enabled replication from %1 to %2 for %3

after repeated retries.

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.

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.

%n

%nType "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.

%n

%nThe 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.

PThe 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.

%n

%nType "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.

%n

%nThe initialization of the system volume can take some time.

The time is dependent on the amount of data in the system volume.

%n

%nThe 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.

%n

%nWARNING - BYPASSING THE SYSTEM VOLUME INITIALIZATION IS NOT RECOMMENDED.

Applications may fail in unexpected ways.

%n

%nThe value SysvolReady is located by clicking on HKEY_LOCAL_MACHINE

and then clicking on System, CurrentControlSet, Services, Netlogon,

and Parameters.

%n

%nThe Netlogon service can be restarted by typing "net stop netlogon"

followed by "net start netlogon".

The File Replication Service will not check access to the API "%1".

%n

%nAccess checks can be enabled for "%1" by running regedt32.

%n

%nClick on Start, Run, and type regedt32.

%n

%nClick 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.

%n

%nPermissions can be changed by highlighting "%1" and then clicking on the

toolbar option Security and then Permissions...

 The File Replication Service did not grant the user "%3" access to the

API "%1".

%n

%nPermissions for "%1" can be changed by running regedt32.

%n

%nClick on Start, Run, and type regedt32.

%n

%nClick 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...

%n

%nAccess checks can be disabled for "%1". Double click on "%2" and

change the string to Disabled.

TThe File Replication Service moved the preexisting files in %1 to %2.

%n

%nThe 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.

%n

%nIn some cases, the File Replication Service may copy a file

from %2 into %1 instead of replicating the file from some other

replicating partner.

%n

%nSpace can be recovered at any time by deleting the files in %2.

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.

%n

%nThe current value of the staging space limit is %1 KB.

%n

%nTo change the staging space limit, run regedt32.

%n

%nClick on Start, Run and type regedt32.

%n

%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,

CurrentControlSet, Services, NtFrs, Parameters, and the value

"Staging Space Limit in KB".

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.

%n

%nThe staging space limit is %1 KB and the file size is %2 KB.

%n

%nTo change the staging space limit, run regedt32.

%n

%nClick on Start, Run and type regedt32.

%n

%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,

CurrentControlSet, Services, NtFrs, Parameters, and the value

"Staging Space Limit in KB".

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".

%n

%nThe File Replication Service will try using the name "%1" until the

computer's DNS name appears.

The File Replication Service detected an invalid parameter value in the

registry.  %1.

%n

%nThe expected registry key name is "%2".

%nThe expected value name is "%3".

%nThe expected registry data type is %4.

%nThe allowed range for this parameter is %5

%nThe data units for this parameter value are %6.

%nThe File Replication Service is using a default value of "%7".

%n

%nTo change this parameter, run regedt32.

%n

%nClick on Start, Run and type regedt32.

%n

%nClick on the window entitled HKEY_LOCAL_MACHINE.

%nClick down the key path: "%8"

%nDouble click on the value name -

%n    "%9"

%nand update the value.

%nIf 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.

The File Replication Service is deleting this computer from the replica set "%1" as an attempt to

recover from the error state,

%n Error status = %2

%n 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.

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.

%n

%n %2

%n

QoS [Adapter %2]:%nThe BestEffortLimit value set in the registry exceeds the LinkSpeed. Defaulting to Unlimited BestEffort.

QoS [Adapter %2]:%nThe registry entry for BestEffortLimit is not supported over WAN links. Defaulting to Unlimited BestEffort mode.

QoS [Adapter %2]:%nTotal 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.

DFS could not contact the %1 Active Directory. DFS will be using cached data. The return code is in the record data.

DFS Root %1 failed during initialization. The root will not be available.

DFS is unable to return the entire list of trusted domains to the client. There are too many trusted domains.

DFS was unable to move all matching links of root: %1 for path %2 to new path %3

,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.

LDFS 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.

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.

lPUT failed for file %1 on Close. ErrorStatus: %2.

tDELETE failed for file %1 on Close. ErrorStatus: %2.

xPROPPATCH failed for file %1 on Close. ErrorStatus: %2.

PROPPATCH failed for file %1 on SetFileInfo. ErrorStatus: %2.

\EQOS: ***Testing***, with one string %2.

EQOS: ***Testing***, with two strings, string1 is %2, string2 is %3.

A computer QoS policy "%2" has an invalid version number. This policy will not be applied.

A user QoS policy "%2" has an invalid version number. This policy will not be applied.

A computer QoS policy "%2" does not specify a DSCP value or throttle rate. This policy will not be applied.

A user QoS policy "%2" does not specify a DSCP value or throttle rate. This policy will not be applied.

(Exceeded the maximum number of computer QoS policies. 

The computer QoS policy "%2" and subsequent computer QoS policies will not be applied.

Exceeded the maximum number of user QoS policies. 

The user QoS policy "%2" and subsequent user QoS policies will not be applied.

HA computer QoS policy "%2" potentially conflicts with other QoS policies. 

See documentation for rules about which policy will be applied at packet send time.

@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.

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.

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.

The server's call to a system service failed unexpectedly.

The server was unable to perform an operation due to a shortage of available resources.

The server could not create its device.  The server could not be started.

The server could not create a process.  The server could not be started.

The server could not create a startup thread.  The server could not be started.

The server received an unexpected disconnection from a client.

The server received an incorrectly formatted request from %2.

The server could not open the named pipe file system.  Remote named pipes are disabled.

The server could not start the scavenger thread.  The server could not be started.

4The server's configuration parameter "irpstacksize" is too small for the server to use a local device.  Please increase the value of this parameter.

lThe server was unable to allocate virtual memory.

(The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

The server was unable to allocate from the system paged pool because the server reached the configured limit for paged pool allocations.

The server was unable to allocate from the system nonpaged pool because the pool was empty.

The server was unable to allocate from the system paged pool because the pool was empty.

The server's Registry key %1 was not present.  The server could not start.

The server's Registry key %1 was not present and could not be created.  The server could not start.

The server did not bind to any transports.  The server could not start.

The server could not bind to the transport %1 because another computer on the network has the same name.  The server could not start.

%2

|Unable to create device object %2. Initialization failed.

Unable to allocate required resources. Initialization failed.

 IP has been bound to more than the maximum number of supported interfaces.

Some interfaces on network adapter %2 will not be initialized.

No subnet mask was specified for interface %2. This interface and all

subsequent interfaces on network adapter %3 cannot be initialized.

An invalid address %2 was specified for network adapter %3. This interface

cannot be initialized.

An invalid subnet mask %2 was specified for address %3 on network adapter %4.

This interface cannot be initialized.

,IP could not allocate some resources required to configure network adapter %2.

Some interfaces on this network adapter will not be initialized.

IP could not open the registry key for network adapter %2.

Interfaces on this network adapter will not be initialized.

Unable to read the configured IP addresses for network adapter %2.

IP interfaces will not be initialized on this network adapter.

Unable to read the configured subnet masks for network adapter %2.

IP interfaces will not be initialized on this network adapter.

IP was unable to read its bindings from the registry. No network interfaces

were configured.

DInitialization of IP failed.

4The system detected an address conflict for IP address %2 with the system

having network hardware address %3. The local interface has been disabled.

hThe 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.

(Unable to read or write the NTE Context list for network adapter %2.

IP interfaces on this network adapter may not be initialized completely.

LInitialization of TCP/UDP failed.

LThe driver could not be created.

Unable to open the Registry Parameters to read configuration information.

xUnable to configure the addresses of the WINS servers.

Initialization failed because the transport refused to open initial addresses.

Initialization failed because the transport refused to open initial connections.

TData structure initialization failed.

Initialization failed because the timers could not be started.

LInitialization 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.



Unable to open the Registry Linkage to read configuration information.

Unable to read the driver's bindings to the transport from the registry.

Unable to read the driver's exported linkage configuration information.

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.

HAnother 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.

XThe 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.

NetBT failed to process a request because it encountered OutOfResources

exception(s) in the last 1 hour.

%2 : Has encountered a conflict in resources and could not load.

%2 : Could not allocate the resources necessary for operation.

%2 : Has determined that the network adapter is not functioning properly.

X%2 : Could not find a network adapter.

|%2 : Could not connect to the interrupt number supplied.

x%2 : Has encountered an internal error and has failed.

t%2 : The version number is incorrect for this driver.

l%2 : Has encountered an invalid network address.

l%2 : Does not support the configuration supplied.

%2 : The network adapter has returned an invalid value to the driver.

x%2 : A required parameter is missing from the registry.

%2 : The I/O base address supplied does not match the jumpers on the adapter.

%2 : The download file is invalid.  The driver is unable to load.

%2 : The network adapter has detected an Adapter Check as a result of 

an unrecoverable hardware or software error.

A uniprocessor-specific driver was loaded on a multiprocessor system.  The driver could not load.

The %1 service failed to start due to the following error: %n%2

The %1 service depends on the %2 service which failed to start because of the following error: %n%3

The %1 service depends on the %2 group and no member of this group started.

The %1 service depends on the following nonexistent service: %2

lThe %1 call failed with the following error: %n%2

|The %1 call failed for %2 with the following error: %n%3

The system reverted to its last known good configuration.  The system is restarting....

TNo backslash is in the account name.

Timeout (%1 milliseconds) waiting for the %2 service to connect.

hTimeout (%1 milliseconds) waiting for ReadFile.

Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.

pMessage returned in transaction has incorrect size.

Logon attempt with current password failed with the following error: %n%1

Second logon attempt with old password also failed with the following error: %n%1

Boot-start or system-start driver (%1) must not depend on a service.

|The %1 service has reported an invalid current state %2.

pDetected circular dependencies demand starting %1.

xDetected circular dependencies auto-starting services.

Circular dependency: The %1 service depends on a service in a group which starts later.

Circular dependency: The %1 service depends on a group which starts later.

About to revert to the last known good configuration because the %1 service failed to start.

LThe %1 service hung on starting.

|The %1 service terminated with the following error: %n%2

|The %1 service terminated with service-specific error %2.

At least one service or driver failed during system startup.  Use Event Viewer to examine the event log for details.

The following boot-start or system-start driver(s) failed to load: %1

Windows could not be started as configured.  A previous working configuration was used instead.

The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key.

@Service Control Manager %0

PThe %1 service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.

$The %1 service terminated unexpectedly.  It has done this %2 time(s).  The following corrective action will be taken in %3 milliseconds: %5.

dThe 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: %n%4

hThe Service Control Manager did not initialize successfully. The security

configuration server (scesrv.dll) failed to initialize with error %1.  The

system is restarting...

The %1 service terminated unexpectedly.  It has done this %2 time(s).

$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).

The %1 service was unable to log on as %2 with the currently configured

password due to the following error: %n%3%n%nTo ensure that the service is

configured properly, use the Services snap-in in Microsoft Management

Console (MMC).

The %1 service was unable to log on as %2 with the currently configured

password due to the following error:

%nLogon failure: the user has not been granted the requested logon type at this

computer.%n

%nService: %1

%nDomain and account: %2%n

%nThis service account does not have the necessary user right "Log on as a service."%n

%nUser Action%n

%nAssign "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.%n

%nIf 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.

The %1 service did not shutdown properly after receiving a preshutdown control.

dThe %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.

The %1 command failed to start due to the following error: %n%2

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.

The browser was unable to update the service status bits.  The data is the error.

The browser was unable to update its role.  The data is the error.

The browser was unable to promote itself to master browser.  The computer that currently

believes it is the master browser is %1.

The browser driver was unable to convert a character string to a unicode string.

The browser was unable to add the configuration parameter %1.

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.

The browser has failed to start because the dependent service %1 had invalid service status %2.

Status             Meaning

  1              Service Stopped%n

  2              Start Pending%n

  3              Stop Pending%n

  4              Running%n

  5              Continue Pending%n

  6              Pause Pending%n

  7              Paused%n

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.

The browser was unable to promote itself to master browser.  The computer that currently

believes it is the master browser is unknown.

The browser service has failed to retrieve the backup list too many times on transport %1.

The backup browser is stopping.

The browser has received a GetBrowserServerList request when it is not the master browser.

The browser has failed to start because of an error in the DirectHostBinding parameter to the browser.

The Registry Key %1 was not present.  The Sap Agent could not start.

Winsock startup routine failed.  The Sap Agent cannot continue.

Socket create call failed for main socket. The Sap Agent cannot continue.

Setting broadcast option on socket failed.  The Sap Agent cannot continue.

Binding to SAP Socket failed.  The Sap Agent cannot continue.

Getting bound address of socket failed.  The Sap Agent cannot continue.

Setting option EXTENDED_ADDRESS failed.  The Sap Agent cannot continue.

Setting NWLink option BCASTINTADDR failed.  The Sap Agent cannot continue.

Error allocating memory to hold a card structure.  The Sap Agent cannot continue.

XEnumeration of cards returned 0 cards.

Error creating thread counting event.  The Sap Agent cannot continue.

Error creating receive semaphore.  The Sap Agent cannot continue.

Error creating send event.  The Sap Agent cannot continue.

Error starting receive thread.  The Sap Agent cannot continue.

Error starting worker thread.  The Sap Agent cannot continue.

Error allocating database array.  The Sap Agent cannot continue.

Error allocating hash table.  The Sap Agent cannot continue.

Error starting LPC worker thread.  The Sap Agent cannot continue.

Error creating the LPC port.  The Sap Agent cannot continue.

Error creating the LPC thread event.  The Sap Agent cannot continue.

Error allocating memory for an LPC Client structure.  The Sap Agent cannot continue.

Error allocating buffer to hold LPC worker thread handles.  The Sap Agent cannot continue.

The value for WANFilter in the registry must be 0-2.  The Sap Agent cannot continue.

Error creating event for card list access synchronization.  The Sap Agent cannot continue.

Error creating event for database access synchronization.  The Sap Agent cannot continue.

Error creating WAN control semaphore.  The Sap Agent cannot continue.

Socket create call failed for WAN socket.  The Sap Agent cannot continue.

Binding to WAN socket failed.  The Sap Agent cannot continue.

Error starting WAN worker thread.  The Sap Agent cannot continue.

Error starting WAN check thread.  The Sap Agent cannot continue.

Error on getsockopt IPX_MAX_ADAPTER_NUM.  Data is the error code.  The Sap Agent cannot continue.

Error allocating buffer to hold WAN notify thread handles.  The Sap Agent cannot continue.

Error creating the WAN thread event.  The Sap Agent cannot continue.

p%2 failed to register itself with the NDIS wrapper.

\%2 failed to bind to network adapter %3.

T%2 could not find network adapter %3.

%2 failed while setting object identifier %3 on network adapter %4.

%2 failed while querying object identifier %3 on network adapter %4.

p%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.

%2 had no frame types configured for the binding to adapter %3.

%2 failed to initialize because the driver device could not be created.

%2 could not bind to any adapters. The transport could not start.

Unable to start a DCOM Server: %3.

The error:%n"%%%2"%nHappened while starting this command:%n%1

Unable to start a DCOM Server: %3 as %4/%5.

The error:%n"%%%2"%nHappened while starting this command:%n%1

Access denied attempting to launch a DCOM Server.

The server is:%n%1%nThe user is %2/%3, SID=%4.

Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion.

The server is:%n%1%nThe user is %2/%3, SID=%4.

DCOM got error "%%%1" and was unable to logon %2\%3

in order to run the server:%n%4

DCOM got error "%%%1" attempting to start the service %2 with arguments "%3"

in order to run the server:%n%4

DCOM got error "%%%1" from the computer %2 when attempting to

activate the server:%n%3

DCOM got error "%%%1" when attempting to

activate the server:%n%2

DCOM got error "%%%1" from the computer %2 when attempting to

the server:%n%3 with file %4.

DCOM was unable to communicate with the computer %1 using any of the configured

protocols.

The server %1 did not register with DCOM within the required timeout.

The server %1 could not be contacted to establish the connection to the client

There is an assertion failure in DCOM.  Context follows:

%1

%2

%3

DCOM server attempted to listen on an invalid endpoint.

Protseq:  %1

Endpoint: %2

Flags:    %3

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.

Unable to start DNS Client Service.

Failed to load DLL %2, Error: %1.

Please reinstall this DLL from installation CD.

hUnable 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.

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.

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.

XUnable 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.

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.

(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.

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.

The WMI service was unable to open the WMI service device. The status code is in the additional data.

An internal error occured in Distributed Link Tracking.  The error code was %1.

TService failed to start.  Error = %1

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.

<File Replication Service

|The File Replication Service stopped without cleaning up.

The File Replication Service has stopped after taking an assertion failure.

xThe File Replication Service failed a consistency check

%n  (%3)

%nin "%1" at line %2.

%n

%nThe 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.

%n

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.

LThe 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.

%n

%nThe volume's type can be found by typing "chkdsk %4".

%n

%nThe volume can be upgraded to NTFS 5.0 or later by typing "chkntfs /E %4".

The File Replication Service on the computer %1 cannot communicate with

the File Replication Service on the computer %2.

%n

%nVerify that the computer %2 is up and running.

%n

%nVerify that the File Replication Service is running on %2 by

typing "net start ntfrs" on %2.

%n

%nVerify 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.

%n

%nThe DNS server is responsible for mapping computer names to IP addresses.

The commands "ipconfig" and "nslookup" help diagnose problems with the

DNS server.

%n

%nTyping "ipconfig /all" will list the computer's IP address and the IP

address of the computer's DNS servers. Type "ping <DNS server's IP address>"

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.

%n

%nSome network problems between %1 and %2 can be cleared up by flushing

the DNS Resolver Cache. Type "ipconfig /flushdns".

%n

%nSome network problems between %1 and %2 can be cleared up by renewing

the IP address. Type "ipconfig /release" followed by "ipconfig /renew".

%n

%nSome 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".

%n

%nSome problems between %1 and %2 can be cleared up by restarting

the File Replication Service. Type "net stop ntfrs" followed by

"net start ntfrs".

%n

%nSome 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.

%n

%nOther network and computer problems are beyond the scope of

this event log message.

The File Replication Service is stopping on computer %1 because there is no free

space on the volume containing %2.

%n

%nThe available space on the volume can be found by typing

"dir %2".

%n

%nOnce 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.

%n

%nFor more information about the automatic restart right click on

My Computer and then click on Manage, System Tools, Services, File

Replication Service, and Recovery.

%n

%nFor more information about managing space on a volume type "copy /?",

"rename /?", "del /?", "rmdir /?", and "dir /?".

hThe File Replication Service on computer %1 is stopping because the

database %2 is corrupted.

%n

%nThe database can be recovered by typing "esentutl /d %2 /l%3 /s%4".

%n

%nOnce the database has been successfully recovered the

File Replication Service can be restarted by typing "net start ntfrs".

The File Replication Service could not grant an unknown user access to the

API "%1".

%n

%nAccess checks can be disabled for "%1" by running regedt32.

%n

%nClick on Start, Run, and type regedt32.

%n

%nClick 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.

%n

%nPermissions can be changed by highlighting "%1" and then clicking on the

toolbar option Security and then Permissions...

@The File Replication Service cannot enable replication on the comptuer %1

until a backup/restore application completes.

%n

%nA 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.

%n

%nThe backup/restore application may still be running. Check with your

local administrator before proceeding further.

%n

%nThe computer can be rebooted by clicking on Start, Shutdown, and

selecting Restart.

%n

%nWARNING - DELETING THE REGISTRY KEY IS NOT RECOMMENDED!

Applications may fail in unexpected ways.

%n

%nThe registry key can be deleted by running regedt32.

%n

%nClick on Start, Run, and type regedt32.

%n

%nClick 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.

The File Replication Service is stopping on the computer %1 because

a universally unique ID (UUID) cannot be created.

%n

%nThe SDK function UuidCreate() returned the error "%2".

%n

%nThe 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.

%n

%nThe 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.

The File Replication Service cannot replicate %1 with the computer

%2 because the computer's SID cannot be determined from the distinguished

name "%3".

%n

%nThe File Replication Service will retry later.

8The 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.

DThe 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.

0The 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.

<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.

pThe 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.

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.

dThe 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.

pThe 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.

HThe 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.

TThe 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.

HThe 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.

TThe 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.

pThe 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.

The File Replication Service cannot replicate %1 because the pathname

of the customer designated staging directory:

%n    %2

%n is not the fully qualified pathname of an existing, accessible local directory.

The File Replication Service cannot replicate %1 because it overlaps

the File Replication Service's logging pathname %2.

The File Replication Service cannot replicate %1 because it overlaps

the File Replication Service's working directory %2.

The File Replication Service cannot replicate %1 because it overlaps

the staging directory %2.

The File Replication Service cannot replicate %1 because it overlaps

the replicating directory %2.

The File Replication Service cannot replicate %1 because it overlaps

the staging directory %2 of the replicating directory %3.

`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.

%n

%nCheck that the path leading up to the root directory exists and is

accessible.


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.

%n

%nThe connection to the partner computer is:

%n  "%2"

%nThe detected time difference is:  %3 minutes.

%n

%nNote: 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.

%n

%nIf 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.)

%n

%nTo change this parameter, run regedt32.

%n

%nClick on Start, Run and type regedt32.

%n

%nClick on the window entitled HKEY_LOCAL_MACHINE.

%nClick down the key path:

%n   "System\CurrentControlSet\Services\NtFrs\Parameters"

%nDouble click on the value name

%n   "Partner Clock Skew In Minutes"

%nand update the value.

%n

%nIf 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.

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.

%n

%nThe file name is: "%2"

%nThe connection to the partner computer is:

%n  "%3"

%n

%nNote: 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.

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,

%n    "%2"

%nThe customer designated root path for this replica set is:

%n    "%3"

%n

The service is unable to start replication on this replica set.  Among the

possible errors to check are:

%n  --  an invalid staging path,

%n  --  a missing directory,

%n  --  a missing disk volume,

%n  --  a file system on the volume that does not support ACLs,

%n  --  a sharing conflict on the staging directory with some other application.

%n

%nCorrect the problem and the service will attempt to restart replication

automatically at a later time.

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,

%n    "%2"

%nThe customer designated root path for this replica set is:

%n    "%3"

%n

The service is unable to start replication on this replica set.  Among the

possible errors to check are:

%n  --  an invalid root path,

%n  --  a missing directory,

%n  --  a missing disk volume,

%n  --  a file system on the volume that does not support NTFS 5.0

%n  --  a sharing conflict on the pre-install directory with some other application.

%n

%nCorrect the problem and the service will attempt to restart replication

automatically at a later time.

\The File Replication Service is unable to add this computer to the following

replica set:

%n    "%1"

%n

%nThis could be caused by a number of problems such as:

%n  --  an invalid root path,

%n  --  a missing directory,

%n  --  a missing disk volume,

%n  --  a file system on the volume that does not support NTFS 5.0

%n

%nThe information below may help to resolve the problem:

%nComputer DNS name is "%2"

%nReplica set member name is "%3"

%nReplica set root path is "%4"

%nReplica staging directory path is "%5"

%nReplica working directory path is "%6"

%nWindows error status code is %7

%nFRS error status code is %8

%n

%nOther 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.

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:

%n

%n Recovery Steps:

%n

%n [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:

%n

%n    net stop ntfrs

%n    net start ntfrs

%n

%nIf this fails to clear up the problem then proceed as follows.

%n

%n [2] For Active Directory Domain Controllers that DO NOT host any DFS

alternates or other replica sets with replication enabled:

%n

%nIf 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.

%n

%nIf 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.

%n

%nIf 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.

%n

%n

%n [3] For Active Directory Domain Controllers that host DFS alternates

or other replica sets with replication enabled:

%n

%n (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.

%n (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

%nSites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.

%n (3-c) Restore the "system state" of this DC from backup (using ntbackup

or other backup-restore utility) and make it non-authoritative.

%n (3-d) Copy the data from step (3-a) above to the original location

after the sysvol share is published.

%n

%n

%n [4] For other Windows 2000 servers:

%n

%n (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.

%n (4-b)  net stop ntfrs

%n (4-c)  rd /s /q  %1

%n (4-d)  net start ntfrs

%n (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).

%n

%nNote: 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.

<The File Replication Service has detected what appears to be an attempt

to change the root path for the following replica set:

%n    "%1"

%n

%nThis 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.

%n

%nIt 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.

%n

%nInformation related to this event is shown below:

%nComputer DNS name is "%2"

%nReplica set member name is "%3"

%nThe current Replica set root path is "%4"

%nThe desired new Replica set root path is "%5"

%nReplica staging directory path is "%6"

pThe File Replication Service has detected a duplicate connection object between

this computer "%6" and a computer named "%1".

%nThis was detected for the following replica set:

%n    "%2"

%n

%nThis is not allowed and replication will not occur between these two

computers until the duplicate connection objects are removed.

%n

%nIt 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:

%n

%n [1] Start the Active Directory Sites and Services Snapin.

%n [2] Click on "%3, %4, %5, %6, %7".

%n [3] Look for duplicate connections from "%1" in site "%8".

%n [4] Delete all but one of the connections.

0	The File Replication Service has detected a duplicate connection object between

this computer "%7" and a computer named "%1".

%nThis was detected for the following replica set:

%n    "%2"

%n

%nThis is not allowed and replication will not occur between these two

computers until the duplicate connection objects are removed.

%n

%nIt 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:

%n

%n [1] Start the Active Directory Users and Computers Snapin.

%n [2] Click the view button and advanced features to display the system node.

%n [3] Click on "%3, %4, %5".

%n [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".

%n [5] Under "%6" look for duplicate connections from "%1".

%n [6] Delete all but one of the connections.

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.

%nThis was detected for the following replica set:

%n    "%1"

%n

%nChanging the replica root path is a two step process which is triggered by

the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.

%n

%n [1] At the first poll which will occur in %4 minutes this computer will be

deleted from the replica set.

%n [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.

@	The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR.

%n

%n Replica set name is    : "%1"

%n Replica root path is   : "%2"

%n Replica root volume is : "%3"

%n



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.

%n

%n [1] Volume "%3" has been formatted.

%n [2] The NTFS USN journal on volume "%3" has been deleted.

%n [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.

%n [4] File Replication Service was not running on this computer for a long time.

%n [5] File Replication Service could not keep up with the rate of Disk IO activity on "%3".

%n

%n Following recovery steps will be taken to automatically recover from this error state.

%n [1] At the first poll which will occur in %4 minutes this computer will be

deleted from the replica set.

%n [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.

QoS: The Packet Scheduler failed to register with the Generic Packet Classifier (msgpc.sys).

QoS: The Packet Scheduler was unable to allocate required resources for initialization.

QoS: The Packet Scheduler failed to register as a protocol with NDIS.

QoS: The Packet Scheduler failed to register as a miniport with NDIS.

QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_MAXIMUM_FRAME_SIZE.

QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_MAXIMUM_TOTAL_SIZE.

QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_LINK_SPEED.

QoS [Adapter %2]:%nThe Packet Scheduler failed to bind to the network adapter's miniport driver.

QoS [Adapter %2]:%nThe UpperBindings key is missing from the registry.

QoS [Adapter %2]:%nThe Packet Scheduler was unable to register with the NDISWAN Call Manager.

QoS [Adapter %2]:%nThe Packet Scheduler could not initialize the virtual miniport with NDIS.

QoS [Adapter %2]:%nThe Packet Scheduler could not obtain the network adapter's friendly name from NDIS.

QoS [Adapter %2]:%nCould not initialize due to insufficient nonpaged pool memory.

QoS [Adapter %2]:%nCould not allocate non-paged pool memory for storing network addresses.

dAn extra ExitPoint %2 was found at server %3

\The ExitPoint %2 was missing at server %3

XThe Volume %2 was missing at server %3

`The extra Volume %2 was found at server %3

The extra ExitPoint %2 was deleted successfully from the server %3

|Unable to delete the extra ExitPoint %2 at the server %3

The missing ExitPoint %2 was created at the server %3 successfully

Unable to create the missing Exit Point %2 at the server %3

Successfully created the missing volume %2 knowledge at the server %3

|Unable to create the missing Volume %2 info at server %3

lThe extra Volume %2 info was deleted at server %3

tThe extra Volume %2 info was not deleted at server %3

Since the DC %2 was unavailable could not verify volumes knowledge.

Detected Knowledge inconsistency with the volume %2 at server %3

The local Prefix %2 was represented as %3 at remote server %4

The remote Prefix %3 was corrected to %2 at remote server %4

The remote Prefix %3 was NOT corrected to %2 at remote server %4

The machine %2 has become unlinked from the domain. Re-join the machine the machine to this domain.

Dfs could not create reparse point for directory %1 under directory %2. The return code is in the record data.

Share %1 mapped to %2 does not support reparse points. Upgrade Filesystem and retry.

Share %1 mapped to %2 directory overlaps an existing root. The DFS Root will not be created.

Root %1 has too many errors. No further eventlogs will be logged on this root.

DFS could not initialize winsock library. The return code is in the record data.

DFS could not initialize security library. The return code is in the record data.

DFS could not create DFS support thread. The return code is in the record data.

DFS could not initialize IP site cache. The return code is in the record data.

DFS could not synchronize all DFS roots. The return code is in the record data.

DFS could not create event handle. The return code is in the record data.

DFS could not get required computer information. The return code is in the record data.

DFS could not get required cluster information. The return code is in the record data.

DFS could not get required DC information. The return code is in the record data.

DFS could not initialize prefix table. The return code is in the record data.

DFS could not initialize DFS namespace.The return code is in the record data.

DFS could not Register DFS Namespaces. The return code is in the record data.

DFS could not initialize User/kernel communication package. The return code is in the record data.

DFS could not contact any DC for Domain DFS operations. This operation will be retried periodically.

DFS could not initialize site support table. The return code is in the record data.

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.

DFS does not support multiple roots on Standard server SKU. Please cleanup the roots or upgrade.

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.

DFS was unable to delete link: %2  for root: %1 during a link move operation. 

The list of folder targets for the following Distributed File System (DFS) folder is corrupt. DFS folder: %1

LA 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

$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

HA 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

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.

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.

Bridge: The bridge could not be initialized because the bridge failed to register as a protocol with NDIS.

Bridge: The bridge could not be initialized because the bridge's miniport device name is missing from the registry.

Bridge: The bridge could not be initialized because the bridge failed to register as a miniport with NDIS.

Bridge: The bridge could not be initialized because the bridge failed to create a device object.

Bridge: The bridge could not be initialized because the bridge failed to determine a MAC address for itself.

|Bridge: The bridge failed to create its virtual miniport.

Bridge: The bridge could not initialize its miniport because Ethernet was not offered as a supported medium.

Bridge: The bridge could not initialize because it failed to create a system thread.

Bridge: The bridge could not initialize because it failed to reference its system thread.

Bridge: The bridge could not initialize because it failed to create a packet pool.

Bridge: The bridge could not initialize because it failed to create a buffer pool.

Bridge: The bridge could not initialize because it failed to allocate memory.

Bridge [Adapter %2]:%nThe bridge could not determine the network adapter's link speed. The network adapter will not be used.

Bridge [Adapter %2]:%nThe bridge could not determine the network adapter's MAC address. The network adapter will not be used.

Bridge [Adapter %2]:%nThe bridge could not modify the network adapter's packet filter. The network adapter will not function correctly.

Bridge [Adapter %2]:%nThe bridge could not retrieve the network adapter's description string. The network adapter will not be used.

Bridge [Adapter %2]:%nThe bridge failed to bind to the network adapter. The network adapter will not be used.

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.

|Computer QoS policies failed to refresh. Error code: %2.

tUser QoS policies failed to refresh. Error code: %2.

QoS failed to open the computer-level root key for QoS policies. Error code: %2.

QoS failed to open the user-level root key for QoS policies. Error code: %2.

DA 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. 

4A 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. 

 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.

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.

8QoS 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. 

(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. 

QoS failed to read or validate the "%2" field for the computer QoS policy "%3".

QoS failed to read or validate the "%2" field for the user QoS policy "%3".

QoS failed to read or set inbound TCP throughput level, error code: "%2".

QoS failed to read or set the DSCP marking override setting, error code: "%2".

4VS_VERSION_INFO?_?_?StringFileInfo040904B0LCompanyNameMicrosoft CorporationLFileDescriptionNet Event Handlerr)FileVersion6.1.7601.24383 (win7sp1_ldr.190212-0600):
InternalNameNetEvent.Dll.LegalCopyright Microsoft Corporation. All rights reserved.JOriginalFilenameNetEvent.Dll.MUIj%ProductNameMicrosoft Windows Operating SystemBProductVersion6.1.7601.24383DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGX

Anon7 - 2022
AnonSec Team