# message_table_23_0x00000409

message_identifier: 0x00000011
message_string:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer '%1'. NtpClient will try the DNS lookup again in %3 minutes. The error was: %2


message_identifier: 0x00000010
message_string:
Time Provider NtpClient: An unexpected error occurred during DNS lookup of the manually configured peer '%1'. This peer will not be used as a time source. The error was: %2


message_identifier: 0x00000013
message_string:
Logging was requested, but the time service encountered an error while trying to set up the log file: %1. The error was: %2. Please make sure that 'Local Service' has permission to write to the file or directory.


message_identifier: 0x00000012
message_string:
The time provider NtpClient failed to establish a trust relationship between this computer and the %1 domain in order to securely synchronize time. NtpClient will try again in %3 minutes. The error was: %2


message_identifier: 0x00000015
message_string:
The time service is configured to use one or more input providers, however, none of the input providers are available. The time service has no source of accurate time.


message_identifier: 0x00000014
message_string:
Logging was requested, but the time service encountered an error while trying to write to the log file: %1. The error was: %2


message_identifier: 0x00000017
message_string:
The time provider NtpServer encountered an error while digitally signing the NTP response for symmetric peer %1. NtpServer cannot provide secure (signed) time to the peer and will not send a packet. The error was: %2


message_identifier: 0x00000016
message_string:
The time provider NtpServer encountered an error while digitally signing the NTP response for peer %1. NtpServer cannot provide secure (signed) time to the client and will ignore the request. The error was: %2


message_identifier: 0x00000019
message_string:
The time provider NtpClient cannot determine whether the response received from %1 has  a valid signature. The response will be ignored. The error was: %2


message_identifier: 0x00000018
message_string:
Time Provider NtpClient: No valid response has been received from domain controller %1 after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: %2


message_identifier: 0x0000002f
message_string:
Time Provider NtpClient: No valid response has been received from manually configured peer %1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: %2


message_identifier: 0x0000002a
message_string:
The time service attempted to create a named event which was already opened. This could be the result of an attempt to compromise your system's security.


message_identifier: 0x0000002b
message_string:
The time provider '%1' returned an error when notified of a network configuration change. The error will be ignored. The error was: %2


message_identifier: 0x00000092
message_string:
The RODC has received %1 requests in the previous %2 minutes. %3 have resulted in success, and %4 have resulted in failure.


message_identifier: 0x00000024
message_string:
The time service has not synchronized the system time for %1 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization.


message_identifier: 0x00000027
message_string:
The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available.


message_identifier: 0x00000020
message_string:
The time service discovered that the system time zone information was corrupted. The time service tried to reset the system time zone to GMT, but failed. The time service cannot start. The error was: %1


message_identifier: 0x00000021
message_string:
The time service has jumped the local system clock by %1 seconds. This occurs when the time source and local system time are far enough apart that clock rate adjustments cannot be made to reach the time specified by the time source.


message_identifier: 0x00000022
message_string:
The time service has detected that the system time needs to be  changed by %1 seconds. The time service will not change the system time by more than %2 seconds. Verify that your time and time zone are correct, and that the time source %3 is working properly.


message_identifier: 0x00000029
message_string:
The time service has been configured to use one or more input providers, however, none of the input providers are still running. The time service has no source of accurate time.


message_identifier: 0x0000001a
message_string:
Time Provider NtpClient: The response received from domain controller %1 has a bad signature. The response may have been tampered with and will be ignored.


message_identifier: 0x0000001c
message_string:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are accessible. NtpClient has no source of accurate time.


message_identifier: 0x0000001b
message_string:
Time Provider NtpClient: The response received from domain controller %1 is missing the signature. The response may have been tampered with and will be ignored.


message_identifier: 0x0000001e
message_string:
The time service encountered an error while reading its configuration from the registry and cannot start. The error was: %1


message_identifier: 0x0000001d
message_string:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for %1 minutes. NtpClient has no source of accurate time.


message_identifier: 0x0000001f
message_string:
The time service discovered that the system time zone information was corrupted. Because many system components require valid time zone information, the time service has reset the system time zone to GMT. Use the Date/Time control panel to set the correct time zone.


message_identifier: 0x00000033
message_string:
Time Provider NtpClient: The time sample received from peer %1 differs from the local time by %2 seconds. The observed transmission delay from the server was %3 milliseconds.


message_identifier: 0x00000032
message_string:
The time service detected a time difference of greater than %1 milliseconds for %2 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.


message_identifier: 0x00000031
message_string:
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will continue trying to locate an AD DC every %1 minutes. This message will not be logged again until after a domain controller is found.


message_identifier: 0x00000030
message_string:
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer '%1'. NtpClient will continue to try the DNS lookup every %3 minutes. This message will not be logged again until a successful lookup of this manually configured peer occurs. The error was: %2


message_identifier: 0x00000036
message_string:
The time service encountered an error while refreshing its configuration in the registry and cannot start. The error was: %1


message_identifier: 0x00000060
message_string:
The time sample was rejected because: The peer is not synchronized, or reachability has been lost in one, or both, directions. This may also indicate that the peer has incorrectly sent an NTP request instead of an NTP response.


message_identifier: 0x00000063
message_string:
The time sample was rejected because: The peer is not synchronized, or it has been too long since the peer's last synchronization.


message_identifier: 0x00000065
message_string:
The time sample was rejected because: Packet contains unreasonable root delay or root dispersion values. This may be caused by poor network conditions.


message_identifier: 0x00000066
message_string:
Maintains date and time synchronization on all clients and servers in the network. If this service is stopped, date and time synchronization will be unavailable. If this service is disabled, any services that explicitly depend on it will fail to start.%0


message_identifier: 0x0000008c
message_string:
The time service has stopped advertising as a time source because the local machine is not an Active Directory Domain Controller.


message_identifier: 0x0000008e
message_string:
The time service has stopped advertising as a time source because the local clock is not synchronized.


message_identifier: 0x0000000b
message_string:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is not a member of a domain. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.


message_identifier: 0x0000000c
message_string:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.


message_identifier: 0x0000000a
message_string:
The time provider '%1' returned an error when asked for time samples. The error will be ignored. The error was: %2


message_identifier: 0x0000000f
message_string:
The time provider NtpClient was unable to find a domain controller to use as a time source.  NtpClient will fall back to the remaining configured time sources, if any are available. The error was: %1


message_identifier: 0x0000000d
message_string:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but the computer is joined to a Windows NT 4.0 domain. Windows NT 4.0 domain controllers do not have a time service and do not support domain hierarchy as a time source. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.


message_identifier: 0x0000000e
message_string:
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in %1 minutes.


message_identifier: 0x00000006
message_string:
The time service encountered an error while reading its configuration from the registry, and will continue running with its previous configuration. The error was: %1


message_identifier: 0x00000007
message_string:
The time provider '%1' returned an error while updating its configuration. The error will be ignored. The error was: %2


message_identifier: 0x00000008
message_string:
The time provider '%1' returned an error when notified of a polling interval change. The error will be ignored. The error was: %2


message_identifier: 0x00000009
message_string:
The time provider '%1' returned an error when notified of a time jump. The error will be ignored. The error was: %2


message_identifier: 0x00000088
message_string:
NtpClient was unable to set a manual peer to use as a time source because of an unexpected error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


message_identifier: 0x00000082
message_string:
NtpClient was unable to set a domain peer to use as a time source because of failure in establishing  a trust relationship between this computer and the '%3' domain in order to securely synchronize time. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


message_identifier: 0x00000083
message_string:
NtpClient was unable to set a domain peer to use as a time source because of DNS resolution error on '%3'. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1.


message_identifier: 0x00000081
message_string:
NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


message_identifier: 0x00000086
message_string:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on '%3'. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


message_identifier: 0x00000087
message_string:
NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '%3'. The same time source '%4' has been either specified as manual peer in NtpServer or selected as domain peer.  NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


message_identifier: 0x00000084
message_string:
NtpClient was unable to set a domain peer to use as a time source because of duplicate error on '%3'.  The same time source '%4' has been specified as manual peer in NtpServer. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


message_identifier: 0x00000085
message_string:
NtpClient was unable to set a domain peer to use a time source because of an unexpected error.  NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1


# message_table_24_0x00000409

message_identifier: 0xb0000029
message_string:
The last sleep transition was unsuccessful. This error could be caused if the system stopped responding, failed, or lost power during the sleep transition.


message_identifier: 0x00000059
message_string:
ACPI thermal zone %2 has been enumerated.
            %n_PSV = %4K
            %n_TC1 = %5
            %n_TC2 = %6
            %n_TSP = %7ms
            %n_AC0 = %8K
            %n_AC1 = %9K
            %n_AC2 = %10K
            %n_AC3 = %11K
            %n_AC4 = %12K
            %n_AC5 = %13K
            %n_AC6 = %14K
            %n_AC7 = %15K
            %n_AC8 = %16K
            %n_AC9 = %17K
            %n_CRT = %18K
            %n_HOT = %19K
            %n_PSL - see event data.


message_identifier: 0x00000058
message_string:
The system was hibernated due to a critical thermal event.%nHibernate Time = %3
            %nACPI Thermal Zone = %2
            %n_HOT = %4K


message_identifier: 0xb000003f
message_string:
The application or service %3 is attempting to update the system timer resolution to a value of %1.


message_identifier: 0x00000056
message_string:
The system was shut down due to a critical thermal event.
            %nShutdown Time = %3
            %nACPI Thermal Zone = %2
            %n_CRT = %4K


message_identifier: 0xb000004f
message_string:
Timer tick distribution policy:
            %n
            %nDisabled: %1
            %nOverridden: %2


message_identifier: 0xb0000053
message_string:
ACPI thermal zone %2 has %5 active cooling.
            %nEventTime = %3
            %n_AC0 = %6K
            %n_AC1 = %7K
            %n_AC2 = %8K
            %n_AC3 = %9K
            %n_AC4 = %10K
            %n_AC5 = %11K
            %n_AC6 = %12K
            %n_AC7 = %13K
            %n_AC8 = %14K
            %n_AC9 = %15K
            %n_TMP = %16K


message_identifier: 0xb0000051
message_string:
ACPI thermal zone %2 has %5 passive cooling.
            %nEventTime = %3
            %n_PSV = %7K
            %n_TMP = %8K
            %n_TC1 = %9
            %n_TC2 = %10
            %n_TSP = %11ms
            %nDelta P = %12
            %n_PSL - see event data.


message_identifier: 0xb001003f
message_string:
The application or service %5 is attempting to update the system timer resolution to a value of %1.


message_identifier: 0xb000005a
message_string:
Processor %1 was throttled by an entity other than the kernel power manager. %nIA32_CLOCK_MODULATION MSR = %2. %nElapsed time since last event logged = %3s. %nLog interval = %4 events.


message_identifier: 0x00000029
message_string:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


# message_table_26_0x00000409

message_identifier: 0x000003f9
message_string:
The disk space needed to install language pack %1 exceeds the available free disk space. Please free up some space before trying to install again.


message_identifier: 0x000003f8
message_string:
The language pack for %1 cannot be installed because its parent language %2 is not installed. Please install the parent language pack before installing this language pack.


message_identifier: 0x000003f7
message_string:
The language pack version for %1 does not match your current system. Please download the appropriate language pack that matches the version of your system.


message_identifier: 0x000003f6
message_string:
The language pack for %1 is not applicable for this system. Please download the appropriate language pack that targets your system's architecture and SKU.


message_identifier: 0x000003f4
message_string:
The user does not have admin privilege. Please run this command using a user account with admin privilege.


message_identifier: 0x000003f3
message_string:
Failed to start language pack setup wizard because the system is pending reboot. Please restart the system and try running lpksetup again.


message_identifier: 0x000003f0
message_string:
The file %1 is not a valid Language Pack. The language pack might be corrupted. Last error: %2. Please download the language pack file again.


message_identifier: 0xb000138a
message_string:
The OnUILanguageClear callback was called with new language %1, previous language %2 and flags %3. Return value: %4.


message_identifier: 0xb000138b
message_string:
The OnMachineUILanguageInit callback was called with new language %1, previous language %2 and flags %3. Return value: %4.


message_identifier: 0xb000138c
message_string:
The OnMachineUILanguageSwitch callback was called with new language %1, previous language %2 and flags %3. Return value: %4.


message_identifier: 0xb00107d3
message_string:
The call to notify NotifyUILanguageChange that system UI language is changed from %1 to %2 failed with error %3.  To manually evoke the callback, please use the Regional and Language options control panel to change the system UI language back to its original value and then change it to the desired value again.


message_identifier: 0xb0001388
message_string:
The OnUILanguageAdd callback was called with new language %1, previous language %2 and flags %3. Return value: %4.


message_identifier: 0xb0001389
message_string:
The OnUILanguageRemove callback was called with new language %1, previous language %2 and flags %3. Return value: %4.


message_identifier: 0x30000029
message_string:
Notify the system that the system UI language setting has been changed by calling the NotifyUILanguage


message_identifier: 0x30000027
message_string:
Notify the system that the current User's User UI language setting has been changed by calling the NotifyUILanguage


message_identifier: 0xb0000fa5
message_string:
Maximum run attempt limit for a session (boot) reached. Next run will be attempted on after machine reboots.


message_identifier: 0xb0000fa7
message_string:
LanguageCommitted value isn't set under System\CurrentControlSet\Control\MUI\UILanguages.(lpremove is terminating)


message_identifier: 0xb0000fa6
message_string:
Maximum run attempt limit for overall amoutn of machine boots reached. Lpremove won't run again. This is error situation meaning all prior runs have failed


message_identifier: 0x000003ee
message_string:
The language name %1 is invalid, or does not correspond to a supported language.  Please specify the language pack to install using a valid language name format, such as en-US, and ensure that the specifier corresponds to a supported language.


message_identifier: 0xb00007d3
message_string:
The call to NotifyUILanguageChange to change Machine UI language from %1 to %2 failed with error %3


message_identifier: 0x000003e9
message_string:
Failed to start language pack setup wizard. Please restart the system and try running the wizard again.


message_identifier: 0x00000411
message_string:
You cannot uninstall language %1 because the language is the parent language of language %2. Please uninstall the dependent language first.


message_identifier: 0xb00007db
message_string:
The call to notify NotifyUILanguageChange that a new language %1 has been installed has failed with error %2. To manually evoke the callback, you have to uninstall the language pack and reinstall it again.


message_identifier: 0x00000424
message_string:
Failed to change user UI language from %1 to %2. Please go to Regional and Language options control panel to change the user UI language.


message_identifier: 0x00000425
message_string:
Failed to change system UI language from %1 to %2. Please go to Regional and Language options control panel to change the system UI language.


# message_table_28_0x00000409

message_identifier: 0x00001001
message_string:
Display driver %1 detected and recovered from a failure. Some graphics operations may have failed.


message_identifier: 0x00001003
message_string:
Display driver %1 stopped responding. Save your work and reboot the system to restore full display functionality. The next time you reboot the machine, a dialog will be displayed giving you a chance to upload data about this failure to Microsoft.


message_identifier: 0x00001007
message_string:
At least one display adapter on the system has been disabled because its driver is not compatible with the driver for the VGA adapter.


# message_table_29_0x00000409

message_identifier: 0xc00503eb
message_string:
The IPMI device driver attempted to communicate with the IPMI BMC device during device creation. However the communication failed due to a timeout. Either the configured timeouts are too small and the IPMI BMC device responses take longer than the timeouts or the BMC has a technical fault. You can increase the timeouts associated with the IPMI device driver or seek assistance from the BMC device manufacturer.


message_identifier: 0xc00503e8
message_string:
During communication with the IPMI BMC device, the system detected that the BMC entered an error state. The driver attempted to set the BMC state to a working state but failed to do so. After 20 successive attempts, the driver has set the IPMI device to a non working state. It is recommended that you seek assistance from the BMC device manufacturer. You can return the device instance to the working state by disabling and enabling the IPMI device instance labeled æIPMI Device DriverÆ. You can locate the IPMI device instance within the Device Manager user interface.


message_identifier: 0xc00503e9
message_string:
The IPMI device driver attempted to determine if the system supported an IPMI BMC device. The driver attempted to detect the presence of the IPMI BMC by searching the SMBIOS for a Type38 record.  But either no record was found or the record was not compatible with the version of the device driver. If a SMBIOS Type 38 record was detected, the Dump Data field of the event contains a binary representation of the record.


message_identifier: 0x800503ec
message_string:
The IPMI device driver attempted to communicate with the IPMI BMC device during normal operation. However the communication failed due to a timeout. You can increase the timeouts associated with the IPMI device driver.


message_identifier: 0x800503ea
message_string:
The IPMI device driver read an administrator supplied parameter that is invalid. The device driver will use a system defined default value in its place.


# message_table_30_0x00000409

message_identifier: 0xb0001388
message_string:
IPHTTPS: InterfaceName:%1 InterfaceType:%2 RegistryState:%3 CurrentState:%4 URL:%5 AuthenticationMode:%6


message_identifier: 0xb0001398
message_string:
IPHTTPS: Global connectivity state change. GlobalAddressCount = %1 Ipv4Connectivity = %2 Ipv6Connectivity = %3 CorpConnectivity = %4


message_identifier: 0x01000fa2
message_string:
Teredo server primary or secondary IPv4 address is invalid. Primary IPv4 address: %1. Error Code: %2.


message_identifier: 0xb0000fd9
message_string:
Starting Teredo Offload with: %nLocalV6:%3 RemoteV6:%4 %nLocalV4:%5 RemoteV4:%6 %nLocalPort:%7 RemotePort:%8.


message_identifier: 0xb0001047
message_string:
%1:Change notification for compartment %2, HaveGlobalIPv6Address = %3, ICS Enabled =  %4, GlobalIPv4AddressCount = %5.


message_identifier: 0xb0001044
message_string:
6to4: Configuring interface %1 with following parameters:%nICS PrivateInterface = %2 AdvertiseDefaultRoute = %3 Advertises = %4 Forwards = %5 NTStatus = %6.


# message_table_31_0x00000409

message_identifier: 0xc0001b6b
message_string:
The %1 service depends on a service in a group which starts later. Change the order in the service dependency tree to ensure that all services required to start this service are starting before this service is started.


message_identifier: 0xc0001b6c
message_string:
The %1 service depends on a group which starts later. Change the order in the service dependency tree to ensure that all services required to start this service are starting before this service is started.


message_identifier: 0x80001b7f
message_string:
A service process other than the one launched by the Service Control Manager connected when starting the %1 service.  The Service Control Manager launched process %2 and process %3 connected instead.%n%n  Note that if this service is configured to start under a debugger, this behavior is expected.


message_identifier: 0x40001b85
message_string:
A service was installed in the system.%n%nService Name:  %1%nService File Name:  %2%nService Type:  %3%nService Start Type:  %4%nService Account:  %5


message_identifier: 0x40001b82
message_string:
The %1 service was successfully sent a %2 control.%n%n The reason specified was: %3 [%4]%n%n Comment: %5


