mirror of https://github.com/tongzx/nt5src
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4598 lines
156 KiB
4598 lines
156 KiB
;/*++ BUILD Version: 0001 // Increment this if a change has global effects
|
|
;
|
|
;Copyright (c) 1992-1996 Microsoft Corporation
|
|
;
|
|
;Module Name:
|
|
;
|
|
; netevent.h
|
|
;
|
|
;Abstract:
|
|
;
|
|
; Definitions for network events.
|
|
;
|
|
;Author:
|
|
;
|
|
; Portable Systems Group 6-May-1992
|
|
;
|
|
;Revision History:
|
|
;
|
|
;Notes:
|
|
;
|
|
; This file is generated by the MC tool from the netevent.mc file.
|
|
;
|
|
;--*/
|
|
;
|
|
;#ifndef _NETEVENT_
|
|
;#define _NETEVENT_
|
|
;
|
|
|
|
SeverityNames=(Success=0x0:STATUS_SEVERITY_SUCCESS
|
|
Informational=0x1:STATUS_SEVERITY_INFORMATIONAL
|
|
Warning=0x2:STATUS_SEVERITY_WARNING
|
|
Error=0x3:STATUS_SEVERITY_ERROR
|
|
)
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Lanman Server Events (2000 - 2999)
|
|
;// 2000-2499 are generated by the server driver (kernel mode)
|
|
;// 2500-2999 are generated by the server service (user mode)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
|
|
;
|
|
;// Server driver events, issued from kernel mode. Don't use %1 for
|
|
;// server-supplied insertion strings -- the I/O system provides the
|
|
;// first string.
|
|
;
|
|
|
|
MessageId=2000 Severity=Error SymbolicName=EVENT_SRV_SERVICE_FAILED
|
|
Language=English
|
|
The server's call to a system service failed unexpectedly.
|
|
.
|
|
|
|
MessageId=2001 Severity=Error SymbolicName=EVENT_SRV_RESOURCE_SHORTAGE
|
|
Language=English
|
|
The server was unable to perform an operation due to a shortage of available resources.
|
|
.
|
|
|
|
MessageId=2002 Severity=Error SymbolicName=EVENT_SRV_CANT_CREATE_DEVICE
|
|
Language=English
|
|
The server could not create its device. The server could not be started.
|
|
.
|
|
|
|
MessageId=2003 Severity=Error SymbolicName=EVENT_SRV_CANT_CREATE_PROCESS
|
|
Language=English
|
|
The server could not create a process. The server could not be started.
|
|
.
|
|
|
|
MessageId=2004 Severity=Error SymbolicName=EVENT_SRV_CANT_CREATE_THREAD
|
|
Language=English
|
|
The server could not create a startup thread. The server could not be started.
|
|
.
|
|
|
|
MessageId=2005 Severity=Error SymbolicName=EVENT_SRV_UNEXPECTED_DISC
|
|
Language=English
|
|
The server received an unexpected disconnection from a client.
|
|
.
|
|
|
|
MessageId=2006 Severity=Error SymbolicName=EVENT_SRV_INVALID_REQUEST
|
|
Language=English
|
|
The server received an incorrectly formatted request from %2.
|
|
.
|
|
|
|
MessageId=2007 Severity=Error SymbolicName=EVENT_SRV_CANT_OPEN_NPFS
|
|
Language=English
|
|
The server could not open the named pipe file system. Remote named pipes are disabled.
|
|
.
|
|
|
|
MessageId=2009 Severity=Warning SymbolicName=EVENT_SRV_CANT_GROW_TABLE
|
|
Language=English
|
|
The server could not expand a table because the table reached the maximum size.
|
|
.
|
|
|
|
MessageId=2010 Severity=Error SymbolicName=EVENT_SRV_CANT_START_SCAVENGER
|
|
Language=English
|
|
The server could not start the scavenger thread. The server could not be started.
|
|
.
|
|
|
|
MessageId=2011 Severity=Error SymbolicName=EVENT_SRV_IRP_STACK_SIZE
|
|
Language=English
|
|
The server's configuration parameter "irpstacksize" is too small for the server to use a local device. Please increase the value of this parameter.
|
|
.
|
|
|
|
MessageId=2012 Severity=Warning SymbolicName=EVENT_SRV_NETWORK_ERROR
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=2013 Severity=Warning SymbolicName=EVENT_SRV_DISK_FULL
|
|
Language=English
|
|
The %2 disk is at or near capacity. You may need to delete some files.
|
|
.
|
|
|
|
MessageId=2016 Severity=Error SymbolicName=EVENT_SRV_NO_VIRTUAL_MEMORY
|
|
Language=English
|
|
The server was unable to allocate virtual memory.
|
|
.
|
|
|
|
MessageId=2017 Severity=Error SymbolicName=EVENT_SRV_NONPAGED_POOL_LIMIT
|
|
Language=English
|
|
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.
|
|
.
|
|
|
|
MessageId=2018 Severity=Error SymbolicName=EVENT_SRV_PAGED_POOL_LIMIT
|
|
Language=English
|
|
The server was unable to allocate from the system paged pool because the server reached the configured limit for paged pool allocations.
|
|
.
|
|
|
|
MessageId=2019 Severity=Error SymbolicName=EVENT_SRV_NO_NONPAGED_POOL
|
|
Language=English
|
|
The server was unable to allocate from the system nonpaged pool because the pool was empty.
|
|
.
|
|
|
|
MessageId=2020 Severity=Error SymbolicName=EVENT_SRV_NO_PAGED_POOL
|
|
Language=English
|
|
The server was unable to allocate from the system paged pool because the pool was empty.
|
|
.
|
|
|
|
MessageId=2021 Severity=Warning SymbolicName=EVENT_SRV_NO_WORK_ITEM
|
|
Language=English
|
|
The server was unable to allocate a work item %2 times in the last %3 seconds.
|
|
.
|
|
|
|
MessageId=2022 Severity=Warning SymbolicName=EVENT_SRV_NO_FREE_CONNECTIONS
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=2023 Severity=Warning SymbolicName=EVENT_SRV_NO_FREE_RAW_WORK_ITEM
|
|
Language=English
|
|
The server was unable to find a free raw work item %2 times in the last %3 seconds.
|
|
.
|
|
|
|
MessageId=2024 Severity=Warning SymbolicName=EVENT_SRV_NO_BLOCKING_IO
|
|
Language=English
|
|
The server was unable to allocate resources for blocking I/O %2 times in the last %3 seconds.
|
|
.
|
|
|
|
MessageId=2025 Severity=Warning SymbolicName=EVENT_SRV_DOS_ATTACK_DETECTED
|
|
Language=English
|
|
The server has detected an attempted Denial-Of-Service attack from client %2, and has disconnected the connection.
|
|
.
|
|
|
|
MessageId=2026 Severity=Warning SymbolicName=EVENT_SRV_TOO_MANY_DOS
|
|
Language=English
|
|
The server has detected too many Denial-Of-Service attacks and will stop logging
|
|
events for any more of them. Be advised it is likely someone is actively attacking
|
|
your machine.
|
|
.
|
|
|
|
MessageId=2027 Severity=Warning SymbolicName=EVENT_SRV_OUT_OF_WORK_ITEM_DOS
|
|
Language=English
|
|
The server has detected a potential Denial-of-Service attack caused by consuming all the work-items. Some connections
|
|
were disconnected to protect against this. If this is not the case, please raise the MaxWorkItems for the server or
|
|
disable DoS detection. This event will not be logged again for 24 hours.
|
|
.
|
|
|
|
;
|
|
;// Server service events, issued from user mode. %1 is the first
|
|
;// service-supplied insertion string.
|
|
;
|
|
|
|
MessageId=2501 Severity=Error SymbolicName=EVENT_SRV_KEY_NOT_FOUND
|
|
Language=English
|
|
The server's Registry key %1 was not present. The server could not start.
|
|
.
|
|
|
|
MessageId=2502 Severity=Error SymbolicName=EVENT_SRV_KEY_NOT_CREATED
|
|
Language=English
|
|
The server's Registry key %1 was not present and could not be created. The server could not start.
|
|
.
|
|
|
|
MessageId=2503 Severity=Error SymbolicName=EVENT_SRV_NO_TRANSPORTS_BOUND
|
|
Language=English
|
|
The server did not bind to any transports. The server could not start.
|
|
.
|
|
|
|
MessageId=2504 Severity=Warning SymbolicName=EVENT_SRV_CANT_BIND_TO_TRANSPORT
|
|
Language=English
|
|
The server could not bind to the transport %1.
|
|
.
|
|
|
|
MessageId=2505 Severity=Error SymbolicName=EVENT_SRV_CANT_BIND_DUP_NAME
|
|
Language=English
|
|
The server could not bind to the transport %1 because another computer on the network has the same name. The server could not start.
|
|
.
|
|
|
|
MessageId=2506 Severity=Warning SymbolicName=EVENT_SRV_INVALID_REGISTRY_VALUE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=2507 Severity=Warning SymbolicName=EVENT_SRV_INVALID_SD
|
|
Language=English
|
|
The security descriptor stored in the Registry for the share %1 was invalid. The share was not automatically recreated.
|
|
.
|
|
|
|
MessageId=2508 Severity=Warning SymbolicName=EVENT_SRV_CANT_LOAD_DRIVER
|
|
Language=English
|
|
The server service was unable to load the server driver.
|
|
.
|
|
|
|
MessageId=2509 Severity=Warning SymbolicName=EVENT_SRV_CANT_UNLOAD_DRIVER
|
|
Language=English
|
|
The server service was unable to unload the server driver.
|
|
.
|
|
|
|
MessageId=2510 Severity=Warning SymbolicName=EVENT_SRV_CANT_MAP_ERROR
|
|
Language=English
|
|
The server service was unable to map error code %1.
|
|
.
|
|
|
|
MessageId=2511 Severity=Warning SymbolicName=EVENT_SRV_CANT_RECREATE_SHARE
|
|
Language=English
|
|
The server service was unable to recreate the share %1 because the directory %2 no longer exists. Please run "net share %1 /delete" to delete the share, or recreate the directory %2.
|
|
.
|
|
|
|
MessageId=2512 Severity=Warning SymbolicName=EVENT_SRV_CANT_CHANGE_DOMAIN_NAME
|
|
Language=English
|
|
The server service was unable to change the domain name from %1 to %2.
|
|
.
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Lanman Redirector Events
|
|
;//
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=3001 SymbolicName=EVENT_RDR_RESOURCE_SHORTAGE
|
|
Language=English
|
|
The redirector was unable to allocate memory.
|
|
.
|
|
|
|
MessageId=3002 SymbolicName=EVENT_RDR_CANT_CREATE_DEVICE
|
|
Language=English
|
|
The redirector could not create its device. The redirector could not be started.
|
|
.
|
|
|
|
MessageId=3003 SymbolicName=EVENT_RDR_CANT_CREATE_THREAD
|
|
Language=English
|
|
The redirector could not create a system thread.
|
|
.
|
|
|
|
MessageId=3004 SymbolicName=EVENT_RDR_CANT_SET_THREAD
|
|
Language=English
|
|
The redirector could not set the priority for a system thread.
|
|
.
|
|
|
|
MessageId=3005 SymbolicName=EVENT_RDR_INVALID_REPLY
|
|
Language=English
|
|
The redirector received an incorrectly formatted response from %2.
|
|
.
|
|
|
|
MessageId=3006 SymbolicName=EVENT_RDR_INVALID_SMB
|
|
Language=English
|
|
The redirector received an SMB that was too short.
|
|
.
|
|
|
|
MessageId=3007 SymbolicName=EVENT_RDR_INVALID_LOCK_REPLY
|
|
Language=English
|
|
The redirector received an incorrect response from %2 to a lock request.
|
|
.
|
|
|
|
MessageId=3009 SymbolicName=EVENT_RDR_FAILED_UNLOCK
|
|
Language=English
|
|
The redirector failed to unlock part of a file on server %2.
|
|
.
|
|
|
|
MessageId=3011 SymbolicName=EVENT_RDR_CLOSE_BEHIND
|
|
Language=English
|
|
The redirector failed to write data to server %2 after the file was closed.
|
|
.
|
|
|
|
MessageId=3012 SymbolicName=EVENT_RDR_UNEXPECTED_ERROR
|
|
Language=English
|
|
An unexpected network error has occurred on the virtual circuit to %2.
|
|
.
|
|
|
|
MessageId=3013 SymbolicName=EVENT_RDR_TIMEOUT
|
|
Language=English
|
|
The redirector has timed out a request to %2.
|
|
.
|
|
|
|
MessageId=3014 SymbolicName=EVENT_RDR_INVALID_OPLOCK
|
|
Language=English
|
|
The redirector received an invalid oplock level from %2.
|
|
.
|
|
|
|
MessageId=3015 SymbolicName=EVENT_RDR_CONNECTION_REFERENCE
|
|
Language=English
|
|
The redirector dereferenced a connection through zero.
|
|
.
|
|
|
|
MessageId=3016 SymbolicName=EVENT_RDR_SERVER_REFERENCE
|
|
Language=English
|
|
The redirector dereferenced a server through zero.
|
|
.
|
|
|
|
MessageId=3017 SymbolicName=EVENT_RDR_SMB_REFERENCE
|
|
Language=English
|
|
The redirector dereferenced the allocated SMB count through zero.
|
|
.
|
|
|
|
MessageId=3018 SymbolicName=EVENT_RDR_ENCRYPT
|
|
Language=English
|
|
The redirector accessed a share-level server that indicates it encrypts passwords.
|
|
This combination is not supported.
|
|
.
|
|
|
|
MessageId=3019 SymbolicName=EVENT_RDR_CONNECTION
|
|
Language=English
|
|
The redirector failed to determine the connection type.
|
|
.
|
|
|
|
MessageId=3021 SymbolicName=EVENT_RDR_MAXCMDS
|
|
Language=English
|
|
The redirector failed to allocate a multiplex table entry. This indicates that
|
|
the MAXCMDS parameter to the redirector is insufficient for the users needs.
|
|
.
|
|
|
|
MessageId=3022 SymbolicName=EVENT_RDR_OPLOCK_SMB
|
|
Language=English
|
|
The redirector failed to allocate a buffer for an oplock break.
|
|
.
|
|
|
|
|
|
MessageId=3023 SymbolicName=EVENT_RDR_DISPOSITION
|
|
Language=English
|
|
The redirector failed to map the requested file disposition (for NtCreateFile).
|
|
.
|
|
|
|
MessageId=3024 SymbolicName=EVENT_RDR_CONTEXTS
|
|
Language=English
|
|
The redirector is allocating additional resources for input/output request packet contexts. This is
|
|
probably caused by a resource leak in the redirector.
|
|
.
|
|
|
|
|
|
MessageId=3025 SymbolicName=EVENT_RDR_WRITE_BEHIND_FLUSH_FAILED
|
|
Language=English
|
|
A write-behind operation has failed to the remote server %2. The data contains the amount requested to write and the amount actually written.
|
|
.
|
|
|
|
MessageId=3026 SymbolicName=EVENT_RDR_AT_THREAD_MAX
|
|
Language=English
|
|
The redirector was unable to create a worker thread because it has already created the maximum number of configured work threads.
|
|
.
|
|
|
|
MessageId=3027 SymbolicName=EVENT_RDR_CANT_READ_REGISTRY
|
|
Language=English
|
|
The redirector was unable to initialize variables from the Registry.
|
|
.
|
|
|
|
MessageId=3028 SymbolicName=EVENT_RDR_TIMEZONE_BIAS_TOO_LARGE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=3029 SymbolicName=EVENT_RDR_PRIMARY_TRANSPORT_CONNECT_FAILED
|
|
Language=English
|
|
The redirector has failed to connect to the server %2 on the primary transport. The data contains the error.
|
|
.
|
|
|
|
MessageId=3030 SymbolicName=EVENT_RDR_DELAYED_SET_ATTRIBUTES_FAILED
|
|
Language=English
|
|
The redirector was unable to update the file attributes on a file located on server %2.
|
|
The data contains the name of the file.
|
|
.
|
|
|
|
MessageId=3031 SymbolicName=EVENT_RDR_DELETEONCLOSE_FAILED
|
|
Language=English
|
|
The redirector was unable to delete the file specified on server %2 when it was closed by the application.
|
|
The data contains the name of the file.
|
|
.
|
|
|
|
MessageId=3032 SymbolicName=EVENT_RDR_CANT_BIND_TRANSPORT
|
|
Language=English
|
|
The redirector was unable to register the domain %2 on to transport %3 for the following reason: %4. Transport has been taken offline.
|
|
.
|
|
|
|
MessageId=3033 SymbolicName=EVENT_RDR_CANT_REGISTER_ADDRESS
|
|
Language=English
|
|
The redirector was unable to register the address for transport %3 for the following reason: %4. Transport has been taken offline.
|
|
.
|
|
|
|
MessageId=3034 SymbolicName=EVENT_RDR_CANT_GET_SECURITY_CONTEXT
|
|
Language=English
|
|
The redirector was unable to initialize security context or query context attributes.
|
|
.
|
|
|
|
MessageId=3035 SymbolicName=EVENT_RDR_CANT_BUILD_SMB_HEADER
|
|
Language=English
|
|
The redirector was unable to build SMB header.
|
|
.
|
|
|
|
MessageId=3036 SymbolicName=EVENT_RDR_SECURITY_SIGNATURE_MISMATCH
|
|
Language=English
|
|
The redirector detected a security signature mismatch. The connection has been disconnected.
|
|
.
|
|
|
|
;
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// IPv6 Events
|
|
;//
|
|
;// Codes 3100 - 3199
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=3100
|
|
Severity=Informational
|
|
SymbolicName=EVENT_TCPIP6_STARTED
|
|
Language=English
|
|
The Microsoft IPv6 Developer Edition driver was started.
|
|
.
|
|
|
|
;
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// STREAMS Environment Events
|
|
;//
|
|
;// Codes 4000 - 4099
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=4000 Severity=Error SymbolicName=EVENT_STREAMS_STRLOG
|
|
Language=English
|
|
%2.
|
|
.
|
|
|
|
MessageId=4001 Severity=Warning SymbolicName=EVENT_STREAMS_ALLOCB_FAILURE
|
|
Language=English
|
|
Unable to allocate a %2 byte message.
|
|
.
|
|
|
|
MessageId=4002 Severity=Warning SymbolicName=EVENT_STREAMS_ALLOCB_FAILURE_CNT
|
|
Language=English
|
|
%2 message allocations have failed since initialization.
|
|
.
|
|
|
|
MessageId=4003 Severity=Warning SymbolicName=EVENT_STREAMS_ESBALLOC_FAILURE
|
|
Language=English
|
|
Unable to allocate a %2 byte external message.
|
|
.
|
|
|
|
MessageId=4004 Severity=Warning SymbolicName=EVENT_STREAMS_ESBALLOC_FAILURE_CNT
|
|
Language=English
|
|
%2 external message allocations have failed since initialization.
|
|
.
|
|
|
|
;
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// TCP/IP Events
|
|
;//
|
|
;// Codes 4100 - 4299
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
;//
|
|
;// Common TCP/IP messages
|
|
;//
|
|
;// Codes 4100 - 4149
|
|
;//
|
|
;//
|
|
;
|
|
MessageId=4100 Severity=Error SymbolicName=EVENT_TCPIP_CREATE_DEVICE_FAILED
|
|
Language=English
|
|
Unable to create device object %2. Initialization failed.
|
|
.
|
|
|
|
MessageId=4101 Severity=Error SymbolicName=EVENT_TCPIP_NO_RESOURCES_FOR_INIT
|
|
Language=English
|
|
Unable to allocate required resources. Initialization failed.
|
|
.
|
|
|
|
;
|
|
;//
|
|
;// ARP messages
|
|
;//
|
|
;// Codes 4150-4174
|
|
;
|
|
|
|
;
|
|
;//
|
|
;// IP Loopback messages
|
|
;//
|
|
;// Codes 4175-4184
|
|
;//
|
|
;
|
|
|
|
;
|
|
;//
|
|
;// IP/ICMP messages
|
|
;//
|
|
;// Codes 4185 - 4224
|
|
;
|
|
MessageId=4185 Severity=Error SymbolicName=EVENT_TCPIP_TOO_MANY_NETS
|
|
Language=English
|
|
IP has been bound to more than the maximum number of supported interfaces.
|
|
Some interfaces on adapter %2 will not be initialized.
|
|
.
|
|
|
|
MessageId=4186 Severity=Error SymbolicName=EVENT_TCPIP_NO_MASK
|
|
Language=English
|
|
No subnet mask was specified for interface %2. This interface and
|
|
all subsequent interfaces on adapter %3 cannot be initialized.
|
|
.
|
|
|
|
MessageId=4187 Severity=Error SymbolicName=EVENT_TCPIP_INVALID_ADDRESS
|
|
Language=English
|
|
Invalid address %2 was specified for adapter %3. This interface
|
|
cannot be initialized.
|
|
.
|
|
|
|
MessageId=4188 Severity=Error SymbolicName=EVENT_TCPIP_INVALID_MASK
|
|
Language=English
|
|
Invalid subnet mask %2 was specified for address %3 on adapter %4.
|
|
This interface cannot be initialized.
|
|
.
|
|
|
|
MessageId=4189 Severity=Error SymbolicName=EVENT_TCPIP_NO_ADAPTER_RESOURCES
|
|
Language=English
|
|
IP could not allocate some resources required to configure adapter %2.
|
|
Some interfaces on this adapter will not be initialized.
|
|
.
|
|
|
|
MessageId=4190 Severity=Warning SymbolicName=EVENT_TCPIP_DHCP_INIT_FAILED
|
|
Language=English
|
|
IP was unable to initialize adapter %2 for configuration by DHCP.
|
|
If DHCP is enabled on this adapter, the primary interface may not be
|
|
configured properly. Interfaces on this adapter not configured by
|
|
DHCP will be unaffected.
|
|
.
|
|
|
|
MessageId=4191 Severity=Error SymbolicName=EVENT_TCPIP_ADAPTER_REG_FAILURE
|
|
Language=English
|
|
IP could not open the registry key for adapter %2.
|
|
Interfaces on this adapter will not be initialized.
|
|
.
|
|
|
|
MessageId=4192 Severity=Warning SymbolicName=EVENT_TCPIP_INVALID_DEFAULT_GATEWAY
|
|
Language=English
|
|
Invalid default gateway address %2 was specified for adapter %3.
|
|
Some remote networks may not be reachable as a result.
|
|
.
|
|
|
|
MessageId=4193 Severity=Error SymbolicName=EVENT_TCPIP_NO_ADDRESS_LIST
|
|
Language=English
|
|
Unable to read the configured IP addresses for adapter %2.
|
|
IP interfaces will not be initialized on this adapter.
|
|
.
|
|
|
|
MessageId=4194 Severity=Error SymbolicName=EVENT_TCPIP_NO_MASK_LIST
|
|
Language=English
|
|
Unable to read the configured subnet masks for adapter %2.
|
|
IP interfaces will not be initialized on this adapter.
|
|
.
|
|
|
|
MessageId=4195 Severity=Error SymbolicName=EVENT_TCPIP_NO_BINDINGS
|
|
Language=English
|
|
IP was unable to read its bindings from the registry. No network interfaces
|
|
were configured.
|
|
.
|
|
|
|
MessageId=4196 Severity=Error SymbolicName=EVENT_TCPIP_IP_INIT_FAILED
|
|
Language=English
|
|
Initialization of IP failed.
|
|
.
|
|
|
|
MessageId=4197 Severity=Warning SymbolicName=EVENT_TCPIP_TOO_MANY_GATEWAYS
|
|
Language=English
|
|
More than the maximum number of default gateways were specified for
|
|
adapter %2. Some remote networks may not be reachable as a result.
|
|
.
|
|
|
|
MessageId=4198 Severity=Error SymbolicName=EVENT_TCPIP_ADDRESS_CONFLICT1
|
|
Language=English
|
|
The system detected an address conflict for IP address %2 with the system
|
|
having network hardware address %3. The local interface has been disabled.
|
|
.
|
|
|
|
MessageId=4199 Severity=Error SymbolicName=EVENT_TCPIP_ADDRESS_CONFLICT2
|
|
Language=English
|
|
The system detected an address conflict for IP address %2 with the system
|
|
having network hardware address %3. Network operations on this system may
|
|
be disrupted as a result.
|
|
.
|
|
|
|
MessageId=4200 Severity=Error SymbolicName=EVENT_TCPIP_NTE_CONTEXT_LIST_FAILURE
|
|
Language=English
|
|
Unable to read or write the NTE Context list for adapter %2.
|
|
IP interfaces on this adapter may not be initialized completely.
|
|
.
|
|
|
|
MessageId=4201 Severity=Informational SymbolicName=EVENT_TCPIP_MEDIA_CONNECT
|
|
Language=English
|
|
The system detected that network adapter %2 was connected to the network,
|
|
and has initiated normal operation over the network adapter.
|
|
.
|
|
|
|
MessageId=4202 Severity=Informational SymbolicName=EVENT_TCPIP_MEDIA_DISCONNECT
|
|
Language=English
|
|
The system detected that network adapter %2 was disconnected from the network,
|
|
and the adapter's network configuration has been released. If the network
|
|
adapter was not disconnected, this may indicate that it has malfunctioned.
|
|
Please contact your vendor for updated drivers.
|
|
.
|
|
|
|
;
|
|
;//
|
|
;// TCP messages
|
|
;//
|
|
;// Codes 4225 - 4264
|
|
;//
|
|
;
|
|
MessageId=4225 Severity=Error SymbolicName=EVENT_TCPIP_TCP_INIT_FAILED
|
|
Language=English
|
|
Initialization of TCP/UDP failed.
|
|
.
|
|
|
|
|
|
;
|
|
;//
|
|
;// UDP messages
|
|
;//
|
|
;// Codes 4265 - 4280
|
|
;//
|
|
;
|
|
MessageId=4265 Severity=Warning SymbolicName=EVENT_TCPIP_UDP_LIMIT_REACHED
|
|
Language=English
|
|
Backlog of pending datagram sends reached. Please increase the value of Tcpip\Parameters\DGMaxSendFree in the registry.
|
|
.
|
|
|
|
;//
|
|
;// IPSEC messages
|
|
;//
|
|
;// Codes 4281 - 4299
|
|
;//
|
|
;
|
|
MessageId=4281 Severity=Error SymbolicName=EVENT_IPSEC_NO_RESOURCES_FOR_INIT
|
|
Language=English
|
|
Unable to allocate required resources. Initialization failed.
|
|
.
|
|
|
|
MessageId=4282 Severity=Error SymbolicName=EVENT_IPSEC_CREATE_DEVICE_FAILED
|
|
Language=English
|
|
Unable to create device object %2. Initialization failed.
|
|
.
|
|
|
|
MessageId=4283 Severity=Error SymbolicName=EVENT_IPSEC_BAD_SPI_RECEIVED
|
|
Language=English
|
|
Received %2 packet(s) with a bad Security Parameters Index from %3.
|
|
This could be a temporary glitch; if it persists please stop and restart the IPSec Policy Agent service on this machine.
|
|
.
|
|
|
|
MessageId=4284 Severity=Error SymbolicName=EVENT_IPSEC_UNEXPECTED_CLEARTEXT
|
|
Language=English
|
|
Received %2 packet(s) in the clear from %3 which should have been secured.
|
|
This could be a temporary glitch; if it persists please stop and restart the IPSec Policy Agent service on this machine.
|
|
.
|
|
|
|
MessageId=4285 Severity=Error SymbolicName=EVENT_IPSEC_AUTH_FAILURE
|
|
Language=English
|
|
Failed to authenticate the hash for %2 packet(s) received from %3.
|
|
This could be a temporary glitch; if it persists please stop and restart the IPSec Policy Agent service on this machine.
|
|
.
|
|
|
|
MessageId=4286 Severity=Error SymbolicName=EVENT_IPSEC_BAD_PACKET_SYNTAX
|
|
Language=English
|
|
Received %2 packet(s) from %3 with invalid packet syntax.
|
|
This could be a temporary glitch; if it persists please stop and restart the IPSec Policy Agent service on this machine.
|
|
.
|
|
|
|
MessageId=4287 Severity=Error SymbolicName=EVENT_IPSEC_BAD_PROTOCOL_RECEIVED
|
|
Language=English
|
|
Received %2 packet(s) from %3 with inproper protocol identifier.
|
|
This could be a temporary glitch; if it persists please stop and restart the IPSec Policy Agent service on this machine.
|
|
.
|
|
|
|
MessageId=4288 Severity=Error SymbolicName=EVENT_IPSEC_GENERIC_FAILURE
|
|
Language=English
|
|
Received %2 packet(s) from %3 that failed the IPSec processing for an unknown reason.
|
|
This could be a temporary glitch; if it persists please stop and restart the IPSec Policy Agent service on this machine..
|
|
.
|
|
|
|
MessageId=4289 Severity=Error SymbolicName=EVENT_IPSEC_NEG_FAILURE
|
|
Language=English
|
|
The IPSec driver failed the oakley negotiation with %2 since no filter
|
|
exists to protect packets to that destination.
|
|
Please check the configuration on this machine to ensure at least one
|
|
filter matches the destination.
|
|
.
|
|
|
|
MessageId=4290 Severity=Informational SymbolicName=EVENT_IPSEC_DROP_PACKET_INBOUND
|
|
Language=English
|
|
The IPSec driver has dropped the following inbound packet:
|
|
%nSource IP Address: %2
|
|
%nDestination IP Address: %3
|
|
%nProtocol: %4
|
|
%nSource Port: %5
|
|
%nDestination Port: %6
|
|
%nOffset for IPSec status code: 0x14
|
|
%nOffset for Offload status code: 0x10
|
|
%nOffset for Offload flags(0=no offload): 0x20
|
|
%nOffset for packet start: 0x28
|
|
.
|
|
|
|
MessageId=4291 Severity=Informational SymbolicName=EVENT_IPSEC_DROP_PACKET_OUTBOUND
|
|
Language=English
|
|
The IPSec driver has dropped the following outbound packet:
|
|
%nSource IP Address: %2
|
|
%nDestination IP Address: %3
|
|
%nProtocol: %4
|
|
%nSource Port: %5
|
|
%nDestination Port: %6
|
|
%nOffset for IPSec status code: 0x14
|
|
%nOffset for Offload status code: 0x10
|
|
%nOffset for Offload flags: 0x20
|
|
%nOffset for packet start: 0x28
|
|
.
|
|
|
|
|
|
;
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// NBT Events
|
|
;//
|
|
;// Codes 4300 - 4399
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
;
|
|
;// Don't use %1 for driver supplied insertion strings. The IO subsystem
|
|
;// supplies the first string!!
|
|
;
|
|
MessageId=4300 Severity=Error SymbolicName=EVENT_NBT_CREATE_DRIVER
|
|
Language=English
|
|
The driver could not be created.
|
|
.
|
|
MessageId=4301 Severity=Error SymbolicName=EVENT_NBT_OPEN_REG_PARAMS
|
|
Language=English
|
|
Unable to open the Registry Parameters to read configuration information.
|
|
.
|
|
MessageId=4302 Severity=Warning SymbolicName=EVENT_NBT_NO_BACKUP_WINS
|
|
Language=English
|
|
The backup WINS server address is not configured in the registry.
|
|
.
|
|
MessageId=4303 Severity=Warning SymbolicName=EVENT_NBT_NO_WINS
|
|
Language=English
|
|
The primary WINS server address is not configured in the registry.
|
|
.
|
|
MessageId=4304 Severity=Warning SymbolicName=EVENT_NBT_BAD_BACKUP_WINS_ADDR
|
|
Language=English
|
|
The backup WINS server address is not formated correctly in the registry.
|
|
.
|
|
MessageId=4305 Severity=Warning SymbolicName=EVENT_NBT_BAD_PRIMARY_WINS_ADDR
|
|
Language=English
|
|
The primary WINS server address is not formated correctly in the registry.
|
|
.
|
|
MessageId=4306 Severity=Error SymbolicName=EVENT_NBT_NAME_SERVER_ADDRS
|
|
Language=English
|
|
Unable to configure the addresses of the WINS servers.
|
|
.
|
|
MessageId=4307 Severity=Error SymbolicName=EVENT_NBT_CREATE_ADDRESS
|
|
Language=English
|
|
Initialization failed because the transport refused to open initial Addresses.
|
|
.
|
|
MessageId=4308 Severity=Error SymbolicName=EVENT_NBT_CREATE_CONNECTION
|
|
Language=English
|
|
Initialization failed because the transport refused to open initial Connections.
|
|
.
|
|
MessageId=4309 Severity=Error SymbolicName=EVENT_NBT_NON_OS_INIT
|
|
Language=English
|
|
Data structure initialization failed.
|
|
.
|
|
MessageId=4310 Severity=Error SymbolicName=EVENT_NBT_TIMERS
|
|
Language=English
|
|
Initialization failed because the timers could not be started.
|
|
.
|
|
MessageId=4311 Severity=Error SymbolicName=EVENT_NBT_CREATE_DEVICE
|
|
Language=English
|
|
Initialization failed because the driver device could not be created.
|
|
.
|
|
MessageId=4312 Severity=Warning SymbolicName=EVENT_NBT_NO_DEVICES
|
|
Language=English
|
|
There are no adapters configured for this protocol stack.
|
|
.
|
|
MessageId=4313 Severity=Error SymbolicName=EVENT_NBT_OPEN_REG_LINKAGE
|
|
Language=English
|
|
Unable to open the Registry Linkage to read configuration information.
|
|
.
|
|
MessageId=4314 Severity=Error SymbolicName=EVENT_NBT_READ_BIND
|
|
Language=English
|
|
Unable to read the driver's bindings to the transport from the registry.
|
|
.
|
|
MessageId=4315 Severity=Error SymbolicName=EVENT_NBT_READ_EXPORT
|
|
Language=English
|
|
Unable to read the driver's exported linkage configuration information.
|
|
.
|
|
MessageId=4316 Severity=Warning SymbolicName=EVENT_NBT_OPEN_REG_NAMESERVER
|
|
Language=English
|
|
Unable to open the Registry to read the WINS server addresses.
|
|
.
|
|
MessageId=4317 Severity=Warning SymbolicName=EVENT_SCOPE_LABEL_TOO_LONG
|
|
Language=English
|
|
The Netbios Name Scope has a component longer than 63 characters. Each label
|
|
in the Scope cannot be longer than 63 bytes. Use the Control Panel, Network
|
|
applet to change the scope.
|
|
.
|
|
MessageId=4318 Severity=Warning SymbolicName=EVENT_SCOPE_TOO_LONG
|
|
Language=English
|
|
The Netbios Name Scope is too long. The scope cannot be longer than
|
|
255 bytes. Use the Control Panel, Network applet to change the scope.
|
|
.
|
|
MessageId=4319 Severity=Error SymbolicName=EVENT_NBT_DUPLICATE_NAME
|
|
Language=English
|
|
A duplicate name has been detected on the TCP network. The IP address of
|
|
the machine that sent the message is in the data. Use nbtstat -n in a
|
|
command window to see which name is in the Conflict state.
|
|
.
|
|
MessageId=4320 Severity=Error SymbolicName=EVENT_NBT_NAME_RELEASE
|
|
Language=English
|
|
Another machine has sent a name release message to this machine 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.
|
|
.
|
|
MessageId=4321 Severity=Error SymbolicName=EVENT_NBT_DUPLICATE_NAME_ERROR
|
|
Language=English
|
|
The name "%2" could not be registered on the Interface with IP address %3.
|
|
The machine with the IP address %4 did not allow the name to be claimed by
|
|
this machine.
|
|
.
|
|
MessageId=4322 Severity=Error SymbolicName=EVENT_NBT_NO_RESOURCES
|
|
Language=English
|
|
NetBT failed to process a request because it encountered OutOfResources
|
|
exception(s) in the last 1 hour.
|
|
.
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// NDIS Environment Events
|
|
;//
|
|
;// Codes 5000 - 5099
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
|
|
MessageId=5000 Severity=Error SymbolicName=EVENT_NDIS_RESOURCE_CONFLICT
|
|
Language=English
|
|
%2 : Has encountered a conflict in resources and could not load.
|
|
.
|
|
|
|
MessageId=5001 Severity=Error SymbolicName=EVENT_NDIS_OUT_OF_RESOURCE
|
|
Language=English
|
|
%2 : Could not allocate the resources necessary for operation.
|
|
.
|
|
|
|
MessageId=5002 Severity=Error SymbolicName=EVENT_NDIS_HARDWARE_FAILURE
|
|
Language=English
|
|
%2 : Has determined that the adapter is not functioning properly.
|
|
.
|
|
|
|
MessageId=5003 Severity=Error SymbolicName=EVENT_NDIS_ADAPTER_NOT_FOUND
|
|
Language=English
|
|
%2 : Could not find an adapter.
|
|
.
|
|
|
|
MessageId=5004 Severity=Error SymbolicName=EVENT_NDIS_INTERRUPT_CONNECT
|
|
Language=English
|
|
%2 : Could not connect to the interrupt number supplied.
|
|
.
|
|
|
|
MessageId=5005 Severity=Error SymbolicName=EVENT_NDIS_DRIVER_FAILURE
|
|
Language=English
|
|
%2 : Has encountered an internal error and has failed.
|
|
.
|
|
|
|
MessageId=5006 Severity=Error SymbolicName=EVENT_NDIS_BAD_VERSION
|
|
Language=English
|
|
%2 : The version number is incorrect for this driver.
|
|
.
|
|
|
|
MessageId=5007 Severity=Warning SymbolicName=EVENT_NDIS_TIMEOUT
|
|
Language=English
|
|
%2 : Timed out during an operation.
|
|
.
|
|
|
|
MessageId=5008 Severity=Error SymbolicName=EVENT_NDIS_NETWORK_ADDRESS
|
|
Language=English
|
|
%2 : Has encountered an invalid network address.
|
|
.
|
|
|
|
MessageId=5009 Severity=Error SymbolicName=EVENT_NDIS_UNSUPPORTED_CONFIGURATION
|
|
Language=English
|
|
%2 : Does not support the configuration supplied.
|
|
.
|
|
|
|
MessageId=5010 Severity=Error SymbolicName=EVENT_NDIS_INVALID_VALUE_FROM_ADAPTER
|
|
Language=English
|
|
%2 : The adapter has returned an invalid value to the driver.
|
|
.
|
|
|
|
MessageId=5011 Severity=Error SymbolicName=EVENT_NDIS_MISSING_CONFIGURATION_PARAMETER
|
|
Language=English
|
|
%2 : A required parameter is missing from the Registry.
|
|
.
|
|
|
|
MessageId=5012 Severity=Error SymbolicName=EVENT_NDIS_BAD_IO_BASE_ADDRESS
|
|
Language=English
|
|
%2 : The I/O base address supplied does not match the jumpers on the adapter.
|
|
.
|
|
|
|
MessageId=5013 Severity=Informational SymbolicName=EVENT_NDIS_RECEIVE_SPACE_SMALL
|
|
Language=English
|
|
%2 : The adapter is configured such that the receive space is smaller than
|
|
the maximum packet size. Some packets may be lost.
|
|
.
|
|
|
|
MessageId=5014 Severity=Warning SymbolicName=EVENT_NDIS_ADAPTER_DISABLED
|
|
Language=English
|
|
%2 : The adapter is disabled. The driver cannot open the adapter.
|
|
.
|
|
|
|
MessageId=5015 Severity=Warning SymbolicName=EVENT_NDIS_IO_PORT_CONFLICT
|
|
Language=English
|
|
%2 : There is an I/O port conflict.
|
|
.
|
|
|
|
MessageId=5016 Severity=Warning SymbolicName=EVENT_NDIS_PORT_OR_DMA_CONFLICT
|
|
Language=English
|
|
%2 : There is an I/O port or DMA channel conflict.
|
|
.
|
|
|
|
MessageId=5017 Severity=Warning SymbolicName=EVENT_NDIS_MEMORY_CONFLICT
|
|
Language=English
|
|
%2 : There is a memory conflict at address 0x%3.
|
|
.
|
|
|
|
MessageId=5018 Severity=Warning SymbolicName=EVENT_NDIS_INTERRUPT_CONFLICT
|
|
Language=English
|
|
%2 : There is a interrupt conflict at interrupt number %3.
|
|
.
|
|
|
|
MessageId=5019 Severity=Warning SymbolicName=EVENT_NDIS_DMA_CONFLICT
|
|
Language=English
|
|
%2 : There is a resource conflict at DMA channel %3.
|
|
.
|
|
|
|
MessageId=5020 Severity=Error SymbolicName=EVENT_NDIS_INVALID_DOWNLOAD_FILE_ERROR
|
|
Language=English
|
|
%2 : The download file is invalid. The driver is unable to load.
|
|
.
|
|
MessageId=5021 Severity=Warning SymbolicName=EVENT_NDIS_MAXRECEIVES_ERROR
|
|
Language=English
|
|
%2 : The specified Registry entry MaxReceives is out of range. Using
|
|
default value.
|
|
.
|
|
MessageId=5022 Severity=Warning SymbolicName=EVENT_NDIS_MAXTRANSMITS_ERROR
|
|
Language=English
|
|
%2 : The specified Registry entry MaxTransmits is out of range. Using
|
|
default value.
|
|
.
|
|
MessageId=5023 Severity=Warning SymbolicName=EVENT_NDIS_MAXFRAMESIZE_ERROR
|
|
Language=English
|
|
%2 : The specified Registry entry MaxFrameSize is out of range. Using
|
|
default value.
|
|
.
|
|
MessageId=5024 Severity=Warning SymbolicName=EVENT_NDIS_MAXINTERNALBUFS_ERROR
|
|
Language=English
|
|
%2 : The specified Registry entry MaxInternalBufs is out of range. Using
|
|
default value.
|
|
.
|
|
MessageId=5025 Severity=Warning SymbolicName=EVENT_NDIS_MAXMULTICAST_ERROR
|
|
Language=English
|
|
%2 : The specified Registry entry MaxMulticast is out of range. Using
|
|
default value.
|
|
.
|
|
MessageId=5026 Severity=Warning SymbolicName=EVENT_NDIS_PRODUCTID_ERROR
|
|
Language=English
|
|
%2 : The specified Registry entry ProductId is out of range. Using
|
|
default value.
|
|
.
|
|
MessageId=5027 Severity=Warning SymbolicName=EVENT_NDIS_LOBE_FAILUE_ERROR
|
|
Language=English
|
|
%2 : A Token Ring Lobe Wire Fault has occurred. Verify cable
|
|
connections. The adapter will continue to try to reinsert back
|
|
into the ring.
|
|
.
|
|
MessageId=5028 Severity=Warning SymbolicName=EVENT_NDIS_SIGNAL_LOSS_ERROR
|
|
Language=English
|
|
%2 : The adapter had detected a loss of signal on the ring. The adapter
|
|
will continue to try to reinsert back into the ring.
|
|
.
|
|
MessageId=5029 Severity=Warning SymbolicName=EVENT_NDIS_REMOVE_RECEIVED_ERROR
|
|
Language=English
|
|
%2 : The adapter has received a request to deinsert from the
|
|
ring. The adapter will continue to try to reinsert back into the ring.
|
|
.
|
|
MessageId=5030 Severity=Informational SymbolicName=EVENT_NDIS_TOKEN_RING_CORRECTION
|
|
Language=English
|
|
%2 : The adapter has successfully reinserted back into the ring.
|
|
.
|
|
MessageId=5031 Severity=Error SymbolicName=EVENT_NDIS_ADAPTER_CHECK_ERROR
|
|
Language=English
|
|
%2 : The adapter has detected an Adapter Check as a result of some
|
|
unrecoverable hardware of software error. Please contact your service provider.
|
|
.
|
|
MessageId=5032 Severity=Warning SymbolicName=EVENT_NDIS_RESET_FAILURE_ERROR
|
|
Language=English
|
|
%2 : The adapter failed to reset within a specified time. The adapter will
|
|
continue to try to reset. This could be the result of a hardware failure.
|
|
.
|
|
MessageId=5033 Severity=Warning SymbolicName=EVENT_NDIS_CABLE_DISCONNECTED_ERROR
|
|
Language=English
|
|
%2 : The adapter has detected that the Token Ring cable is disconnected from
|
|
the adapter. Please reconnect the Token Ring cable. The adapter will continue
|
|
to try to reset until the connection is repaired.
|
|
.
|
|
MessageId=5034 Severity=Warning SymbolicName=EVENT_NDIS_RESET_FAILURE_CORRECTION
|
|
Language=English
|
|
%2 : The adapter has successfully completed a previously failed reset.
|
|
.
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// General NT System Events
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
|
|
;//
|
|
;// Eventlog Events 6000 - 6099
|
|
;//
|
|
|
|
MessageId=6000 SymbolicName=EVENT_LOG_FULL
|
|
Language=English
|
|
The %1 log file is full.
|
|
.
|
|
|
|
MessageId=6001 SymbolicName=EVENT_LogFileNotOpened
|
|
Language=English
|
|
The %1 log file cannot be opened.
|
|
.
|
|
|
|
MessageId=6002 SymbolicName=EVENT_LogFileCorrupt
|
|
Language=English
|
|
The %1 log file is corrupted and will be cleared.
|
|
.
|
|
|
|
MessageId=6003 SymbolicName=EVENT_DefaultLogCorrupt
|
|
Language=English
|
|
The Application log file could not be opened. %1 will be used as the default
|
|
log file.
|
|
.
|
|
|
|
MessageId=6004 SymbolicName=EVENT_BadDriverPacket
|
|
Language=English
|
|
A driver packet received from the I/O subsystem was invalid. The data is the
|
|
packet.
|
|
.
|
|
|
|
MessageId=6005 SymbolicName=EVENT_EventlogStarted
|
|
Language=English
|
|
The Event log service was started.
|
|
.
|
|
|
|
MessageId=6006 SymbolicName=EVENT_EventlogStopped
|
|
Language=English
|
|
The Event log service was stopped.
|
|
.
|
|
|
|
MessageId=6007 SymbolicName=TITLE_EventlogMessageBox
|
|
Language=English
|
|
Eventlog Service %0
|
|
.
|
|
|
|
MessageId=6008 SymbolicName=EVENT_EventlogAbnormalShutdown
|
|
Language=English
|
|
The previous system shutdown at %1 on %2 was unexpected.
|
|
.
|
|
|
|
MessageId=6009 SymbolicName=EVENT_EventLogProductInfo
|
|
Language=English
|
|
Microsoft (R) Windows (R) %1 %2 %3 %4.
|
|
.
|
|
|
|
MessageId=6010 Severity=Error SymbolicName=EVENT_ServiceNoEventLog
|
|
Language=English
|
|
The %1 service was unable to set up an event source.
|
|
.
|
|
|
|
MessageId=6011 SymbolicName=EVENT_ComputerNameChange
|
|
Language=English
|
|
The NetBIOS name and DNS host name of this machine have been changed from %1 to %2.
|
|
.
|
|
|
|
MessageId=6012 SymbolicName=EVENT_DNSDomainNameChange
|
|
Language=English
|
|
The DNS domain assigned to this computer has been changed from %1 to %2.
|
|
.
|
|
|
|
;//
|
|
;// System Events 6100 - 6199
|
|
;//
|
|
|
|
MessageId=6100 Severity=Error SymbolicName=EVENT_UP_DRIVER_ON_MP
|
|
Language=English
|
|
A uniprocessor-specific driver was loaded on a multiprocessor system. The driver could not load.
|
|
.
|
|
;//
|
|
;// Service Controller Events 7000 - 7899
|
|
;//
|
|
|
|
MessageId=7000 Severity=Error SymbolicName=EVENT_SERVICE_START_FAILED
|
|
Language=English
|
|
The %1 service failed to start due to the following error: %n%2
|
|
.
|
|
|
|
MessageId=7001 Severity=Error SymbolicName=EVENT_SERVICE_START_FAILED_II
|
|
Language=English
|
|
The %1 service depends on the %2 service which failed to start because of the following error: %n%3
|
|
.
|
|
|
|
MessageId=7002 Severity=Error SymbolicName=EVENT_SERVICE_START_FAILED_GROUP
|
|
Language=English
|
|
The %1 service depends on the %2 group and no member of this group started.
|
|
.
|
|
|
|
MessageId=7003 Severity=Error SymbolicName=EVENT_SERVICE_START_FAILED_NONE
|
|
Language=English
|
|
The %1 service depends on the following nonexistent service: %2
|
|
.
|
|
|
|
MessageId=7005 Severity=Error SymbolicName=EVENT_CALL_TO_FUNCTION_FAILED
|
|
Language=English
|
|
The %1 call failed with the following error: %n%2
|
|
.
|
|
|
|
MessageId=7006 Severity=Error SymbolicName=EVENT_CALL_TO_FUNCTION_FAILED_II
|
|
Language=English
|
|
The %1 call failed for %2 with the following error: %n%3
|
|
.
|
|
|
|
MessageId=7007 Severity=Error SymbolicName=EVENT_REVERTED_TO_LASTKNOWNGOOD
|
|
Language=English
|
|
The system reverted to its last known good configuration. The system is restarting....
|
|
.
|
|
|
|
MessageId=7008 Severity=Error SymbolicName=EVENT_BAD_ACCOUNT_NAME
|
|
Language=English
|
|
No backslash is in the account name.
|
|
.
|
|
|
|
MessageId=7009 Severity=Error SymbolicName=EVENT_CONNECTION_TIMEOUT
|
|
Language=English
|
|
Timeout (%1 milliseconds) waiting for the %2 service to connect.
|
|
.
|
|
|
|
MessageId=7010 Severity=Error SymbolicName=EVENT_READFILE_TIMEOUT
|
|
Language=English
|
|
Timeout (%1 milliseconds) waiting for ReadFile.
|
|
.
|
|
|
|
MessageId=7011 Severity=Error SymbolicName=EVENT_TRANSACT_TIMEOUT
|
|
Language=English
|
|
Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.
|
|
.
|
|
|
|
MessageId=7012 Severity=Error SymbolicName=EVENT_TRANSACT_INVALID
|
|
Language=English
|
|
Message returned in transaction has incorrect size.
|
|
.
|
|
|
|
MessageId=7013 Severity=Error SymbolicName=EVENT_FIRST_LOGON_FAILED
|
|
Language=English
|
|
Logon attempt with current password failed with the following error: %n%1
|
|
.
|
|
|
|
MessageId=7014 Severity=Error SymbolicName=EVENT_SECOND_LOGON_FAILED
|
|
Language=English
|
|
Second logon attempt with old password also failed with the following error: %n%1
|
|
.
|
|
|
|
MessageId=7015 Severity=Error SymbolicName=EVENT_INVALID_DRIVER_DEPENDENCY
|
|
Language=English
|
|
Boot-start or system-start driver (%1) must not depend on a service.
|
|
.
|
|
|
|
MessageId=7016 Severity=Error SymbolicName=EVENT_BAD_SERVICE_STATE
|
|
Language=English
|
|
The %1 service has reported an invalid current state %2.
|
|
.
|
|
|
|
MessageId=7017 Severity=Error SymbolicName=EVENT_CIRCULAR_DEPENDENCY_DEMAND
|
|
Language=English
|
|
Detected circular dependencies demand starting %1.
|
|
.
|
|
|
|
MessageId=7018 Severity=Error SymbolicName=EVENT_CIRCULAR_DEPENDENCY_AUTO
|
|
Language=English
|
|
Detected circular dependencies auto-starting services.
|
|
.
|
|
|
|
MessageId=7019 Severity=Error SymbolicName=EVENT_DEPEND_ON_LATER_SERVICE
|
|
Language=English
|
|
Circular dependency: The %1 service depends on a service in a group which starts later.
|
|
.
|
|
|
|
MessageId=7020 Severity=Error SymbolicName=EVENT_DEPEND_ON_LATER_GROUP
|
|
Language=English
|
|
Circular dependency: The %1 service depends on a group which starts later.
|
|
.
|
|
|
|
MessageId=7021 Severity=Error SymbolicName=EVENT_SEVERE_SERVICE_FAILED
|
|
Language=English
|
|
About to revert to the last known good configuration because the %1 service failed to start.
|
|
.
|
|
|
|
MessageId=7022 Severity=Error SymbolicName=EVENT_SERVICE_START_HUNG
|
|
Language=English
|
|
The %1 service hung on starting.
|
|
.
|
|
|
|
MessageId=7023 Severity=Error SymbolicName=EVENT_SERVICE_EXIT_FAILED
|
|
Language=English
|
|
The %1 service terminated with the following error: %n%2
|
|
.
|
|
|
|
MessageId=7024 Severity=Error SymbolicName=EVENT_SERVICE_EXIT_FAILED_SPECIFIC
|
|
Language=English
|
|
The %1 service terminated with service-specific error %2.
|
|
.
|
|
|
|
MessageId=7025 Severity=Error SymbolicName=EVENT_SERVICE_START_AT_BOOT_FAILED
|
|
Language=English
|
|
At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
|
|
.
|
|
|
|
MessageId=7026 Severity=Error SymbolicName=EVENT_BOOT_SYSTEM_DRIVERS_FAILED
|
|
Language=English
|
|
The following boot-start or system-start driver(s) failed to load: %1
|
|
.
|
|
|
|
MessageId=7027 Severity=Error SymbolicName=EVENT_RUNNING_LASTKNOWNGOOD
|
|
Language=English
|
|
Windows 2000 could not be started as configured. A previous working configuration was used instead.
|
|
.
|
|
|
|
MessageId=7028 Severity=Error SymbolicName=EVENT_TAKE_OWNERSHIP
|
|
Language=English
|
|
The %1 Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry key.
|
|
.
|
|
|
|
;//
|
|
;// This Text is used as a title for the message box used to display
|
|
;// MessageId 7027. It is not an event or error message.
|
|
;//
|
|
MessageId=7029 Severity=Error SymbolicName=TITLE_SC_MESSAGE_BOX
|
|
Language=English
|
|
Service Control Manager %0
|
|
.
|
|
|
|
MessageId=7030 Severity=Error SymbolicName=EVENT_SERVICE_NOT_INTERACTIVE
|
|
Language=English
|
|
The %1 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
|
|
.
|
|
|
|
;//
|
|
;// Parameter %4 is the value, in decimal, of the SC_ACTION_ constant for
|
|
;// the action described in parameter %5.
|
|
;//
|
|
MessageId=7031 Severity=Error SymbolicName=EVENT_SERVICE_CRASH
|
|
Language=English
|
|
The %1 service terminated unexpectedly. It has done this %2 time(s). The following corrective action will be taken in %3 milliseconds: %5.
|
|
.
|
|
|
|
;//
|
|
;// Parameter %1 is the value, in decimal, of the SC_ACTION_ constant for
|
|
;// the action described in parameter %2.
|
|
;//
|
|
MessageId=7032 Severity=Error SymbolicName=EVENT_SERVICE_RECOVERY_FAILED
|
|
Language=English
|
|
The Service Control Manager tried to take a corrective action (%2) after the unexpected termination of the %3 service, but this action failed with the following error: %n%4
|
|
.
|
|
|
|
MessageId=7033 Severity=Error SymbolicName=EVENT_SERVICE_SCESRV_FAILED
|
|
Language=English
|
|
The Service Control Manager did not initialize successfully. The security
|
|
configuration server (scesrv.dll) failed to initialize with error %1. The
|
|
system is restarting...
|
|
.
|
|
|
|
MessageId=7034 Severity=Error SymbolicName=EVENT_SERVICE_CRASH_NO_ACTION
|
|
Language=English
|
|
The %1 service terminated unexpectedly. It has done this %2 time(s).
|
|
.
|
|
|
|
;//
|
|
;// Parameter %2 is the string name of the control
|
|
;//
|
|
MessageId=7035 Severity=Informational SymbolicName=EVENT_SERVICE_CONTROL_SUCCESS
|
|
Language=English
|
|
The %1 service was successfully sent a %2 control.
|
|
.
|
|
|
|
;//
|
|
;// Parameter %2 is the string name of the control
|
|
;//
|
|
MessageId=7036 Severity=Informational SymbolicName=EVENT_SERVICE_STATUS_SUCCESS
|
|
Language=English
|
|
The %1 service entered the %2 state.
|
|
.
|
|
|
|
MessageId=7037 Severity=Error SymbolicName=EVENT_SERVICE_CONFIG_BACKOUT_FAILED
|
|
Language=English
|
|
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).
|
|
.
|
|
|
|
MessageId=7038 Severity=Error SymbolicName=EVENT_FIRST_LOGON_FAILED_II
|
|
Language=English
|
|
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).
|
|
.
|
|
|
|
;//
|
|
;// Schedule (AT command) Service Events 7900 - 7999
|
|
;//
|
|
|
|
MessageId=7900 SymbolicName=EVENT_COMMAND_NOT_INTERACTIVE
|
|
Language=English
|
|
The %1 command is marked as an interactive command. However, the system is
|
|
configured to not allow interactive command execution. This command may not
|
|
function properly.
|
|
.
|
|
|
|
MessageId=7901 SymbolicName=EVENT_COMMAND_START_FAILED
|
|
Language=English
|
|
The %1 command failed to start due to the following error: %n%2
|
|
.
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Lanman Bowser/Browser Events (8000-8499)
|
|
;//
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=8003 Severity=Error SymbolicName=EVENT_BOWSER_OTHER_MASTER_ON_NET
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=8004 Severity=Warning SymbolicName=EVENT_BOWSER_PROMOTED_WHILE_ALREADY_MASTER
|
|
Language=English
|
|
A request has been submitted to promote the computer to backup when it is already a
|
|
master browser.
|
|
.
|
|
|
|
MessageId=8005 Severity=Warning SymbolicName=EVENT_BOWSER_NON_MASTER_MASTER_ANNOUNCE
|
|
Language=English
|
|
The browser has received a server announcement indicating that the computer %2
|
|
is a master browser, but this computer is not a master browser.
|
|
.
|
|
|
|
MessageId=8006 Severity=Warning SymbolicName=EVENT_BOWSER_ILLEGAL_DATAGRAM
|
|
Language=English
|
|
The browser has received an illegal datagram from the remote computer %2 to name %3 on transport %4. The data is the datagram.
|
|
.
|
|
|
|
MessageId=8007 Severity=Error SymbolicName=EVENT_BROWSER_STATUS_BITS_UPDATE_FAILED
|
|
Language=English
|
|
The browser was unable to update the service status bits. The data is the error.
|
|
.
|
|
|
|
MessageId=8008 Severity=Error SymbolicName=EVENT_BROWSER_ROLE_CHANGE_FAILED
|
|
Language=English
|
|
The browser was unable to update its role. The data is the error.
|
|
.
|
|
|
|
MessageId=8009 Severity=Error SymbolicName=EVENT_BROWSER_MASTER_PROMOTION_FAILED
|
|
Language=English
|
|
The browser was unable to promote itself to master browser. The computer that currently
|
|
believes it is the master browser is %1.
|
|
.
|
|
|
|
MessageId=8010 Severity=Error SymbolicName=EVENT_BOWSER_NAME_CONVERSION_FAILED
|
|
Language=English
|
|
The browser driver was unable to convert a character string to a unicode string.
|
|
.
|
|
|
|
MessageId=8011 Severity=Error SymbolicName=EVENT_BROWSER_OTHERDOMAIN_ADD_FAILED
|
|
Language=English
|
|
The browser was unable to add the configuration parameter %1.
|
|
.
|
|
|
|
MessageId=8012 Severity=Success SymbolicName=EVENT_BOWSER_ELECTION_RECEIVED
|
|
Language=English
|
|
The browser driver has received an election packet from computer %2 on network %3. The data is the packet received.
|
|
.
|
|
|
|
MessageId=8013 Severity=Informational SymbolicName=EVENT_BOWSER_ELECTION_SENT_GETBLIST_FAILED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=8014 Severity=Informational SymbolicName=EVENT_BOWSER_ELECTION_SENT_FIND_MASTER_FAILED
|
|
Language=English
|
|
The browser driver has forced an election on network %2 because it was unable to find a master browser for that network.
|
|
.
|
|
|
|
MessageId=8015 Severity=Informational SymbolicName=EVENT_BROWSER_ELECTION_SENT_LANMAN_NT_STARTED
|
|
Language=English
|
|
The browser has forced an election on network %1 because a Windows 2000 Server (or domain master) browser is started.
|
|
.
|
|
|
|
MessageId=8016 Severity=Error SymbolicName=EVENT_BOWSER_ILLEGAL_DATAGRAM_THRESHOLD
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=8017 Severity=Error SymbolicName=EVENT_BROWSER_DEPENDANT_SERVICE_FAILED
|
|
Language=English
|
|
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
|
|
.
|
|
MessageId=8019 Severity=Error SymbolicName=EVENT_BROWSER_MASTER_PROMOTION_FAILED_STOPPING
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=8020 Severity=Error SymbolicName=EVENT_BROWSER_MASTER_PROMOTION_FAILED_NO_MASTER
|
|
Language=English
|
|
The browser was unable to promote itself to master browser. The computer that currently
|
|
believes it is the master browser is unknown.
|
|
.
|
|
MessageId=8021 Severity=Warning SymbolicName=EVENT_BROWSER_SERVER_LIST_FAILED
|
|
Language=English
|
|
The browser was unable to retrieve a list of servers from the browser master %1 on the network %2.
|
|
The data is the error code.
|
|
.
|
|
MessageId=8022 Severity=Warning SymbolicName=EVENT_BROWSER_DOMAIN_LIST_FAILED
|
|
Language=English
|
|
The browser was unable to retrieve a list of domains from the browser master %1 on the network %2.
|
|
The data is the error code.
|
|
.
|
|
MessageId=8023 Severity=Warning SymbolicName=EVENT_BROWSER_ILLEGAL_CONFIG
|
|
Language=English
|
|
The value for the parameter %1 to the browser service was illegal.
|
|
.
|
|
MessageId=8024 Severity=Informational SymbolicName=EVENT_BOWSER_OLD_BACKUP_FOUND
|
|
Language=English
|
|
The backup browser server %2 is out-of-date. Consider upgrading this computer.
|
|
.
|
|
MessageId=8025 Severity=Success SymbolicName=EVENT_BROWSER_SERVER_LIST_RETRIEVED
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=8026 Severity=Success SymbolicName=EVENT_BROWSER_DOMAIN_LIST_RETRIEVED
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=8027 Severity=Informational SymbolicName=EVENT_BOWSER_PDC_LOST_ELECTION
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=8028 Severity=Informational SymbolicName=EVENT_BOWSER_NON_PDC_WON_ELECTION
|
|
Language=English
|
|
The browser running on this computer has won a browser election on network %2.
|
|
This computer is a member of a domain, so the Domain Controller should become the master
|
|
browser.
|
|
.
|
|
MessageId=8029 SymbolicName=EVENT_BOWSER_CANT_READ_REGISTRY
|
|
Language=English
|
|
The browser driver was unable to initialize variables from the Registry.
|
|
.
|
|
|
|
MessageId=8030 SymbolicName=EVENT_BOWSER_MAILSLOT_DATAGRAM_THRESHOLD_EXCEEDED
|
|
Language=English
|
|
The browser driver has discarded too many mailslot messages.
|
|
.
|
|
MessageId=8031 SymbolicName=EVENT_BOWSER_GETBROWSERLIST_THRESHOLD_EXCEEDED
|
|
Language=English
|
|
The browser driver has discarded too many GetBrowserServerList requests.
|
|
.
|
|
|
|
MessageId=8032 Severity=Error SymbolicName=EVENT_BROWSER_BACKUP_STOPPED
|
|
Language=English
|
|
The browser service has failed to retrieve the backup list too many times on transport %1.
|
|
The backup browser is stopping.
|
|
.
|
|
MessageId=8033 Severity=Informational SymbolicName=EVENT_BROWSER_ELECTION_SENT_LANMAN_NT_STOPPED
|
|
Language=English
|
|
The browser has forced an election on network %1 because a master browser was stopped.
|
|
.
|
|
|
|
MessageId=8034 Severity=Error SymbolicName=EVENT_BROWSER_GETBLIST_RECEIVED_NOT_MASTER
|
|
Language=English
|
|
The browser has received a GetBrowserServerList request when it is not the master browser.
|
|
.
|
|
|
|
MessageId=8035 Severity=Informational SymbolicName=EVENT_BROWSER_ELECTION_SENT_ROLE_CHANGED
|
|
Language=English
|
|
The browser has forced an election on network %1 because the Domain Controller (or Server) has changed its role.
|
|
.
|
|
|
|
MessageId=8036 Severity=Error SymbolicName=EVENT_BROWSER_NOT_STARTED_IPX_CONFIG_MISMATCH
|
|
Language=English
|
|
The browser has failed to start because of an error in the DirectHostBinding parameter to the browser.
|
|
.
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Sap Agent Events (8500-8999)
|
|
;//
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=8500 Severity=Error SymbolicName=NWSAP_EVENT_KEY_NOT_FOUND
|
|
Language=English
|
|
The Registry Key %1 was not present. The Sap Agent could not start.
|
|
.
|
|
|
|
MessageId=8501 Severity=Error SymbolicName=NWSAP_EVENT_WSASTARTUP_FAILED
|
|
Language=English
|
|
Winsock startup routine failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8502 Severity=Error SymbolicName=NWSAP_EVENT_SOCKET_FAILED
|
|
Language=English
|
|
Socket create call failed for main socket. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8503 Severity=Error SymbolicName=NWSAP_EVENT_SETOPTBCAST_FAILED
|
|
Language=English
|
|
Setting broadcast option on socket failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8504 Severity=Error SymbolicName=NWSAP_EVENT_BIND_FAILED
|
|
Language=English
|
|
Binding to SAP Socket failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8505 Severity=Error SymbolicName=NWSAP_EVENT_GETSOCKNAME_FAILED
|
|
Language=English
|
|
Getting bound address of socket failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8506 Severity=Error SymbolicName=NWSAP_EVENT_OPTEXTENDEDADDR_FAILED
|
|
Language=English
|
|
Setting option EXTENDED_ADDRESS failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8507 Severity=Error SymbolicName=NWSAP_EVENT_OPTBCASTINADDR_FAILED
|
|
Language=English
|
|
Setting NWLink option BCASTINTADDR failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8508 Severity=Error SymbolicName=NWSAP_EVENT_CARDMALLOC_FAILED
|
|
Language=English
|
|
Error allocating memory to hold a card structure. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8509 Severity=Error SymbolicName=NWSAP_EVENT_NOCARDS
|
|
Language=English
|
|
Enumeration of cards returned 0 cards.
|
|
.
|
|
|
|
MessageId=8510 Severity=Error SymbolicName=NWSAP_EVENT_THREADEVENT_FAIL
|
|
Language=English
|
|
Error creating thread counting event. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8511 Severity=Error SymbolicName=NWSAP_EVENT_RECVSEM_FAIL
|
|
Language=English
|
|
Error creating receive semaphore. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8512 Severity=Error SymbolicName=NWSAP_EVENT_SENDEVENT_FAIL
|
|
Language=English
|
|
Error creating send event. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8513 Severity=Error SymbolicName=NWSAP_EVENT_STARTRECEIVE_ERROR
|
|
Language=English
|
|
Error starting receive thread. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8514 Severity=Error SymbolicName=NWSAP_EVENT_STARTWORKER_ERROR
|
|
Language=English
|
|
Error starting worker thread. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8515 Severity=Error SymbolicName=NWSAP_EVENT_TABLE_MALLOC_FAILED
|
|
Language=English
|
|
Error allocating database array. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8516 Severity=Error SymbolicName=NWSAP_EVENT_HASHTABLE_MALLOC_FAILED
|
|
Language=English
|
|
Error allocating hash table. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8517 Severity=Error SymbolicName=NWSAP_EVENT_STARTLPCWORKER_ERROR
|
|
Language=English
|
|
Error starting LPC worker thread. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8518 Severity=Error SymbolicName=NWSAP_EVENT_CREATELPCPORT_ERROR
|
|
Language=English
|
|
Error creating the LPC port. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8519 Severity=Error SymbolicName=NWSAP_EVENT_CREATELPCEVENT_ERROR
|
|
Language=English
|
|
Error creating the LPC thread event. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8520 Severity=Error SymbolicName=NWSAP_EVENT_LPCLISTENMEMORY_ERROR
|
|
Language=English
|
|
Error allocating memory for an LPC Client structure. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8521 Severity=Error SymbolicName=NWSAP_EVENT_LPCHANDLEMEMORY_ERROR
|
|
Language=English
|
|
Error allocating buffer to hold LPC worker thread handles. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8522 Severity=Error SymbolicName=NWSAP_EVENT_BADWANFILTER_VALUE
|
|
Language=English
|
|
The value for WANFilter in the registry must be 0-2. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8523 Severity=Error SymbolicName=NWSAP_EVENT_CARDLISTEVENT_FAIL
|
|
Language=English
|
|
Error creating event for card list access synchronization. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8524 Severity=Error SymbolicName=NWSAP_EVENT_SDMDEVENT_FAIL
|
|
Language=English
|
|
Error creating event for database access synchronization. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8525 Severity=Warning SymbolicName=NWSAP_EVENT_INVALID_FILTERNAME
|
|
Language=English
|
|
Name too long in key %1: Name = %s. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8526 Severity=Error SymbolicName=NWSAP_EVENT_WANSEM_FAIL
|
|
Language=English
|
|
Error creating WAN control semaphore. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8527 Severity=Error SymbolicName=NWSAP_EVENT_WANSOCKET_FAILED
|
|
Language=English
|
|
Socket create call failed for WAN socket. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8528 Severity=Error SymbolicName=NWSAP_EVENT_WANBIND_FAILED
|
|
Language=English
|
|
Binding to WAN socket failed. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8529 Severity=Error SymbolicName=NWSAP_EVENT_STARTWANWORKER_ERROR
|
|
Language=English
|
|
Error starting WAN worker thread. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8530 Severity=Error SymbolicName=NWSAP_EVENT_STARTWANCHECK_ERROR
|
|
Language=English
|
|
Error starting WAN check thread. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8531 Severity=Error SymbolicName=NWSAP_EVENT_OPTMAXADAPTERNUM_ERROR
|
|
Language=English
|
|
Error on getsockopt IPX_MAX_ADAPTER_NUM. Data is the error code. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8532 Severity=Error SymbolicName=NWSAP_EVENT_WANHANDLEMEMORY_ERROR
|
|
Language=English
|
|
Error allocating buffer to hold WAN notify thread handles. The Sap Agent cannot continue.
|
|
.
|
|
|
|
MessageId=8533 Severity=Error SymbolicName=NWSAP_EVENT_WANEVENT_ERROR
|
|
Language=English
|
|
Error creating the WAN thread event. The Sap Agent cannot continue.
|
|
.
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Transport Events (9000-9499)
|
|
;//
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=9001 Severity=Warning SymbolicName=EVENT_TRANSPORT_RESOURCE_POOL
|
|
Language=English
|
|
%2 could not allocate a resource of type %3 due to system resource problems.
|
|
.
|
|
|
|
MessageId=9002 Severity=Warning SymbolicName=EVENT_TRANSPORT_RESOURCE_LIMIT
|
|
Language=English
|
|
%2 could not allocate a resource of type %3 due to its configured size of %4.
|
|
.
|
|
|
|
MessageId=9003 Severity=Warning SymbolicName=EVENT_TRANSPORT_RESOURCE_SPECIFIC
|
|
Language=English
|
|
%2 could not allocate a resource of type %3 due to a specifically configured limit of %4.
|
|
.
|
|
|
|
MessageId=9004 Severity=Error SymbolicName=EVENT_TRANSPORT_REGISTER_FAILED
|
|
Language=English
|
|
%2 failed to register itself with the NDIS wrapper.
|
|
.
|
|
|
|
MessageId=9005 Severity=Error SymbolicName=EVENT_TRANSPORT_BINDING_FAILED
|
|
Language=English
|
|
%2 failed to bind to adapter %3.
|
|
.
|
|
|
|
MessageId=9006 Severity=Error SymbolicName=EVENT_TRANSPORT_ADAPTER_NOT_FOUND
|
|
Language=English
|
|
%2 could not find adapter %3.
|
|
.
|
|
|
|
MessageId=9007 Severity=Error SymbolicName=EVENT_TRANSPORT_SET_OID_FAILED
|
|
Language=English
|
|
%2 failed while setting OID %3 on adapter %4.
|
|
.
|
|
|
|
MessageId=9008 Severity=Error SymbolicName=EVENT_TRANSPORT_QUERY_OID_FAILED
|
|
Language=English
|
|
%2 failed while querying OID %3 on adapter %4.
|
|
.
|
|
|
|
MessageId=9009 Severity=Informational SymbolicName=EVENT_TRANSPORT_TRANSFER_DATA
|
|
Language=English
|
|
%2 could not transfer a packet from the adapter. The packet was dropped.
|
|
.
|
|
|
|
MessageId=9010 Severity=Informational SymbolicName=EVENT_TRANSPORT_TOO_MANY_LINKS
|
|
Language=English
|
|
%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.
|
|
.
|
|
|
|
MessageId=9011 Severity=Informational SymbolicName=EVENT_TRANSPORT_BAD_PROTOCOL
|
|
Language=English
|
|
%2 received an unexpected %3 packet from a remote computer.
|
|
.
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// IPX/SPX Events (9500-9999)
|
|
;//
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=9501 Severity=Informational SymbolicName=EVENT_IPX_NEW_DEFAULT_TYPE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=9502 Severity=Warning SymbolicName=EVENT_IPX_SAP_ANNOUNCE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=9503 Severity=Warning SymbolicName=EVENT_IPX_ILLEGAL_CONFIG
|
|
Language=English
|
|
The value for the %2 parameter %3 was illegal.
|
|
.
|
|
|
|
MessageId=9504 Severity=Error SymbolicName=EVENT_IPX_INTERNAL_NET_INVALID
|
|
Language=English
|
|
%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.
|
|
.
|
|
|
|
MessageId=9505 Severity=Error SymbolicName=EVENT_IPX_NO_FRAME_TYPES
|
|
Language=English
|
|
%2 had no frame types configured for the binding to adapter %3.
|
|
.
|
|
|
|
MessageId=9506 Severity=Error SymbolicName=EVENT_IPX_CREATE_DEVICE
|
|
Language=English
|
|
%2 failed to initialize because the driver device could not be created.
|
|
.
|
|
|
|
MessageId=9507 Severity=Error SymbolicName=EVENT_IPX_NO_ADAPTERS
|
|
Language=English
|
|
%2 could not bind to any adapters. The transport could not start.
|
|
.
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// DCOM Events (10000-10999)
|
|
;//
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;
|
|
|
|
MessageId=10000 Severity=Error SymbolicName=EVENT_RPCSS_CREATEPROCESS_FAILURE
|
|
Language=English
|
|
Unable to start a DCOM Server: %3.
|
|
The error:%n"%%%2"%nHappened while starting this command:%n%1
|
|
.
|
|
|
|
MessageId=10001 Severity=Error SymbolicName=EVENT_RPCSS_RUNAS_CREATEPROCESS_FAILURE
|
|
Language=English
|
|
Unable to start a DCOM Server: %3 as %4/%5.
|
|
The error:%n"%%%2"%nHappened while starting this command:%n%1
|
|
.
|
|
|
|
MessageId=10002 Severity=Error SymbolicName=EVENT_RPCSS_LAUNCH_ACCESS_DENIED
|
|
Language=English
|
|
Access denied attempting to launch a DCOM Server.
|
|
The server is:%n%1%nThe user is %2/%3, SID=%4.
|
|
.
|
|
|
|
MessageId=10003 Severity=Error SymbolicName=EVENT_RPCSS_DEFAULT_LAUNCH_ACCESS_DENIED
|
|
Language=English
|
|
Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion.
|
|
The server is:%n%1%nThe user is %2/%3, SID=%4.
|
|
.
|
|
|
|
MessageId=10004 Severity=Error SymbolicName=EVENT_RPCSS_RUNAS_CANT_LOGIN
|
|
Language=English
|
|
DCOM got error "%%%1" and was unable to logon %2\%3
|
|
in order to run the server:%n%4
|
|
.
|
|
|
|
MessageId=10005 Severity=Error SymbolicName=EVENT_RPCSS_START_SERVICE_FAILURE
|
|
Language=English
|
|
DCOM got error "%%%1" attempting to start the service %2 with arguments "%3"
|
|
in order to run the server:%n%4
|
|
.
|
|
|
|
MessageId=10006 Severity=Error SymbolicName=EVENT_RPCSS_REMOTE_SIDE_ERROR
|
|
Language=English
|
|
DCOM got error "%%%1" from the computer %2 when attempting to
|
|
activate the server:%n%3
|
|
.
|
|
|
|
MessageId=10007 Severity=Error SymbolicName=EVENT_RPCSS_ACTIVATION_ERROR
|
|
Language=English
|
|
DCOM got error "%%%1" when attempting to
|
|
activate the server:%n%2
|
|
.
|
|
|
|
MessageId=10008 Severity=Error SymbolicName=EVENT_RPCSS_REMOTE_SIDE_ERROR_WITH_FILE
|
|
Language=English
|
|
DCOM got error "%%%1" from the computer %2 when attempting to
|
|
the server:%n%3 with file %4.
|
|
.
|
|
|
|
MessageId=10009 Severity=Error SymbolicName=EVENT_RPCSS_REMOTE_SIDE_UNAVAILABLE
|
|
Language=English
|
|
DCOM was unable to communicate with the computer %1 using any of the configured
|
|
protocols.
|
|
.
|
|
|
|
MessageId=10010 Severity=Error SymbolicName=EVENT_RPCSS_SERVER_START_TIMEOUT
|
|
Language=English
|
|
The server %1 did not register with DCOM within the required timeout.
|
|
.
|
|
|
|
MessageId=10011 Severity=Error SymbolicName=EVENT_RPCSS_SERVER_NOT_RESPONDING
|
|
Language=English
|
|
The server %1 could not be contacted to establish the connection to the client
|
|
.
|
|
|
|
MessageId=10012 Severity=Error SymbolicName=EVENT_DCOM_ASSERTION_FAILURE
|
|
Language=English
|
|
There is an assertion failure in DCOM. Context follows:
|
|
%1
|
|
%2
|
|
%3
|
|
.
|
|
|
|
MessageId=10013 Severity=Error SymbolicName=EVENT_DCOM_INVALID_ENDPOINT_DATA
|
|
Language=English
|
|
DCOM server attempted to listen on an invalid endpoint.
|
|
Protseq: %1
|
|
Endpoint: %2
|
|
Flags: %3
|
|
.
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// DNS Caching Resolvers Service and DNS API Events (11000-11999)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
;//
|
|
;// Errors
|
|
;//
|
|
;
|
|
|
|
MessageId=11000
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_DLL
|
|
Language=English
|
|
Unable to start DNS Client Service.
|
|
Failed to load DLL %2, Error: %1.
|
|
Please reinstall this DLL from installation CD.
|
|
.
|
|
|
|
MessageId=11001
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_ENTRY
|
|
Language=English
|
|
Unable to start DNS Client service. Can not find entry %3 in DLL %2.
|
|
Please reinstall this DLL from installation CD. For specific error
|
|
code, see the record data displayed below.
|
|
.
|
|
|
|
MessageId=11002
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_CONTROL
|
|
Language=English
|
|
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. For specific error
|
|
code, see the record data displayed below.
|
|
.
|
|
|
|
MessageId=11003
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_DONE_EVENT
|
|
Language=English
|
|
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. For specific error code,
|
|
see the record data displayed below.
|
|
.
|
|
|
|
MessageId=11004
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_RPC
|
|
Language=English
|
|
Unable to start DNS Client service. Could not start the
|
|
Remote Procedure Call (RPC) interface for this service.
|
|
To correct the problem, you may restart the RPC and DNS
|
|
Client services. To do so, use the following commands at a command
|
|
prompt: (1) type "net start rpc" to start the RPC service, and (2)
|
|
type "net start dnscache" to start the DNS Client service. For
|
|
specific error code information, see the record data displayed below.
|
|
.
|
|
|
|
MessageId=11005
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_SHUTDOWN_NOTIFY
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=11006
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_NO_UPDATE
|
|
Language=English
|
|
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. For
|
|
specific error code information, see the record data displayed below.
|
|
.
|
|
|
|
MessageId=11007
|
|
Severity=Error
|
|
SymbolicName=EVENT_DNS_CACHE_START_FAILURE_LOW_MEMORY
|
|
Language=English
|
|
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. For specific error code, see the record data
|
|
displayed below.
|
|
.
|
|
|
|
|
|
;
|
|
;//
|
|
;// Warnings
|
|
;//
|
|
;
|
|
|
|
MessageId=11050
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNS_CACHE_NETWORK_PERF_WARNING
|
|
Language=English
|
|
The DNS Client service could not contact any DNS servers for
|
|
a repeated number of attempts. For the next %3 seconds the
|
|
DNS Client service will not use the network to avoid further
|
|
network performance problems. It will resume its normal behavior
|
|
after that. If this problem persists, verify your TCP/IP
|
|
configuration, specifically check that you have a preferred
|
|
(and possibly an alternate) DNS server configured. If the problem
|
|
continues, verify network conditions to these DNS servers or contact
|
|
your network administrator.
|
|
.
|
|
|
|
MessageId=11051
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNS_CACHE_UNABLE_TO_REACH_SERVER_WARNING
|
|
Language=English
|
|
The DNS Client service failed to reach DNS server at address %1. It will
|
|
not use this DNS server for %2 seconds.
|
|
.
|
|
|
|
Messageid=11150
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_TIMEOUT
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11151
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_SERVERFAIL
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11152
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_NOTSUPP
|
|
Language=English
|
|
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) resource record using the
|
|
specific DNS name for this adapter, contact your DNS server or network
|
|
systems administrator.
|
|
.
|
|
|
|
Messageid=11153
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_REFUSED
|
|
Language=English
|
|
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) resource record using the specific DNS domain
|
|
name for this adapter, contact your DNS server or network systems
|
|
administrator.
|
|
.
|
|
|
|
Messageid=11154
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_SECURITY
|
|
Language=English
|
|
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. For specific error code information, see the record data
|
|
displayed below.
|
|
.
|
|
|
|
Messageid=11155
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_OTHER
|
|
Language=English
|
|
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. For specific error code
|
|
information, see the record data displayed below.
|
|
.
|
|
|
|
|
|
Messageid=11156
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_REGISTRATION_FAILED_TIMEOUT
|
|
Language=English
|
|
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. For specific error code
|
|
information, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11157
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_REGISTRATION_FAILED_SERVERFAIL
|
|
Language=English
|
|
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 DNS server failure. This may be due to a zone transfer lock on
|
|
the DNS server for the zone that your computer needs 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. For specific error code information, see the record data
|
|
displayed below.
|
|
.
|
|
|
|
Messageid=11158
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_REGISTRATION_FAILED_NOTSUPP
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11159
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_REGISTRATION_FAILED_REFUSED
|
|
Language=English
|
|
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 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.
|
|
.
|
|
|
|
Messageid=11160
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_REGISTRATION_FAILED_SECURITY
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11161
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_REGISTRATION_FAILED_OTHER
|
|
Language=English
|
|
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 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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11162
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_TIMEOUT_PRIMARY_DN
|
|
Language=English
|
|
The system failed to register host (A) 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.
|
|
.
|
|
|
|
Messageid=11163
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_SERVERFAIL_PRIMARY_DN
|
|
Language=English
|
|
The system failed to register host (A) 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.
|
|
.
|
|
|
|
Messageid=11164
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_NOTSUPP_PRIMARY_DN
|
|
Language=English
|
|
The system failed to register host (A) 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 either
|
|
(a) the DNS server does not support the DNS dynamic update protocol, or
|
|
(b) the authoritative zone for the specified DNS domain name does not
|
|
accept dynamic updates.%n%n
|
|
To register the DNS host (A) resource records using the specific DNS
|
|
domain name and IP addresses for this adapter, contact your DNS server
|
|
or network systems administrator.
|
|
.
|
|
|
|
Messageid=11165
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_REFUSED_PRIMARY_DN
|
|
Language=English
|
|
The system failed to register host (A) 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) resource records using the specific DNS
|
|
domain name and IP addresses for this adapter, contact your DNS server
|
|
or network systems administrator.
|
|
.
|
|
|
|
Messageid=11166
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_SECURITY_PRIMARY_DN
|
|
Language=English
|
|
The system failed to register host (A) 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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11167
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_REGISTRATION_FAILED_OTHER_PRIMARY_DN
|
|
Language=English
|
|
The system failed to register host (A) 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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
;
|
|
;//
|
|
;// Deregistration update errors
|
|
;//
|
|
;
|
|
|
|
Messageid=11180
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_TIMEOUT
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11181
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_SERVERFAIL
|
|
Language=English
|
|
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
|
|
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
|
|
.
|
|
|
|
Messageid=11182
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_NOTSUPP
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11183
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_REFUSED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11184
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_SECURITY
|
|
Language=English
|
|
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
|
|
For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11185
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_OTHER
|
|
Language=English
|
|
The 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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11186
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_DEREGISTRATION_FAILED_TIMEOUT
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11187
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_DEREGISTRATION_FAILED_SERVERFAIL
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11188
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_DEREGISTRATION_FAILED_NOTSUPP
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
Messageid=11189
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_DEREGISTRATION_FAILED_REFUSED
|
|
Language=English
|
|
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 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.
|
|
.
|
|
|
|
Messageid=11190
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_DEREGISTRATION_FAILED_SECURITY
|
|
Language=English
|
|
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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11191
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_PTR_DEREGISTRATION_FAILED_OTHER
|
|
Language=English
|
|
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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11192
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_TIMEOUT_PRIMARY_DN
|
|
Language=English
|
|
The system failed to update and remove host (A) 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 A 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.
|
|
.
|
|
|
|
Messageid=11193
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_SERVERFAIL_PRIMARY_DN
|
|
Language=English
|
|
The system failed to update and remove host (A) 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 A 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.
|
|
.
|
|
|
|
Messageid=11194
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_NOTSUPP_PRIMARY_DN
|
|
Language=English
|
|
The system failed to update and remove host (A) 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 A RRs does
|
|
not currently accept DNS dynamic updates.
|
|
.
|
|
|
|
Messageid=11195
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_REFUSED_PRIMARY_DN
|
|
Language=English
|
|
The system failed to update and remove host (A) 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.
|
|
.
|
|
|
|
Messageid=11196
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_SECURITY_PRIMARY_DN
|
|
Language=English
|
|
The system failed to update and remove host (A) 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. For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
Messageid=11197
|
|
Severity=Warning
|
|
SymbolicName=EVENT_DNSAPI_DEREGISTRATION_FAILED_OTHER_PRIMARY_DN
|
|
Language=English
|
|
The system failed to update and remove host (A) 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.
|
|
For specific error code, see the record data displayed below.
|
|
.
|
|
|
|
;
|
|
;//
|
|
;// Information
|
|
;//
|
|
;
|
|
|
|
Messageid=11200
|
|
Severity=Informational
|
|
SymbolicName=EVENT_DNSAPI_REGISTERED_ADAPTER
|
|
Language=English
|
|
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
|
|
.
|
|
|
|
Messageid=11201
|
|
Severity=Informational
|
|
SymbolicName=EVENT_DNSAPI_REGISTERED_PTR
|
|
Language=English
|
|
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
|
|
.
|
|
|
|
Messageid=11202
|
|
Severity=Informational
|
|
SymbolicName=EVENT_DNSAPI_REGISTERED_ADAPTER_PRIMARY_DN
|
|
Language=English
|
|
The system registered host (A) 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
|
|
.
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// WMI Service Events (12000-12499)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
|
|
;
|
|
;//
|
|
;// Errors
|
|
;//
|
|
;
|
|
MessageId=12000
|
|
Severity=Error
|
|
SymbolicName=EVENT_WMI_CANT_OPEN_DEVICE
|
|
Language=English
|
|
The WMI service was unable to open the WMI service device. The status code is in the additional data.
|
|
.
|
|
|
|
|
|
;
|
|
;//
|
|
;// Warnings
|
|
;//
|
|
;
|
|
MessageId=12100
|
|
Severity=Warning
|
|
SymbolicName=EVENT_WMI_INVALID_MOF
|
|
Language=English
|
|
The binary MOF in the resource named %1 in the image file %2 is not valid.
|
|
.
|
|
|
|
|
|
MessageId=12101
|
|
Severity=Warning
|
|
SymbolicName=EVENT_WMI_MOF_LOAD_FAILURE
|
|
Language=English
|
|
The binary MOF in the resource named %1 in the image file %2 could not be loaded.
|
|
.
|
|
|
|
MessageId=12102
|
|
Severity=Warning
|
|
SymbolicName=EVENT_WMI_INVALID_REGINFO
|
|
Language=English
|
|
The registration information for the image file %1 is not valid.
|
|
.
|
|
|
|
MessageId=12103
|
|
Severity=Warning
|
|
SymbolicName=EVENT_WMI_INVALID_REGPATH
|
|
Language=English
|
|
The registry path (%1) passed by a kernel mode driver is invalid. The driver device object is in the additional data.
|
|
.
|
|
|
|
MessageId=12104
|
|
Severity=Warning
|
|
SymbolicName=EVENT_WMI_CANT_RESOLVE_INSTANCE
|
|
Language=English
|
|
An event was fired specifying a static instance name that could not be resolved.
|
|
.
|
|
|
|
MessageId=12105
|
|
Severity=Warning
|
|
SymbolicName=EVENT_WMI_CANT_GET_EVENT_DATA
|
|
Language=English
|
|
An error occured while attempting to query for the event data referenced by a fired event.
|
|
.
|
|
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Trk Services Events (12500-12999)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
|
|
MessageId = 12500
|
|
Severity = Error
|
|
SymbolicName = EVENT_TRK_INTERNAL_ERROR
|
|
Language = English
|
|
An internal error occured in Distributed Link Tracking. The error code was %1.
|
|
.
|
|
|
|
MessageId = 12501
|
|
Severity = Informational
|
|
SymbolicName = EVENT_TRK_SERVICE_START_SUCCESS
|
|
Language = English
|
|
Service started successfully
|
|
.
|
|
|
|
MessageId = 12502
|
|
Severity = Error
|
|
SymbolicName = EVENT_TRK_SERVICE_START_FAILURE
|
|
Language = English
|
|
Service failed to start. Error = %1
|
|
.
|
|
|
|
MessageId = 12503
|
|
Severity = Error
|
|
SymbolicName = EVENT_TRK_SERVICE_CORRUPT_LOG
|
|
Language = English
|
|
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.
|
|
.
|
|
|
|
MessageId = 12504
|
|
Severity = Warning
|
|
SymbolicName = EVENT_TRK_SERVICE_VOL_QUOTA_EXCEEDED
|
|
Language = English
|
|
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.
|
|
.
|
|
|
|
MessageId = 12505
|
|
Severity = Informational
|
|
SymbolicName = EVENT_TRK_SERVICE_VOLUME_CREATE
|
|
Language = English
|
|
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.
|
|
.
|
|
|
|
MessageId = 12506
|
|
Severity = Informational
|
|
SymbolicName = EVENT_TRK_SERVICE_VOLUME_CLAIM
|
|
Language = English
|
|
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.
|
|
.
|
|
|
|
MessageId = 12507
|
|
Severity = Informational
|
|
SymbolicName = EVENT_TRK_SERVICE_DUPLICATE_VOLIDS
|
|
Language = English
|
|
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.
|
|
.
|
|
|
|
MessageId = 12508
|
|
Severity = Warning
|
|
SymbolicName = EVENT_TRK_SERVICE_MOVE_QUOTA_EXCEEDED
|
|
Language = English
|
|
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.
|
|
.
|
|
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// ATM Protocol Events (13000-13499)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
|
|
MessageId=13100 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_VERSNOSUPP
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation Service does not support the version (1.0) supported by this LAN Emulation Client.
|
|
.
|
|
|
|
MessageId=13101 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_VERSNOSUPP
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The LAN Emulation Service does not support the version (1.0) supported by this LAN Emulation Client.
|
|
.
|
|
|
|
MessageId=13102 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_REQPARMINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The configuration parameters are incompatible with the desired Emulated LAN.
|
|
.
|
|
|
|
MessageId=13103 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_REQPARMINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The join parameters are incompatible with the desired Emulated LAN.
|
|
.
|
|
|
|
MessageId=13104 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_DUPLANDEST
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. This LAN Emulation client attempted to register a MAC address (%3) that is already in use by another client.
|
|
.
|
|
|
|
MessageId=13105 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_DUPATMADDR
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. This LAN Emulation client attempted to register an ATM address (%3) that is already in use by another client.
|
|
.
|
|
|
|
MessageId=13106 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_INSUFFRES
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation Service does not have sufficient resources to process the request.
|
|
.
|
|
|
|
MessageId=13107 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_INSUFFRES
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The LAN Emulation Service does not have sufficient resources to process the request.
|
|
.
|
|
|
|
MessageId=13108 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_NOACCESS
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation Service disallowed this request for security reasons.
|
|
.
|
|
|
|
MessageId=13109 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_NOACCESS
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The LAN Emulation Service disallowed this request for security reasons.
|
|
.
|
|
|
|
MessageId=13110 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_REQIDINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The supplied LAN Emulation Client ID is invalid.
|
|
.
|
|
|
|
MessageId=13111 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_REQIDINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The supplied LAN Emulation Client ID is invalid.
|
|
.
|
|
|
|
MessageId=13112 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_LANDESTINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The supplied MAC Address (%3) cannot be a multicast address or, on an Ethernet/802.3 Emulated LAN, a Route Descriptor.
|
|
.
|
|
|
|
MessageId=13113 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_LANDESTINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The supplied MAC Address (%3) cannot be a multicast address or, on an Ethernet/802.3 Emulated LAN, a Route Descriptor.
|
|
.
|
|
|
|
MessageId=13114 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_ATMADDRINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The supplied ATM Address (%3) is not in a recognizable format.
|
|
.
|
|
|
|
MessageId=13115 Severity=Error SymbolicName=EVENT_ATMLANE_JOINREQ_FAIL_ATMADDRINVAL
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Join Request failed. The supplied ATM Address (%3) is not in a recognizable format.
|
|
.
|
|
|
|
MessageId=13116 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_NOCONF
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation client is not recognized.
|
|
.
|
|
|
|
MessageId=13117 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_CONFERROR
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. No other information is available.
|
|
.
|
|
|
|
MessageId=13118 Severity=Error SymbolicName=EVENT_ATMLANE_CFGREQ_FAIL_INSUFFINFO
|
|
Language=English
|
|
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation client has not provided sufficient information to allow assignment to an Emulated LAN.
|
|
.
|
|
|
|
MessageId=13200 Severity=Error SymbolicName=EVENT_ATMARPS_ADDRESS_ALREADY_EXISTS
|
|
Language=English
|
|
The Local ATM address (%2) can not be used because it is already registered by another node in the network.
|
|
.
|
|
|
|
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// File Replication Service (NtFrs) Events (13500-13999)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
|
|
MessageId=13500 Severity=Error SymbolicName=EVENT_FRS_ERROR
|
|
Language=English
|
|
File Replication Service
|
|
.
|
|
|
|
MessageId=13501 Severity=Informational SymbolicName=EVENT_FRS_STARTING
|
|
Language=English
|
|
The File Replication Service is starting.
|
|
.
|
|
|
|
MessageId=13502 Severity=Informational SymbolicName=EVENT_FRS_STOPPING
|
|
Language=English
|
|
The File Replication Service is stopping.
|
|
.
|
|
|
|
MessageId=13503 Severity=Informational SymbolicName=EVENT_FRS_STOPPED
|
|
Language=English
|
|
The File Replication Service has stopped.
|
|
.
|
|
|
|
MessageId=13504 Severity=Error SymbolicName=EVENT_FRS_STOPPED_FORCE
|
|
Language=English
|
|
The File Replication Service stopped without cleaning up.
|
|
.
|
|
|
|
MessageId=13505 Severity=Error SymbolicName=EVENT_FRS_STOPPED_ASSERT
|
|
Language=English
|
|
The File Replication Service has stopped after taking an assertion failure.
|
|
.
|
|
|
|
MessageId=13506 Severity=Error SymbolicName=EVENT_FRS_ASSERT
|
|
Language=English
|
|
The 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.
|
|
.
|
|
|
|
MessageId=13507 Severity=Error SymbolicName=EVENT_FRS_VOLUME_NOT_SUPPORTED
|
|
Language=English
|
|
The File Replication Service cannot start replica set %1 on computer %2
|
|
for directory %3 because the type of volume %4 is not NTFS 5.0 or later.
|
|
%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".
|
|
.
|
|
|
|
MessageId=13508 Severity=Warning SymbolicName=EVENT_FRS_LONG_JOIN
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13509 Severity=Warning SymbolicName=EVENT_FRS_LONG_JOIN_DONE
|
|
Language=English
|
|
The File Replication Service has enabled replication from %1 to %2 for %3
|
|
after repeated retries.
|
|
.
|
|
|
|
MessageId=13510 Severity=Error SymbolicName=EVENT_FRS_CANNOT_COMMUNICATE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13511 Severity=Error SymbolicName=EVENT_FRS_DATABASE_SPACE
|
|
Language=English
|
|
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 /?".
|
|
.
|
|
|
|
MessageId=13512 Severity=Warning SymbolicName=EVENT_FRS_DISK_WRITE_CACHE_ENABLED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13513 Severity=Error SymbolicName=EVENT_FRS_JET_1414
|
|
Language=English
|
|
The 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".
|
|
.
|
|
|
|
MessageId=13514 Severity=Warning SymbolicName=EVENT_FRS_SYSVOL_NOT_READY
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13515 Severity=Warning SymbolicName=EVENT_FRS_SYSVOL_NOT_READY_PRIMARY
|
|
Language=English
|
|
The File Replication Service may be preventing the computer %1 from becoming a
|
|
domain controller while the system volume is being initialized and then
|
|
shared as SYSVOL.
|
|
%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".
|
|
.
|
|
|
|
MessageId=13516 Severity=Informational SymbolicName=EVENT_FRS_SYSVOL_READY
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13517 Severity=Warning SymbolicName=EVENT_FRS_ACCESS_CHECKS_DISABLED
|
|
Language=English
|
|
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...
|
|
.
|
|
|
|
MessageId=13518 Severity=Warning SymbolicName=EVENT_FRS_ACCESS_CHECKS_FAILED_USER
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13519 Severity=Error SymbolicName=EVENT_FRS_ACCESS_CHECKS_FAILED_UNKNOWN
|
|
Language=English
|
|
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...
|
|
.
|
|
|
|
MessageId=13520 Severity=Warning SymbolicName=EVENT_FRS_MOVED_PREEXISTING
|
|
Language=English
|
|
The 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.
|
|
.
|
|
|
|
MessageId=13521 Severity=Error SymbolicName=EVENT_FRS_CANNOT_START_BACKUP_RESTORE_IN_PROGRESS
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13522 Severity=Warning SymbolicName=EVENT_FRS_STAGING_AREA_FULL
|
|
Language=English
|
|
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".
|
|
.
|
|
|
|
MessageId=13523 Severity=Warning SymbolicName=EVENT_FRS_HUGE_FILE
|
|
Language=English
|
|
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".
|
|
.
|
|
|
|
MessageId=13524 Severity=Error SymbolicName=EVENT_FRS_CANNOT_CREATE_UUID
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13525 Severity=Warning SymbolicName=EVENT_FRS_NO_DNS_ATTRIBUTE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13526 Severity=Error SymbolicName=EVENT_FRS_NO_SID
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=13527
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_OPEN_RPC_BINDING_ERROR_SET
|
|
Language=English
|
|
The RPC binding failed in the Open function of the FileReplicaSet Object. The
|
|
counter data for this object will not be available. The FileReplicaSet object
|
|
contains the performance counters of the Replica sets whose files are being
|
|
replicated by the File Replication Service.
|
|
.
|
|
MessageId=13528
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_OPEN_RPC_BINDING_ERROR_CONN
|
|
Language=English
|
|
The RPC binding failed in the Open function of the FileReplicaConn Object. The
|
|
counter data for this object will not be available. The FileReplicaConn object
|
|
contains the performance counters of the connections over which files are being
|
|
replicated by the File Replication Service.
|
|
.
|
|
MessageId=13529
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_OPEN_RPC_CALL_ERROR_SET
|
|
Language=English
|
|
The RPC call failed in the Open function of the FileReplicaSet Object. The
|
|
counter data for this object will not be available. The FileReplicaSet object
|
|
contains the performance counters of the Replica sets whose files are being
|
|
replicated by the File Replication Service.
|
|
.
|
|
MessageId=13530
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_OPEN_RPC_CALL_ERROR_CONN
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=13531
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_COLLECT_RPC_BINDING_ERROR_SET
|
|
Language=English
|
|
The RPC binding failed in the Collect function of the FileReplicaSet Object. The
|
|
counter data for this object will not be available till the binding succeeds.
|
|
The FileReplicaSet object contains the performance counters of the Replica sets
|
|
whose files are being replicated by the File Replication Service.
|
|
.
|
|
MessageId=13532
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_COLLECT_RPC_BINDING_ERROR_CONN
|
|
Language=English
|
|
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.
|
|
.
|
|
MessageId=13533
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_COLLECT_RPC_CALL_ERROR_SET
|
|
Language=English
|
|
The RPC call failed in the Collect function of the FileReplicaSet Object. The
|
|
counter data for this object will not be available till the call succeeds. The
|
|
FileReplicaSet object contains the performance counters of the Replica sets
|
|
whose files are being replicated by the File Replication Service.
|
|
.
|
|
MessageId=13534
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_COLLECT_RPC_CALL_ERROR_CONN
|
|
Language=English
|
|
The RPC call failed in the Collect function of the FileReplicaConn Object. The
|
|
counter data for this object will not be available till the call succeeds. The
|
|
FileReplicaConn object contains the performance counters of the connections over
|
|
which files are being replicated by the File Replication Service.
|
|
.
|
|
MessageId=13535
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_VIRTUALALLOC_ERROR_SET
|
|
Language=English
|
|
The call to VirtualAlloc failed in the Open function of the FileReplicaSet
|
|
Object. The counter data for this object will not be available. The
|
|
FileReplicaSet object contains the performance counters of the Replica sets
|
|
whose files are being replicated by the File Replication Service.
|
|
.
|
|
MessageId=13536
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_VIRTUALALLOC_ERROR_CONN
|
|
Language=English
|
|
The call to VirtualAlloc failed in the Open function of the FileReplicaConn
|
|
Object. The counter data for this object will not be available. The
|
|
FileReplicaConn object contains the performance counters of the connections over
|
|
which files are being replicated by the File Replication Service.
|
|
.
|
|
MessageId=13537
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_REGISTRY_ERROR_SET
|
|
Language=English
|
|
The call to the Registry failed in the Open function of the FileReplicaSet
|
|
Object. The counter data for this object will not be available. The
|
|
FileReplicaSet object contains the performance counters of the Replica sets
|
|
whose files are being replicated by the File Replication Service.
|
|
.
|
|
MessageId=13538
|
|
Severity=Error
|
|
Facility=Application
|
|
SymbolicName=NTFRSPRF_REGISTRY_ERROR_CONN
|
|
Language=English
|
|
The call to the Registry failed in the Open function of the FileReplicaConn
|
|
Object. The counter data for this object will not be available. The
|
|
FileReplicaConn object contains the performance counters of the connections over
|
|
which files are being replicated by the File Replication Service.
|
|
.
|
|
|
|
MessageId=13539 Severity=Error SymbolicName=EVENT_FRS_ROOT_NOT_VALID
|
|
Language=English
|
|
The File Replication Service cannot replicate %1 because the
|
|
pathname of the replicated directory is not the fully qualified
|
|
pathname of an existing, accessible local directory.
|
|
.
|
|
|
|
MessageId=13540 Severity=Error SymbolicName=EVENT_FRS_STAGE_NOT_VALID
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13541 Severity=Error SymbolicName=EVENT_FRS_OVERLAPS_LOGGING
|
|
Language=English
|
|
The File Replication Service cannot replicate %1 because it overlaps
|
|
the File Replication Service's logging pathname %2.
|
|
.
|
|
|
|
MessageId=13542 Severity=Error SymbolicName=EVENT_FRS_OVERLAPS_WORKING
|
|
Language=English
|
|
The File Replication Service cannot replicate %1 because it overlaps
|
|
the File Replication Service's working directory %2.
|
|
.
|
|
|
|
MessageId=13543 Severity=Error SymbolicName=EVENT_FRS_OVERLAPS_STAGE
|
|
Language=English
|
|
The File Replication Service cannot replicate %1 because it overlaps
|
|
the staging directory %2.
|
|
.
|
|
|
|
MessageId=13544 Severity=Error SymbolicName=EVENT_FRS_OVERLAPS_ROOT
|
|
Language=English
|
|
The File Replication Service cannot replicate %1 because it overlaps
|
|
the replicating directory %2.
|
|
.
|
|
|
|
MessageId=13545 Severity=Error SymbolicName=EVENT_FRS_OVERLAPS_OTHER_STAGE
|
|
Language=English
|
|
The File Replication Service cannot replicate %1 because it overlaps
|
|
the staging directory %2 of the replicating directory %3.
|
|
.
|
|
|
|
MessageId=13546 Severity=Error SymbolicName=EVENT_FRS_PREPARE_ROOT_FAILED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13547 Severity=Warning SymbolicName=EVENT_FRS_BAD_REG_DATA
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13548 Severity=Error SymbolicName=EVENT_FRS_JOIN_FAIL_TIME_SKEW
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13549 Severity=Error SymbolicName=EVENT_FRS_RMTCO_TIME_SKEW
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13550 Severity=Error SymbolicName=EVENT_FRS_CANT_OPEN_STAGE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13551 Severity=Error SymbolicName=EVENT_FRS_CANT_OPEN_PREINSTALL
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13552 Severity=Error SymbolicName=EVENT_FRS_REPLICA_SET_CREATE_FAIL
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13553 Severity=Informational SymbolicName=EVENT_FRS_REPLICA_SET_CREATE_OK
|
|
Language=English
|
|
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"
|
|
.
|
|
|
|
MessageId=13554 Severity=Informational SymbolicName=EVENT_FRS_REPLICA_SET_CXTIONS
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13555 Severity=Error SymbolicName=EVENT_FRS_IN_ERROR_STATE
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13556 Severity=Error SymbolicName=EVENT_FRS_REPLICA_NO_ROOT_CHANGE
|
|
Language=English
|
|
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"
|
|
.
|
|
|
|
MessageId=13557 Severity=Error SymbolicName=EVENT_FRS_DUPLICATE_IN_CXTION_SYSVOL
|
|
Language=English
|
|
The 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.
|
|
.
|
|
|
|
MessageId=13558 Severity=Error SymbolicName=EVENT_FRS_DUPLICATE_IN_CXTION
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13559 Severity=Error SymbolicName=EVENT_FRS_ROOT_HAS_MOVED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13560 Severity=Warning SymbolicName=EVENT_FRS_ERROR_REPLICA_SET_DELETED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13561 Severity=Error SymbolicName=EVENT_FRS_REPLICA_IN_JRNL_WRAP_ERROR
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageId=13562 Severity=Warning SymbolicName=EVENT_FRS_DS_POLL_ERROR_SUMMARY
|
|
Language=English
|
|
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
|
|
.
|
|
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// PSCHED Events
|
|
;//
|
|
;// Codes 14000 - 14299
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
|
|
;//
|
|
;// Driver wide events (14000 - 14099)
|
|
;//
|
|
|
|
MessageID=14000 Severity=Error SymbolicName=EVENT_PS_GPC_REGISTER_FAILED
|
|
Language=English
|
|
QoS: The Packet Scheduler failed to register with the Generic Packet Classifier (msgpc.sys).
|
|
.
|
|
|
|
MessageId=14001 Severity=Error SymbolicName=EVENT_PS_NO_RESOURCES_FOR_INIT
|
|
Language=English
|
|
QoS: The Packet Scheduler was unable to allocate required resources for initialization.
|
|
.
|
|
|
|
MessageId=14002 Severity=Error SymbolicName=EVENT_PS_REGISTER_PROTOCOL_FAILED
|
|
Language=English
|
|
QoS: The Packet Scheduler failed to register as a protocol with NDIS.
|
|
.
|
|
|
|
MessageId=14003 Severity=Error SymbolicName=EVENT_PS_REGISTER_MINIPORT_FAILED
|
|
Language=English
|
|
QoS: The Packet Scheduler failed to register as a miniport with NDIS.
|
|
.
|
|
|
|
;//
|
|
;// Adapter events (14100 - 14199)
|
|
;//
|
|
|
|
MessageID=14100 Severity=Warning SymbolicName=EVENT_PS_BAD_BESTEFFORT_LIMIT
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe BestEffortLimit value set in the registry exceeds the LinkSpeed. Defaulting to Unlimited BestEffort.
|
|
.
|
|
|
|
MessageId=14101 Severity=Error SymbolicName=EVENT_PS_QUERY_OID_GEN_MAXIMUM_FRAME_SIZE
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe netcard driver failed the query for OID_GEN_MAXIMUM_FRAME_SIZE.
|
|
.
|
|
|
|
MessageId=14102 Severity=Error SymbolicName=EVENT_PS_QUERY_OID_GEN_MAXIMUM_TOTAL_SIZE
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe netcard driver failed the query for OID_GEN_MAXIMUM_TOTAL_SIZE.
|
|
.
|
|
|
|
MessageId=14103 Severity=Error SymbolicName=EVENT_PS_QUERY_OID_GEN_LINK_SPEED
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe netcard driver failed the query for OID_GEN_LINK_SPEED.
|
|
.
|
|
|
|
MessageId=14104 Severity=Error SymbolicName=EVENT_PS_BINDING_FAILED
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe Packet Scheduler failed to bind to the netcard's miniport driver.
|
|
.
|
|
|
|
MessageId=14105 Severity=Error SymbolicName=EVENT_PS_MISSING_ADAPTER_REGISTRY_DATA
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe UpperBindings key is missing from the registry.
|
|
.
|
|
|
|
MessageId=14106 Severity=Error SymbolicName=EVENT_PS_REGISTER_ADDRESS_FAMILY_FAILED
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe Packet Scheduler was unable to register with the NDISWAN Call Manager.
|
|
.
|
|
|
|
MessageId=14107 Severity=Error SymbolicName=EVENT_PS_INIT_DEVICE_FAILED
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe Packet Scheduler could not initialize the virtual miniport with NDIS.
|
|
.
|
|
|
|
MessageId=14108 Severity=Error SymbolicName=EVENT_PS_WMI_INSTANCE_NAME_FAILED
|
|
Language=English
|
|
QoS [Adapter %2]:%nThe Packet Scheduler could not obtain the adapter's friendly name from NDIS.
|
|
.
|
|
|
|
MessageId=14109 Severity=Warning SymbolicName=EVENT_PS_WAN_LIMITED_BESTEFFORT
|
|
Language=English
|
|
Qos [Adapter %2]:%nThe registry entry for BestEffortLimit is not supported over WAN links. Defaulting to Unlimited BestEffort mode.
|
|
.
|
|
|
|
MessageId=14110 Severity=Error SymbolicName=EVENT_PS_RESOURCE_POOL
|
|
Language=English
|
|
QoS [Adapter %2]:%nCould not initialize due to insufficient nonpaged pool memory.
|
|
.
|
|
|
|
MessageID=14111 Severity=Warning SymbolicName=EVENT_PS_ADMISSIONCONTROL_OVERFLOW
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
MessageID=14112 Severity=Error SymbolicName=EVENT_PS_NETWORK_ADDRESS_FAIL
|
|
Language=English
|
|
QoS [Adapter %2]:%nCould not allocate non paged pool memory for storing Network Addresses.
|
|
.
|
|
|
|
;
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// Distributed File System (Dfs) Events (14300-14599)
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;
|
|
|
|
;//
|
|
;// Server-side (dfs.sys) errors (14300-14399)
|
|
;//
|
|
|
|
MessageId=14300 Severity=Error SymbolicName=EXTRA_EXIT_POINT
|
|
Language=English
|
|
An extra ExitPoint %2 was found at server %3
|
|
.
|
|
|
|
MessageId=14301 Severity=Error SymbolicName=MISSING_EXIT_POINT
|
|
Language=English
|
|
The ExitPoint %2 was missing at server %3
|
|
.
|
|
|
|
MessageId=14302 Severity=Error SymbolicName=MISSING_VOLUME
|
|
Language=English
|
|
The Volume %2 was missing at server %3
|
|
.
|
|
|
|
MessageId=14303 Severity=Error SymbolicName=EXTRA_VOLUME
|
|
Language=English
|
|
The extra Volume %2 was found at server %3
|
|
.
|
|
|
|
MessageId=14304 Severity=Error SymbolicName=EXTRA_EXIT_POINT_DELETED
|
|
Language=English
|
|
The extra ExitPoint %2 was deleted successfully from the server %3
|
|
.
|
|
|
|
MessageId=14305 Severity=Error SymbolicName=EXTRA_EXIT_POINT_NOT_DELETED
|
|
Language=English
|
|
Unable to delete the extra ExitPoint %2 at the server %3
|
|
.
|
|
|
|
MessageId=14306 Severity=Error SymbolicName=MISSING_EXIT_POINT_CREATED
|
|
Language=English
|
|
The missing ExitPoint %2 was created at the server %3 successfully
|
|
.
|
|
|
|
MessageId=14307 Severity=Error SymbolicName=MISSING_EXIT_POINT_NOT_CREATED
|
|
Language=English
|
|
Unable to create the missing Exit Point %2 at the server %3
|
|
.
|
|
|
|
MessageId=14308 Severity=Error SymbolicName=MISSING_VOLUME_CREATED
|
|
Language=English
|
|
Successfully created the missing volume %2 knowledge at the server %3
|
|
.
|
|
|
|
MessageId=14309 Severity=Error SymbolicName=MISSING_VOLUME_NOT_CREATED
|
|
Language=English
|
|
Unable to create the missing Volume %2 info at server %3
|
|
.
|
|
|
|
MessageId=14310 Severity=Error SymbolicName=EXTRA_VOLUME_DELETED
|
|
Language=English
|
|
The extra Volume %2 info was deleted at server %3
|
|
.
|
|
|
|
MessageId=14311 Severity=Error SymbolicName=EXTRA_VOLUME_NOT_DELETED
|
|
Language=English
|
|
The extra Volume %2 info was not deleted at server %3
|
|
.
|
|
|
|
MessageId=14312 Severity=Error SymbolicName=COULD_NOT_VERIFY_VOLUMES
|
|
Language=English
|
|
Since the DC %2 was unavailable could not verify volumes knowledge.
|
|
.
|
|
|
|
MessageId=14313 Severity=Error SymbolicName=KNOWLEDGE_INCONSISTENCY_DETECTED
|
|
Language=English
|
|
Detected Knowledge inconsistency with the volume %2 at server %3
|
|
.
|
|
|
|
MessageId=14314 Severity=Error SymbolicName=PREFIX_MISMATCH
|
|
Language=English
|
|
The local Prefix %2 was represented as %3 at remote server %4
|
|
.
|
|
|
|
MessageId=14315 Severity=Error SymbolicName=PREFIX_MISMATCH_FIXED
|
|
Language=English
|
|
The remote Prefix %3 was corrected to %2 at remote server %4
|
|
.
|
|
|
|
MessageId=14316 Severity=Error SymbolicName=PREFIX_MISMATCH_NOT_FIXED
|
|
Language=English
|
|
The remote Prefix %3 was NOT corrected to %2 at remote server %4
|
|
.
|
|
|
|
MessageId=14317 Severity=Error SymbolicName=MACHINE_UNJOINED
|
|
Language=English
|
|
The machine %2 has become unlinked from the domain. Re-join the machine the machine to this domain.
|
|
.
|
|
|
|
MessageId=14318 Severity=Informational SymbolicName=DFS_REFERRAL_REQUEST
|
|
Language=English
|
|
Dfs received a referral request for "%2". The return code is in the data.
|
|
.
|
|
|
|
;//
|
|
;// Client-side Dfs (mup.sys) errors (14400-14499)
|
|
;//
|
|
|
|
MessageId=14400 Severity=Informational SymbolicName=NOT_A_DFS_PATH
|
|
Language=English
|
|
The path "%2" is not a dfs path
|
|
.
|
|
|
|
MessageId=14401 Severity=Informational SymbolicName=LM_REDIR_FAILURE
|
|
Language=English
|
|
Dfs was unable to open the Lan Redir
|
|
.
|
|
|
|
MessageId=14402 Severity=Informational SymbolicName=DFS_CONNECTION_FAILURE
|
|
Language=English
|
|
Dfs was unable to open a connection to server %2. The error returned is in the record data.
|
|
.
|
|
|
|
MessageId=14403 Severity=Informational SymbolicName=DFS_REFERRAL_FAILURE
|
|
Language=English
|
|
Dfs was unable to obtain a referral for "%2" from %3. The error returned is in the record data.
|
|
.
|
|
|
|
MessageId=14404 Severity=Informational SymbolicName=DFS_REFERRAL_SUCCESS
|
|
Language=English
|
|
Dfs obtained a referral for "%2" from %3
|
|
.
|
|
|
|
MessageId=14405 Severity=Informational SymbolicName=DFS_MAX_DNR_ATTEMPTS
|
|
Language=English
|
|
Dfs reached its limit of attempts of resolution of "%2".
|
|
.
|
|
|
|
MessageId=14406 Severity=Informational SymbolicName=DFS_SPECIAL_REFERRAL_FAILURE
|
|
Language=English
|
|
Dfs was unable to obtain the special referral table from %2. The error returned is in the record data.
|
|
.
|
|
|
|
MessageId=14407 Severity=Informational SymbolicName=DFS_OPEN_FAILURE
|
|
Language=English
|
|
Dfs failed on open of %2 directed to %3. The error returned is in the record data.
|
|
.
|
|
|
|
;//
|
|
;// Dfs service (dfssvc) errors (14500-14599)
|
|
;//
|
|
|
|
MessageId=14500 Severity=Informational SymbolicName=NET_DFS_ENUM
|
|
Language=English
|
|
NetrDfsEnum received an enumeration. The return code is in the record data.
|
|
.
|
|
|
|
MessageId=14501 Severity=Informational SymbolicName=NET_DFS_ENUMEX
|
|
Language=English
|
|
NetrDfsEnumEx received an enumeration. The return code is in the record data.
|
|
.
|
|
MessageId=14502 Severity=Error SymbolicName=DFS_ERROR_CREATE_DIRECTORY_FAILURE
|
|
Language=English
|
|
Dfs could not create directory %1. The return code is in the record data.
|
|
.
|
|
|
|
MessageId=14503 Severity=Error SymbolicName=DFS_ERROR_CREATE_REPARSEPOINT_FAILURE
|
|
Language=English
|
|
Dfs could not create reparse point for share %1 mapped to directory %2. The return code is in the record data.
|
|
.
|
|
|
|
MessageId=14504 Severity=Error SymbolicName=DFS_ERROR_UNSUPPORTED_FILESYSTEM
|
|
Language=English
|
|
Share %1 mapped to %2 does not support reparse points. Upgrade Filesystem and retry.
|
|
.
|
|
|
|
MessageId=14505 Severity=Error SymbolicName=DFS_ERROR_OVERLAPPING_DIRECTORIES
|
|
Language=English
|
|
Share %1 mapped to %2 directory overlaps an existing root. The DFS Root will not be created. The return code is in the record data.
|
|
.
|
|
|
|
MessageId=14506 Severity=Error SymbolicName=DFS_ERROR_AD_WRITE_ERROR
|
|
Language=English
|
|
DFS could not write to the Active Directory on Root %1. The return code is in the record data.
|
|
.
|
|
|
|
MessageId=14507 Severity=Error SymbolicName=DFS_ERROR_AD_READ_ERROR
|
|
Language=English
|
|
DFS could not read from the Active Directory on Root %1. The return code is in the record data.
|
|
.
|
|
|
|
MessageId=14508 Severity=Error SymbolicName=DFS_ERROR_DIRECTORY_NOT_EMPTY
|
|
Language=English
|
|
Directory %1 mapped to %2 is not empty. The directory will not be removed.
|
|
.
|
|
|
|
MessageId=14509 Severity=Error SymbolicName=DFS_ERROR_TOO_MANY_ERRORS
|
|
Language=English
|
|
Root %1 has too many errors. No further eventlogs will be logged on this root.
|
|
.
|
|
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
;//
|
|
;// BRIDGE Events
|
|
;//
|
|
;// Codes 14600 - 14899
|
|
;//
|
|
;/////////////////////////////////////////////////////////////////////////
|
|
|
|
;//
|
|
;// Driver-wide events (14600 - 14699)
|
|
;//
|
|
|
|
MessageID=14600 Severity=Error SymbolicName=EVENT_BRIDGE_PROTOCOL_REGISTER_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not be initialized because the bridge failed to register as a protocol with NDIS.
|
|
.
|
|
|
|
MessageID=14601 Severity=Error SymbolicName=EVENT_BRIDGE_MINIPROT_DEVNAME_MISSING
|
|
Language=English
|
|
Bridge: The bridge could not be initialized because the bridge's miniport device name is missing from the registry.
|
|
.
|
|
|
|
MessageID=14602 Severity=Error SymbolicName=EVENT_BRIDGE_MINIPORT_REGISTER_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not be initialized because the bridge failed to register as a miniport with NDIS.
|
|
.
|
|
|
|
MessageID=14603 Severity=Error SymbolicName=EVENT_BRIDGE_DEVICE_CREATION_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not be initialized because the bridge failed to create a device object.
|
|
.
|
|
|
|
MessageID=14604 Severity=Error SymbolicName=EVENT_BRIDGE_NO_BRIDGE_MAC_ADDR
|
|
Language=English
|
|
Bridge: The bridge could not be initialized because the bridge failed to determine a MAC address for itself.
|
|
.
|
|
|
|
MessageID=14605 Severity=Error SymbolicName=EVENT_BRIDGE_MINIPORT_INIT_FAILED
|
|
Language=English
|
|
Bridge: The bridge's attempt to create its virtual miniport failed.
|
|
.
|
|
|
|
MessageID=14606 Severity=Error SymbolicName=EVENT_BRIDGE_ETHERNET_NOT_OFFERED
|
|
Language=English
|
|
Bridge: The bridge could not initialize its miniport because Ethernet was not offered as a supported medium.
|
|
.
|
|
|
|
MessageID=14607 Severity=Error SymbolicName=EVENT_BRIDGE_THREAD_CREATION_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not initialize because it failed to create a system thread.
|
|
.
|
|
|
|
MessageID=14608 Severity=Error SymbolicName=EVENT_BRIDGE_THREAD_REF_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not initialize because it failed to reference its system thread.
|
|
.
|
|
|
|
MessageID=14609 Severity=Error SymbolicName=EVENT_BRIDGE_PACKET_POOL_CREATION_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not initialize because it failed to create a packet pool.
|
|
.
|
|
|
|
MessageID=14610 Severity=Error SymbolicName=EVENT_BRIDGE_BUFFER_POOL_CREATION_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not initialize because it failed to create a buffer pool.
|
|
.
|
|
|
|
MessageID=14611 Severity=Error SymbolicName=EVENT_BRIDGE_INIT_MALLOC_FAILED
|
|
Language=English
|
|
Bridge: The bridge could not initialize because it failed to allocate memory.
|
|
.
|
|
|
|
;//
|
|
;// Adapter-specific events (14700 - 14799)
|
|
;//
|
|
|
|
MessageID=14700 Severity=Error SymbolicName=EVENT_BRIDGE_ADAPTER_LINK_SPEED_QUERY_FAILED
|
|
Language=English
|
|
Bridge [Adapter %2]:%nThe bridge could not determine the adapter's link speed. The adapter will not be used.
|
|
.
|
|
|
|
MessageID=14701 Severity=Error SymbolicName=EVENT_BRIDGE_ADAPTER_MAC_ADDR_QUERY_FAILED
|
|
Language=English
|
|
Bridge [Adapter %2]:%nThe bridge could not determine the adapter's MAC address. The adapter will not be used.
|
|
.
|
|
|
|
MessageID=14702 Severity=Error SymbolicName=EVENT_BRIDGE_ADAPTER_FILTER_FAILED
|
|
Language=English
|
|
Bridge [Adapter %2]:%nThe bridge could not modify the adapter's packet filter. The adapter will not function correctly.
|
|
.
|
|
|
|
MessageID=14703 Severity=Error SymbolicName=EVENT_BRIDGE_ADAPTER_NAME_QUERY_FAILED
|
|
Language=English
|
|
Bridge [Adapter %2]:%nThe bridge could not retrieve the adapter's description string. The adapter will not be used.
|
|
.
|
|
|
|
MessageID=14704 Severity=Error SymbolicName=EVENT_BRIDGE_ADAPTER_BIND_FAILED
|
|
Language=English
|
|
Bridge [Adapter %2]:%nThe bridge's attempt to bind to the adapter failed. The adapter will not be used.
|
|
.
|
|
|
|
;//
|
|
;// DAV Redir Events (14800 - 14899)
|
|
;//
|
|
|
|
MessageID=14800 Severity=Warning SymbolicName=EVENT_DAV_REDIR_DELAYED_WRITE_FAILED
|
|
Language=English
|
|
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.
|
|
.
|
|
|
|
;//
|
|
;// WebClient Service Events (14900 - 14999)
|
|
;//
|
|
|
|
MessageID=14901 Severity=Warning SymbolicName=EVENT_WEBCLIENT_CLOSE_PUT_FAILED
|
|
Language=English
|
|
PUT failed for file %1 on Close. ErrorStatus: %2.
|
|
.
|
|
|
|
MessageID=14902 Severity=Warning SymbolicName=EVENT_WEBCLIENT_CLOSE_DELETE_FAILED
|
|
Language=English
|
|
DELETE failed for file %1 on Close. ErrorStatus: %2.
|
|
.
|
|
|
|
MessageID=14903 Severity=Warning SymbolicName=EVENT_WEBCLIENT_CLOSE_PROPPATCH_FAILED
|
|
Language=English
|
|
PROPPATCH failed for file %1 on Close. ErrorStatus: %2.
|
|
.
|
|
|
|
MessageID=14904 Severity=Warning SymbolicName=EVENT_WEBCLIENT_SETINFO_PROPPATCH_FAILED
|
|
Language=English
|
|
PROPPATCH failed for file %1 on SetFileInfo. ErrorStatus: %2.
|
|
.
|
|
|
|
;
|
|
;#endif // _NETEVENT
|
|
;
|
|
|