message_identifier: 0xc0001b73
message_string:
Windows could not be started as configured. Starting Windows using a previous working configuration.


message_identifier: 0xc0001b81
message_string:
The %1 service was unable to log on as %2 with the currently configured password due to the following error: %nLogon failure: the user has not been granted the requested logon type at this computer.%n %nService: %1 %nDomain and account: %2%n %nThis service account does not have the required user right "Log on as a service."%n %nUser Action%n %nAssign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.%n %nIf you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.


message_identifier: 0xc0001b7e
message_string:
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).


message_identifier: 0xc0001b7d
message_string:
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).


message_identifier: 0xc0001b63
message_string:
A timeout (%1 milliseconds) was reached while waiting for a transaction response from the %2 service.


message_identifier: 0x80001b84
message_string:
The following service is taking more than %2 minutes to start and may have stopped responding: %1%n%nContact your system administrator or service vendor for approximate startup times for this service.%n%nIf you think this service might be slowing system response or logon time, talk to your system administrator about whether the service should be disabled until the problem is identified.%n%nYou may have to restart the computer in safe mode before you can disable the service.


# message_table_32_0x00000409

message_identifier: 0x40000fa2
message_string:
The logon hours restriction policy is applied to the logged on user. The user's session has been locked, disconnected or logged off depending on the policy setting. User Name: %1 Domain Name: %2


message_identifier: 0x80000fa6
message_string:
The Windows logon process has failed to spawn a user application. Application name: %1. Command line parameters: %2.


message_identifier: 0x80001773
message_string:
The winlogon notification subscriber <%1> was unavailable to handle a critical notification event.


message_identifier: 0x80001776
message_string:
The winlogon notification subscriber <%1> took %2 second(s) to handle the notification event (%3).


message_identifier: 0x80001775
message_string:
The winlogon notification subscriber <%1> is taking long time to handle the notification event (%2).


# message_table_33_0x00000409

message_identifier: 0x00000011
message_string:
Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions: %1


message_identifier: 0x00000010
message_string:
Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.


message_identifier: 0x00000012
message_string:
Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on %1 at %2: %3


message_identifier: 0x00000015
message_string:
Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates: %1


message_identifier: 0x00000016
message_string:
Restart Required: To complete the installation of the following updates, the computer will be restarted within %1 minutes: %2


message_identifier: 0x00000021
message_string:
Windows Update was unable to connect to proxy server %1 because valid credentials (user name and password) were required, but were either not available or were incorrect. Please check your proxy credentials, and then try searching again for updates.


# message_table_34_0x00000409

message_identifier: 0xb0000025
message_string:
Server application is attempting to receive the SSL client certificate, which will be provided if available. If the client certificate is not available, a renegotiation will be initiated.


message_identifier: 0x40003aa7
message_string:
Unable to convert all entries on IP Listen-Only list.  Driver will listen on all available interfaces.


message_identifier: 0xb0000034
message_string:
Parsing of request (request ID %2) failed due to reason: %3. Request may not be compliant with HTTP/1.1.


message_identifier: 0xc0003aa2
message_string:
An error occured while initializing namespace reservation identified by URL prefix %2.  The error status code is contained within the returned data.


message_identifier: 0xc0003aa8
message_string:
Unable to initialize the security package %2 for server side authentication.  The data field contains the error number.


message_identifier: 0xc0003aa9
message_string:
Unable to create the centralized W3C log file. Make sure that the logging directory is correct and this computer has write access to that directory.


message_identifier: 0xb000002b
message_string:
Attempt (on connection ID %1) to authenticate client completed. Authentication type %2. Security status: %3.


message_identifier: 0xb000002e
message_string:
Successfully associated QoS flow with connection (connection ID %1). Bandwidth throttled to: %2 Bytes per second.


message_identifier: 0xc0003aad
message_string:
An error occured while using SSL configuration for socket address %2.  The error status code is contained within the returned data.


message_identifier: 0xb0000004
message_string:
Server application passed response (request ID %1, connection ID %2, method %4, header length %5, number of entity chunks %6, cache policy %7) with status code %3.


message_identifier: 0xb0000003
message_string:
Delivered request to server application (request pointer %1, request ID %2, site ID %3) from request queue %4 for URI %5 with status %6.


message_identifier: 0xb0010010
message_string:
Response (request pointer %1, corresponding to request ID %4, site ID %2, number of bytes %3, endoding %5) queued for sending from the cache.


message_identifier: 0xb0010011
message_string:
Response (request pointer %1, site ID %2, number of bytes %3, encoding %5) queued for sending with status code 304 (cache not modified).


message_identifier: 0xb000000d
message_string:
Response sent (corresponding to request ID %1) with status code %2. If disconnect is required, a TCP FIN has been sent.


message_identifier: 0xb000000e
message_string:
Error occurred while sending the last response (corresponding to request ID %1) with status code %2. A TCP Reset has been sent.


message_identifier: 0xc0003a9a
message_string:
Unable to write to the log file %2 for site W3SVC%3. Disk may be full. If this is a network path, make sure that network connectivity is not broken.


message_identifier: 0xb0000018
message_string:
Connection (connection pointer %1) cleanup started due to either the sending of a TCP Reset, receiving of a TCP Reset, or after the mutual exchange of TCP Fins.


message_identifier: 0xb0000011
message_string:
Response (request pointer %1, site ID %2, number of bytes %3) queued for sending with status code 304 (cache not modified).


message_identifier: 0xc0003a9d
message_string:
Unable to bind to the underlying transport for %2. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.


message_identifier: 0xc0003a9e
message_string:
Owner of the log file or directory %2 is invalid. This could be because another user has already created the log file or the directory.


message_identifier: 0xc0003a98
message_string:
Unable to create log file %2. Make sure that the logging directory is correct and this computer has write access to that directory.


message_identifier: 0xc0003a99
message_string:
Unable to create the log file for site W3SVC%2. Make sure that the logging directory for the site is correct and this computer has write access to that directory.


message_identifier: 0xc0003a9b
message_string:
Unable to create the centralized binary log file. Make sure that the logging directory is correct and this computer has write access to that directory.


message_identifier: 0xc0003a9c
message_string:
Unable to write to the centralized binary log file %2. Disk may be full. If this is a network path, make sure that network connectivity is not broken.


message_identifier: 0xc0003aa4
message_string:
Unable to write to the error log file. Disk may be full. The data field contains the error number.


message_identifier: 0xc0003aa1
message_string:
An error occured while initializing namespace reservations.  The error status code is contained within the returned data.


message_identifier: 0xb000004d
message_string:
Cached slices match content. Req. %1, CacheEntry %2, slices %3 (%4,%5,...), ranges %6 (%7-%8, %9-%10,...)


message_identifier: 0xc0003aaa
message_string:
Unable to write to the centralized W3C log file %2. Disk may be full. If this is a network path, make sure that network connectivity is not broken.


# message_table_35_0x00000409

message_identifier: 0x0100000c
message_string:
The crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error.


# message_table_36_0x00000409

message_identifier: 0xb0000019
message_string:
Remote Desktop Services: Session reconnection succeeded:%n%nUser: %1%nSession ID: %2%nSource Network Address: %3


message_identifier: 0xb0000018
message_string:
Remote Desktop Services: Session has been disconnected:%n%nUser: %1%nSession ID: %2%nSource Network Address: %3


message_identifier: 0xb0000013
message_string:
Registering with Service Control Manager to monitor Remote Desktop Service status failed with %1, retry in ten minutes.


message_identifier: 0xb0000016
message_string:
Remote Desktop Services: Shell start notification received:%n%nUser: %1%nSession ID: %2%nSource Network Address: %3


message_identifier: 0xb0000015
message_string:
Remote Desktop Services: Session logon succeeded:%n%nUser: %1%nSession ID: %2%nSource Network Address: %3


# message_table_37_0x00000409

message_identifier: 0xb0000834
message_string:
Network Diagnostics Framework stopped because it completed the user initiated diagnostics session. %n%nResult: Success, problems repaired. [%1]


message_identifier: 0xb0000898
message_string:
Network Diagnostics Framework stopped because it completed the user initiated diagnostics session. %n%nResult: Failed during diagnosis. [%1]


message_identifier: 0xb00008fc
message_string:
Network Diagnostics Framework stopped because it completed the user initiated diagnostics session. %n%nResult: Failed during repair. [%1]


message_identifier: 0x00001068
message_string:
An error occurred. The Network Diagnostics Framework failed to complete the diagnosis phase of operation. A Windows Error Report was generated. [%1]


message_identifier: 0xb00009c4
message_string:
Network Diagnostics Framework stopped because it completed the user initiated diagnostics session. %n%nResult: Cancelled during repair. [%1]


message_identifier: 0x00001450
message_string:
The Network Diagnostics Framework failed to execute the following repair: %n%nRepair option: %3 %n%nRepairGuid: %4


message_identifier: 0xb0000bb8
message_string:
An error occurred. The Network Diagnostics Framework failed to complete operation. A Windows Error Report was generated. [%1].


message_identifier: 0x00000fa0
message_string:
The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered: %n%nHelper Class Name: %7%n%nRoot Cause: %1 %n%nRoot Cause Guid: %2 %n%nRepair option: %3 %n%nRepairGuid: %4 %n%nSeconds required for repair: %5 %n%nSecurity context required for repair: %6%n%nInterface: %8 (%9)


message_identifier: 0x00001388
message_string:
The Network Diagnostics Framework has completed the repair phase of operation. The following repair option or work-around was executed: %n%nHelper Class Name: %7 %n%nRepair option: %3 %n%nRepairGuid: %4 %n%nThe repair option appears to have successfully fixed the diagnosed problem.


message_identifier: 0x000014b4
message_string:
An error occurred. The Network Diagnostics Framework failed to complete the repair phase of operation. A Windows Error Report was generated. [%1]


message_identifier: 0xb00007d0
message_string:
Network Diagnostics Framework stopped because it completed the user initiated diagnostics session. %n%nResult: Success, no problems found. [%1]


message_identifier: 0xb0000960
message_string:
Network Diagnostics Framework stopped because it completed the user initiated diagnostics session. %n%nResult: Cancelled during diagnosis. [%1]


message_identifier: 0xb00003e8
message_string:
Network Diagnostics Framework started because the user requested a diagnostics session. %n%nHelper Class Name: %1 %n%nNumber of parameters: %2 %n%nAttributes passed to helper class: %n%3


message_identifier: 0x00001004
message_string:
The Network Diagnostics Framework has completed the diagnosis phase of operation, but no network problem was identified.


message_identifier: 0x000013ec
message_string:
The Network Diagnostics Framework (NDF) has completed the repair phase of operation. The following repair option or work-around was executed: %n%nHelper Class Name: %7 %n%nRepair option: %3 %n%nRepairGuid: %4 %n%nThe repair option appears to have successfully fixed the diagnosed problem. But NDF has detected the existence of other network problems. NDF should be re-run to diagnose these problems.


# message_table_38_0x00000409

message_identifier: 0x0000c363
message_string:
The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM


message_identifier: 0x0000c360
message_string:
Another routing protocol component has already been enabled on this interface.  Only one routing protocol component may be  enabled on an interface at any time.


message_identifier: 0x0000c35d
message_string:
The protocol component that is attempting to deregister is currently enabled on one or more interfaces.


message_identifier: 0x0000c359
message_string:
IPMGM could not schedule a task to be executed. This may have been caused by a memory allocation failure. The data is the error code.


# message_table_39_0x00000409

message_identifier: 0x80000bbc
message_string:
Windows start-up process has failed to synchronize with the local security subsystem during setup.


message_identifier: 0x0000000b
message_string:
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.


# message_table_41_0x00000409

message_identifier: 0x00000201
message_string:
BitLocker Drive Encryption recovery information was backed up successfully to Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2


message_identifier: 0x00000202
message_string:
Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services.%nErrorcode: %2%nProtector GUID: %1%nVolume GUID: %3


message_identifier: 0x00000203
message_string:
BitLocker Drive Encryption recovery information for the specified protector is already present in Active Directory Domain Services.%nProtector GUID: %1%nVolume GUID: %2


message_identifier: 0x00000204
message_string:
A BitLocker certificate data recovery agent was created, because it was missing on the volume or added to the list of data recovery agents.%nCertificate thumbprint: %1%nProtector GUID: %2%nVolume GUID: %3


message_identifier: 0x00000205
message_string:
A BitLocker certificate data recovery agent was removed, because is no longer in the list of data recovery agents.%nCertificate thumbprint: %1%nProtector GUID: %2%nVolume GUID: %3


message_identifier: 0x00000206
message_string:
The attempt to create a data recovery agent protector on the BitLocker volume failed.%nErrorcode: %1%nCertificate thumbprint: %2%nVolume GUID: %3


message_identifier: 0x00000208
message_string:
The management of the data recovery agents failed on this drive because this feature of BitLocker Drive Encryption is not supported. To enable this functionality, upgrade your operating system to Windows 7 Enterprise. %nErrorcode: %1%nVolume GUID: %2


# message_table_42_0x00000409

message_identifier: 0xb0000004
message_string:
Windows Disk Diagnostic attempted to schedule interactive recovery for a S.M.A.R.T. fault but encountered an error.  The error code was %1.


message_identifier: 0xb0000005
message_string:
Windows Disk Diagnostic detected a S.M.A.R.T. fault on disk %1 (volumes %2; hardware id %3). However, as this disk is known to report false errors, Windows Disk Diagnostic ignored this event and exited silently.


message_identifier: 0xb0000002
message_string:
Windows Disk Diagnostic was invoked for a S.M.A.R.T. fault, but no new faults were detected.  The diagnostic will exit without performing any corrective action.


message_identifier: 0xb2000004
message_string:
Windows Disk Diagnostic Resolver is exiting because the user requested suppression of any S.M.A.R.T. faults that were detected.


message_identifier: 0xb2000005
message_string:
Windows Disk Diagnostic Resolver is exiting because no S.M.A.R.T. faults were detected on this computer.


message_identifier: 0xb1000003
message_string:
Windows Disk Diagnostic Data Collection will be cancelled because the CEIP policy was not configured and the data collection retry limit has been reached.


message_identifier: 0xb1000002
message_string:
Windows Disk Diagnostic Data Collection will be deferred because the CEIP policy was not configured.


message_identifier: 0x00000001
message_string:
Windows Disk Diagnostic detected a S.M.A.R.T. fault on disk %1 (volumes %2).  This disk might fail; back up your computer now. All data on the hard disk, including files, documents, pictures, programs, and settings might be lost if your hard disk fails.  To determine if the hard disk needs to be repaired or replaced, contact the manufacturer of your computer.  If you can't back up (for example, you have no CDs or other backup media), you should shut down your computer and restart when you have backup media available.  In the meantime, do not save any critical files to this disk.


# message_table_44_0x00000409

message_identifier: 0xb000cb32
message_string:
The DHCP Quarantine Enforcement Client could not bind to the Quarantine Agent. The following error occured %1.


message_identifier: 0xb000cb34
message_string:
The network connection corresponding to the Network Card with address %1 was removed from a previously assigned quarantine configuration by the DHCP Quarantine Enforcement Client.


message_identifier: 0xb000cb33
message_string:
The network connection corresponding to the Network Card with address %1 was assigned quarantine configuration by the DHCP Quarantine Enforcement Client.


# message_table_45_0x00000409

message_identifier: 0xb0000330
message_string:
The print spooler service detected an invalid RPC protocol sequence %1, expecting %2, error code %3.


message_identifier: 0xb0000331
message_string:
The RPC end-point policy for the print spooler service is disabled. See the event user data for context information.


message_identifier: 0xb0000143
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler could not create or update the print queue because Windows failed to bind to container: %1.  Error: %2. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb000016f
message_string:
Windows could not initialize printer %1 because the print processor %2 could not be found. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.


message_identifier: 0xb0000145
message_string:
While attempting to remove the printer from the Active Directory directory service, Windows failed to delete print queue %1 at %2.  Error: %3


message_identifier: 0xb0000329
message_string:
The print spooler failed to recursively delete the directory %1, error code %2. See the event user data for context information.


message_identifier: 0xb0000147
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler could not create print queue %1 under container %2 because Mandatory properties could not be set.  Error: %3. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb0000146
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler could not create or update the print queue under container %1.  Error: %2. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb0000149
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: %1. This can occur if DNS cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb00000d9
message_string:
A printer setup operation failed during the installation process, error code %5, HRESULT %6. See the event user data for context information.


message_identifier: 0xb000034c
message_string:
The print spooler selected the isolation mode %1 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox) for printer %2, printer driver %3.


message_identifier: 0xb000034b
message_string:
The print spooler service recorded %1 successful and %2 failed RPC requests for all active print driver sandbox hosts.


message_identifier: 0xb000034a
message_string:
The print job %1 was sent through the print processor %2 on printer %3, driver %4, in the isolation mode %5 (0 - loaded in the spooler, 1 - loaded in shared sandbox, 2 - loaded in isolated sandbox). Win32 error code returned by the print processor: %6.


message_identifier: 0xb000034f
message_string:
Cached printer %1 has been scheduled for deletion due to a logon scavenging operation. This printer is no longer referenced in the registry.


message_identifier: 0xb000034e
message_string:
Cached printer %1 has been scavenged and deleted. This printer's age (%2 seconds) has surpassed the expiry age of %3 seconds.


message_identifier: 0xb0000205
message_string:
Group Policy was unable to update per computer printer connection %1. Error code %2. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry updating the printer connection.


message_identifier: 0xb0000336
message_string:
Unknown print processor (%1) or invalid data type (%4), error %7, Client Side Rendering is disabled. See the event user data for more context information.


message_identifier: 0xb0000334
message_string:
Client side rendering to %1 failed, error code %4. The print spooler service will retry server side rendering. See the event user data for more context information.


message_identifier: 0xb0000335
message_string:
The print spooler Client Side Rendering is attempting to render the job %1 on the server (Server Side Rendering), status %3. See the event user data for context information.


message_identifier: 0xb0000332
message_string:
The print spooler RPC server failed to start, error code %1. See the event user data for context information.


message_identifier: 0xb0000151
message_string:
The print queue could not be found on domain %1.  It may have been deleted from the Active Directory directory service. Windows will attempt to republish the print queue.  Error: %2


message_identifier: 0xb0000206
message_string:
Group Policy was unable to delete the per user printer connection %1. Error code %2. The printer connection is still available to users on this computer. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry deleting the printer connection.


message_identifier: 0xb0000338
message_string:
A fatal error occurred while printing job %1, id %2 on the print queue %3. The print filter pipeline process was terminated. Error information: %4.


message_identifier: 0xb0000339
message_string:
Client side rendering to %1 failed, error code %4. The print spooler service will not retry server side rendering. See the event user data for more context information.


message_identifier: 0xb000007d
message_string:
Ending page job %3 at printer %4 failed, error code %2. See the event user data for context information.


message_identifier: 0xb0000156
message_string:
The print spooler removed print queue %1 from the Active Directory directory service because it does not have a Universal Naming Convention (UNC) name or server name listed. No user action is required.


message_identifier: 0xb000015c
message_string:
This version of %1 is incompatible with this version of Windows. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.


message_identifier: 0xb00001f9
message_string:
Failed to create Phase2Init event in WaitForSpoolerInitialization: Error %2. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb000032d
message_string:
The print spooler failed to copy the file %1 to %2, error code %4. See the event user data for context information.


message_identifier: 0xb0000152
message_string:
Printer %1 was successfully removed from the Active Directory directory service. The printer can no longer be located by searching Active Directory. No user action is required.


message_identifier: 0xb0000203
message_string:
Group Policy was unable to delete per computer printer connection %1. Error %2. The printer connection is still available to users on this computer. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry deleting the printer connection.


message_identifier: 0xb000025b
message_string:
The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key %1. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.


message_identifier: 0xb00001f7
message_string:
The system failed to initialize the local print provider: Error %2. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb0000150
message_string:
Print queue %1 was successfully updated in the Active Directory directory service container %2. No user action is required.


message_identifier: 0xb0000157
message_string:
The print spooler was unable to connect to print queue %1 based on the information published in the Active Directory. Error %2. No user action is required. If this print queue continues to be unreachable it may be removed from Active Directory.


message_identifier: 0xb000014c
message_string:
The printer was successfully published to the Active Directory directory service. The print queue %1 was successfully created in container %2. No user action is required.


message_identifier: 0xb0000148
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the primary domain query failed. Error: %1. This can occur if Domain Name System (DNS) cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb0000328
message_string:
The print spooler failed to load a plug-in module %1, error code %2. See the event user data for context information.


message_identifier: 0xb000012d
message_string:
Printer %1 was deleted, and users will no longer be able to print to this printer. No user action is required.


message_identifier: 0xb000032c
message_string:
The print spooler failed to delete the file %1, error code %4. See the event user data for context information.


message_identifier: 0xb000032b
message_string:
The print spooler failed to move the file %1 to %2, error code %4. See the event user data for context information.


message_identifier: 0xb0000133
message_string:
Document %1, %2 owned by %3 on %4 was printed on %5 through port %6.  Size in bytes: %7. Pages printed: %8. No user action is required.


message_identifier: 0xb0000134
message_string:
Document %1, %2 owned by %3 was paused on %4. This document will not print until the document owner resumes the print job. No user action is required.


message_identifier: 0xb0000137
message_string:
An administrator moved document %1, %2 owned by %3 to position %4 on %5. This changes when the document will print. No user action is required.


message_identifier: 0xb0000158
message_string:
The print spooler removed print queue %1 from the Active Directory directory service. No user action is required.


message_identifier: 0xb0000159
message_string:
The print spooler removed print queue %1 from the Active Directory directory service because it is a duplicate of another print queue. No user action is required.


message_identifier: 0xb0000162
message_string:
%1 initialization failed at %2. Error: %3. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb0000259
message_string:
The print spooler failed to download and import the printer driver from %1 into the driver store for driver %2. Error code= %3.


message_identifier: 0xb0000258
message_string:
The print spooler failed to import the printer driver that was downloaded from %1 into the driver store for driver %2. Error code= %3. This can occur if there is a problem with the driver or the digital signature of the driver.


message_identifier: 0xb000015f
message_string:
The attempt for %1 to use a Windows NT 4.0 (kernel mode) driver failed because this version of Windows does not support Windows NT 4.0 printer drivers. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.


message_identifier: 0xb000032a
message_string:
The print spooler failed to delete the directory %1 and the contained files, error code %2. See the event user data for context information.


message_identifier: 0xb00002bf
message_string:
The print filter pipeline host is shutting down due to an error in signaling the Component Object Model (COM) proxy in the spooler. Error %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00001fc
message_string:
Failed to initialize the router cache: Error %2. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00001fb
message_string:
The system failed to initialize the name cache: Error %2. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00001fe
message_string:
InitializeProvider cannot allocate memory for %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00001fd
message_string:
The print spooler cannot start because the PrinterBusEnumerator could not start. Error code %2. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb000013a
message_string:
Document %1, %2 owned by %3 timed out while printing on %4. The spooler waited for %5 milliseconds and no data was received.


message_identifier: 0xb000013b
message_string:
The print spooler failed to share printer %2 with shared resource name %3. Error %1. The printer cannot be used by others on the network.


message_identifier: 0xb000013e
message_string:
Failed to upgrade printer settings for printer %1 driver %2. Error: %3. The device settings for the printer are set to those configured by the manufacturer.


message_identifier: 0xb000013f
message_string:
Printer %1 failed to initialize because a suitable %2 driver could not be found. The new printer settings that you specified have not taken effect. Install or reinstall the printer driver. You might need to contact the vendor for an updated driver.


message_identifier: 0xb0000063
message_string:
The print spooler encountered a fatal error while executing a critical operation (%1, error %2) and must immediately terminate. Try to manually restart the print spooler service (from Control Panel | Administrative Tools | Services or from an elevated command prompt running: net start spooler).


message_identifier: 0xb0000354
message_string:
Driver %1 could not be installed for printer connection %3. The print system selected the replacement driver %2 for the printer connection. No user action is required.


message_identifier: 0xb0000140
message_string:
Printer %1 failed to initialize because none of its ports (%2) could be found. This can occur if the ports were deleted or the port information is invalid.


message_identifier: 0xb00000d4
message_string:
Parsing inf (%4) for printer driver %5 succeeded (processor architecture %7). See the event user data for context information.


message_identifier: 0xb00000d5
message_string:
Parsing inf (%4) for printer driver %5 failed (processor architecture %7), error code %8, HRESULT %9. See the event user data for context information.


message_identifier: 0xb00000d7
message_string:
Installing printer driver %5 failed, error code %10, HRESULT %11. See the event user data for context information.


message_identifier: 0xb00000d8
message_string:
A printer setup operation succeeded during the installation process. See the event user data for context information.


message_identifier: 0xb000006b
message_string:
Starting document job %3 for printer %4 failed, error code %2. See the event user data for context information.


message_identifier: 0xb000015d
message_string:
The print spooler failed to create a symbolic link between HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Print\\Printers and HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers. Error %1. This only affects older applications, but is probably a sign that the system itself is in a poor condition or that the print spooler does not have the proper registry permissions.


message_identifier: 0xb00001f8
message_string:
Failed to initialize the router work crew: Error %2. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb000006f
message_string:
Ending document job %3 for printer %4 failed, error code %2. See the event user data for context information.


message_identifier: 0xb000006a
message_string:
Starting document job %3 for printer %4 succeeded. See the event user data for context information.


message_identifier: 0xb000025a
message_string:
The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key %1\%2. This can occur if the key name or values are malformed or missing.


message_identifier: 0xb0000353
message_string:
Point and Print not allowed by policy for queue %1. Cannot make a Point and Print connection to this queue. Error %2.


message_identifier: 0xb000025c
message_string:
The print spooler encountered an unknown driver type while saving %1 cache information. This can occur because of a protocol or network error.


message_identifier: 0xb0000175
message_string:
The spooler has detected that a component has an unusually large number of open Graphical Device Interface (GDI) objects. As a result, some enhanced metafile (EMF) print jobs might not print until the spooler is restarted.


message_identifier: 0xb0000174
message_string:
The document %1, owned by %2, failed to print on printer %3. Try to print the document again, or restart the print spooler. %nData type: %4. Size of the spool file in bytes: %5. Number of bytes printed: %6. Total number of pages in the document: %7. Number of pages printed: %8. Client computer: %9. Win32 error code returned by the print processor: %10. %11


message_identifier: 0xb0000170
message_string:
The print spooler failed to verify printer driver package %1 for environment %2. Win32 system error code %3. This can occur after an operating system upgrade or because of data loss on the hard drive. The print spooler will try to regenerate the driver information from the driver store, which is where drivers are saved before they are installed. No user action is required.


message_identifier: 0xb0000171
message_string:
The print spooler failed to verify printer driver package for environment %1. Win32 system error code %2. This can occur because of insufficient memory or other system failures. No user action is required.


message_identifier: 0xb0000172
message_string:
The print spooler failed to regenerate the printer driver information for driver %1 for environment %2. Win32 system error code %3. This can occur after an operating system upgrade or because of data loss on the hard drive.


message_identifier: 0xb00000e0
message_string:
A remote print driver package operation %1 failed with error code %2, server name %3. This was most likely caused by an unexpected error in the protocol communication between the client and the print server.


message_identifier: 0xb00001f6
message_string:
The print spooler failed to get the computer name. Error %2. This can occur due to system instability or a lack of system resources.


message_identifier: 0xb00000db
message_string:
Copying printer driver package %5 failed, error code %8, HRESULT %9. See the event user data for context information.


message_identifier: 0xb00000dc
message_string:
Retrieving CSR cache information for printer %3 succeeded. See the event user data for context information.


message_identifier: 0xb00000dd
message_string:
Retrieving CSR cache information for printer %3 failed, error code %2. See the event user data for context information.


message_identifier: 0xb000014f
message_string:
While attempting to remove the printer from the Active Directory directory service, the print spooler failed to delete print queue %1 from container %2.  Error: %3


message_identifier: 0xb0000201
message_string:
Group Policy was unable to add per computer connection %1. Error code %2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.


message_identifier: 0xb000015b
message_string:
Print queue %1 could not be deleted (pruned) from the Active Directory directory service.  Error: %2. The spooler will periodically try to remove the entry until it is successful. Continued failures may indicate an Active Directory problem, a basic network problem, or a communication problem between the domain controller and the print server.


message_identifier: 0xb000016c
message_string:
Windows could not load print processor %1 because EnumDatatypes did not return any data. Module: %2. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.


message_identifier: 0xb0000204
message_string:
Group Policy was unable to deploy per computer printer connection %1. Error %2. The printer connection is not available to users on this computer. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry adding the printer connection.


message_identifier: 0xb00000cd
message_string:
Deleting CSR printer connection %3 failed, error code %2. See the event user data for context information.


message_identifier: 0xb000014d
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler failed to create or update print queue %1 in container %2.  Error: %3. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb000015e
message_string:
Document %1 failed to print and was deleted because of corruption in the spooled file. The associated driver is: %2. Try printing the document again.


message_identifier: 0xb0000207
message_string:
Group Policy was unable to deploy per user printer connection %1. Error code %2. The printer connection is not available to the users on this computer to which the Group Policy object applies. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry adding the printer connection.


message_identifier: 0xb0000202
message_string:
Group Policy was unable to delete per computer connection %1. Error %2. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.


message_identifier: 0xb0000200
message_string:
InitializePrintProvider failed for provider %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb0000164
message_string:
Failed to install or update driver %1 on cluster spooler resource %2. Win32 error: %3. The printer driver is different from the driver in use on other computers (nodes) in the cluster. This can occur because of a transient failure in replication between nodes, or if the nodes are running Windows 2000 (which does not automatically replicate drivers).


message_identifier: 0xb000032f
message_string:
The print spooler service failed to register the RPC server protocol sequence %1, error code %3. See the event user data for context information.


message_identifier: 0xb0000208
message_string:
Group Policy was unable to update per user printer connection %1. Error code %2. This can occur if the name of the printer connection is incorrect, if there is a Group Policy problem, or if the print spooler cannot contact the print server. Group Policy will periodically retry updating the printer connection.


message_identifier: 0xb000016b
message_string:
The print spooler %1 failed to start. To determine the cause of this error, examine the preceding events in the Event Log.


message_identifier: 0xb000016e
message_string:
The print server security descriptor for %1 is invalid. The default print server security descriptor will be used.


message_identifier: 0xb000016d
message_string:
Windows could not load print processor %1 because EnumDatatypes failed. Error code %2. Module: %3. Please obtain and install a new version of the driver from the manufacturer (if available), or choose an alternate driver that works with this print device.


message_identifier: 0xb0000168
message_string:
Updating the color profile failed for printer %1 with Win32 error code %2. The colors printed may not be correctly matched to the colors in the document being printed.


message_identifier: 0xb00002bd
message_string:
The print filter pipeline host cannot initialize with the Component Object Model (COM) system. Error %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00002be
message_string:
The print filter pipeline host is shutting down due to the following error: Error %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00001ff
message_string:
The print spooler failed to load print provider %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb00000c9
message_string:
Adding CSR printer connection %3 failed, error code %2. See the event user data for context information.


message_identifier: 0xb0000356
message_string:
Print Client Side Rendering synchronization for printer information cache completed with code %1 for printer %2.


message_identifier: 0xb0000352
message_string:
The print spooler called the function %2 in print driver module %1. This call initialized the Component Object Model (COM) system without properly un-initializing it.


message_identifier: 0xb00002c0
message_string:
The print filter pipeline host is shutting down because the query interface for ISignal in the Component Object Model (COM) proxy in the spooler failed. Error %1. This can occur because of system instability or a lack of system resources.


message_identifier: 0xb0000160
message_string:
The priority of document %1, %2 owned by %3 was changed to %4 on %5. Windows prints the document with the highest priority number before other print jobs with lower priority numbers. Documents that are currently printing are unaffected by changes in priority. No user action is required.


message_identifier: 0xb0000142
message_string:
While attempting to publish the printer to the Active Directory directory service, Windows failed to publish property %1 at %2.  Error: %3


message_identifier: 0xb000007b
message_string:
Starting page failed at printer %3, error code %2. See the event user data for context information.


message_identifier: 0xb0000169
message_string:
Printer %1 failed to initialize its ports. Win32 error: %2. This error usually occurs because of a problem with the port monitor. Try recreating the port using a standard TCP/IP printer port, if possible. This problem does not affect other printers.


message_identifier: 0xb000014b
message_string:
While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container on domain %1.  Error: %2. The printer is not published in Active Directory and cannot be located by searching Active Directory.


message_identifier: 0xb0000355
message_string:
Print Client Side Rendering synchronization for print job cache completed with code %1 for printer %2.


message_identifier: 0xb000014e
message_string:
The printer was successfully removed from the Active Directory directory service. Print queue %1 was successfully deleted from container %2. The printer can no longer be located by searching Active Directory. No user action is required.


message_identifier: 0xb0000167
message_string:
The attempt to install printer %1 into an offline operating system image failed with Win32 error code %2. This can occur if the printer driver requires user input or displays a user interface (UI) during installation.


message_identifier: 0xb000016a
message_string:
The print spooler could not initialize because resolving the local machine name to IP addresses failed with error code %1. This may be a transient error. Try to manually restart the print spooler service (from Control Panel | Administrative Tools | Services or from an elevated command prompt running: net start spooler).


# message_table_46_0x00000409

message_identifier: 0xb0000022
message_string:
An in-flight scenario from provider %1 (event ID %2) timed out and was stopped automatically by the Scenario Event Mapper.


message_identifier: 0xb0000023
message_string:
The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of scenarios are already in flight.


message_identifier: 0xb0000020
message_string:
The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers.  The context logger dropped event count was %3.


message_identifier: 0xb0000021
message_string:
The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers.  The context logger dropped event count was %3.


message_identifier: 0xb0000026
message_string:
The Scenario Event Mapper is configured with more than the maximum number of scenarios.  The scenario for provider %1 (event ID %2) will be ignored.


message_identifier: 0xb0000027
message_string:
The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider %1 (event ID %2).  The scenario will be ignored.


message_identifier: 0xb0000024
message_string:
The Scenario Event Mapper was unable to start a scenario for provider %1 (event ID %2).  The error code was %3.


message_identifier: 0xb0000025
message_string:
The Scenario Event Mapper was unable to stop a scenario for provider %1 (event ID %2).  The error code was %3.


message_identifier: 0x000003ac
message_string:
Stack correlation event. This event contains a call stack which is associated with a prior event which is correlated by the MatchId.


message_identifier: 0xb0000028
message_string:
The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 (event ID %2).  The scenario will be ignored.


message_identifier: 0xb6002781
message_string:
The user does not have permission to change the system locale (specified by the SystemLocale element).


message_identifier: 0xb60009c4
message_string:
Windows has detected inconsistencies in NLS internal data. To correct this problem, log off of Windows and log on again.


message_identifier: 0xb60032c9
message_string:
The user reset all customizations for their user locale "%1" (specified by the UserLocale element) to the system default.


message_identifier: 0xbc0007d1
message_string:
MUI Callback failed for file %1 because it can not be loaded. To correct this error, replace this file or repair your Windows installation.


message_identifier: 0x00000328
message_string:
File Set Information was requested (%1) for file object %3 with key %4 for type %6 with %5 as extra information.


message_identifier: 0x000002c2
message_string:
Image %1 failed IntegrityCheck reason is %3. Image flags are %2. Error ignored due to debugger %4.


message_identifier: 0xb6002716
message_string:
The selected system locale (specified by the SystemLocale element) is not installed on the system. The system locale was not changed.


message_identifier: 0xb6002710
message_string:
The user tried to apply an unattended XML file (%1) in an unsupported format. Reason: %3 (Line %2). The system has not been changed.


message_identifier: 0xb6002713
message_string:
The user locale "%1" (specified by the UserLocale element) is not a supported locale name or is not installed on the system. The user locale was not changed.


message_identifier: 0xb6002719
message_string:
Error while changing location preference (geoid): %1. This error may be caused by an unsupported location preference (geoid) or a Group Policy restriction. Error code is %2. Error message: %3


message_identifier: 0xb600271d
message_string:
Error while the user changed setting "%1" with value "%2" for the current user locale. Error code is: %3. Error message: %4


message_identifier: 0xb0000029
message_string:
The Scenario Event Mapper is configured with more than the maximum number of providers.  The provider %1 will be ignored.


message_identifier: 0xb600271e
message_string:
The selected calendar "%1;" (specified by the Calendar element) is not a supported calendar. The user locale was not changed.


message_identifier: 0xb600271f
message_string:
The selected TwoDigitYearMax "%1;" (specified by the TwoDigitYearMax element) is not a supported value. The user locale was not changed.


message_identifier: 0xb000002a
message_string:
The Scenario Event Mapper is configured with an unsupported scenario. The scenario for provider %1 (event ID %2) encountered error code %3 and will be ignored.


message_identifier: 0xbc0007da
message_string:
Unable to parse the cacheable file list or write to the resource cache manifest. If configuration file was specified as command-line parameter, check that file exists and has correct format.  New resource cache will not be built.


message_identifier: 0xbc0007db
message_string:
Changes made to resource cache manifest cannot be written to disk. New resource cache will not be built.


message_identifier: 0xbc000bb8
message_string:
MUI notification for UI Language change has been invoked with flags set to %1 and the new languages set to %2 and the previous languages set to %3. The extended flags is set to %4


message_identifier: 0x000003c4
message_string:
A data corruption was detected and handled in a ReadyBoost cache. This corruption was most likely caused by faulty hardware. While ReadyBoost will always detect and handle these errors, seeing a lot of these may mean that the ReadyBoost device has worn out which reduces its performance. You should consider replacing the ReadyBoost cache device.


message_identifier: 0x0000032e
message_string:
File FSCTL was requested (%1) for file object %3 with key %4 for type %6 with %5 as extra information.


message_identifier: 0x3000000f
message_string:
The SEM received a request to start a new scenario, but the maximum number of scenarios were already in-flight.


message_identifier: 0x000003c5
message_string:
A ReadyBoost cache failed to persist across boot. This may happen if the cache device was modified on another computer or if this computer was booted into another operating system.


message_identifier: 0xb60003e9
message_string:
The NLS operation failed because the registry key %1 cannot be opened. Error code is %2. Error message: %3


message_identifier: 0xbc0007d4
message_string:
MUI Callback file %1 cannot be found. To correct this error, repair the registry or copy the file to the specified location.


message_identifier: 0x01000006
message_string:
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '%3'.


message_identifier: 0x01000005
message_string:
{Registry Hive Recovered} Registry hive (file): '%3' was corrupted and it has been recovered. Some data might have been lost.


message_identifier: 0xb5000004
message_string:
A trip point change notification (Notify(thermal_zone, 0x81)) for ACPI thermal zone %2 has been received.
            %n_TMP = %3K
            %n_PSV = %4K
            %n_AC0 = %5K
            %n_AC1 = %6K
            %n_AC2 = %7K
            %n_AC3 = %8K
            %n_AC4 = %9K
            %n_AC5 = %10K
            %n_AC6 = %11K
            %n_AC7 = %12K
            %n_AC8 = %13K
            %n_AC9 = %14K
            %n_HOT = %15K
            %n_CRT = %16K


message_identifier: 0x000003c7
message_string:
A ReadyBoost cache was deleted due to repeated data corruption instances on the associated device that have been detected and handled. While ReadyBoost will always detect and handle these errors, repeated corruption instances may mean that the ReadyBoost device has worn out which reduces its performance. You should consider replacing the ReadyBoost device.


message_identifier: 0x000003c3
message_string:
A memory corruption was detected and handled. Memory diagnostics should be run on this machine and, if necessary, memory chips should be replaced.


message_identifier: 0xb60003ed
message_string:
NLS operation failed for %1 locale because the file %2\globalization\%1.nlp is missing.  To fix this problem, reinstall this custom locale.


message_identifier: 0xb60003ee
message_string:
NLS operation failed for %1 locale because the file %2\globalization\%1.nlp is corrupted.  To fix this problem, reinstall this custom locale.


message_identifier: 0x000003c8
message_string:
A ReadyBoost cache was deleted due to repeated I/O failures on the associated device. This typically happens when the device (e.g. an SD card) is removed, but it may also indicate faulty hardware.


message_identifier: 0xb60005df
message_string:
Group Policy does not allow custom user locales for standards and formats. The user was unable to select "%1" as their user locale.


message_identifier: 0x3000000c
message_string:
When a scenario has remained in-flight beyond the maximum time window it is automatically terminated by the SEM.


message_identifier: 0xb600283c
message_string:
Group Policy has prevented the user from changing the system locale (specified by the SystemLocale element).


message_identifier: 0xbc000bc5
message_string:
The system is constrained in RAM, total disk space or free disk space, so the MUI resource cache will not be maintained.


message_identifier: 0xb60003ec
message_string:
NLS codepage operation failed for the codepage %1 because the file %2 is corrupted. To correct this error, replace this file or repair your Windows installation.


message_identifier: 0xbc000bbc
message_string:
MUI resource cache manifest entry for file %1 has been updated. Affinity: '%2', Sequence: %3, and Priority: %4


message_identifier: 0x0d00000a
message_string:
The system firmware has allocated a memory region previously determined to be unreliable. This has the potential to cause system instability and/or data corruption.


message_identifier: 0xb60005dc
message_string:
Group Policy has prevented process number %1 (%2) from changing the standards and format information for the user.


message_identifier: 0x0b000362
message_string:
Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3.


message_identifier: 0x00000387
message_string:
The backing-file for the real-time session "%1" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers.


message_identifier: 0xb60003eb
message_string:
NLS codepage operation failed for the codepage %1 because the file %2 is missing.  To correct this error, replace this file or repair your Windows installation.


message_identifier: 0xbc000bbf
message_string:
New resource cache built and installed on system. New cache index is %1, live cache index is %2 and config is set to %3.


message_identifier: 0x0000038a
message_string:
The maximum file size for session "%1" has been reached. As a result, events might be lost (not logged) to file "%2". The maximum files size is currently set to %5 bytes.


message_identifier: 0x0000038b
message_string:
An error was encountered while tracing session "%2" was switching to the "%1" event log file. Error: %3


message_identifier: 0xb5000003
message_string:
A temperature change notification (Notify(thermal_zone, 0x80)) for ACPI thermal zone %2 has been received.
            %n_TMP = %3K
            %n_PSV = %4K
            %n_AC0 = %5K
            %n_AC1 = %6K
            %n_AC2 = %7K
            %n_AC3 = %8K
            %n_AC4 = %9K
            %n_AC5 = %10K
            %n_AC6 = %11K
            %n_AC7 = %12K
            %n_AC8 = %13K
            %n_AC9 = %14K
            %n_HOT = %15K
            %n_CRT = %16K


message_identifier: 0xb5000005
message_string:
The active cooling device %6 has been turned %8.
            %nThermal zone device instance: %2
            %nActive cooling package: _AC%3
            %nNamespace object: _AL%4


message_identifier: 0xbc0007d2
message_string:
MUI Callback failed for file %1 registered as type %2 because the function %3 does not exist in the dll. To correct this error, replace the file or fix the registry entry.


message_identifier: 0xbc0007d3
message_string:
MUI Callback failed for file %1 because it is not signed by Microsoft. To correct this error, replace with the original file that came with this Windows installation.


# message_table_47_0x00000409

message_identifier: 0x00000464
message_string:
The number of printers per session limit was reached. The following print queue was not created: %n%nPrinter = %1%nPort = %2


message_identifier: 0x00000462
message_string:
The Print Spooler failed to add the print queue for printer %1, port %2 because of a port error. The Print Spooler will try again.


message_identifier: 0x00000463
message_string:
The Print Spooler failed to add the printer %1, port %2 because of a port error. The Print Spooler will not try again to add the printer.


message_identifier: 0x0000045a
message_string:
Error communicating with the Spooler system service.  Open the Services snap-in and confirm that the Print Spooler service is running.


message_identifier: 0x0000045c
message_string:
The printer %1 cannot be redirected by using Remote Desktop Easy Print. The client computer may not have a version of the Remote Desktop Connection client or Microsoft .NET Framework installed that supports this driver.


message_identifier: 0x800005dd
message_string:
The Remote Desktop Services could not find a corresponding driver called %1 for printer %2. The Remote Desktop Fallback Printer Driver %3 was used.


message_identifier: 0x00000459
message_string:
There is not enough memory to complete the operation. Save your work, close other programs, and then try again.


message_identifier: 0x00000458
message_string:
Failed to register for user printing preferences change notification.  Open the Services snap-in and confirm that the Printer Spooler service is running


message_identifier: 0x00000457
message_string:
Driver %1 required for printer %2 is unknown. Contact the administrator to install the driver before you log in again.


message_identifier: 0x00000456
message_string:
An error occurred during processing of %1. The file might be corrupted. Run Setup again to reinstall the file.


message_identifier: 0x0000044c
message_string:
TS RDPDR Device Redirection failed to initialize for a single user session %1.  Serial, Parallel, Printer, and File System Redirection will be disabled.  Look in the System event log for other related errors.


message_identifier: 0x0000044f
message_string:
An internal communication error occurred.  Redirected printing will no longer function for a single user session.  Check the status of the Remote Desktop Device Redirector in the System folder of Device Manager.


message_identifier: 0x0000044e
message_string:
Driver %1 required for printer %2 is not installed on the server. Contact the administrator to install the driver before you log in again.


# message_table_48_0x00000409

message_identifier: 0x00000c4e
message_string:
A file system error occurred while opening or writing to the
system message log file %1. Message logging has been
switched off due to the error. The error code is the data.


message_identifier: 0x00000c44
message_string:
The service has stopped due to repeated consecutive
occurrences of a network control block (NCB) error.  The last bad NCB follows
in raw data.


message_identifier: 0x000014e7
message_string:
There are multiple network control block (NCB) requests for the same session.
The NCB request was refused.  The NCB is the data.


message_identifier: 0x000014e8
message_string:
There has been a network adapter error. The only NetBIOS
command that may be issued is an NCB RESET. The network control block (NCB) is
the data.


message_identifier: 0x000014ec
message_string:
The requested resources are not available.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014ea
message_string:
The maximum number of applications was exceeded.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x00001504
message_string:
A network adapter malfunction has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x00000c79
message_string:
A virtual circuit error occurred on the session to %1.
The network control block (NCB) command and return code is the data.


message_identifier: 0x00000c70
message_string:
The user accounts database (NET.ACC) is missing.  The local
security system is restoring the backup database
made at %1.
Any updates made to the database made after this time are lost.



message_identifier: 0x00000c71
message_string:
Local security could not be started because the user accounts database
(NET.ACC) was missing or corrupted, and no usable backup
database was present.

THE SYSTEM IS NOT SECURE.


message_identifier: 0x00000c72
message_string:
Local security could not be started because an error
occurred during initialization. The error code returned is %1.

THE SYSTEM IS NOT SECURE.



message_identifier: 0x000014d5
message_string:
The NetBIOS interface is busy.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014d6
message_string:
There are too many network control block (NCB) commands outstanding.
The NCB request was refused.  The NCB is the data.


message_identifier: 0x000014d8
message_string:
The network control block (NCB) command completed while a cancel was occurring.
The NCB is the data.


message_identifier: 0x00001282
message_string:
The share name entered may not be accessible from some MS-DOS workstations.
Are you sure you want to use this share name? %1: %0


message_identifier: 0x00000bd4
message_string:
The user accounts database (NET.ACC) is missing. The local
security system is restoring the backup database
made on %1 at %2.
Any updates made to the database after this time are lost.



message_identifier: 0x00000bd5
message_string:
Local security could not be started because the user accounts database
(NET.ACC) was missing or corrupted, and no usable backup
database was present.

THE SYSTEM IS NOT SECURE.



message_identifier: 0x00000bd1
message_string:
A defective sector on drive %1 has been replaced (hotfixed).
No data was lost.  You should run CHKDSK soon to restore full
performance and replenish the volume's spare sector pool.

The hotfix occurred while processing a remote request.


message_identifier: 0x00000bd2
message_string:
A disk error occurred on the HPFS volume in drive %1.
The error occurred while processing a remote request.


message_identifier: 0x00000bd3
message_string:
The user accounts database (NET.ACC) is corrupted.  The local security
system is replacing the corrupted NET.ACC with the backup
made on %1 at %2.
Any updates made to the database after this time are lost.



message_identifier: 0x00000c6f
message_string:
The user accounts database (NET.ACC) is corrupted.  The local security
system is replacing the corrupted NET.ACC with the backup
made at %1.
Any updates made to the database after this time are lost.



message_identifier: 0x00000c6c
message_string:
WARNING:  Because of a lazy-write error, drive %1 now
contains some corrupted data.  The cache is stopped.


message_identifier: 0x00000c63
message_string:
There was an error expanding %1 as a group name. Try
splitting the group into two or more smaller groups.


message_identifier: 0x00000e69
message_string:
The Workstation service is already running. Windows will ignore command options for the workstation.


message_identifier: 0x00000be1
message_string:
The replicator cannot update directory %1. It has tree integrity
and is the current directory for some process.


message_identifier: 0x00000e5e
message_string:
An error occurred while saving your profile : Access Denied. The state of your remembered connections has not changed.


message_identifier: 0x00000c9b
message_string:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2
failed because %1 does not support signing or sealing the Netlogon
session.

Either upgrade the Domain controller or set the RequireSignOrSeal
registry entry on this machine to 0.


message_identifier: 0x0000168c
message_string:
Global group SERVERS exists in domain %1 and has members.
This group defines Lan Manager BDCs in the domain.
Lan Manager BDCs are not permitted in NT domains.


message_identifier: 0x0000168b
message_string:
The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is
attempting to convert it to NT 4.0 format. The JETCONV converter
will write to the Application event log when it is finished.


message_identifier: 0x00000bba
message_string:
%1 network errors occurred in the last %2 minutes.
Please review the server's error log.  The server and/or
network hardware may need service.


message_identifier: 0x000014f9
message_string:
An interface failure has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014f8
message_string:
An analog loopback failure has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014f7
message_string:
A digital loopback failure has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014f6
message_string:
A RAM test failure has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014f5
message_string:
A ROM checksum failure has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014f4
message_string:
A system error has occurred.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x00000bbe
message_string:
The error log is full.  No errors will be logged until
the file is cleared or the limit is raised.


message_identifier: 0x00000bbb
message_string:
There were %1 bad password attempts in the last %2 minutes.
Please review the server's audit trail.


message_identifier: 0x00000bbc
message_string:
There were %1 access-denied errors in the last %2 minutes.
Please review the server's audit trail.


message_identifier: 0x00000c8a
message_string:
This computer could not authenticate with %2, a Windows domain controller
for domain %1, and therefore this computer might deny logon requests.
This inability to authenticate might be caused by another computer on the
same network using the same name or the password for this computer account
is not recognized. If this message appears again, contact your system
administrator.


message_identifier: 0x0000157e
message_string:
The time difference with the primary domain controller %1
exceeds the maximum allowed skew of %2 seconds.


message_identifier: 0x0000157d
message_string:
The update log on %1 is full, and no further updates
can be added until the primary domain controller %2
retrieves the updates.


message_identifier: 0x0000157c
message_string:
The update log on %1 is over 80%% capacity. The primary
domain controller %2 is not retrieving the updates.


message_identifier: 0x00000c84
message_string:
The server could not create a thread.
The THREADS parameter in the CONFIG.SYS file should be increased.


message_identifier: 0x00000ca4
message_string:
The UPS service failed to execute a user specified shutdown
command file %1.  The error code is the data.


message_identifier: 0x000014a2
message_string:
Do you want to resume loading the profile?  The command which
caused the error will be ignored. %1: %0


message_identifier: 0x000014a0
message_string:
The password entered is longer than 14 characters.  Computers
with Windows prior to Windows 2000 will not be able to use
this account. Do you want to continue this operation? %1: %0


message_identifier: 0x00000bcf
message_string:
There is a problem with a configuration of user specified
shut down command file.  The UPS service started anyway.


message_identifier: 0x00000bc0
message_string:
The audit log is full.  No audit entries will be logged
until the file is cleared or the limit is raised.


message_identifier: 0x00000859
message_string:
The Workstation service is in an inconsistent state. Restart the computer before restarting the Workstation service.


message_identifier: 0x000016b5
message_string:
The dynamic registration request for the DNS record '%1' has been rejected by the
remote domain controller '%2'. Error: '%3'

%n%nFor computers and users to locate this domain controller, this record must be
registered in DNS. If the problem persists, please contact your domain administrator.


message_identifier: 0x000016b4
message_string:
The dynamic deregistration of the DNS record '%1' for the remote domain controller
'%3' failed on the following DNS server:

%n%nDNS server IP address: %4
%nReturned Response Code (RCODE): %5
%nReturned Status Code: %6

%n%nUSER ACTION

%nTo prevent remote computers from attempting to connect to the domain controller '%3'
using an invalid record, delete the record '%1' manually or troubleshoot the root cause
behind the dynamic deregistration failure. To learn more about troubleshooting DNS, see
Help and Support.

%n%nADDITIONAL DATA
%nError Value: %2


message_identifier: 0x000016b7
message_string:
The remoting of the dynamic update request for the local domain controller's DNS records
through a secure session has failed with error '%1'.

%n%nFor other computers and member servers to locate this domain controller, the appropriate
records must be registered in DNS. On this domain controller, look for events related to
failure to set up a secure session to determine why the request is failing. If the problem
persists, please contact your domain administrator.


message_identifier: 0x000016b6
message_string:
The dynamic deregistration request of the DNS record '%1' has been rejected by the
remote domain controller '%2'. Error: '%3'

%n%nTo prevent remote computers from connecting unnecessarily to this domain controller,
an administrator with sufficient privileges must manually delete the record on the DNS
server that hosts it.


message_identifier: 0x000016b1
message_string:
The NetLogon service on this domain controller has been configured to use port %1
for incoming RPC connections over TCP/IP from remote machines. However, the
following error occurred when Netlogon attempted to register this port with the RPC
endpoint mapper service: %n%2 %nThis will prevent the NetLogon service on remote
machines from connecting to this domain controller over TCP/IP that may result in
authentication problems.

%n%nUSER ACTION

%nThe specified port is configured via the Group Policy or via a registry value 'DcTcpipPort'
under the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters'
registry key; the value configured through the Group Policy takes precedence. If the
port specified is in error, reset it to a correct value. You can also remove this
configuration for the port in which case the port will be assigned dynamically by
the endpoint mapper at the time the NetLogon service on remote machines makes RPC connections
to this domain controller. After the misconfiguration is corrected, restart the NetLogon
service on this machine and verify that this event log no longer appears.


message_identifier: 0x000016b0
message_string:
The deregistration of some DNS domain controller locator records was aborted
at the time of this domain controller demotion because the DNS deregistrations
took too long.

%n%nUSER ACTION

%nManually delete the DNS records listed in the file
'%SystemRoot%\System32\Config\Netlogon.dns' from the DNS database.


message_identifier: 0x000016b3
message_string:
The dynamic registration of the DNS record '%1' for the remote domain controller '%3'
failed on the following DNS server:

%n%nDNS server IP address: %4
%nReturned Response Code (RCODE): %5
%nReturned Status Code: %6

%n%nFor computers and users to locate the domain controller '%3', this record must be
registered in DNS.

%n%nUSER ACTION

%nDetermine what might have caused this failure, resolve the problem, and initiate
registration of the DNS records by the domain controller '%3'. For help with determining
and resolving the problem, see Help and Support for information about troubleshooting
DNS. To initiate registration of the DNS records by the domain controller '%3', run
'nltest.exe /dsregdns' from the command prompt on the domain controller '%3' or restart
the Net Logon service on the domain controller '%3'. Nltest.exe is a command line tool
that is built into Windows Server.
%n As a workaround, you can manually add this record to DNS, but it is not recommended
because you then must manually update any changes it requires hereafter.

%n%nADDITIONAL DATA
%nError Value: %2


message_identifier: 0x000016b2
message_string:
During the past %1 hours, this domain controller has received %2 connections
from dual-stack IPv4/IPv6 clients with partial subnet-site mappings. A client
has a partial subnet-site mapping if its IPv4 address is mapped to a site but
its global IPv6 address is not mapped to a site, or vice versa. To ensure correct
behavior for applications running on member computers and servers that rely on
subnet-site mappings, dual-stack IPv4/IPv6 clients must have both IPv4 and global
IPv6 addresses mapped to the same site. If a partially mapped client attempts
to connect to this domain controller using its unmapped IP address, its mapped
address is used for the client's site mapping.

%n%nThe log files %SystemRoot%\debug\netlogon.log or %SystemRoot%\debug\netlogon.bak
contain the name, unmapped IP address and mapped IP address for each partially
mapped client. The log files may also contain unrelated debugging information.
To locate the information pertaining to partial-subnet mappings, search for
lines that contain the text 'PARTIAL_CLIENT_SITE_MAPPING:'. The first word after
this text is the client name. Following the client name is the client's unmapped
IP address (the IP address that does not have a subnet-site mapping) and the
client's mapped IP address, which was used to return site information.

%n%nUSER ACTION

%nUse the Active Directory Sites and Services management console (MMC) snap-in
to add the subnet mapping for the unmapped IP addresses to the same site being
used by the mapped IP addresses. When adding site mappings for IPv6 addresses,
you should use global IPv6 addresses and not for instance temporary, link-local
or site-local IPv6 addresses.

%n%nThe default maximum size of the log files is %3 bytes. The current maximum
size is %4 bytes. To set a different maximum size, create the following registry
DWORD value to specify the maximum size in bytes:

%nHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize


message_identifier: 0x00000d59
message_string:
WARNING: You have until %1 to logoff. If you
have not logged off at this time, your session will be
disconnected, and any open files or devices you
have open may lose data.


message_identifier: 0x00000d5a
message_string:
WARNING: You must log off at %1 now.  You have
two minutes to log off, or you will be disconnected.


message_identifier: 0x000014ca
message_string:
The name specified in the network control block (NCB) is in use on a remote adapter.
The NCB is the data.


message_identifier: 0x000014cd
message_string:
The network protocol has detected two or more identical
names on the network.	The network control block (NCB) is the data.


message_identifier: 0x000014ce
message_string:
An unexpected protocol packet was received.  There may be an
incompatible remote device.  The network control block (NCB) is the data.


message_identifier: 0x000014c0
message_string:
The message segment specified in the network control block (NCB) is
illogical.  The NCB is the data.


message_identifier: 0x000014c1
message_string:
The name already exists in the local adapter name table.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014c2
message_string:
The network adapter name table is full.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014c3
message_string:
The network name has active sessions and is now de-registered.
The network control block (NCB) command completed.  The NCB is the data.


message_identifier: 0x000014c4
message_string:
A previously issued Receive Lookahead command is active
for this session.  The network control block (NCB) command was rejected.
The NCB is the data.


message_identifier: 0x000014c5
message_string:
The local session table is full. The network control block (NCB) request was refused.
The NCB is the data.


message_identifier: 0x000014c6
message_string:
A network control block (NCB) session open was rejected.  No LISTEN is outstanding
on the remote computer.  The NCB is the data.


message_identifier: 0x000014c8
message_string:
The call name specified in the network control block (NCB) cannot be found or
did not answer.  The NCB is the data.


message_identifier: 0x000014c9
message_string:
The name specified in the network control block (NCB) was not found.  Cannot put '*' or
00h in the NCB name.  The NCB is the data.


message_identifier: 0x000016a8
message_string:
Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes
of the computer object in Active Directory failed because the Domain Controller
'%1' had more than one account with the name '%2' corresponding to this computer.
Not having SPNs registered may result in authentication failures for this computer.
Contact your domain administrator who may need to manually resolve the account name
collision.


message_identifier: 0x000016a9
message_string:
Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes
of the computer object in Active Directory failed because this computer account
name, '%2' could not be mapped to the computer object on Domain Controller '%1'.
Not having SPNs registered may result in authentication failures for this computer.
Contact your domain administrator. The following technical information may be
useful for the resolution of this failure:%n
DsCrackNames status = 0x%3, crack error = 0x%4.


message_identifier: 0x000016a0
message_string:
Site '%2' does not have any LDAP servers for non-domain NC '%3'.
LDAP servers in site '%1' have been automatically selected to
cover site '%2' for non-domain NC '%3' based on configured
Directory Server replication costs.


message_identifier: 0x000016a2
message_string:
Site '%2' is no longer manually configured in the registry as
covered by this Domain Controller for domain '%3'. As a result,
site '%2' does not have any Domain Controllers for domain '%3'.
Domain Controllers in site '%1' have been automatically
selected to cover site '%2' for domain '%3' based on configured
Directory Server replication costs.


message_identifier: 0x000016a3
message_string:
This Domain Controller no longer automatically covers site '%1' for domain '%2'.
However, site '%1' is still (manually) covered by this Domain Controller for
domain '%2' since this site has been manually configured in the registry.


message_identifier: 0x000016a4
message_string:
Site '%2' is no longer manually configured in the registry as
covered by this Global Catalog server for forest '%3'. As a result,
site '%2' does not have any Global Catalog servers for forest '%3'.
Global Catalog servers in site '%1' have been automatically
selected to cover site '%2' for forest '%3' based on configured
Directory Server replication costs.


message_identifier: 0x000016a5
message_string:
This Global Catalog server no longer automatically covers site '%1' for forest '%2'.
However, site '%1' is still (manually) covered by this Global catalog for
forest '%2' since this site has been manually configured in the registry.


message_identifier: 0x000016a6
message_string:
Site '%2' is no longer manually configured in the registry as
covered by this LDAP server for non-domain NC '%3'. As a result,
site '%2' does not have any LDAP servers for non-domain NC '%3'.
LDAP servers in site '%1' have been automatically
selected to cover site '%2' for non-domain NC '%3' based on
configured Directory Server replication costs.


message_identifier: 0x000016a7
message_string:
This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'.
However, site '%1' is still (manually) covered by this LDAP server for
non-domain NC '%2' since this site has been manually configured in the registry.


message_identifier: 0x000013aa
message_string:
Printing Failed

"%1" failed to print on %2 on %3.  The Printer is %4.

For more help use the print troubleshooter.


message_identifier: 0x000016aa
message_string:
None of the IP addresses (%2) of this Domain Controller map to the configured site '%1'.
While this may be a temporary situation due to IP address changes, it is generally
recommended that the IP address of the Domain Controller (accessible to machines in
its domain) maps to the Site which it services. If the above list of IP addresses is
stable, consider moving this server to a site (or create one if it does not already
exist) such that the above IP address maps to the selected site. This may require the
creation of a new subnet object (whose range includes the above IP address) which maps
to the selected site object.


message_identifier: 0x000016ab
message_string:
The following error occurred while reading a parameter '%2' in the
Netlogon %1 registry section:%n%3


message_identifier: 0x000016ac
message_string:
The Netlogon %1 registry key contains an invalid value 0x%2 for parameter '%3'.
The minimum and maximum values allowed for this parameter are 0x%4 and 0x%5, respectively.
The value of 0x%6 has been assigned to this parameter.


message_identifier: 0x000016ad
message_string:
The session setup from the computer %1 failed to authenticate.
The following error occurred: %n%2


message_identifier: 0x000016ae
message_string:
Dynamic DNS updates have been manually disabled on this domain controller.

%n%nUSER ACTION

%nReconfigure this domain controller to use dynamic DNS updates or manually add the DNS
records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database.


message_identifier: 0x000016af
message_string:
During the past %1 hours there have been %2 connections to this Domain
Controller from client machines whose IP addresses don't map to any of
the existing sites in the enterprise. Those clients, therefore, have
undefined sites and may connect to any Domain Controller including
those that are in far distant locations from the clients. A client's site
is determined by the mapping of its subnet to one of the existing sites.
To move the above clients to one of the sites, please consider creating
subnet object(s) covering the above IP addresses with mapping to one of the
existing sites.  The names and IP addresses of the clients in question have
been logged on this computer in the following log file
'%SystemRoot%\debug\netlogon.log' and, potentially, in the log file
'%SystemRoot%\debug\netlogon.bak' created if the former log becomes full.
The log(s) may contain additional unrelated debugging information. To filter
out the needed information, please search for lines which contain text
'NO_CLIENT_SITE:'. The first word after this string is the client name and
the second word is the client IP address. The maximum size of the log(s) is
controlled by the following registry DWORD value
'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize';
the default is %3 bytes.  The current maximum size is %4 bytes.  To set a
different maximum size, create the above registry value and set the desired
maximum size in bytes.


message_identifier: 0x00000dca
message_string:
The following services are dependent on the %1 service.
Stopping the %1 service will also stop these services.


message_identifier: 0x000013a9
message_string:
Printing Failed

"%1" failed to print on %2 on %3.

For more help use the print troubleshooter.


message_identifier: 0x000013a8
message_string:
The error code is %1.
There was an error retrieving the message. Make sure the file
NET.MSG is available.


message_identifier: 0x00000982
message_string:
A user's session with this server has been deleted
because the user's logon hours are no longer valid.


message_identifier: 0x00000a97
message_string:
Unable to create offline join information. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required.


message_identifier: 0x0000158d
message_string:
The computer or domain %1 trusts domain %2.  (This may be an indirect
trust.)  However, %2 is not a valid name for a trusted domain.
The name of the trusted domain should be changed to a valid name.


message_identifier: 0x0000158a
message_string:
The computer has rebooted from a bugcheck.  The bugcheck was:
%1.
%2
A full dump was not saved.


message_identifier: 0x0000158c
message_string:
The computer or domain %1 trusts domain %2.  (This may be an indirect
trust.)  However, %1 and %2 have the same machine security identifier
(SID).  NT should be re-installed on either %1 or %2.


message_identifier: 0x00000a9d
message_string:
Unable to load the specified offline registry hive. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required.


message_identifier: 0x00000a9c
message_string:
Could not verify the current machine's hostname against the saved value in the join completion information.


message_identifier: 0x00001588
message_string:
The server %1 and %2 both claim to be the primary domain
controller for the %3 domain. One of the servers should be
demoted or removed from the domain.


message_identifier: 0x00001589
message_string:
The computer %1 tried to connect to the server %2 using
the trust relationship established by the %3 domain. However, the
computer lost the correct security identifier (SID)
when the domain was reconfigured. Reestablish the trust
relationship.


message_identifier: 0x00001587
message_string:
The servers %1 and  %3 both claim to be an NT Domain Controller for
the %2 domain. One of the servers should be removed from the
domain because the servers have different security identifiers
(SID).


message_identifier: 0x00001583
message_string:
The %1 Log is full.  If this is the first time you have seen this
message, take the following steps:%n
1. Click Start, click Run, type "eventvwr", and then click OK.%n
2. Click %1, click the Action menu, click Clear All Events, and then click No.
%n
If this dialog reappears, contact your helpdesk or system administrator.


message_identifier: 0x00000cb3
message_string:
Initialization failed because of an invalid line in the
configuration file %1. The invalid line is the data.


message_identifier: 0x00000cb6
message_string:
The files do not fit to the boot-block configuration
file %1. Change the BASE and ORG definitions or the order
of the files.


message_identifier: 0x00000cb5
message_string:
The file %1 has been changed after initialization.
The boot-block loading was temporarily terminated.


message_identifier: 0x00000cbb
message_string:
The fault-tolerance error-log file, LANROOT\LOGS\FT.LOG, had the
update in progress bit set upon opening, which means that the
system crashed while working on the error log.


message_identifier: 0x000014b6
message_string:
The data descriptor array specified in the network control block (NCB) is
invalid.  The NCB is the data.


message_identifier: 0x000014b5
message_string:
Illegal network control block (NCB) buffer length on SEND DATAGRAM,
SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS.
The NCB is the data.


message_identifier: 0x000014b9
message_string:
A network control block (NCB) command timed-out.  The session may have
terminated abnormally.  The NCB is the data.


message_identifier: 0x000014b8
message_string:
The message correlator specified in the network control block (NCB) is
invalid.  The NCB is the data.


message_identifier: 0x000014bd
message_string:
No resource was available in the network adapter.
The network control block (NCB) request was refused.  The NCB is the data.


message_identifier: 0x000014bc
message_string:
The session number specified in the network control block (NCB) is not active.
The NCB is the data.


message_identifier: 0x000008c5
message_string:
The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.


message_identifier: 0x00000a8b
message_string:
An attempt to resolve the DNS name of a domain controller in the domain being joined has failed.  Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windows Help.


message_identifier: 0x00000a89
message_string:
The specified computer account could not be found. Contact an administrator to verify the account is in the domain. If the account has been deleted unjoin, reboot, and rejoin the domain.


message_identifier: 0x00000a88
message_string:
The specified computer name is incompatible with the default language used on the domain controller.


message_identifier: 0x0000110f
message_string:
Type the domain or server where you want to change a password, or
press ENTER if it is for domain %1: %0.


message_identifier: 0x000008de
message_string:
The computer name could not be added as a message alias.  The name may already exist on the network.


message_identifier: 0x00001691
message_string:
Netlogon got the following error while trying to get the subnet to site
mapping information from the DS: %n%1


message_identifier: 0x00001692
message_string:
'%1' tried to determine its site by looking up its IP address ('%2')
in the Configuration\Sites\Subnets container in the DS.  No subnet matched
the IP address.  Consider adding a subnet object for this IP address.


message_identifier: 0x00001693
message_string:
The site name for this computer is '%1'.  That site name is not a valid
site name.  A site name must be a valid DNS label.
Rename the site to be a valid name.


message_identifier: 0x00001694
message_string:
The subnet object '%1' appears in the Configuration\Sites\Subnets
container in the DS.  The name is not syntactically valid.  The valid
syntax is xx.xx.xx.xx/yy where xx.xx.xx.xx is a valid IP subnet number
and yy is the number of bits in the subnet mask.

Correct the name of the subnet object.


message_identifier: 0x00001695
message_string:
Dynamic registration or deletion of one or more DNS records associated with DNS
domain '%1' failed.  These records are used by other computers to locate this
server as a domain controller (if the specified domain is an Active Directory
domain) or as an LDAP server (if the specified domain is an application partition).

%n%nPossible causes of failure include:

%n- TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers
%n- Specified preferred and alternate DNS servers are not running
%n- DNS server(s) primary for the records to be registered is not running
%n- Preferred or alternate DNS servers are configured with wrong root hints
%n- Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration

%n%nUSER ACTION

%nFix possible misconfiguration(s) specified above and initiate registration or deletion of
the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain
controller or by restarting Net Logon service on the domain controller.


message_identifier: 0x00001696
message_string:
Dynamic registration or deregistration of one or more DNS records failed with the following error: %n%1


message_identifier: 0x00001697
message_string:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2
is not responsive.  The current RPC call from Netlogon on \\%3 to %1 has been cancelled.


message_identifier: 0x00001698
message_string:
Site '%2' does not have any Domain Controllers for domain '%3'.
Domain Controllers in site '%1' have been automatically
selected to cover site '%2' for domain '%3' based on configured
Directory Server replication costs.


message_identifier: 0x0000169a
message_string:
Site '%2' does not have any Global Catalog servers for forest '%3'.
Global Catalog servers in site '%1' have been automatically
selected to cover site '%2' for forest '%3' based on configured
Directory Server replication costs.


message_identifier: 0x0000169c
message_string:
Attempt to update HOST Service Principal Names (SPNs) of the computer
object in Active Directory failed. The updated values were '%1' and '%2'.
The following error occurred: %n%3


message_identifier: 0x0000169d
message_string:
Attempt to update DNS Host Name of the computer object
in Active Directory failed. The updated value was '%1'.
The following error occurred: %n%2


message_identifier: 0x0000169e
message_string:
No suitable Domain Controller is available for domain %1.
An NT4 or older domain controller is available but it cannot
be used for authentication purposes in the Windows 2000 or newer
domain that this computer is a member of.
The following error occurred:%n%2


message_identifier: 0x0000169f
message_string:
The domain of this computer, %1 has been downgraded from Windows 2000
or newer to Windows NT4 or older. The computer cannot function properly
in this case for authentication purposes. This computer needs to rejoin
the domain.
The following error occurred:%n%2


message_identifier: 0x00001671
message_string:
Client with computer name %1 failed to acknowledge receipt of the
boot data.  Remote boot of this client was not completed.


message_identifier: 0x00001677
message_string:
Client with computer name %1 was not booted because the boot block
configuration file %2 for this client does not contain boot block
line and/or loader line.


message_identifier: 0x00001674
message_string:
Client with computer name %1 was not booted due to insufficient memory
at the remote boot server.


message_identifier: 0x00001675
message_string:
Client with computer name %1 will be booted without using checksums
because checksum for file %2 could not be calculated.


message_identifier: 0x00000c19
message_string:
This computer is configured to be the primary domain controller of its domain.
However, the computer %1 is currently claiming to be the primary domain controller
of the domain.


message_identifier: 0x00000c17
message_string:
This computer is configured as a member of a workgroup, not as
a member of a domain. The Netlogon service does not need to run in this
configuration.


message_identifier: 0x00000c1f
message_string:
The service failed to release the long-term lock on the
segment for network control blocks (NCBs). The error code is the data.


message_identifier: 0x00000c1e
message_string:
The service failed to obtain a long-term lock on the
segment for network control blocks (NCBs). The error code is the data.


message_identifier: 0x0000168f
message_string:
The dynamic deletion of the DNS record '%1' failed on the following DNS server:

%n%nDNS server IP address: %3
%nReturned Response Code (RCODE): %4
%nReturned Status Code: %5

%n%nUSER ACTION

%nTo prevent remote computers from connecting unnecessarily to the domain controller,
delete the record manually or troubleshoot the failure to dynamically delete the
record. To learn more about debugging DNS, see Help and Support Center.

%n%nADDITIONAL DATA
%nError Value: %2


message_identifier: 0x0000168e
message_string:
The dynamic registration of the DNS record '%1' failed on the following DNS server:

%n%nDNS server IP address: %3
%nReturned Response Code (RCODE): %4
%nReturned Status Code: %5

%n%nFor computers and users to locate this domain controller, this record must be
registered in DNS.

%n%nUSER ACTION

%nDetermine what might have caused this failure, resolve the problem, and initiate
registration of the DNS records by the domain controller. To determine what might
have caused this failure, run DCDiag.exe. To learn more about DCDiag.exe, see Help
and Support Center. To initiate registration of the DNS records by this domain 
controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller
or restart Net Logon service. %n  Or, you can manually add this record to DNS, but it
is not recommended.

%n%nADDITIONAL DATA
%nError Value: %2


message_identifier: 0x0000168d
message_string:
The following DNS server that is authoritative for the DNS domain controller
locator records of this domain controller does not support dynamic DNS updates:

%n%nDNS server IP address: %1
%nReturned Response Code (RCODE): %2
%nReturned Status Code: %3

%n%nUSER ACTION

%nConfigure the DNS server to allow dynamic DNS updates or manually add the DNS
records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database.


message_identifier: 0x0000168a
message_string:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 from computer
%2 using account %4 failed.  %2 is declared to be a BDC in domain %3.
However, %2 tried to connect as either a DC in a trusted domain,
a member workstation in domain %3, or as a server in domain %3.
Use the Active Directory Users and Computers tool or Server Manager to remove the BDC account for %2.


message_identifier: 0x00001686
message_string:
Service failed to initialize from its database.  The database may be
missing or corrupted.  Service will attempt restoring the database
from the backup.


message_identifier: 0x00001684
message_string:
Service experienced error adding security accounts or setting
file permissions.  These accounts are the RPLUSER local group
and the user accounts for the individual RPL workstations.


message_identifier: 0x0000166a
message_string:
Netlogon has detected two machine accounts for server "%1".
The server can be either a Windows 2000 Server that is a member of the
domain or the server can be a LAN Manager server with an account in the
SERVERS global group.  It cannot be both.


message_identifier: 0x0000166b
message_string:
This domain has more global groups than can be replicated to a LanMan
BDC.  Either delete some of your global groups or remove the LanMan
BDCs from the domain.


message_identifier: 0x0000166f
message_string:
Service experienced a severe error and can no longer provide remote boot
for 3Com 3Start remote boot clients.


message_identifier: 0x00001668
message_string:
Replication of the %1 Secret "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001661
message_string:
Replication of the %1 Domain Object "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001663
message_string:
Replication of the %1 Local Group "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001662
message_string:
Replication of the %1 Global Group "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001665
message_string:
Replication of the %1 Policy Object "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001664
message_string:
Replication of the %1 User "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001667
message_string:
Replication of the %1 Account Object "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00001666
message_string:
Replication of the %1 Trusted Domain Object "%2" from primary domain controller
%3 failed with the following error: %n%4


message_identifier: 0x00000f4d
message_string:
The name specified for the user's home directory (%1) is not a universal naming convention (UNC) name.


message_identifier: 0x00000f47
message_string:
The current local clock is %1
Do you want to set the local computer's time to match the
time at %2? %3: %0


message_identifier: 0x00001658
message_string:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2
failed because the computer %3 does not have a local security database account.


message_identifier: 0x00001659
message_string:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2
failed because the Domain Controller did not have an account %4
needed to set up the session by this computer %3.

%n%nADDITIONAL DATA
%nIf this computer is a member of or a Domain Controller in the specified domain, the
aforementioned account is a computer account for this computer in the specified domain.
Otherwise, the account is an interdomain trust account with the specified domain.


message_identifier: 0x00001654
message_string:
The partial synchronization replication of the %1 database from the
primary domain controller %2 failed with the following error: %n%3


message_identifier: 0x00001655
message_string:
The full synchronization replication of the %1 database from the
primary domain controller %2 completed successfully.


message_identifier: 0x00001656
message_string:
The full synchronization replication of the %1 database from the
primary domain controller %2 failed with the following error: %n%3


message_identifier: 0x00001657
message_string:
This computer was not able to set up a secure session with a domain
controller in domain %1 due to the following: %n%2
%nThis may lead to authentication problems. Make sure that this
computer is connected to the network. If the problem persists,
please contact your domain administrator.

%n%nADDITIONAL INFO
%nIf this computer is a domain controller for the specified domain, it
sets up the secure session to the primary domain controller emulator in the specified
domain. Otherwise, this computer sets up the secure session to any domain controller
in the specified domain.


message_identifier: 0x00001651
message_string:
The full synchronization request from the server %1 completed
successfully. %2 object(s) has(have) been returned to
the caller.


message_identifier: 0x00001653
message_string:
The partial synchronization replication of the %1 database from the
primary domain controller %2 completed successfully. %3 change(s) is(are)
applied to the database.


message_identifier: 0x00000c38
message_string:
The server failed to register for the ReleaseMemory alert,
with recipient %1. The error code from
NetAlertStart is the data.


message_identifier: 0x00000c34
message_string:
The server failed to start. Either all three chdev
parameters must be zero or all three must be nonzero.


message_identifier: 0x00000c36
message_string:
The network %1 ran out of network control blocks (NCBs).  You may need to increase NCBs
for this network.  The following information includes the
number of NCBs submitted by the server when this error occurred:


message_identifier: 0x00000c37
message_string:
The server cannot create the %1 mailslot needed to send
the ReleaseMemory alert message.  The error received is:


message_identifier: 0x00000c30
message_string:
Initialization parameters controlling resource usage other
than net buffers are sized so that too much memory is needed.


message_identifier: 0x00000c3b
message_string:
Initialization failed because of a system execution failure on
path %1. There is not enough memory to start the process.
The system error code is the data.


message_identifier: 0x00000c3c
message_string:
Longterm lock of the server buffers failed.
Check swap disk's free space and restart the system to start the server.


message_identifier: 0x0000165a
message_string:
The session setup from the computer %1 failed to authenticate.
The name(s) of the account(s) referenced in the security database is
%2.  The following error occurred: %n%3


message_identifier: 0x0000165b
message_string:
The session setup from computer '%1' failed because the security database
does not contain a trust account '%2' referenced by the specified computer.

%n%nUSER ACTION

%nIf this is the first occurrence of this event for the specified computer
and account, this may be a transient issue that doesn't require any action
at this time.

If this is a Read-Only Domain Controller and '%2' is a legitimate machine
account for the computer '%1' then '%1' should be marked cacheable for this
location if appropriate or otherwise ensure connectivity to a domain controller 
capable of servicing the request (for example a writable domain controller).

Otherwise, the following steps may be taken to resolve this problem:

%n%nIf '%2' is a legitimate machine account for the computer '%1', then '%1'
should be rejoined to the domain.

%n%nIf '%2' is a legitimate interdomain trust account, then the trust should
be recreated.

%n%nOtherwise, assuming that '%2' is not a legitimate account, the following
action should be taken on '%1':

%n%nIf '%1' is a Domain Controller, then the trust associated with '%2' should be deleted.

%n%nIf '%1' is not a Domain Controller, it should be disjoined from the domain.


message_identifier: 0x0000164f
message_string:
The partial synchronization request from the server %1 completed
successfully. %2 changes(s) has(have) been returned to the
caller.


message_identifier: 0x00000ee9
message_string:
You have specified a value that is incompatible
with servers with down-level software. Please specify a lower value.


message_identifier: 0x00000ee6
message_string:
The syntax of this command is:

AT [id] [/DELETE]
AT time [/EVERY:date | /NEXT:date] command

The AT command schedules a program command to run at a
later date and time on a server.  It also displays the
list of programs and commands scheduled to be run.

You can specify the date as M,T,W,Th,F,Sa,Su or 1-31
for the day of the month.

You can specify the time in the 24 hour HH:MM format.


message_identifier: 0x00001646
message_string:
The Netlogon service could not add the RPC interface.  The
service was terminated. The following error occurred: %n%1


message_identifier: 0x00001644
message_string:
The Netlogon service could not initialize the replication data
structures successfully. The service was terminated.  The following
error occurred: %n%1


message_identifier: 0x00001649
message_string:
The change log cache maintained by the Netlogon service for %1
database changes is inconsistent. The Netlogon service is resetting
the change log.


message_identifier: 0x00001648
message_string:
The Netlogon service failed to register the service with the
service controller. The service was terminated. The following
error occurred: %n%1


message_identifier: 0x00000c21
message_string:
Initialization failed because of a system execution failure on
path %1. The system error code is the data.


message_identifier: 0x00000c26
message_string:
Initialization failed because of an open/create error on the
file %1. The system error code is the data.


message_identifier: 0x00000c24
message_string:
A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed.
The data shown is in this format:
DWORD  approx CS:IP of call to ioctl or fsctl
WORD   error code
WORD   ioctl or fsctl number


message_identifier: 0x00000c5f
message_string:
The workstation encountered an error while responding to an SSI revalidation request.
The function code and the error codes are the data.


message_identifier: 0x00000c5e
message_string:
The workstation encountered an error while trying to start the user accounts database.
The error code is the data.


# message_table_49_0x00000409

message_identifier: 0xb00002cb
message_string:
Task Compatibility module failed to delete  LSA store for upgrade. Additional Data: Error Value: %1.


message_identifier: 0xb0000146
message_string:
Task Scheduler did not launch task "%1"  because computer is running on batteries. User Action: If launching the task on batteries is required, change the respective flag in the task configuration.


message_identifier: 0x000002c1
message_string:
Task Scheduler failed to start directory monitoring for the Task Compatibility module. Additional Data: Error Value: %1.


message_identifier: 0x000002c0
message_string:
Task Scheduler failed to initialize LSA for starting the Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1.


message_identifier: 0xb0000137
message_string:
Task Scheduler failed to start Task Engine "%1"  process due to an error occurring in "%3" . Command="%2" . Additional Data: Error Value: %4.


message_identifier: 0xb00002c9
message_string:
Task Compatibility module failed to load task  "%1" for upgrade. Additional Data: Error Value: %2.


message_identifier: 0x000002ce
message_string:
Task scheduler was unable to upgrade the credential store from the Beta 2 version.  You may need to re-register any tasks that require passwords. Additional Data: Error Value: %1.


message_identifier: 0xb00002c6
message_string:
Task Compatibility module failed to upgrade existing tasks. Upgrade will be attempted again next time 'Task Scheduler' service starts. Additional Data: Error Value: %1.


message_identifier: 0x000002cc
message_string:
Task Compatibility module failed to upgrade existing scheduled tasks. Additional Data: Error Value: %1.


message_identifier: 0xb00002ca
message_string:
Task Compatibility module failed to register  task  "%1" for upgrade. Additional Data: Error Value: %2.


message_identifier: 0xb00100c9
message_string:
Task Scheduler successfully completed task "%1" , instance "%2" , action "%3" with return code %4.


message_identifier: 0xb0000086
message_string:
Task Engine "%1"  for user "%2" is approaching its preset limit of tasks. User Action: Reduce the number of tasks running in the specified user context.


message_identifier: 0xb0000080
message_string:
Task Scheduler did not launch task "%1" , because current time exceeds the configured task end time. User Action: Extend the end time boundary for the task if required.


message_identifier: 0xb0000083
message_string:
Task Scheduler failed to start task "%1" because the number of tasks in the task queue exceeding the quota currently configured to %2. User Action: Reduce the number of running tasks or increase the configured queue quota.


message_identifier: 0xb000012f
message_string:
Task Scheduler is shutting down Task Engine "%1"  due to an error in "%2" .  Additional Data: Error Value: %3.


message_identifier: 0xb0000132
message_string:
For Task Scheduler Task Engine "%1" , the thread pool failed to process the message. Additional Data: Error Value: %2.


message_identifier: 0xb0000133
message_string:
Task Scheduler service failed to connect to the Task Engine "%1"  process. Additional Data: Error Value: %2.


message_identifier: 0xb0000135
message_string:
Task Scheduler %1 tasks orphaned during Task Engine "%2"  shutdown. User Action: Find the process run by this task in the Task Manager and kill it manually.


message_identifier: 0xb00002cd
message_string:
Task Compatibility module failed to determine if upgrade is needed. Additional Data: Error Value: %1.


message_identifier: 0xb0000093
message_string:
Task Scheduler recovered sucessfully the image of task "%1" after a corruption occured during OS upgrade.


message_identifier: 0xb0000096
message_string:
Task Scheduler failed to subscribe for the event trigger for task "%1". Additional Data: Error Value: %2.


message_identifier: 0xb0000094
message_string:
Task Scheduler failed to recover the image of task "%1" after a corruption occured during OS upgrade. Additional Data: Error Value: 0x%2.


message_identifier: 0xb000013b
message_string:
Task Engine "%1"  process failed to connect to the Task Scheduler service. Additional Data: Error Value: %2.


message_identifier: 0xb000013c
message_string:
Task Engine "%1"  failed to send a message to the Task Scheduler service. Additional Data: Error Value: %2.


message_identifier: 0xb0000140
message_string:
Task Engine "%1"  received a message from Task Scheduler service requesting to stop task instance "%2" .


message_identifier: 0xb0000142
message_string:
Task Scheduler did not launch task "%1"  because instance "%2"  of the same task is already running.


message_identifier: 0xb0000144
message_string:
Task Scheduler queued instance "%2"  of task "%1"  and will launch it as soon as instance "%3"  completes.


message_identifier: 0xb0000147
message_string:
Task Scheduler stopped instance "%2"  of task "%1"  because the computer is switching to battery power.


message_identifier: 0xb0000149
message_string:
Task Scheduler terminated "%2"  instance of the "%1"  task due to exceeding the time allocated for execution, as configured in the task definition. User Action: Increase the configured task timeout or investigate external reasons for the delay.


message_identifier: 0xb00002c8
message_string:
Task Compatibility module failed to read  existing store to upgrade tasks. Additional Data: Error Value: %1.


message_identifier: 0xb00000cc
message_string:
Task Scheduler failed to retrieve the event triggering values for task "%1" . The event will be ignored. Additional Data: Error Value: %2.


message_identifier: 0xb00000cb
message_string:
Task Scheduler failed to launch action "%3" in instance "%2" of task "%1". Additional Data: Error Value: %4.


message_identifier: 0xb00002c4
message_string:
Task Compatibility module failed to set security descriptor "%1"  for task "%2" . Additional Data: Error Value: %3.


message_identifier: 0x00000198
message_string:
Task Scheduler service failed to initialize idle state detection module. Idle tasks may not be started as required. Additional Data: Error Value: %1.


message_identifier: 0x00000199
message_string:
Task Scheduler service failed to initialize time change notification. System time updates may not be picked by the service and task schedules may not be updated. Additional Data: Error Value: %1.


message_identifier: 0x00000194
message_string:
Task Scheduler service has encountered RPC initialization error in "%1". Additional Data: Error Value: %2.


message_identifier: 0x00000191
message_string:
Task Scheduler service failed to start due to an error in "%1" . Additional Data: Error Value: %2.


message_identifier: 0xb000014b
message_string:
Task Scheduler will continue to execute Instance "%2"  of task "%1"  even after the designated timeout, due to a failure to create the timeout mechanism. Additional Data: Error Value: %3.


message_identifier: 0x0000019c
message_string:
Task Scheduler service failed to launch tasks triggered by computer startup. Additional Data: Error Value: %1.


message_identifier: 0xb0000068
message_string:
Task Scheduler failed to log on "%1" . Failure occurred in "%2" . User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: %3.


message_identifier: 0xb0000067
message_string:
Task Scheduler failed to start instance "%2" of "%1"  task for user "%3" . Additional Data: Error Value: %4.


message_identifier: 0xb00000ca
message_string:
Task Scheduler failed to complete task "%1" , instance "%2" , action "%3" . Additional Data: Error Value: %4.


message_identifier: 0xb00000cd
message_string:
Task Scheduler failed to match the pattern of events for task "%1" . The events will be ignored. Additional Data: Error Value: %2.


message_identifier: 0xb000019a
message_string:
Task Scheduler service failed to set a wakeup timer. As a result, some scheduled tasks may not run while the system is suspended. Additional Data: Error Value: %1.


message_identifier: 0xb0000084
message_string:
Task Scheduler task launching queue quota is approaching its preset limit of tasks currently configured to %1. User Action: Reduce the number of running tasks or increase the configured queue quota.


message_identifier: 0xb0000085
message_string:
Task Scheduler failed to start task %1" in TaskEngine "%2"  for user "%3". User Action: Reduce the number of tasks running in the specified user context.


message_identifier: 0xb0000079
message_string:
Task Scheduler launched "%3"  instance of task "%1"  due to user "%2"  disconnecting from the console trigger.


message_identifier: 0xb0000078
message_string:
Task Scheduler launched "%3"  instance of task "%1"  due to user "%2"  connecting to the console trigger.


message_identifier: 0x000002bf
message_string:
Task Scheduler failed to initialize Net Schedule API for starting the Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1.


message_identifier: 0xb0000074
message_string:
Task Scheduler validated the configuration for task "%1" , but credentials could not be stored. User Action: Re-register the task ensuring the credentials are valid. Additional Data: Error Value: %2.


message_identifier: 0x000002bd
message_string:
Task Scheduler service failed to start Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1.


message_identifier: 0x000002be
message_string:
Task Scheduler failed to initialize the RPC server for starting the Task Compatibility module. Tasks may not be able to register on previous Window versions. Additional Data: Error Value: %1.


message_identifier: 0xb0000071
message_string:
Task registered task "%1" , but not all specified triggers will start the task. User Action: Ensure all the task triggers are valid as configured. Additional Data: Error Value: %2.


message_identifier: 0xb0000070
message_string:
Task Scheduler could not start task "%1"  because the network was unavailable. User Action: Ensure the computer is connected to the required network as specified in the task. If the task does not require network presence, remove the network condition from the task configuration.


message_identifier: 0xb0000073
message_string:
Task Scheduler failed to roll back a transaction when updating or deleting a task. Additional Data: Error Value: %1.


message_identifier: 0xb0000072
message_string:
Task Scheduler could not launch task "%1"  as scheduled. Instance "%2"  is started now as required by the configuration option to start the task when available, if schedule is missed.


message_identifier: 0xb00002c2
message_string:
Task Compatibility module failed to update task "%1"  to the required status %2. Additional Data: Error Value: %3.


message_identifier: 0xb00002c7
message_string:
Task Compatibility module failed to upgrade NetSchedule account "%1" . Additional Data: Error Value: %2.


message_identifier: 0xb000007e
message_string:
Task Scheduler failed to execute task "%1" . Attempting to restart. Additional Data: Error Value: %2.


message_identifier: 0xb000007d
message_string:
Task Scheduler launched "%3"  instance of task "%1"  due to user "%2"  unlocking the computer trigger.


message_identifier: 0xb000007f
message_string:
Task Scheduler failed to execute task "%1"  due to a shutdown race condition. Attempting to restart.


message_identifier: 0xb000007a
message_string:
Task Scheduler launched "%3"  instance of task "%1"  due to user "%2"  remotely connecting trigger.


message_identifier: 0xb000014c
message_string:
Task Scheduler did not launch task "%1"  because user "%2" was not logged on when the launching conditions were met. User Action: Ensure user is logged on or change the task definition to allow launching when user is logged off.


message_identifier: 0xb000007c
message_string:
Task Scheduler launched "%3"  instance of task "%1"  due to user "%2"  locking the computer trigger.


message_identifier: 0xb000007b
message_string:
Task Scheduler launched "%3"  instance of task "%1"  due to user "%2"  remotely disconnecting trigger.


message_identifier: 0xb000014d
message_string:
Task Scheduler did not launch task "%1"  because target session is RemoteApp session. User Action: If launching the task on RemoteApp sessions is required, change the respective flag in the task configuration.


# message_table_50_0x00000409

message_identifier: 0xc0060007
message_string:
No IRQ available for status change interrupts for PCMCIA controller: this controller will not be able to detect hot insertions/removals of PC-Cards.


message_identifier: 0xc0060006
message_string:
The IRQ of %2 was selected for a network PCMCIA PCCARD.  This IRQ is not supported for PCCARDs on this system.  For network service, please change the configuration.


message_identifier: 0xc0060001
message_string:
A memory window for reading the PCCARD configuration could not be found.  No PCMCIA PCCARDS were configured.


# message_table_51_0x00000409

message_identifier: 0x000003ec
message_string:
The Remote Desktop Session Host server cannot issue a client license.  It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client's computer.


message_identifier: 0x400003f4
message_string:
Remote session from client name %1 exceeded the maximum allowed failed logon attempts. The session was forcibly terminated.


message_identifier: 0x000003f3
message_string:
The remote session could not be established from remote desktop client %1 because its temporary license has expired.


message_identifier: 0xc000046a
message_string:
The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.


message_identifier: 0xb0000473
message_string:
The roaming user profile cache manager for Terminal Services could not start because an incorrect value was specified for the maximum cache size. Error Code: %1


message_identifier: 0xb0000475
message_string:
The "Limit the size of the entire roaming user profile cache" Group Policy setting has been disabled, but the roaming user profile cache manager for Terminal Services has encountered a problem. Error Code: %1


message_identifier: 0xb0000474
message_string:
The "Limit the size of the entire roaming user profile cache" Group Policy setting has been enabled, but the roaming user profile cache manager for Terminal Services has encountered a problem. Error Code: %1


message_identifier: 0xb0000477
message_string:
The "Limit the size of the entire roaming user profile cache" Group Policy setting has been disabled.


message_identifier: 0xb0000476
message_string:
The "Limit the size of the entire roaming user profile cache" Group Policy setting has been enabled.


message_identifier: 0xb0000479
message_string:
The roaming user profile cache manager for Terminal Services deleted the roaming user profile for the user %1 because the roaming user profile cache exceeded the %2 gigabyte limit.


message_identifier: 0xb0000478
message_string:
The roaming user profile cache manager for Terminal Services could not delete the roaming user profile for the user %1. The roaming user profile cache might still exceed the %2 gigabyte limit. Error Code: %3


message_identifier: 0xc000041a
message_string:
The Terminal Server listener %1 is configured with inconsistent authentication and encryption settings. The Encryption Level is currently set to %2 and Security Layer is set to %3. These settings were automatically corrected to allow connections to proceed. Please change the Security Layer and Encryption Level settings in Group Policy or by using the Terminal Services Configuration tool in the Administrative Tools folder.


message_identifier: 0xc000041b
message_string:
The Terminal Server is configured to use SSL with user selected certificate, however, no usable certificate was found on the server. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder.


message_identifier: 0xc000041c
message_string:
The Terminal Server is configured to use a certificate that will expire in %2 days. %1 The SHA1 hash of the certificate is in the event data. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder.


message_identifier: 0xc000041d
message_string:
The Terminal Server is configured to use a certificate that is expired. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder.


message_identifier: 0xc000041e
message_string:
The Terminal Server is configured to use a certificate that does not contain an Enhanced Key Usage attribute of Server Authentication. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder.


message_identifier: 0xc000041f
message_string:
The Terminal Server is configured to use a certificate but is unable to access the private key associated with this certificate. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder.


message_identifier: 0xc0000424
message_string:
The Terminal Services User Home Directory was not set because the path specified does not exist or not accessible. The default Home Directory Path was used instead. User Name: %1 Domain: %2


message_identifier: 0xc0000413
message_string:
The Remote Desktop Session Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Session Host server is a member of the Terminal Server Computers group on the license server.


message_identifier: 0xc000046b
message_string:
The Remote Desktop Session Host server could not contact the Remote Desktop license server %1. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS.


message_identifier: 0xc0000404
message_string:
The remote session could not be established from remote desktop client %1 because its license could not be renewed.


message_identifier: 0xc0000428
message_string:
The terminal server cannot install a new template-based certificate to be used for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption. The following error occured: %1.


message_identifier: 0xc0000400
message_string:
TermService clustering failed to initialize because the Session Directory Provider failed to initialize, hresult=%1.


message_identifier: 0xc0000425
message_string:
Remote Desktop Session Host server was unable to retrieve users Licensing information from AD. Error %1


message_identifier: 0xb00003ee
message_string:
The terminal server received large number of incomplete connections.  The system may be under attack.


message_identifier: 0xc0000427
message_string:
A new template-based certificate to be used by the terminal server for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption has been installed. The name for this certificate is %1. The SHA1 hash of the certificate is provided in the event data.


message_identifier: 0xc0000426
message_string:
The terminal server is configured to use a template-based certificate for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption, but the subject name on the certificate is invalid. %1 The SHA1 hash of the certificate is in the event data. Therefore, the default certificate will be used by the terminal server for authentication. To resolve this issue, make sure that template used to create this certificate is configured to use DNS name as subject name
.


message_identifier: 0xc0000421
message_string:
The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL connections. The relevant status code was %1.


message_identifier: 0xc0000420
message_string:
A new self signed certificate to be used for Terminal Server authentication on SSL connections was generated. The name on this certificate is %1. The SHA1 hash of the certificate is in the event data.


message_identifier: 0xc0000423
message_string:
The Terminal Server authentication certificate configuration data was invalid and the service reset it. If the computer was configured to use a specific certificate, please verify it is available in the certificate store and use the administrative tools to select it again.


message_identifier: 0xb000047a
message_string:
Remote Desktop Services: Remote control session initiated:%n%n%1 initiated a remote control session:%nUser: %2%nDomain: %3


message_identifier: 0xb000047b
message_string:
Remote Desktop Services: Remote control session connection succeeded:%n%n%1 initiated a remote control session:%nUser: %2%nDomain: %3


message_identifier: 0xb000047e
message_string:
Remote Desktop Services: User config data have been merged:%n%nUser: %1%nDomain: %2%nSource Network Address: %3


message_identifier: 0xb000047d
message_string:
Remote Desktop Services: User authentication succeeded:%n%nUser: %1%nDomain: %2%nSource Network Address: %3


message_identifier: 0xc0000469
message_string:
The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed licenses.  A RD Licensing server is required for continuous operation.  A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.


message_identifier: 0x0000042d
message_string:
The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Session Host server has not been configured. Licensing mode must be configured for continuous operation.


message_identifier: 0xc000046d
message_string:
The certificate issued by the Remote Desktop license server to the Remote Desktop Session Host server is not valid. The license server will not issue Terminal Services client access licenses to clients connecting to the Remote Desktop Session Host server. To resolve this issue, delete the certificate on the Remote Desktop Session Host server and then restart the Remote Desktop Services service.


message_identifier: 0xc0000422
message_string:
The Terminal Server has failed to replace the expired self signed certificate used for Terminal Server authentication on SSL connections. The relevant status code was %1.


message_identifier: 0xb000047c
message_string:
Remote Desktop Services: Remote control session connection failed:%n%n%1 initiated a remote control session:%nUser: %2%nDomain: %3


message_identifier: 0xc000042e
message_string:
A logon request was denied because the terminal server is currently in drain mode and therefore not accepting new user logons. To configure the server to allow new user logons, use the Terminal Services Configuration tool.


message_identifier: 0xc0000468
message_string:
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses.  A RD Licensing server is required for continuous operation.  A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.


message_identifier: 0xc000042f
message_string:
A connection request was denied because the terminal server is currently configured to not accept connections. To configure the server to allow connections, use the chglogon command-line tool.


message_identifier: 0xc000046c
message_string:
The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Session Host server.


message_identifier: 0xc000042b
message_string:
The terminal server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: %1.


message_identifier: 0xb0000472
message_string:
The roaming user profile cache manager for Terminal Services could not start because an incorrect value was specified for the monitoring interval. Error Code: %1


message_identifier: 0xc0000416
message_string:
Failed to load Terminal Server Profile path. Note that the profile path must be less than 256 characters in length. User Name: %1 Domain: %2


message_identifier: 0xc0000429
message_string:
The template-based certificate that is being used by the terminal server for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption has expired and cannot be replaced by the terminal server. The following error occurred: %1.


# message_table_52_0x00000409

message_identifier: 0x000003ee
message_string:
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. %2


message_identifier: 0x000003ec
message_string:
The following DNS server(s) were successfully validated as active servers that can service this client. %2


message_identifier: 0xb000eac5
message_string:
SourceAddress: %1 SourcePort: %2 DestinationAddress: %3 DestinationPort: %4 Protocol: %5 ReferenceContext: %6


message_identifier: 0x000003f2
message_string:
The primary DNS suffix for this machine (%1) does not match the Active Directory domain (%2) that it is currently joined to.


message_identifier: 0x000003f0
message_string:
The primary DNS suffix for this machine is missing. In the absence of a primary DNS suffix, short unqualified names may not resolve through DNS


message_identifier: 0xb0000403
message_string:
DNS Name resolution for the name, %1, failed because the client was unable to contact DNS servers. At least one of the interfaces is not in a private network and name resolution will not fall back to LLMNR or NetBIOS


message_identifier: 0xb00003f9
message_string:
The DNS server's response to a query for name %1 indicates that no records of the type queried are available, but could indicate that other records for the same name are present.


message_identifier: 0xb00003f8
message_string:
A name not found error was returned for the name %1. Check to ensure that the name is correct. The response was sent by the server at %3.


message_identifier: 0x000003ff
message_string:
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule %1 failed with error %2


message_identifier: 0xb00003e8
message_string:
There are currently no IPv4 DNS servers configured for any interface on this host. Please configure DNS server settings, or renew your dynamic IP settings.


message_identifier: 0xb00003fa
message_string:
The response for the query %1 was a Link Local IP address %3. The response was sent by the server at %5.


message_identifier: 0xb00003fc
message_string:
Read DNS Name Resolution Policy Table: Key Name %1: DNSSEC Settings: DnsSecValidationRequired %2, DnsQueryOverIPSec %3, DnsEncryption %4 Direct Access Settings: DirectAccessServerList %5, EnableRemoteIPSEC %6  RemoteEncryption %7 ProxyType %8 ProxyName %9


message_identifier: 0xb00003fb
message_string:
There are currently no IPv6 DNS servers configured for any interface on this host. Please configure DNS server settings, or renew your dynamic IP settings.


message_identifier: 0xb00003fd
message_string:
Matched Effective policy for query name %1: Key Name %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8


# message_table_53_0x00000409

message_identifier: 0xb0000004
message_string:
The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair this file because a repair attempt is already underway for the same file.


message_identifier: 0xb0000005
message_string:
The system file %1 was reported as being corrupted but Windows determined that the file is not actually damaged. It may have been repaired already.


message_identifier: 0xb0000007
message_string:
The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows successfully repaired the damaged file.


message_identifier: 0xb0000001
message_string:
The file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair %1 because it is not a protected system file.


message_identifier: 0xb0000002
message_string:
The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows will not attempt to repair %1 because too many corrupted files have been detected recently.  Frequent corruptions may indicate a problem with the disk on this computer.


message_identifier: 0xb0000003
message_string:
The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair this file because the same file has been repaired too many times over a recent period of time.


message_identifier: 0xb0000009
message_string:
The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file, but the operation was cancelled before it could be completed.  Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0x0000000b
message_string:
The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows could not attempt to repair %1 because a previous repair operation was pended.  Reboot the computer and run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0x0000000c
message_string:
Windows detected that program file %1 is corrupted, causing application %2 to stop working. To restore the file, reinstall %3 version %4.


message_identifier: 0x0000000a
message_string:
The system file %1 may be corrupted, but Windows could not determine if the file was actually damaged (error code %3). No repair action was taken. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0x0000000e
message_string:
The file %1 may be corrupted, which may have caused the application %2 to stop working. Windows did not attempt to repair %1 because it could not find its corresponding installer package.


message_identifier: 0xb0000011
message_string:
The program file %1 was reported as being possibly corrupted, causing application %2 to stop working. Windows performed additional diagnostics and determined that the file is not an executable image. To avoid potential user data loss, Windows will not attempt to repair the file.


message_identifier: 0xb0000010
message_string:
Windows detected that program file %1 is corrupted, causing application %2 to stop working. Reinstalling %3 version %4 may repair the file. However, Windows is not launching a %3 reinstallation because that product has already been reinstalled too many times recently.


message_identifier: 0xb1000001
message_string:
The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows could not repair this file automatically (error code %3). Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0xb1000003
message_string:
The system file %1 is corrupted, which may have caused the application %2 to stop working. Windows could not attempt to repair %1 because the operation was disabled by group policy.  Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0xb1000002
message_string:
The system file %1 may be corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file, but the operation was disabled by group policy.  Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0xb000000d
message_string:
The program file %1 was reported as being possibly corrupted, causing application %2 to stop working. Windows performed additional diagnostics and determined that the file is not actually damaged.


message_identifier: 0xb000000f
message_string:
Windows detected that program file %1 is corrupted, causing application %2 to stop working. Reinstalling %3 version %4 may repair the file. However, Windows is not launching a %3 reinstallation because too many product reinstalls have run recently.


message_identifier: 0x00000006
message_string:
The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows was unable to repair this file (error code %3).  Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.


message_identifier: 0x00000008
message_string:
The system file %1 was corrupted, which may have caused the application %2 to stop working. Windows attempted to repair the file. A reboot is required to finish this repair.


# message_table_54_0x00000409

message_identifier: 0x80000434
message_string:
The reason supplied by user %6 for the last unexpected shutdown of this computer is: %1%n
Reason Code: %2%n
Problem ID: %3%n
Bugcheck String: %4%n
Comment: %5


message_identifier: 0x40000430
message_string:
Error Instrument: ProcessName: %1  WindowTitle: %2  MsgCaption: %3  MsgText: %4  CallerModuleName: %5  BaseAddr: %6  ImageSize: %7   ReturnAddr: %8


message_identifier: 0x80000432
message_string:
The process %1 has initiated the %5 of computer %2 on behalf of user %7 for the following reason: %3%n
Reason Code: %4%n
Shutdown Type: %5%n
Comment: %6


# message_table_55_0x00000415

message_identifier: 0xc0050004
message_string:
Partycja podrzędna %2 nie określiła wersji magistrali maszyny wirtualnej. W tej instalacji gościa należy zainstalować magistralę maszyny wirtualnej o wersji protokołu %3.


message_identifier: 0xc0050005
message_string:
Partycja podrzędna %2 zbyt wiele razy określiła nieprawidłową wersję magistrali maszyny wirtualnej. Kolejne niepowodzenia dotyczące tej partycji nie będą rejestrowane.


message_identifier: 0xc0050002
message_string:
Partycja nadrzędna używa innej wersji magistrali maszyny wirtualnej. W tej instalacji gościa należy zainstalować zgodną wersję magistrali maszyny wirtualnej.


message_identifier: 0xc0050003
message_string:
Partycja podrzędna %2 używa innej wersji magistrali maszyny wirtualnej (%3) niż to wystąpienie nadrzędne (%4). W tej instalacji gościa należy zainstalować zgodną wersję magistrali maszyny wirtualnej.


message_identifier: 0xc0050001
message_string:
Wykryto warstwę HAL programowalnego kontrolera przerwań (PIC). Aby uruchomić magistralę maszyny wirtualnej, należy zaktualizować system, tak aby używał warstwy HAL zaawansowanego programowalnego kontrolera przerwań (APIC).


# message_table_55_0x00000407

message_identifier: 0xc0050004
message_string:
Die untergeordnete Partition %2 hat keine VMBus-Version bereitgestellt. Sie müssen für diese Gastinstallation VMBus mit Protokollversion %3 installieren.


message_identifier: 0xc0050005
message_string:
Die untergeordnete Partition %2 hat zu häufig falsche VMBus-Versionen bereitgestellt. Weitere Fehler werden für diese Partition nicht protokolliert.


message_identifier: 0xc0050002
message_string:
Die übergeordnete Partition verwendet eine andere VMBus-Version. Sie müssen für diese Gastinstallation eine übereinstimmende VMBus-Version installieren.


message_identifier: 0xc0050003
message_string:
Die untergeordnete Partition %2 verwendet eine andere VMBus-Version (%3) als die übergeordnete Instanz (%4). Sie müssen für diese Gastinstallation eine übereinstimmende VMBus-Version installieren.


message_identifier: 0xc0050001
message_string:
Es wurde eine PIC-HAL erkannt. Um VMBus zu starten, muss das System aktualisiert werden, damit eine APIC-HAL verwendet wird.


# message_table_55_0x00000405

message_identifier: 0xc0050004
message_string:
Podřízený oddíl %2 neuváděl žádnou verzi sběrnice VMBus. V této instalaci hostovaného počítače je nutné nainstalovat sběrnici VMBus s verzí protokolu %3.


message_identifier: 0xc0050005
message_string:
U podřízeného oddílu %2 byla příliš mnohokrát zadána nesprávná verze sběrnice VMBus. Následující selhání nebudou pro daný oddíl protokolována.


message_identifier: 0xc0050002
message_string:
Nadřazený oddíl používá jinou verzi sběrnice VMBus. V této instalaci hostovaného počítače je třeba nainstalovat odpovídající verzi sběrnice VMBus.


message_identifier: 0xc0050003
message_string:
Podřízený oddíl %2 používá jinou verzi sběrnice VMBus (%3) než tato nadřazená instance (%4). V této instalaci hostovaného počítače je třeba nainstalovat odpovídající verzi sběrnice VMBus.


message_identifier: 0xc0050001
message_string:
Byla zjištěna vrstva hal PIC. Aby bylo možné spustit sběrnici VMBus, je nutné aktualizovat systém na používání vrstvy hal APIC.


# message_table_55_0x00000411

message_identifier: 0xc0050003
message_string:
子パーティション %2 で、この親インスタンス (%4) とは異なる VMBus バージョン (%3) が使用されています。このゲスト インストールで、対応するバージョンの VMBus をインストールする必要があります。


# message_table_55_0x00000410

message_identifier: 0xc0050004
message_string:
Nessuna versione di VMBus nella partizione figlio %2. Installare nell'installazione guest VMBus con versione di protocollo %3. 


message_identifier: 0xc0050005
message_string:
La partizione figlio %2 ha fornito troppe volte versioni di VMBus non corrette. Per questa partizione non verranno registrati ulteriori errori.


message_identifier: 0xc0050002
message_string:
La partizione padre utilizza un'altra versione di VMBus. Installare nell'installazione guest una versione di VMBus corrispondente.


message_identifier: 0xc0050003
message_string:
La partizione figlio %2 utilizza una  versione di VMBus (%3) diversa da quella utilizzata dall'istanza padre (%4). Installare nell'installazione guest una versione di VMBus corrispondente.


message_identifier: 0xc0050001
message_string:
HAL PIC rilevato. Per avviare VMBus, è necessario aggiornare il sistema per l'utilizzo di un HAL APIC.


# message_table_55_0x00000413

message_identifier: 0xc0050004
message_string:
De onderliggende partitie %2 heeft geen VMBus-versie opgegeven. U moet VMBus met protocolversie %3 installeren in deze gastinstallatie.


message_identifier: 0xc0050005
message_string:
De onderliggende partitie %2 heeft te vaak verkeerde VMBus-versies opgegeven. Volgende fouten voor die partitie worden niet in het logboek geregistreerd.


message_identifier: 0xc0050002
message_string:
De bovenliggende partitie gebruikt een andere VMBus-versie. U moet dezelfde VMBus-versie installeren in deze gastinstallatie.


message_identifier: 0xc0050003
message_string:
De onderliggende partitie %2 gebruikt een andere VMBus-versie (%3) dan dit bovenliggende exemplaar (%4). U moet dezelfde VMBus-versie installeren in deze gastinstallatie.


message_identifier: 0xc0050001
message_string:
PIC HAL aangetroffen. Als u VMBus wilt starten, moet u uw systeem bijwerken voor het gebruik van een APIC HAL.


# message_table_55_0x00000c0a

message_identifier: 0xc0050004
message_string:
La partición secundaria %2 no proporciona la versión de VMBus. Debe instalar VMBus con la versión de protocolo %3 en esta instalación de invitado.


message_identifier: 0xc0050005
message_string:
La partición secundaria %2 proporciona versiones de VMBus incorrectas demasiadas veces. No se registrarán los errores sucesivos para esa partición.


message_identifier: 0xc0050002
message_string:
La partición primaria usa una versión distinta de VMBus. Debe instalar una versión de VMBus coincidente en esta instalación de invitado.


message_identifier: 0xc0050003
message_string:
La partición secundaria %2 usa una versión distinta de VMBus (%3) que la primaria (%4). Debe instalar una versión de VMBus coincidente en esta instalación de invitado.


# message_table_55_0x0000041f

message_identifier: 0xc0050004
message_string:
%2 alt bölümü VMBus sürümünü sağlamadı. Bu konuk yüklemeye protokol sürümü %3 olan VMBus'ı yüklemeniz gerekiyor.


message_identifier: 0xc0050005
message_string:
%2 alt bölümü çok fazla kez yanlış VMBus sürümleri sağladı. Bu bölümle ilgili bundan sonra oluşacak hatalar günlüğe yazılmayacak.


message_identifier: 0xc0050002
message_string:
Ana bölüm farklı bir VMBus sürümü kullanıyor. Bu konuk yüklemeye eşleşen bir VMBus sürümü yüklemeniz gerekiyor.


message_identifier: 0xc0050003
message_string:
%2 alt bölümü bu üst örnekten (%4) farklı bir VMBus sürümü (%3) kullanıyor. Bu konuk yüklemeye eşleşen bir VMBus sürümü yüklemeniz gerekiyor.


message_identifier: 0xc0050001
message_string:
PIC hal algılandı. VMBus'ı başlatmak için, sisteminizi APIC hal kullanacak şekilde güncelleştirmeniz gerekiyor.


# message_table_55_0x00000416

message_identifier: 0xc0050004
message_string:
A partição secundária %2 não forneceu uma versão de VMBus. Você precisa instalar um VMBus com versão de protocolo %3 nesta instalação convidada.


message_identifier: 0xc0050005
message_string:
A partição secundária %2 forneceu versões de VMBus erradas várias vezes. Nenhuma outra falha será registrada para essa partição.


message_identifier: 0xc0050002
message_string:
A partição principal usa uma versão de VMBus diferente. Você precisa instalar uma versão de VMBus compatível nesta instalação convidada.


message_identifier: 0xc0050003
message_string:
A partição secundária %2 usa uma versão de VMBus diferente (%3) da utilizada nesta instância principal (%4). Você precisa instalar uma versão de VMBus compatível nesta instalação convidada.


message_identifier: 0xc0050001
message_string:
HAL do PIC detectada. Para iniciar o VMBus, é necessário atualizar o sistema para usar uma HAL da APIC.


# message_table_55_0x00000419

message_identifier: 0xc0050004
message_string:
В дочернем разделе %2 не предоставлено данных о версии VMBus. В этой виртуальной системе нужно установить шину VMBus с протоколом версии %3.


message_identifier: 0xc0050005
message_string:
В дочернем разделе %2 слишком много раз предоставлены неверные данные о версии VMBus. Последующие ошибки в этом разделе не будут заноситься в журнал.


message_identifier: 0xc0050002
message_string:
В родительском разделе используется другая версия VMBus. В этой виртуальной системе необходимо установить соответствующую версию VMBus.


message_identifier: 0xc0050003
message_string:
В дочернем разделе %2 используется версия VMBus (%3), отличная от родительской (%4). В этой виртуальной системе необходимо установить соответствующую версию VMBus.


message_identifier: 0xc0050001
message_string:
Установлено, что используется слой HAL PIC. Для запуска VMBus в системе нужно обновить слой HAL до APIC.


# message_table_55_0x00000409

message_identifier: 0xc0050004
message_string:
The child partition %2 provided no VMBus version. You need to Install VMBus with protocol version %3 in this guest installation.


message_identifier: 0xc0050005
message_string:
The child partition %2 provided wrong VMBus versions too many times. Further failures will not be logged for that partition.


message_identifier: 0xc0050002
message_string:
The parent partition uses a different VMBus version. You need to Install a matching VMBus version in this guest installation.


message_identifier: 0xc0050003
message_string:
The child partition %2 uses a different VMBus version (%3) than this parent instance (%4). You need to Install a matching VMBus version in this guest installation.


# message_table_55_0x0000041d

message_identifier: 0xc0050004
message_string:
Den underordnade partitionen %2 tillhandahöll ingen VMBus-version. Du måste installera VMBus med ett protokoll av %3-version i den här gästinstallationen.


message_identifier: 0xc0050005
message_string:
Den underordnade partitionen %2 tillhandahöll fel VMBus-versioner för många gånger. Inga fler fel kommer att loggas för den aktuella partitionen.


message_identifier: 0xc0050002
message_string:
Den överordnade partitionen använder en annan VMBus-version. Du måste installera en matchande VMBus-version i den här gästinstallationen.


message_identifier: 0xc0050003
message_string:
Den underordnade partitionen %2 använder en annan VMBus-version (%3) än den här överordnade instansen (%4). Du måste installera en matchande VMBus-version i den här gästinstallationen.


message_identifier: 0xc0050001
message_string:
PIC HAL identifierat. Om du vill starta VMBus måste du uppdatera systemet så att ett APIC HAL används.


# message_table_55_0x0000040e

message_identifier: 0xc0050004
message_string:
A(z) %2 gyermekpartíció nem adott meg VMBus-verziót. Telepítse a VMBus %3 protokollverzióját ezen a vendégtelepítésen.


message_identifier: 0xc0050005
message_string:
A(z) %2 gyermekpartíció túl sokszor adott meg helytelen VMBus-verziókat. A további sikertelen kísérletek nem lesznek naplózva ehhez a partícióhoz.


message_identifier: 0xc0050002
message_string:
A szülőpartíción más verziójú VMBus fut. Telepítse a VMBus megfelelő verzióját ezen a vendégtelepítésen.


message_identifier: 0xc0050003
message_string:
A(z) %2 gyermekpartíción más verziójú VMBus fut (%3), mint ezen a szülőpéldányon (%4). Telepítse a VMBus megfelelő verzióját ezen a vendégtelepítésen.


message_identifier: 0xc0050001
message_string:
A rendszer PIC típusú hardverabsztrakciós réteget észlelt. A VMBus indításához a rendszert APIC típusú hardverabsztrakciós réteg használatára kell frissíteni.


# message_table_55_0x0000040c

message_identifier: 0xc0050004
message_string:
La partition enfant %2 n’a fourni aucune version VMBus. Vous devez installer VMBus avec la version de protocole %3 dans cette installation invitée.


message_identifier: 0xc0050005
message_string:
La partition enfant %2 a fourni des versions VMBus incorrectes de trop nombreuses fois. Tout autre problème ne sera pas enregistré pour cette partition.


message_identifier: 0xc0050002
message_string:
La partition parente utilise une version VMBus différente. Vous devez installer une version VMBus correspondante dans cette installation invitée.


message_identifier: 0xc0050003
message_string:
La partition enfant %2 utilise une version VMBus différente (%3) que cette instance parente (%4). Vous devez installer une version VMBus correspondante dans cette installation invitée.


message_identifier: 0xc0050001
message_string:
Couche HAL PIC détectée. Pour démarrer VMBus, vous devez mettre à jour votre système pour pouvoir utiliser une couche HAL APIC.


# message_table_55_0x00000816

message_identifier: 0xc0050004
message_string:
A partição subordinada %2 não forneceu qualquer versão de VMBus. Tem de instalar o VMBus com a versão de protocolo %3 nesta instalação de convidado.


message_identifier: 0xc0050005
message_string:
A partição subordinada %2 forneceu versões de VMBus incorrectas demasiadas vezes. Não serão registadas mais falhas para essa partição.


message_identifier: 0xc0050002
message_string:
A partição principal utiliza uma versão de VMBus diferente. Tem de instalar uma versão de VMBus correspondente nesta instalação de convidado.


message_identifier: 0xc0050003
message_string:
A partição subordinada %2 utiliza uma versão de VMBus diferente (%3) em relação a esta instância principal (%4). Tem de instalar uma versão de VMBus correspondente nesta instalação de convidado.


message_identifier: 0xc0050001
message_string:
HAL de PIC detectado. Para iniciar o VMBus, necessita de actualizar o sistema para utilizar um HAL de APIC.


# message_table_56_0x00000409

message_identifier: 0x00000002
message_string:
The Transaction (UOW=%1, Description='%3') blocked a Freeze from completing.  Freeze is necessary to ensure that a VSS snapshot is transactionally consistent.  The ResourceManager (RmId=%4, Description='%6') may not be functioning correctly, since it did not allow the transaction to drain in the allotted time.  Contact the vendor for that ResourceManager for assistance.


message_identifier: 0x00000003
message_string:
The transaction (UOW=%1, Description='%3') was heuristically aborted and forgotten from the TransactionManager (TmId=%4, LogPath=%6) so that the TransactionManager can continue to make forward progress.  This may cause data corruption in any subordinate ResourceManagers or Transactionmanager.


message_identifier: 0x00000001
message_string:
The Transaction (UOW=%1, Description='%3') was unable to be committed, and instead rolled back; this was due to an error message returned by CLFS while attempting to write a Prepare or Commit record for the Transaction.  The CLFS error returned was: %4.


message_identifier: 0x00000004
message_string:
The TransactionManager (TmId=%1, LogPath=%3) has failed to advance its log tail, due to the transaction (UOW=%4, Description='%6') being unresolved for some time.  The transaction must be forced to resolve in order for the TransactionManager to continue to provide transactional services.  Forcing the incorrect outcome may cause data corruption in any subordinate ResourceManagers or Transactionmanagers.


# message_table_57_0x00000409

message_identifier: 0x00000011
message_string:
A corrected hardware error has occurred.%n%nComponent: %5%nError Source: %1%n%nBus:Device:Function: %9:%10:%11%nVendor ID:Device ID: %15:%16%nClass Code: %17%n%nThe details view of this entry contains further information.


message_identifier: 0x00000010
message_string:
A fatal hardware error has occurred.%n%nComponent: %5%nError Source: %1%n%nBus:Device:Function: %9:%10:%11%nVendor ID:Device ID: %15:%16%nClass Code: %17%n%nThe details view of this entry contains further information.


message_identifier: 0x00000013
message_string:
A corrected hardware error has occurred.%n%nReported by component: Processor Core%nError Source: %1%nError Type: %7%nProcessor ID: %2%n%nThe details view of this entry contains further information.


message_identifier: 0x00000012
message_string:
A fatal hardware error has occurred.%n%nReported by component: Processor Core%nError Source: %1%nError Type: %7%nProcessor ID: %2%n%nThe details view of this entry contains further information.


message_identifier: 0x00000015
message_string:
A corrected hardware error has occurred.%n%nComponent: AMD Northbridge%nError Source: %1%nError Type: %7%nProcessor ID: %2%n%nThe details view of this entry contains further information.


message_identifier: 0x00000014
message_string:
A fatal hardware error has occurred.%n%nComponent: AMD Northbridge%nError Source: %1%nError Type: %7%nProcessor ID: %2%n%nThe details view of this entry contains further information.


message_identifier: 0x00000017
message_string:
A corrected hardware error has occurred.%n%nComponent: Memory%nError Source: %1%nError Type: %19%n%nThe details view of this entry contains further information.


message_identifier: 0x00000016
message_string:
A fatal hardware error has occurred.%n%nComponent: Memory%nError Source: %1%nError Type: %19%n%nThe details view of this entry contains further information.


message_identifier: 0x00000019
message_string:
A corrected hardware error has occurred.%n%nComponent: PCI/PCI-X Bus%nError Source: %1%nError Type: %5%nSegment:Bus: %7:%6%n%nThe details view of this entry contains further information.


message_identifier: 0x00000018
message_string:
A fatal hardware error has occurred.%n%nComponent: PCI/PCI-X Bus%nError Source: %1%nError Type: %5%nSegment:Bus: %7:%6%n%nThe details view of this entry contains further information.


message_identifier: 0x0000002d
message_string:
A corrected hardware error has occurred.%n%nComponent: PCI/PCI-X Device%nError Source: %1%nError Type: %5%n%nThe details view of this entry contains further information.


message_identifier: 0x0000002e
message_string:
A fatal hardware error has occurred.%n%nComponent: Memory%nError Source: %1%n%nThe details view of this entry contains further information.


message_identifier: 0x0000002f
message_string:
A corrected hardware error has occurred.%n%nComponent: Memory%nError Source: %1%n%nThe details view of this entry contains further information.


message_identifier: 0x0000002a
message_string:
A fatal hardware error has occurred.%n%nComponent: PCI/PCI-X Bus%nError Source: %1%nError Type: %5%n%nThe details view of this entry contains further information.


message_identifier: 0x0000002b
message_string:
A corrected hardware error has occurred.%n%nComponent: PCI/PCI-X Bus%nError Source: %1%nError Type: %5%n%nThe details view of this entry contains further information.


message_identifier: 0x0000002c
message_string:
A fatal hardware error has occurred.%n%nComponent: PCI/PCI-X Device%nError Source: %1%nError Type: %5%n%nThe details view of this entry contains further information.


message_identifier: 0x00000026
message_string:
A fatal hardware error has occurred.%n%nReported by component: Processor Core%nError Source: %1%nError Type: %2%nCPU APIC ID: %3%n%nThe details view of this entry contains further information.


message_identifier: 0x00000027
message_string:
A corrected hardware error has occurred.%n%nReported by component: Processor Core%nError Source: %1%nError Type: %2%nCPU APIC ID: %3%n%nThe details view of this entry contains further information.


message_identifier: 0x00000028
message_string:
A fatal hardware error has occurred.%n%nComponent: %5%nError Source: %1%n%nThe details view of this entry contains further information.


message_identifier: 0x00000029
message_string:
A corrected hardware error has occurred.%n%nComponent: %5%nError Source: %1%n%nThe details view of this entry contains further information.


message_identifier: 0x0000001a
message_string:
A fatal hardware error has occurred.%n%nComponent: PCI/PCI-X Device%nError Source: %1%nError Type: %5%n%nSegment:Bus:Device:Function: %12:%11:%10:%9%nVendor ID:Device ID: %6:%7%nClass Code: %8%n%nThe details view of this entry contains further information.


message_identifier: 0x0000001b
message_string:
A corrected hardware error has occurred.%n%nComponent: PCI/PCI-X Device%nError Source: %1%nError Type: %5%n%nSegment:Bus:Device:Function: %12:%11:%10:%9%nVendor ID:Device ID: %6:%7%nClass Code: %8%n%nThe details view of this entry contains further information.


message_identifier: 0x00000002
message_string:
A corrected hardware error has occurred. A record describing the condition is contained in the data section of this event.


message_identifier: 0x00000003
message_string:
A hardware event has occurred. An informational record describing the condition is contained in the data section of this event.


message_identifier: 0x00000001
message_string:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.


# message_table_58_0x00000409

message_identifier: 0x000007d4
message_string:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: %21 (%22) consumed %24 bytes, %28 (%29) consumed %31 bytes, and %35 (%36) consumed %38 bytes.


message_identifier: 0xb00003eb
message_string:
The Windows Resource Exhaustion Detector received a notification that the computer is low on virtual memory.


# message_table_59_0x00000409

message_identifier: 0x00006012
message_string:
Metadata rebuild: An attempt to write a copy of metadata on volume %2 failed and may appear as disk corruption. If failures continue, decrypt volume.


message_identifier: 0x00006011
message_string:
Metadata write: Volume %2 returning errors while trying to modify metadata. If failures continue, decrypt volume.


message_identifier: 0x00006035
message_string:
The system firmware failed to enable overwriting of system memory on restart. The firmware should be upgraded.


message_identifier: 0x00006034
message_string:
The partition size specified in the partition table is smaller than the size of the file system contained by that partition.  BitLocker TPM based keys cannot be used until the size of the partition calculated from the partition table is consistent with the size of the file system calculated from the bytes per sector and number of sectors fields in the boot sector.


message_identifier: 0x0000600c
message_string:
The conversion operation on volume %2 encountered a bad sector error. Please validate the data on this volume.


message_identifier: 0x0000602b
message_string:
Metadata rebuild: An attempt build a new set of metadata on %2 failed at commit and may appear as disk corruption. If failures continue, decrypt volume.


message_identifier: 0x0000602a
message_string:
Metadata check: Metadata record on volume %2 could not be read and has been marked for rebuild. If failures continue, decrypt volume.


message_identifier: 0x00006028
message_string:
Metadata initial read: Failover metadata record on volume %2 could not be found. Volume needs recovery.


message_identifier: 0x00006029
message_string:
Metadata initial read: Failover metadata record on volume %2 used. If failures continue, decrypt volume.


message_identifier: 0x00006026
message_string:
Metadata commit: Update verification of metadata on volume %2 failed. If failures continue, decrypt volume.


message_identifier: 0x00006027
message_string:
Metadata initial read: Primary metadata record on volume %2 could not be found. Volume needs recovery.


message_identifier: 0x00006025
message_string:
Metadata commit: An attempt to verify metadata update on volume %2 failed at read. If failures continue, decrypt volume.


message_identifier: 0x00006022
message_string:
Metadata commit: Not all copies of metadata on volume %2 could be written. If failures continue, decrypt volume.


message_identifier: 0x00006023
message_string:
Metadata commit: No copies of metadata on volume %2 could be written. If failures continue, decrypt volume.


message_identifier: 0x00006032
message_string:
The auto-unlock master key was not available from the operating system volume.  Retry the operation via the BitLocker WMI interface.


message_identifier: 0x0000603a
message_string:
Bootmgr determined that the authorization data for the SRK of the TPM is incompatible with BitLocker.


message_identifier: 0x0000603b
message_string:
Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.


message_identifier: 0x00006044
message_string:
An internal BitLocker self-test failed for drive %2 when switching from raw mode to filtering mode. BitLocker cannot continue encrypting data on this drive. Contact your system administrator.


message_identifier: 0x00006042
message_string:
An internal BitLocker self-test failed for drive %2. BitLocker cannot continue encrypting data. Contact your system administrator.


message_identifier: 0x00006041
message_string:
An unexpected error was encountered attempting to retrieve the BitLocker volume master key during restart.


