# Windows 2000 Events

Message:
The service is starting or stopping.  Please try again later.\r\n


Message:
The service did not report an error.\r\n


Message:
An error occurred controlling the device.\r\n


Message:
The %1 service was continued successfully.\r\n


Message:
The %1 service was paused successfully.\r\n


Message:
The %1 service continue is pending%0\r\n


Message:
The %1 service has been started by another process and is pending.%0\r\n


Message:
A service specific error occurred: %1.\r\n


Message:
These workstations have sessions on this server:\r\n


Message:
These workstations have sessions with open files on this server:\r\n


Message:
Continuing will cancel the connections.\r\n


Message:
New connections will not be remembered.\r\n


Message:
An error occured while saving your profile. The state of your remembered connections has not changed.\r\n


Message:
An error occured while reading your profile.\r\n


Message:
An error occurred while restoring the connection to %1.\r\n


Message:
Users have open files on %1.  Continuing the operation will force the files closed.\r\n


Message:
The Workstation service is already running. Windows 2000 will ignore command options for the workstation.\r\n


Message:
There are open files and/or incomplete directory searches pending on the connection to %1.\r\n


Message:
The request will be processed at a domain controller for domain %1.\r\n


Message:
The shared queue cannot be deleted while a print job is being spooled to the queue.\r\n


Message:
%1 has a remembered connection to %2.\r\n


Message:
An error occurred while opening the Help file.\r\n


Message:
Could not find a domain controller for domain %1.\r\n


Message:
This operation is privileged on systems with earlier\r\nversions of the software.\r\n


Message:
Program filenames must end with .EXE.\r\n


Message:
A matching share could not be found so nothing was deleted.\r\n


Message:
A bad value is in the units-per-week field of the user record.\r\n


Message:
Type the password for the shared resource: %0\r\n


Message:
Type the Replicator service password: %0\r\n


Message:
Type your user name, or press ENTER if it is %1: %0\r\n


Message:
Type the domain or server where you want to change a password, or\r\npress ENTER if it is for domain %1: %0.\r\n


Message:
The following running services can be controlled:\r\n


Message:
Statistics are available for the following running services:\r\n


Message:
Please enter the name of the Primary Domain Controller: %0\r\n


Message:
The string you have entered is too long. The maximum\r\nis %1, please reenter. %0\r\n


Message:
Verification of an automatically enrolled certificate has failed. (%1) %2\r\n


Message:
Unknown or unavailable cert type, %3, requested for automatic certificate enrollment.\r\nThis enrollment will not be performed. (%1) %2\r\n


Message:
The enterprise root certificate store could not be updated.\r\n(%1) %2.\r\n


Message:
The NT Smartcard authentication certificate store could not be updated.\r\n(%1) %2.\r\n


Message:
The automatic certificate enrollment subsystem could not access local resources needed for enrollment.  \r\nEnrollment will not been performed. (%1) %2\r\n


Message:
The automatic certificate enrollment subsystem could not access network resources needed for enrollment.  \r\nEnrollment will  been performed. (%1) %2\r\n


Message:
A security failure is preventing automatic certificate enrollment.  \r\nEnrollment will  been performed. (%1) %2\r\n


Message:
Welcome back to the %1 domain.  While you were offline, your settings were stored in a local account. Do you want to move them to your %1 account?%0\r\n


Message:
Your settings cannot be moved because of an error.  (Error code %1!u!)%0\r\n


Message:
The system could not validate %1. Check your account name, and type your password again. Letters in passwords must be typed using the correct case. Make sure that Caps Lock is not accidentially on.%0\r\n


Message:
The system could not validate %1 on %2. Check your account name, and type your password again. Letters in passwords must be typed using the correct case. Make sure that Caps Lock is not accidentially on.%0\r\n


Message:
The user account you just entered does not have the authority to move settings. Please try another account, such as Administrator.%0\r\n


Message:
The WINS server cannot make or accept this connection since the connections \r\nlimit has been reached. This situation is temporary and should resolve by itself\r\nshortly.\r\n


Message:
The exception was encountered during the processing of a group member.\r\n


Message:
The message was successfully sent to %1.\r\n


Message:
The message name %1 was forwarded successfully.\r\n


Message:
The message name %1 was added successfully.\r\n


Message:
The message name forwarding was successfully canceled.\r\n


Message:
The server %1 successfully logged you on as %2.\r\n


Message:
%1 was successfully removed from the list of shares the Server creates\r\non startup.\r\n


Message:
The password was changed successfully.\r\n


Message:
The message was successfully sent to all users of the network.\r\n


Message:
The message was successfully sent to domain %1.\r\n


Message:
The message was successfully sent to all users of this server.\r\n


Message:
The message was successfully sent to group *%1.\r\n


Message:
Share name   Type         Used as  Comment\r\n


Message:
Logoff forced by logon restrictions%0\r\n


Message:
Account system settings were modified%0\r\n


Message:
Limit exceeded:  Workstation ID invalid%0\r\n


Message:
Administrator stopped sharing resource %1%0\r\n


Message:
Account locked due to %1 bad passwords%0\r\n


Message:
Print job %1 has been canceled while printing on %2.\r\n


Message:
Print job %1 has been deleted and will not print.\r\n


Message:
Unable to open TDI device for RW access. Returning IO Status Block in Data.\r\n


Message:
Unable to allocate memory for TDI Information block. Close one or more applications and retry.\r\n


Message:
Error requesting data from Device IO Control. Returning IO Status Block.\r\n


Message:
Unable to read data from the TDI device.\r\n


Message:
Data received from Device IO Control. Returning IO Status Block.\r\n


Message:
Unable to allocate memory for TDI Statistics block. Close one or more applications and retry.\r\n


Message:
The request for data from the TDI Device IO Control failed. Returning the IO Status Block.\r\n


Message:
The buffer passed to CollectTDIPerformanceData was too small to receive the data. No data was returned. The message data shows the available and the required buffer size.\r\n


Message:
The buffer passed was large enough for the counter data. The counters will now be loaded.\r\n


Message:
Unable to read IO control information from NBT device.\r\n


Message:
The data buffer passed to the collection routine was too small to receive the data from the NBT device. No data was returned to the caller. The bytes available and the bytes required are in the message data.\r\n


Message:
NBT endpoint info error in CollectNbtPerformanceData\r\n


Message:
NBT Open failed. See NBT error message.\r\n


Message:
DSIS open failed. See DSIS error message\r\n


Message:
Load of INETMIB1.DLL failed. Make sure the DLL file is in the PATH. WIN32 Error number is returned in the data.\r\n


Message:
Unable to look up address of SnmpMgrStrToOid routine in the MGMTAPI.DLL library. WIN32 Error number is returned in the data.\r\n


Message:
Unable to look up address of an SNMP Extension routine in the INETMIB1.DLL library. WIN32 Error number is returned in the data.\r\n


Message:
Unable to look up ID of this object in MIB. Check for correct MIB.BIN file.\r\n


Message:
Unable to get the Local Computer name. GetLastError code in data.\r\n


Message:
Unable to open the Snmp Mgr interface for the specified computer. GetLastError code returned in data. \r\n


Message:
The value of the version ID counter was changed. The new value (Low 32 bits) is given in the data section.\r\n


Message:
The WINS replication request is being ignored since WINS suspects that the\r\nWins\\Partners key information has changed (because it received a notification \r\nFrom the registry) which makes the current request pertaining to the partner out \r\nof date.\r\n


Message:
WINS is deleting all records of the WINS with owner ID, %d. This owner ID\r\ncorresponds to the address, %s.\r\n


Message:
WINS pulled records from a WINS while doing %1. The partner's address and \r\nthe owner's address whose records were pulled are given in the data section\r\n(second and third DWORD respectively). The number of records pulled is the\r\nfourth DWORD.\r\n


Message:
WINS performed a consistency check on the records. The number of records pulled, \r\nThe address of the WINS whose records were pulled, and the address of the WINS\r\nfrom which these records were pulled are given in the second, third, and fourth \r\nDWORDs in the data section.\r\n


Message:
There is a problem with the printer; please check it.\r\n


Message:
Print job %1 is being held from printing.\r\n


Message:
Print job %1 is queued for printing.\r\n


Message:
The error code is %1.\r\nThere was an error retrieving the message. Make sure the file\r\nNET.MSG is available.\r\n


Message:
Printing Failed\r\n\r\n"%1" failed to print on %2 on %3.\r\n\r\nFor more help use the print troubleshooter.\r\n


Message:
Printing Failed\r\n\r\n"%1" failed to print on %2 on %3.  The Printer is %4.\r\n\r\nFor more help use the print troubleshooter.\r\n


Message:
Printing Complete\r\n\r\n"%1" printed successfully on %2 on %3.\r\n


Message:
A power failure has occurred at %1.  Please terminate all activity with this server.\r\n


Message:
Power has been restored at %1.  Normal operations have resumed.\r\n


Message:
The UPS service is starting shut down at %1.\r\n


Message:
The UPS service is about to perform final shut down.\r\n


Message:
The Workstation must be started with the NET START command.\r\n


Message:
The password entered is longer than 14 characters.  Computers \r\nwith Windows prior to Windows 2000 will not be able to use \r\nthis account. Do you want to continue this operation? %1: %0\r\n


Message:
%1 has a remembered connection to %2. Do you\r\nwant to overwrite the remembered connection? %3: %0\r\n


Message:
Do you want to resume loading the profile?  The command which\r\ncaused the error will be ignored. %1: %0\r\n


Message:
Do you want to continue this operation? %1: %0\r\n


Message:
Do you want to start the Workstation service? %1: %0\r\n


Message:
Is it OK to continue disconnecting and force them closed? %1: %0\r\n


Message:
The printer does not exist.  Do you want to create it? %1: %0\r\n


Message:
The network control block (NCB) request completed successfully.\r\nThe NCB is the data.\r\n


Message:
Illegal network control block (NCB) buffer length on SEND DATAGRAM,\r\nSEND BROADCAST, ADAPTER STATUS, or SESSION STATUS.\r\nThe NCB is the data.\r\n


Message:
The data descriptor array specified in the network control block (NCB) is\r\ninvalid.  The NCB is the data.\r\n


Message:
The command specified in the network control block (NCB) is illegal.\r\nThe NCB is the data.\r\n


Message:
The message correlator specified in the network control block (NCB) is\r\ninvalid.  The NCB is the data.\r\n


Message:
A network control block (NCB) command timed-out.  The session may have\r\nterminated abnormally.  The NCB is the data.\r\n


Message:
An incomplete network control block (NCB) message was received.\r\nThe NCB is the data.\r\n


Message:
The buffer address specified in the network control block (NCB) is illegal.\r\nThe NCB is the data.\r\n


Message:
The session number specified in the network control block (NCB) is not active.\r\nThe NCB is the data.\r\n


Message:
No resource was available in the network adapter.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
The session specified in the network control block (NCB) was closed.\r\nThe NCB is the data.\r\n


Message:
An invalid media type was specified.%0\r\n


Message:
An invalid media subtype was specified.%0\r\n


Message:
This object can only be created as an aggregated object.%0\r\n


Message:
The enumerator has become invalid.%0\r\n


Message:
At least one of the pins involved in the operation is already connected.%0\r\n


Message:
This operation cannot be performed because the filter is active.%0\r\n


Message:
One of the specified pins supports no media types.%0\r\n


Message:
There is no common media type between these pins.%0\r\n


Message:
Two pins of the same direction cannot be connected together.%0\r\n


Message:
The operation cannot be performed because the pins are not connected.%0\r\n


Message:
No sample buffer allocator is available.%0\r\n


Message:
An invalid alignment was specified.%0\r\n


Message:
Cannot change allocated memory while the filter is active.%0\r\n


Message:
One or more buffers are still active.%0\r\n


Message:
Cannot allocate a sample when the allocator is not active.%0\r\n


Message:
Cannot allocate memory because no size has been set.%0\r\n


Message:
Cannot lock for synchronization because no clock has been defined.%0\r\n


Message:
Quality messages could not be sent because no quality sink has been defined.%0\r\n


Message:
A required interface has not been implemented.%0\r\n


Message:
No combination of intermediate filters could be found to make the connection.%0\r\n


Message:
No combination of filters could be found to render the stream.%0\r\n


Message:
The specified program or command file does not exist. \r\n


Message:
Log %1 has been started or restarted and is logging data to file %2.\r\n


Message:
Log %1, logging data to file %2, has been stopped.\r\n


Message:
Counter: %1 has tripped its alert threshold. The counter value of %2 is %3 the limit\r\nvalue of %4.\r\n


Message:
Alert %1 has been started or restarted.\r\n


Message:
The service was unable to open the log file: %1 for log %2 and will be stopped.\r\nCheck the log folder for existence, spelling and permissions or reenter\r\nthe log file name using the configuration program.\r\nThis log will not be started.\r\nThe error returned is: %3.\r\n


Message:
Unable to read the configuration of the %1 log or alert.\r\nThis log or alert will not be started.\r\nThe error code returned is in the data.\r\n


Message:
Unable to read the %1 value of the %2 log or alert configuration.\r\nThe default value will be used.\r\nThe error code returned is in the data.\r\n


Message:
Unable to read the %1 value of the %2 log or alert configuration.\r\nAn error occurred while trying to allocate memory for the default value.\r\nThe error code returned is in the data.\r\n


Message:
Unable to read the %1 value of the %2 log or alert configuration.\r\nNo default value provided.\r\nThe error code returned is in the data.\r\n


Message:
Log Type for the %1 log or alert configuration has invalid value.\r\nThis log or alert will not be started.\r\nThe invalid value is in the data.\r\n


Message:
An error occurred while trying to allocate memory for or read the command\r\nfilename to be executed by the %1 log or alert. The log or alert will continue, but no\r\ncommand file will be executed.\r\n


Message:
***WINS could not allocate an explicit dialogue. Check to see if the system is low on resources.


Message:
WINS could not look up the association block for a NetBIOS over TCP/IP (NetBT) \r\nassociation. Check to see if the message read is corrupted. WINS looks at \r\nbit 11-14 of the message to determine if the association is from another WINS or from an NetBT node. It is possible that the bits are corrupted or that there is \r\na mismatch between what the two WINS servers expect to see in those bits.\r\n


Message:
WINS could not allocate a User Datagram Protocol (UDP) Buffer. Check to see if \r\nthe system is low on resources.\r\n


Message:
***WINS could not free a User Datagram Protocol (UDP) Buffer. Restart WINS.\r\n


Message:
***WINS could not create a communication subsystem thread. Check to see if the system is low on resources.\r\n


Message:
A WINS thread could not signal the main thread after closing its session.\r\nThis would be caused by the last thread in WINS closing the database.\r\n


Message:
A WINS thread could not signal a handle.\r\n


Message:
A WINS thread could not reset a handle.\r\n


Message:
WINS encountered a database error. This may or may not be a serious error.\r\nWINS will try to recover from it. You can check the database error events under\r\n'Application Log' category of the Event Viewer for the Exchange Component, \r\nESENT, source to find out more details about database errors.\r\n\r\nIf you continue to see a large number of these errors consistently over time\r\n(a span of few hours), you may want to restore the WINS database from a backup.\r\n\r\nThe error number is in the second DWORD of the data section.\r\n


Message:
WINS could not update the record with the name, %1. Check the application log for the Exchange component, ESENT.\r\n


Message:
WINS could not update the Owner ID-to-Address mapping table in the database.\r\nThis means the in-memory table that maps to the database table has gotten \r\nout of sync with the database table.\r\n\r\nCheck the application log for the Exchange component, ESENT. The WINS database \r\nmay have to be restored.\r\n


Message:
The Push Thread was requested for a range of records but could not find any \r\nrecords in the range. Make sure that the replication time intervals are set \r\nproperly. If the tombstone interval and timeout intervals are not correct \r\n(that is, much less than the replication interval), the above condition is \r\npossible. This is because the records might get changed into tombstones and \r\nthen deleted before the remote WINS can pull them. Similarly, if the refresh \r\ninterval is set to be much less than the replication interval then the records \r\ncould get released before a WINS can pull them (a released record is not sent).\r\n\r\nMake sure that the replication time intervals are set properly.\r\n


Message:
The Timer thread could not be signaled. This indicates this computer is \r\nextremely overloaded or that the WINS application has failed. Check for low \r\nsystem resources. It may be necessary to restart WINS.\r\n


Message:
***The Timer could not signal the client thread.\r\n


Message:
***WINS could not get information about a key. Check to see if the permissions \r\non the key are set properly, system resources are low, or the registry is having a problem.\r\n


Message:
WINS could not get information about the Pull key. Check to see if the \r\npermissions on the key are set properly, system resources are low, or the \r\nregistry is having a problem.\r\n


Message:
WINS could not get information about the Push key. Check to see if the \r\npermissions on the key are set properly, system resources are low, or the \r\nregistry is having a problem.\r\n


Message:
The network control block (NCB) command was canceled.\r\nThe NCB is the data.\r\n


Message:
The message segment specified in the network control block (NCB) is\r\nillogical.  The NCB is the data.\r\n


Message:
The name already exists in the local adapter name table.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
The network adapter name table is full.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
The network name has active sessions and is now de-registered.\r\nThe network control block (NCB) command completed.  The NCB is the data.\r\n


Message:
A previously issued Receive Lookahead command is active\r\nfor this session.  The network control block (NCB) command was rejected.\r\nThe NCB is the data.\r\n


Message:
The local session table is full. The network control block (NCB) request was refused.\r\nThe NCB is the data.\r\n


Message:
A network control block (NCB) session open was rejected.  No LISTEN is outstanding\r\non the remote computer.  The NCB is the data.\r\n


Message:
The name number specified in the network control block (NCB) is illegal.\r\nThe NCB is the data.\r\n


Message:
The call name specified in the network control block (NCB) cannot be found or\r\ndid not answer.  The NCB is the data.\r\n


Message:
The name specified in the network control block (NCB) was not found.  Cannot put '*' or\r\n00h in the NCB name.  The NCB is the data.\r\n


Message:
The name specified in the network control block (NCB) is in use on a remote adapter.\r\nThe NCB is the data.\r\n


Message:
The name specified in the network control block (NCB) has been deleted.\r\nThe NCB is the data.\r\n


Message:
The session specified in the network control block (NCB) ended abnormally.\r\nThe NCB is the data.\r\n


Message:
The network protocol has detected two or more identical\r\nnames on the network.\tThe network control block (NCB) is the data.\r\n


Message:
An unexpected protocol packet was received.  There may be an\r\nincompatible remote device.  The network control block (NCB) is the data.\r\n


Message:
The NetBIOS interface is busy.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
There are too many network control block (NCB) commands outstanding.\r\nThe NCB request was refused.  The NCB is the data.\r\n


Message:
The adapter number specified in the network control block (NCB) is illegal.\r\nThe NCB is the data.\r\n


Message:
The network control block (NCB) command completed while a cancel was occurring.\r\nThe NCB is the data.\r\n


Message:
The name specified in the network control block (NCB) is reserved.\r\nThe NCB is the data.\r\n


Message:
The network control block (NCB) command is not valid to cancel.\r\nThe NCB is the data.\r\n


Message:
There are multiple network control block (NCB) requests for the same session.\r\nThe NCB request was refused.  The NCB is the data.\r\n


Message:
There has been a network adapter error. The only NetBIOS\r\ncommand that may be issued is an NCB RESET. The network control block (NCB) is\r\nthe data.\r\n


Message:
The maximum number of applications was exceeded.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
The requested resources are not available.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
A system error has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
A ROM checksum failure has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
A RAM test failure has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
A digital loopback failure has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
An analog loopback failure has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
An interface failure has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
An unrecognized network control block (NCB) return code was received.\r\nThe NCB is the data.\r\n


Message:
A network adapter malfunction has occurred.\r\nThe network control block (NCB) request was refused.  The NCB is the data.\r\n


Message:
The network control block (NCB) command is still pending.\r\nThe NCB is the data.\r\n


Message:
The update log on %1 is over 80%% capacity. The primary\r\ndomain controller %2 is not retrieving the updates.\r\n


Message:
The update log on %1 is full, and no further updates\r\ncan be added until the primary domain controller %2\r\nretrieves the updates.\r\n


Message:
The time difference with the primary domain controller %1\r\nexceeds the maximum allowed skew of %2 seconds.\r\n


Message:
The account of user %1 has been locked out on %2\r\ndue to %3 bad password attempts.\r\n


Message:
The Application log file could not be opened.  %1 will be used as the\r\ndefault log file.\r\n


Message:
The %1 Log is full.  If this is the first time you have seen this\r\nmessage take the following steps:%n\r\nStart, Settings, Control Panel, Administrative Tools, Event Viewer%n\r\nSelect %1 Log, from the action menu choose Clear All Events, choose not\r\nto save.%n%n\r\nIf this dialog persists, contact your helpdesk/system administrator.\r\n


Message:
The security database full synchronization has been initiated by the server %1.\r\n


Message:
The Netlogon service failed to register the service with the\r\nservice controller. The service was terminated. The following\r\nerror occurred: %n%1\r\n


Message:
The change log cache maintained by the Netlogon service for\r\ndatabase changes is corrupted. The Netlogon service is resetting\r\nthe change log.\r\n


Message:
The Netlogon service could not create server share %1.  The following\r\nerror occurred: %n%2\r\n


Message:
The down-level logon request for the user %1 from %2 failed.\r\n


Message:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2\r\nfailed because the Windows NT Domain Controller does not have an account\r\nfor the computer %3.\r\n


Message:
The session setup from the computer %1 failed to authenticate.\r\nThe name of the account referenced in the security database is\r\n%2.  The following error occurred: %n%3\r\n


Message:
The session setup from the computer %1 failed because there is\r\nno trust account in the security database for this computer. The name of\r\nthe account referenced in the security database is %2.\r\n


Message:
Could not register control handler with service controller %1.\r\n


Message:
Could not set service status with service controller %1.\r\n


Message:
Could not find the computer name %1.\r\n


Message:
Replication of the %1 Domain Object "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 Global Group "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 Local Group "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 User "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 Policy Object "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 Trusted Domain Object "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 Account Object "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
Replication of the %1 Secret "%2" from primary domain controller\r\n%3 failed with the following error: %n%4\r\n


Message:
The system returned the following unexpected error code: %n%1\r\n


Message:
Netlogon has detected two machine accounts for server "%1".\r\nThe server can be either a Windows 2000 Server that is a member of the\r\ndomain or the server can be a LAN Manager server with an account in the\r\nSERVERS global group. It cannot be both.\r\n


Message:
This domain has more global groups than can be replicated to a LanMan\r\nBDC.  Either delete some of your global groups or remove the LanMan\r\nBDCs from the domain.\r\n


Message:
The Browser driver returned the following error to Netlogon: %n%1\r\n


Message:
Netlogon could not register the %1<1B> name for the following reason: %n%2\r\n


Message:
Service failed to retrieve messages needed to boot remote boot clients.\r\n


Message:
Service experienced a severe error and can no longer provide remote boot\r\nfor 3Com 3Start remote boot clients.\r\n


Message:
Service experienced a severe system error and will shut itself down.\r\n


Message:
Client with computer name %1 failed to acknowledge receipt of the\r\nboot data.  Remote boot of this client was not completed.\r\n


Message:
Client with computer name %1 was not booted due to an error in opening\r\nfile %2.\r\n


Message:
Client with computer name %1 was not booted due to an error in reading\r\nfile %2.\r\n


Message:
Client with computer name %1 was not booted due to insufficent memory\r\nat the remote boot server.\r\n


Message:
Client with computer name %1 will be booted without using checksums\r\nbecause checksum for file %2 could not be calculated.\r\n


Message:
Client with computer name %1 was not booted due to too many lines in\r\nfile %2.\r\n


Message:
Client with computer name %1 was not booted because the boot block\r\nconfiguration file %2 for this client does not contain boot block\r\nline and/or loader line.\r\n


Message:
Client with computer name %1 was not booted due to a bad size of\r\nfile %2.\r\n


Message:
Client with computer name %1 was not booted due to remote boot\r\nservice internal error.\r\n


Message:
Client with computer name %1 was not booted because file %2 has an\r\ninvalid boot header.\r\n


Message:
Client with computer name %1 was not booted due to network error.\r\n


Message:
Client with adapter id %1 was not booted due to lack of resources.\r\n


Message:
Service experienced error copying file or directory %1.\r\n


Message:
Service experienced error deleting file or directory %1.\r\n


Message:
Service experienced error setting permissions on file or directory %1.\r\n


Message:
Service experienced error evaluating RPL configurations.\r\n


Message:
Service experienced error creating RPL profiles for all configurations.\r\n


Message:
Service experienced error accessing registry.\r\n


Message:
Service experienced error replacing possibly outdated RPLDISK.SYS.\r\n


Message:
Service experienced error adding security accounts or setting\r\nfile permissions.  These accounts are the RPLUSER local group\r\nand the user accounts for the individual RPL workstations.\r\n


Message:
Service failed to back up its database.\r\n


Message:
Service failed to initialize from its database.  The database may be\r\nmissing or corrupted.  Service will attempt restoring the database\r\nfrom the backup.\r\n


Message:
Service failed to restore its database from the backup.  Service\r\nwill not start.\r\n


Message:
Service sucessfully restored its database from the backup.\r\n


Message:
Service failed to initialize from its restored database.  Service\r\nwill not start.\r\n


Message:
The session setup to the Windows NT or Windows 2000  Domain Controller %1 from computer\r\n%2 using account %4 failed.  %2 is declared to be a BDC in domain %3.\r\nHowever, %2 tried to connect as either a DC in a trusted domain,\r\na member workstation in domain %3, or as a server in domain %3.\r\nUse the Active Directory Users and Computers tool or Server Manager to remove the BDC account for %2.\r\n


Message:
The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is\r\nattempting to convert it to NT 4.0 format. The JETCONV converter\r\nwill write to the Application event log when it is finished.\r\n


Message:
Global group SERVERS exists in domain %1 and has members.\r\nThis group defines Lan Manager BDCs in the domain.\r\nLan Manager BDCs are not permitted in NT domains.\r\n


Message:
The DNS server for this DC does not support dynamic DNS.\r\nAdd the DNS records from the file '%SystemRoot%\\System32\\Config\\netlogon.dns'\r\nto the DNS server serving the domain referenced in that file.\r\n


Message:
Registration of the DNS record '%1' failed with the following error: %n%2\r\n


Message:
Deregistration of the DNS record '%1' failed with the following error: %n%2\r\n


Message:
Failed to create/open file %1 with the following error: %n%2\r\n


Message:
Netlogon got the following error while trying to get the subnet to site\r\nmapping information from the DS: %n%1\r\n


Message:
'%1' tried to determine its site by looking up its IP address ('%2')\r\nin the Configuration\\Sites\\Subnets container in the DS.  No subnet matched\r\nthe IP address.  Consider adding a subnet object for this IP address.\r\n


Message:
The site name for this computer is '%1'.  That site name is not a valid\r\nsite name.  A site name must be a valid DNS label.\r\nRename the site to be a valid name.\r\n


Message:
The subnet object '%1' appears in the Configuration\\Sites\\Subnets\r\ncontainer in the DS.  The name is not syntactically valid.  The valid\r\nsyntax is xx.xx.xx.xx/yy where xx.xx.xx.xx is a valid IP subnet number\r\nand yy is the number of bits in the subnet mask.\r\n\r\nCorrect the name of the subnet object.\r\n


Message:
Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.\r\n


Message:
Dynamic registration or deregistration of one or more DNS records failed with the following error: %n%1\r\n


Message:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2\r\nis not responsive.  The current RPC call from Netlogon on \\\\%3 to %1 has been cancelled.\r\n


Message:
Site '%2' does not have any Domain Controllers for domain '%3'.\r\nDomain Controllers in site '%1' have been automatically\r\nselected to cover site '%2' based on configured Directory Server\r\nreplication costs.\r\n


Message:
This Domain Controller no longer automatically covers site '%1'.\r\n


Message:
Site '%2' does not have any Global Catalog servers.\r\nGlobal Catalog servers in site '%1' have been automatically\r\nselected to cover site '%2' based on configured Directory Server\r\nreplication costs.\r\n


Message:
This Global Catalog server no longer automatically covers site '%1'.\r\n


Message:
Attempt to update Service Principal Name (SPN) of the computer object \r\nin Active Directory failed.  The following error occurred: %n%1\r\n


Message:
Attempt to update DNS Host Name of the computer object \r\nin Active Directory failed.  The following error occurred: %n%1\r\n


Message:
This DC is both a Global Catalog and the Infrastructure Update master.  These two roles are incompatible.  If another machine exists in the domain, it should be made the Infrastructure Update master.  The machine %1 is a good candidate for this role.  If all domain controllers in this domain are Global Catalogs, then there are no Infrastructure Update tasks to complete, and this message may be ignored.\r\n


Message:
LDAP over SSL will be unavailable at this time because the server was unable to obtain a certificate.\r\n


Message:
Domain operation mode has been changed to Native Mode. The change cannot be reversed. \r\n


Message:
The attempt to establish a replication link with parameters%n\r\n%n\r\nPartition: %1%n\r\nSource DSA DN: %4%n\r\nSource DSA Address: %2%n\r\nInter-site Transport (if any): %5%n\r\n%n\r\nfailed with the following status:%n\r\n%n\r\n%3\r\n%n\r\nThe record data is the status code.  This operation will be retried.\r\n


Message:
The Microsoft Client Service for NetWare redirector has timed out one or more requests to %2.\r\n


Message:
The value named %1 in the Microsoft Client Service for NetWare registry key %2 was invalid.  The value was\r\nignored, and processing continued.\r\n


Message:
The password for %1 on %2 has expired, with %3 grace logins left.%n\r\n


Message:
The Microsoft Client Service for NetWare redirector was unable to allocate memory.\r\n


Message:
The Microsoft Client Service for NetWare redirector could not create its device.  The redirector could not be started.\r\n


Message:
The Microsoft Client Service for NetWare redirector received an incorrectly formatted response from %2.\r\n


Message:
The Microsoft Client Service for NetWare redirector failed to unlock part of a file on server %2.\r\n


Message:
The Microsoft Client Service for NetWare redirector has encountered a network error.\r\n


Message:
An unexpected network error has occurred on the connection to %2.\r\n


Message:
No NetWare or compatible server exists on this network.\r\n


Message:
The Microsoft Client Service for NetWare could not start because it did not bind to any transports.\r\n


Message:
The Microsoft Client Service for NetWare could not bind to the transport %1.\r\n


Message:
The Microsoft Client Service for NetWare redirector (%1) could not be started.\r\n


Message:
The Gateway Account could not be logged on. The error %1 occurred.\r\n


Message:
Device %1 could not be reconnected to %2. Error %3 occurred.\r\n


Message:
The version of the NWLINK transport present does not support all the capabilities required to use the Microsoft Client Service for NetWare properly.\r\n


Message:
Logins to the server has been disabled.%n\r\n


Message:
The password for %1 on %2 has expired.%n\r\n


Message:
The IP Security policy for ISAKMP/Oakley specified an encryption algorithm that is invalid due to export cryptography restrictions.  All 3DES encryption used by ISAKMP/Oakley is weakened to standard DES encyption.  Generally, this is benign.  ISAKMP/Oakley will still be able to negotiate IP security parameters, and protect that negotiation with DES encryption.  This should only be of concern if you demand that the ISAKMP/Oakley negotiation be protected with 3DES encryption.  If this is the case, please contact your network administrator.     \r\n


Message:
The PCMCIA tuple information for the PCCARD in socket %2 could not be parsed.\r\n


Message:
The hardware addresses for %1 are already in use by another device.\r\n


Message:
Unable to initialize interrupt object for %1.\r\n


Message:
Unable to get device object pointer for port object.\r\n


Message:
The return data value is valid and different from the last sample.\r\n


Message:
Unable to connect to specified machine or machine is off line.\r\n


Message:
The specified instance is not present.\r\n


Message:
There is more data to return than would fit in the supplied buffer. Allocate\r\na larger buffer and call the function again.\r\n


Message:
The data item has been added to the query, but has not been validated nor \r\naccessed. No other status information on this data item is available.\r\n


Message:
The selected operation should be retried.\r\n


Message:
A counter with a negative denominator value was detected.\r\n


Message:
A counter with a negative timebase value was detected.\r\n


Message:
A counter with a negative value was detected.\r\n


Message:
The specified object is not found on the system.\r\n


Message:
The specified counter could not be found.\r\n


Message:
A PDH function could not allocate enough temporary memory to complete the\r\noperation. Close some applications or extend the pagefile and retry the \r\nfunction.\r\n


Message:
The handle is not a valid PDH object.\r\n


Message:
A required argument is missing or incorrect.\r\n


Message:
Unable to find the specified function.\r\n


Message:
Unable to parse the counter path. Check the format and syntax of the \r\nspecified path.\r\n


Message:
The buffer passed by the caller is invalid.\r\n


Message:
The requested data is larger than the buffer supplied. Unable to return the\r\nrequested data.\r\n


Message:
Unable to connect to the requested machine.\r\n


Message:
The specified counter path could not be interpreted.\r\n


Message:
The instance name could not be read from the specified counter path.\r\n


Message:
The dialog box data block was missing or invalid.\r\n


Message:
Unable to read the counter and/or explain text from the specified machine.\r\n


Message:
An extensible counter has opened the Event Log for PERFCTRS.DLL\r\n


Message:
An extensible counter has closed the Event Log for PERFCTRS.DLL\r\n


Message:
A request for data from a foreign computer was received by the TDI Collection routine. This request was ignored and no data was returned.\r\n


Message:
A request for a counter object not provided by the TDI Collection routine was received.\r\n


Message:
Successful data request from the TDI device.\r\n


Message:
Provider Information data block released successfully\r\n


Message:
Provider Stats data block released successfully\r\n


Message:
TDI counters are requesting Event Log access to close.\r\n


Message:
NBT device IO Control information read successfully.\r\n


Message:
The TCP data Bindings array has been initialized\r\n


Message:
This file is corrupt: it contains an invalid media type.%0\r\n


Message:
No time stamp has been set for this sample.%0\r\n


Message:
No media time stamp has been set for this sample.%0\r\n


Message:
No media time format has been selected.%0\r\n


Message:
Cannot change balance because audio device is mono only.%0\r\n


Message:
Cannot play back the audio stream: no audio hardware is available, or the hardware is not responding.%0\r\n


Message:
ActiveMovie cannot play MPEG movies on this processor.%0\r\n


Message:
Cannot play back the audio stream: the audio format is not supported.%0\r\n


Message:
Cannot play back the video stream: the video format is not supported.%0\r\n


Message:
ActiveMovie cannot play this video stream because it falls outside the constrained standard.%0\r\n


Message:
Cannot perform the requested function on an object that is not in the filter graph.%0\r\n


Message:
Cannot get or set time related information on an object that is using a time format of TIME_FORMAT_NONE.%0\r\n


Message:
The connection cannot be made because the stream is read only and the filter alters the data.%0\r\n


Message:
Cannot play back the file.  The format is not supported.%0\r\n


Message:
Pins cannot connect due to not supporting the same transport.%0\r\n


Message:
The Video CD can't be read correctly by the device or is the data is corrupt.%0\r\n


Message:
There is not enough Video Memory at this display resolution and number of colors. Reducing resolution might help.%0\r\n


Message:
The VideoPort connection negotiation process has failed.%0\r\n


Message:
Either DirectDraw has not been installed or the Video Card capabilities are not suitable. Make sure the display is not in 16 color mode.%0\r\n


Message:
No VideoPort hardware is available, or the hardware is not responding.%0\r\n


Message:
No Capture hardware is available, or the hardware is not responding.%0\r\n


Message:
This User Operation is inhibited by DVD Content at this time.%0\r\n


Message:
This Operation is not permitted in the current domain.%0\r\n


Message:
Requested Button is not available.%0\r\n


Message:
DVD-Video playback graph has not been built yet.%0\r\n


Message:
DVD-Video playback graph building failed.%0\r\n


Message:
DVD-Video playback graph could not be built due to insufficient decoders.%0\r\n


Message:
Version number of DirectDraw not suitable. Make sure to install dx5 or higher version.%0\r\n


Message:
Copy protection cannot be enabled. Please make sure any other copy protected content is not being shown now.%0\r\n


Message:
This object cannot be used anymore as its time has expired.%0\r\n


Message:
The specified property ID is not supported for the specified property set.%0\r\n


Message:
The Specified property set is not supported.%0\r\n


Message:
The CI service has successfully started.\r\n


Message:
Recovery was performed successfully on PropertyStore in catalog %1.\r\n


Message:
Master merge has been paused on %2 due to error %3.\r\nIt will be rescheduled later.\r\n


Message:
Master merge was started on %2 because the size of the shadow indexes\r\n is more than %3% of the disk.\r\n


Message:
Master merge was started on %2 because more than %3 documents have changed\r\nsince the last master merge.\r\n


Message:
Master merge was started on %2 because the amount of remaining disk\r\n space was less than %3%.\r\n


Message:
An error has been detected on %2 which requires a full content scan.\r\n


Message:
An error has been detected on %2 which requires a partial content scan.\r\n


Message:
A full content scan has started on %2.\r\n


Message:
A partial content scan has started on %2.\r\n


Message:
A content scan could not be completed on %1.\r\n


Message:
Class for extension %1 unknown.  Sample\r\nfile: %2\r\n


Message:
Content index corruption detected in component %1.\r\nStack trace is %2.\r\n


Message:
Recovery is starting on PropertyStore in catalog %1.\r\n


Message:
PropertyStore inconsistency detected in catalog %1.\r\n


Message:
Content index corruption detected in component %2 in catalog %3.\r\nStack trace is %4.\r\n


Message:
Notifications are not enabled on %1 because this is a Dfs-aware share.\r\nThis scope will be periodically scanned.\r\n


Message:
Added virtual root %1 to index. Mapped to %2.\r\n


Message:
Neither the Owner nor the Primary Group account names are valid.\r\nSpecify valid account names for the Owner and Primary Group of\r\nthis directory.\r\n


Message:
The Owner account name is invalid. \r\nSpecify a valid account name or the Owner of this directory.\r\n


Message:
The Primary Group account name is invalid. \r\nSpecify a valid account name for the Primary Group of this directory.\r\n


Message:
The Logon Message entered for the File Server for Macintosh was invalid. \r\nLogon Message should not be greater than 199 characters.\r\nMake the appropriate changes and retry the operation.\r\n


Message:
The User Limit entered for the Share Volume was invalid. \r\nEnter a number between 0 and 4294967295.\r\nMake the appropriate changes and retry the operation.\r\n


Message:
The Sessions Limit field entered for the File Server was invalid. \r\nEnter a number between 0 and 4294967295.\r\nMake the appropriate changes and retry the operation.\r\n


Message:
The server name specified is not of valid length.\r\nSpecify a server name containing not more than 31 single-byte characters \r\nor not more than 15 double-byte characters.\r\n


Message:
Unable to start the File Server for Macintosh service.\r\nA system specific error has occured.\r\nThe error code is in the data\r\n


Message:
The File Server for Macintosh service failed to start. Unable to setup\r\nthe server to accept Remote Procedure Calls.\r\n


Message:
The File Server for Macintosh service failed to start. \r\nSecurity access checking of administrators could not be setup correctly.\r\n


Message:
The File Server for Macintosh service failed to start. \r\nThe Registry could not be opened.\r\n


Message:
The File Server for Macintosh service failed to start. \r\nUnable to open the Appletalk Filing Protocol file system driver (SfmSrv.sys).\r\n


Message:
The Registry contains an invalid value for the server name parameter.\r\nVerify the value of this parameter through the Computer Managerment Console \r\nand in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters Registry key.\r\n


Message:
The File Server for Macintosh service failed to start. \r\nThe Registry contains an invalid value for the server options parameter.\r\nVerify the value of this parameter through the Computer Managerment Console \r\nand in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters Registry key.\r\n


Message:
The CI service attempted to startup but was suppressed because the DonotStartCiSvc registry\r\nparameter was set.\r\n


Message:
The content index filter for file "%1" generated content data more than %2\r\n times the file's size.\r\n


Message:
One or more embedded files in file %1 could not be filtered.\r\n


Message:
The CI filter daemon has prematurely terminated and will be and subsequently\r\n restarted.\r\n


Message:
Content index metadata on drive %2 is corrupt.  Index will be automatically\r\n restored. Running chkdsk /f is recommended.\r\n


Message:
Content index on %1 is corrupt. Please shutdown and restart\r\nthe Indexing Service (cisvc).\r\n


Message:
Cleaning up corrupt content index metadata on %1. Index will\r\n be automatically restored by refiltering all documents.\r\n


Message:
Content index on %1 could not be initialized. Error %2.\r\n


Message:
Error %1 detected in content index on %2.\r\n


Message:
%1 inconsistencies were detected in PropertyStore during recovery of catalog %2.\r\n


Message:
Very low disk space was detected on drive %1. Please free up at least %2MB of\r\nspace for content index to continue.\r\n


Message:
File change notifications for scope %1 are not enabled because of error %2. This scope will be\r\nperiodically scanned.\r\n


Message:
Delete of file "%1" caused a rescan because it was potentially a short filename.\r\nAvoid use of names with the character "~" in them or disable "8 DOT 3" name creation.\r\n


Message:
Read of USN log for NTFS volume %1 failed with error code %2.  Volume will remain\r\noffline until the Indexing Service (cisvc) is restarted.\r\n


Message:
The MaxCatalogs limit has been reached, so the catalog in %1 can't be opened.\r\n


Message:
Master merge cannot be started on %2 due to error %3.\r\n


Message:
Master merge cannot be re-started on %2 due to error %3.\r\n


Message:
The content index could not filter file %2.  The filter operation was retried\r\n %3 times without success.\r\n


Message:
The NTFS filter service failed with error code %1.\r\n


Message:
The filter service could not run since file %1 could not be found on your\r\n system.\r\n


Message:
File change notifications are turned off for scope %1 because of error %2. This\r\nscope will be periodically scanned.\r\n


Message:
%1 failed to logon %2 because of error %3.\r\n


Message:
The path %1 is too long for Content Index.\r\n


Message:
Please check your system time.\r\nIt might be set to an invalid value.\r\n


Message:
Account %1 does not have interactive logon privilege on this computer.\r\nYou can give %1 interactive logon privilege on this computer using the\r\nuser manager administrative tool.\r\n


Message:
The IISADMIN service is not available, so virtual roots cannot be indexed.\r\n


Message:
The content index is corrupt. A content scan will to be scheduled after chkdsk or autochk is run.\r\n


Message:
The content index meta data is corrupt.\r\n


Message:
The content index partition is invalid.\r\n


Message:
The content index is out of index ids.\r\n


Message:
An extensible counter has opened the Event Log for RASCTRS.DLL\r\n


Message:
An extensible counter has closed the Event Log for RASCTRS.DLL\r\n


Message:
Unable to open device driver containing RAS performance data.\r\n


Message:
Unable to perform ioctl to device driver containing RAS performance data.\r\n


Message:
Unable open "Performance" key of RAS driver in registy. Status code is returned in data.\r\n


Message:
Unable to read the "First Counter" value under the Remote Access\\Performance Key. Status codes retuened in data.\r\n


Message:
Unable to read the "First Help" value under the Remote Access\\Performance Key. Status codes retuened in data.\r\n


Message:
Unable to create port information table. Status codes returned in data.\r\n


Message:
Unable to allocate enough memory.  Status codes returned in data.\r\n


Message:
QoS RSVP service failed to start with error %1.\r\n


Message:
QoS RSVP service key in registry is missing or corrupted. Need to reinstall QoS RSVP service to correct this problem.\r\n


Message:
Error %1 while opening QoS RSVP service parameters key, using default values for all RSVP configuration parameters.\r\n


Message:
Received I_AM_DSBM from another DSBM with IP address %1 and priority %2.\r\n


Message:
Received I_AM_DSBM message from another DSBM with priority %1 higher than this DSBM's, hence stopping.\r\n


Message:
Unable to Load DLL IPHLPAPI.DLL, RSVP will not be able to function without this DLL.\r\n


Message:
Error %1 while registering for changes to RSVP service key in registry. RSVP will not be able to respond to changes to registry values.\r\n


Message:
Error %1 while creating the tracefile, hence RSVP will not write RSVP message details to the trace files.\r\n


Message:
Currently allocated bandwidth %1 by QoS ACS is more than the new upper limit %2 set via QoS ACS management console on interface %3. Changes made using QoS ACS management console does not affect existing reservations.\r\n


Message:
There is no upper bound on the amount of bandwidth available for RSVP reservations on interface %1.\r\n


Message:
This host became DSBM for the subnet with %1 IP address.\r\n


Message:
This host is no longer the DSBM on subnet with %1 IP address.\r\n


Message:
Changed maximum peak data rate per flow to be same as maximum data rate per flow as the peak data rate is lower than data rate on subnet %1.\r\n


Message:
Can not send a Reservation Confirm message because RSVP can not find a route to the host with %1 IP address.\r\n


Message:
Unable to allocate sufficient memory to start RSVP service.\r\n


Message:
Encountered %1 error while loading the LPM %2.\r\n


Message:
The LPM %1 is missing one of the necessary functions.\r\n


Message:
Initialization of LPM %1 failed with error %2, ACS will continue to function without this LPM.\r\n


Message:
Initialization of LPM %1 returned invalid Policy Element type %2, ACS will continue to function without this LPM.\r\n


Message:
LPM %1 initialized successfully and handles policy element of type %2.\r\n


Message:
Policy Control Module initialized successfully and there are %1 active LPMs.\r\n


Message:
Policy Control Module failed to initialize with error (%1).\r\n


Message:
PCM received results from an LPM with invalid handle, ignoring the results.\r\n


Message:
PCM received results from an %1 LPM with invalid request handle, ignoring the results.\r\n


Message:
Dropping results for GetPolicyData request from LPM %1 for reasons other than invalid handle and multiple results.\r\n


Message:
PCM received results from an %1 LPM multiple times, ignoring the results.\r\n


Message:
Error %1 while loading the ADSI library required to access directory.\r\n


Message:
This host can not be DSBM on %1 interface as this DSBM is supported only on NT server.\r\n


Message:
Using registry value of %1 from %2 registry key.\r\n


Message:
Using registry value of %1 from %2 registry key in %3 subnet.\r\n


Message:
This host %1 is not in server list of %2 subnet. Add this server to list via QoS ACS management console.\r\n


Message:
This host %1 can not be ACS on any of the subnets as this host has not been added to the ACS server lists in the Directory. Add this server to the list of valid servers for ACS via QoS ACS management console.\r\n


Message:
This host can not be ACS since the Active Directory has not been properly configured via the QoS ACS management console. Please configure the subnets via the QoS ACS mangement console.\r\n


Message:
Restarting ACS as the admission control mode has changed from service specific mode to aggregate mode.\r\n


Message:
Restarting ACS as the admission control mode has changed from aggregate mode to service specific mode.\r\n


Message:
Unloaded all LPMs other than %1, as %1 LPM makes policy decisions using all types of policy elements.\r\n


Message:
The WSAIoctl to snoop RSVP messages failed with %1 error, hence unable to receive RSVP messages on interface %2.\r\n


Message:
This ACS has been configured to manage PPP interfaces but no PPP lines are detected on this host. So the ACS service is not functioning. Enable PPP lines or configure the ACS to manage shared media.\r\n


Message:
QoS RSVP fails to register for SPI event notification -> abandon ipsec support.\r\n


Message:
Shutting QoS RSVP service due to system failure.\r\n


Message:
Shutting QoS RSVP service due to a system failure.\r\n


Message:
QoS RSVP fails to open a signaling socket (TCP) to communicate with clients due to a system failure.\r\n


Message:
QoS RSVP fails to load TRAFFIC.DLL, so traffic control is not functional on this machine. Check %systemroot%\\system32 directory for TRAFFIC.DLL.\r\n


Message:
QoS RSVP has failed to find any interfaces with traffic control enabled. Install QoS traffic control services via network and dial-up connections.\r\n


Message:
QoS RSVP fails to register as a traffic control client. Check for the presence of QoS packet scheduler, the classical IP over ATM provider, or another traffic control provider.\r\n


Message:
QoS RSVP fails to install a network control flow for RSVP packets. On a congested network, RSVP message could be dropped.\r\n


Message:
QoS RSVP fails to uninstall a flow for RSVP packets.\r\n


Message:
No traffic control capability on the specific interface with %1 IP address.\r\n


Message:
This host will not function as ACS on the subnet with %1 IP address, as ACS is not enabled on this subnet.\r\n


Message:
ACS has not been configured for %1 subnet. Please add ACS configuration data using the QoS ACS management console.\r\n


Message:
QoS RSVP fails to engage with the IPSEC Policy Agent\r\n


Message:
Rogue server detection is disabled via registry.\r\n


Message:
DSBM found per service limits in the configuration data of %1 subnet, hence operating in DiffServ mode.\r\n


Message:
QoS RSVP failure in the initialization of memory debugging functions.\r\n


Message:
Found another DSBM with IP address %1 on the %2 interface, hence this host will not attempt to be DSBM on this interface.\r\n


Message:
ACS will not do policy admission control as this ACS is configured to do Resource admission control only.\r\n


Message:
Version number %1 returned by %2 LPM is unsupported by the Policy Control Module in ACS.\r\n


Message:
PCM received invalid results from an %1 LPM, ignoring the results.\r\n


Message:
ACS on this host is managing the non-shared media interface with %1 IP address.\r\n


Message:
There are no non-shared media interfaces on this host which are manageable by this ACS.\r\n


Message:
This host is no longer the DSBM on interface %1 as this interface disappeared.\r\n


Message:
QoS Admission Control Service started.\r\n


Message:
QoS Admission Control Service stopped.\r\n


Message:
QoS Admission Control Service failed to start with error %1.\r\n


Message:
Error (%1) while retrieving the AcsService account name, password and domain name. Enter this data using the QoS ACS management console.\r\n


Message:
Error (%1) while validating AcsService account user name, password. Enter the correct account user name, password using the QoS ACS management console.\r\n


Message:
MSIDLPM could not logon to Kerberos KeyDistribution Center using the supplied account name, password. Hence MSIDLPM will not initialize.\r\n


Message:
Error (%1) while cracking the Kerberos ticket in the Identity Policy element. One of the possible reason could be that ACS is configured with a bad password. Enter the correct password using the QoS ACS management console.\r\n


Message:
Error (%1) while decrypting the policy locator in the Identity Policy element. One of the possible reason could be that ACS is configured with a bad password. Enter the correct password using the QoS ACS management console.\r\n


Message:
ACS was not able to get the Domain Controller name to access the Active Directory, and failed with (%1) error.\r\n


Message:
Error (%1) while opening the root container in DS. ACS configuration parameters are stored under the root container.\r\n


Message:
Error (%1) while opening the Enterprise policy container in DS. Enterprise level ACS configuration parameters are stored in this DS container.\r\n


Message:
Error (%1) while opening the %2 subnet container in DS. Configuration data for this subnet are stored in this container. Enter this data using the QoS ACS management console.\r\n


Message:
Error (%1) while searching for ACS policies in the subnet container with IP address %2. Enter ACS policies using the QoS ACS management console.\r\n


Message:
Error (%1) while reading ACS policies in the subnet container with IP address %2. Enter ACS policies using the QoS ACS management console.\r\n


Message:
Error (%1) while obtaining the credential handle for AcsService account. This handle is used to decode Kerberos tickets. Enter correct account user name, password using the QoS ACS management console.\r\n


Message:
Built-in account for administering the computer/domain\r\n


Message:
Built-in account for guest access to the computer/domain\r\n


Message:
Designated administrators of the domain\r\n


Message:
Administrators have complete and unrestricted access to the computer/domain\r\n


Message:
Members can administer domain servers\r\n


Message:
Power Users can modify the computer and install programs, but cannot read files that belong to other users\r\n


Message:
Users can operate the computer and save documents, but cannot install programs or make potentially damaging changes to the system files and settings\r\n


Message:
Guests can operate the computer and save documents, but cannot install programs or make potentially damaging changes to the system files and settings\r\n


Message:
Members can administer domain user and group accounts\r\n


Message:
Members can administer domain printers\r\n


Message:
Backup Operators can only use a backup program to backup files and folders on to the computer\r\n


Message:
Supports file replication in a domain\r\n


Message:
Key Distribution Center Service Account\r\n


Message:
All workstations and servers joined to the domain\r\n


Message:
All domain controllers in the domain\r\n


Message:
Designated administrators of the schema\r\n


Message:
Enterprise certification and renewal agents\r\n


Message:
Designated administrators of the enterprise\r\n


Message:
Servers in this group can access remote access properties of users\r\n


Message:
Members in this group can modify group policy for the domain\r\n


Message:
A backward compatibility group which allows read access on all users and groups in the domain\r\n


Message:
SAM failed to write changes to the database. This is most likely due to\r\na memory or disk-space shortage. The SAM database will be restored to\r\nan earlier state. Recent changes will be lost. Check the disk-space\r\navailable and maximum pagefile size setting.\r\n


Message:
SAM failed to restore the database to an earlier state. SAM has shutdown.\r\nYou must reboot the machine to re-enable SAM.\r\n


Message:
SAM failed to update the SAM database. It will try again next time you\r\nreboot the machine.\r\n


Message:
SAM failed to start the TCP/IP or SPX/IPX listening thread\r\n


Message:
There are two or more objects that have the same account name attribute\r\nin the SAM database. The Distinguished Name of the account is %1. Delete\r\nall duplicate accounts but ensure that the original account remains.\r\nFor computer accounts, the most recent account is retained. All the other\r\ncases, the older account is kept.\r\n


Message:
There are two or more objects that have the same SID attribute in the SAM\r\ndatatbase. The Distinguished Name of the account is %1. All duplicate \r\naccounts have been deleted. Check the event log for additional Duplicates\r\n


Message:
The SAM database was unable to lockout the account of %1 due to a resource\r\nerror, such as a hard disk write failure (the specific error code is in the\r\nerror data) . Accounts are locked after a certain number of bad passwords are\r\nprovided so please consider resetting the password of the account mentioned\r\nabove.\r\n


Message:
The SAM database attempted to delete the file %1 as it contains account \r\ninformation that is no longer used.  The error is in the record data. Please\r\nhave an admin delete this file.\r\n


Message:
The SAM database attempted to clear the directory %1 in order to remove files\r\nthat were once used by the Directory Service. The error is in record data. \r\nPlease have an admin delete these files.\r\n


Message:
%1 is now the primary domain controller for the domain.\r\n


Message:
The account %1 could not be upgraded since there is an account with an\r\nequivalent name.\r\n


Message:
An error occurred upgrading user %1.  This account will have to added\r\nmanually upon reboot.\r\n


Message:
An error occurred trying to read a user object from the old database.\r\n


Message:
An error occurred upgrading alias %1. This account will have to added\r\nmanually upon reboot.\r\n


Message:
An error occurred trying to read an alias object from the old database.\r\n


Message:
An error occurred upgrading group %1. This account will have to added\r\nmanually upon reboot.\r\n


Message:
An error occurred trying to read a group object from the old database.\r\n


Message:
An error occurred trying to add account %1 to alias %2.  This account will have\r\nto added manually upon reboot.\r\n


Message:
The account with the sid %1 could not be added to group %2.\r\n


Message:
An error occurred trying to add account %1 to group %2.  This account will have\r\nto added manually upon reboot.\r\n


Message:
The account with the rid %1 could not be added to group %2.\r\n


Message:
A fatal error occurred trying to transfer the SAM account database into the\r\ndirectory service. A possible reason is the SAM account database is corrupt.\r\n


Message:
The account krbtgt was renamed to %1 to allow the Kerberos security package to install.\r\n


Message:
Setting the administrator's password to the string you specified failed.\r\nUpon reboot the password will be blank; please reset once logged on.\r\n


Message:
An error occurred trying to upgrade a SAM user's User_Parameters \r\nattribute. The following Notification Package DLL might be the possible \r\noffender: %1. Check the record data of this event for the NT error code.\r\n


Message:
An error occured trying to set User Parameters attribute for this user \r\nThis operation is failed. Check the record data of this event for the NT\r\nerror code.        \r\n


Message:
An error occured trying to upgrade the following SAM User Object - %1.\r\nWe will try to continue upgrading this user. But it might contain inconsistant data. \r\nCheck the record data of this event for the NT error code.\r\n


Message:
An error occurred when trying to add the account %1 to the group %2.  \r\nThe problem, "%3", occurred when trying to open the group. Please add the member manually.\r\n


Message:
An error occurred when trying to add the account %1 to the group %2. \r\nThe problem, "%3", occurred when trying to add the account to the group.  Please add the member manually.\r\n


Message:
The error "%2" occurred when trying to create the well known account %1. Please contact PSS to\r\nrecover.\r\n


Message:
The Security Accounts Manager failed to add the Enterprise Admins group to the local Administrators alias.\r\nTo ensure proper functioning of the domain, please add the member manually.\r\n


Message:
The account-identifier allocator finished initializing. The allocator was\r\ninitialized with the following identifier values: %1 %2 %3 %4 %5 %6 %7 %8.\r\nCheck the record data of this event for the initialization status. Zero\r\nindicates successful initialization, otherwise the record data contains\r\nthe NT error code.\r\n


Message:
The account-identifier pool for this domain controller could not be updated.\r\nA possible reason for this is that the domain controller may be too busy with\r\nother update operations. Subsequent account creations will attempt to update\r\nthe ID pool until successful.\r\n


Message:
The account-identifier allocator was unable to assign a new identifier. The\r\nidentifier pool for this domain controller may have been depleted. If this\r\nproblem persists, restart the domain controller and view the initialization\r\nstatus of the allocator in the event log.\r\n


Message:
An initial account-identifier pool has not yet been allocated to this domain\r\ncontroller. A possible reason for this is that the domain controller has been\r\nunable to contact the master domain controller, possibly due to connectivity\r\nor network problems. Account creation will fail on this domain controller\r\nuntil the pool is obtained.\r\n


Message:
The maximum domain account identifier value has been reached. No further\r\naccount-identifier pools can be allocated to domain controllers in this\r\ndomain.\r\n


Message:
The maximum account identifier allocated to this domain controller has been\r\nassigned. The domain controller has failed to obtain a new identifier pool.\r\nA possible reason for this is that the domain controller has been unable to\r\ncontact the master domain controller. Account creation on this controller will\r\nfail until a new pool has been allocated. There may be network or connectivity\r\nproblems in the domain, or the master domain controller may be offline or\r\nmissing from the domain. Verify that the master domain controller is running\r\nand connected to the domain.\r\n


Message:
The computed account identifier is invalid because it is out of the range of\r\nthe current account-identifier pool belonging to this domain controller. %1.\r\nTry invalidating the account identifier pool owned by this domain controller.\r\nThis will make the domain controller acquire a fresh account identifier pool\r\n


Message:
The domain controller is starting a request for a new account-identifier pool.\r\n


Message:
The request for a new account-identifier pool has completed successfully.\r\n


Message:
The account-identifier-manager object creation completed. If the record data\r\nfor this event has the value zero, the manager object was created. Otherwise,\r\nthe record data will contain the NT error code indicating the failure. The\r\nfailure to create the object may be due to low system resources, insufficient\r\nmemory, or disk space.\r\n


Message:
The account-identifier allocator failed to initialize properly.  The record data\r\ncontains the NT error code that caused the failure.  Windows 2000 will retry the\r\ninitialization until it succeeds; until that time, account creation will be\r\ndenied on this Domain Controller.  Please look for other SAM event logs that\r\nmay indicate the exact reason for the failure.\r\n


Message:
The request for a new account-identifier pool failed because %1. Windows 2000 \r\nwill retry the request until it succeeds. \r\n


Message:
Security Enabled Local Group Changed to Security Enabled Universal Group.\r\n


Message:
Security Enabled Local Group Changed to Security Disabled Local Group.\r\n


Message:
Security Enabled Local Group Changed to Security Disabled Universal Group.\r\n


Message:
Security Enabled Global Group Changed to Security Enabled Universal Group.\r\n


Message:
Security Enabled Global Group Changed to Security Disabled Global Group.\r\n


Message:
Security Enabled Global Group Changed to Security Disabled Universal Group.\r\n


Message:
Security Enabled Universal Group Changed to Security Enabled Local Group.\r\n


Message:
Security Enabled Universal Group Changed to Security Enabled Global Group.\r\n


Message:
Security Enabled Universal Group Changed to Security Disabled Local Group.\r\n


Message:
Security Enabled Universal Group Changed to Security Disbled Global Group.\r\n


Message:
Security Enabled Universal Group Changed to Security Disabled Universal Group.\r\n


Message:
Security Disabled Local Group Changed to Security Enabled Local Group.\r\n


Message:
Security Disabled Local Group Changed to Security Enabled Universal Group.\r\n


Message:
Security Disabled Local Group Changed to Security Disabled Universal Group.\r\n


Message:
Security Disabled Global Group Changed to Security Enabled Global Group.\r\n


Message:
Security Disabled Global Group Changed to Security Enabled Universal Group.\r\n


Message:
Security Disabled Global Group Changed to Security Disabled Universal Group.\r\n


Message:
Security Disabled Universal Group Changed to Security Enabled Universal Group.\r\n


Message:
Security Disabled Universal Group Changed to Security Enabled Global Group.\r\n


Message:
Security Disabled Universal Group Changed to Security Disabled Local Group.\r\n


Message:
Security Disabled Universal Group Changed to Security Disabled Global Group.\r\n


Message:
Member Account Name Is Not Available.\r\n


Message:
Security configuration is backed up to %1.\r\n


Message:
A replica domain controller is promoted. No need to create domain policy object.\r\n


Message:
%1 is registered to create default domain group policy objects.\r\n


Message:
Account policy in GPO %1,if any, is ignored because account policy on domain controllers\r\ncan only be configured through domain level group policy objects.\r\n


Message:
No change has been made to the group policy objects since last propagation.\r\n


Message:
Security policy in the Group policy objects are applied successfully.\r\n


Message:
Security configuration cannot be backed up to security templates directory.\r\nInstead, it is backed up to %1.\r\n


Message:
Default domain policy object cannot be created.\r\n%1\r\n


Message:
Security policies are propagated with warning.\r\n%1\r\n


Message:
Machine is assumed as a non-domain controller. Policy changes are saved in local database.\r\n%1\r\n


Message:
Certificate Services revoked the certificate for request %1 for %2.\r\n


Message:
Certificate Services for %1 was started.\r\n


Message:
Certificate Services issued a new Certificate Revocation List for %1.\r\n


Message:
Certificate Services for %1 was stopped.\r\n


Message:
Certificate Services could not sucessfully complete integration setup with Internet Information Server. Web setup was not completed; CRLs and enrollment pages may not be available. %1.\r\n


Message:
Certificate Services issued a certificate for request %1 for %2.  Additional information: %3\r\n


Message:
Certificate Services left request %1 pending in the queue for %2.  Additional information: %3\r\n


Message:
The METADATA_SECURE attribute cannot be removed from a data item via the GetData method. Use the DeleteData method to remove the secure data.\r\n


Message:
The schema information could not be loaded. A required key or property is missing from the metabase.\r\n


Message:
The CRM log file was originally created on a computer with a different name. It has been updated with the name of the current computer. If this warning appears when the computer name has been changed then no further action is required. %1%0\r\n


Message:
The threading model of the component specified in the registry is inconsistent with the registration database. The faulty component is: %1%0\r\n


Message:
Your computer was not able to renew its address from the network (from the\r\nDHCP Server) for the Network Card with network address %1.  The following\r\nerror occured: %n%2.\r\nYour computer will continue to try and obtain an address on its own from\r\nthe network address (DHCP) server.\r\n


Message:
The DHCP service received the unknown option %1, with a length of %2. \r\nThe raw option data is given below.\r\n


Message:
The DHCP service failed to register with Service Controller. \r\nThe following error occurred: %n%1.\r\n


Message:
The DHCP service failed to initialize its global parameters. \r\nThe following error occurred: %n%1\r\n


Message:
The DHCP service failed to initialize its registry parameters. \r\nThe following error occurred: %n%1\r\n


Message:
Not used\r\nThe MacPrint Service has stopped.\r\n


Message:
The printer %1 is now available to the AppleTalk network.\r\n


Message:
The printer %1 has been removed from the AppleTalk network.\r\n


Message:
status: Spooling to print server "%1" ...\r\n


Message:
An unexpected error was encountered.  \r\nThe errorcode is in the data.\r\n


Message:
Not used\r\nA Macintosh workstation has submitted a print job.  The Macintosh Owner Name\r\nis  %1.\r\n


Message:
Not used\r\nA Macintosh workstation has submitted a print job. The Macintosh Owner\r\nName is not available.\r\n


Message:
Not used\r\nThe Windows 2000 Print System has rejected a print job from a Macintosh\r\nworkstation.\r\n


Message:
Not used\r\nAn error occurred sending a print job to the Windows 2000 Print System.\r\nThe print job has been canceled.\r\n


Message:
Not used\r\nAn error occurred on the AppleTalk network, which caused a Macintosh print\r\njob to be canceled. Unbind and rebind AppleTalk Protocol on the concerned\r\nadapter.\r\n


Message:
Not used\r\nThe print job was canceled because it was not generated using the\r\nstandard LaserWriter driver. The print job must conform  to the\r\nAdobe's Document Structuring Conventions Version 2.0, available\r\nwhen the LaserWriter driver is used.\r\n


Message:
The handle passed to the TrueImage Interpreter loggin routine is invalid.\r\n


Message:
The TrueImage Interpreter was unable to create a required device context.\r\nThe error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to start printing the document.\r\nThe error code returned from the system was %1.\r\n


Message:
***The Name Challenge Request thread could not be created.


Message:
A registry key could not be created or opened.


Message:
The WINS configuration key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.


Message:
The WINS Pull configuration key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.


Message:
The WINS Push configuration key could not be created or opened. Check to see \r\nif the permissions on the key are set properly, system resources are low, or \r\nthe registry is having a problem.


Message:
The WINS\Parameters key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.


Message:
The WINS\Parameters\ConsistencyCheck subkey could not be created or opened. This key should be there if you want WINS to do consistency checks on its database periodically. 

NOTE: Consistency checks have the potential of consuming large amounts of network bandwidth. 

Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.


Message:
The registry change notification event could not be created. Check to see if system resources are low.


Message:
The correct time format is hh:mm:ss. Check the value of SpTime in the registry.


Message:
The registry notification function returned an error.


Message:
***The Name Registration Response could not be sent due to an error. This\r\nerror was encountered by a RPL thread.\r\n


Message:
The Name Registration Response could not be sent due to an error. This error was encountered by the Name Challenge Thread.


Message:
The Name Release Response could not be sent due to an error. This error is often caused by a problem with the NetBIOS over TCP/IP (NetBT) interface.


Message:
The Name Query Response could not be sent due to an error. This error is often caused by a problem with the NetBIOS over TCP/IP (NetBT) interface.


Message:
A record could not be registered because it already existed. However, the same record then could not be found. The WINS database might be corrupt. Check the application log for the Exchange component, ESENT.


Message:
WINS could not create a heap because of a resource shortage. Check to see if the computer is running short of virtual memory.


Message:
Security configuration is not backed up.\r\n%1\r\n


Message:
Security policy cannot be propagated.\r\n%1\r\n


Message:
Default group policy object cannot be created.\r\n%1\r\n


Message:
Policy change from LSA/SAM can't be saved in the policy storage.\r\n%1\r\n


Message:
Policy change from LSA/SAM on DC can't be replicated to other DCs.\r\n%1\r\n


Message:
A name was successfully registered for this node via AppleTalk protocol on adapter "%2".\r\n


Message:
Unable to register name for node on adapter "%2". \r\nEither the name is already in use on the network or is longer \r\nthan 32 characters long.\r\nChange the name of the adapter to a valid one. \r\nUnbind and rebind Appletalk protocol on the adapter.\r\n


Message:
PRAM values for the network range were not within the\r\nnetwork range specified and are being ignored for adapter "%2".\r\n


Message:
Releasing a node acquired on the adapter "%2" because the connected network\r\nis not seeded by any router on the net\r\n


Message:
The node ID obtained during Appletalk initialization on adapter "%2" was assigned to another device.\r\nCurrent node ID was released and a new node ID was acquired from the seed router in the seeded range.\r\n


Message:
Not used\r\nUnable to send a ZIP packet on adapter "%2".\r\n


Message:
Not used\r\nUnable to close a socket opened for a ZIP request on adapter "%2".\r\n


Message:
Unable to close the adapter "%2".\r\nAppletalk protocol may be in an unstable state on the adapter.\r\n


Message:
Unable to get the station address for adapter "%2".\r\nThe error was ignored and processing was continued.\r\n


Message:
Unable to set the lookahead size for adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
Unable to set the packet filter for adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
Not used\r\nAn AARP packet was not completely available in the lookahead data from NDIS\r\non adapter "%2".\r\n


Message:
Packet received on adapter "%2" contained errors and is not being accepted.\r\n


Message:
Unable to start packet reception on the adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
Not used\r\nPacket received contained errors and is not being accepted.\r\n


Message:
Network Number conflicts with an existing router.\r\nThe error was ignored and processing was continued.\r\n


Message:
Not used\r\nUnable to bind to a adapter when in routing configuration.\r\n


Message:
Not used\r\nUnable to bind the ARAP adapter\r\n


Message:
Not used\r\nUnable to retrieve ARAP adapter info\r\n


Message:
The adapter name specified was greater than the maximum length of 32 characters allowed for adapter "%2".\r\nThe adapter has been initialized with a default port name.\r\nIf you change the adapter name, unbind and rebind Appletalk protocol on the adapter.\r\n


Message:
Invalid network range specified for adapter "%2".\r\nAppletalk was not initialized on the adapter.\r\nVerify the values for the Network Range limits for the adapter for AppleTalk Routing are valid using the Routing and Remote Access UI.\r\nIf values are modified, rebind Appletalk protocol on the adapter.\r\n


Message:
The network ranges specified for one or more adapters overlap with those of the\r\nadapter "%2".\r\nAppletalk was not initialized on the adapter.\r\nVerify the values for the Network Range limits for the adapters for AppleTalk Routing are valid using the Routing and Remote Access UI.\r\nIf values are modified, rebind Appletalk protocol on the adapter.\r\n


Message:
Default zone specified was invalid for adapter "%2".\r\nVerify the value for the Default Zone for the adapter for AppleTalk Routing is valid using the Routing and Remote Access UI.\r\n


Message:
No default zone was specified for adapter "%2".\r\nVerify the value for the Default Zone for the adapter for AppleTalk Routing is valid using the Routing and Remote Access UI.\r\n


Message:
Desired zone invalid or not specified.\r\nThe value was ignored and processing was continued.\r\n


Message:
An invalid zone name specified in the zone list for adapter "%2".\r\nThe error was ignored and processing was continued.\r\n


Message:
The default/desired zone name specified is not in the zone list for adapter "%2".\r\nAppletalk was not initialized on the adapter.\r\n


Message:
No adapter is configured to be the default adapter.\r\nAppletalk was not initialized on any adapter.\r\nServices over AppleTalk e.g. Print Server, File Server etc. will not be \r\nfunctional unless a default adapter is specified.\r\n


Message:
Not used\r\nAn invalid adapter is configured to be the default adapter "%2". \r\nLocaltalk adapters cannot be a default adapter in a routing configuration.\r\nAppletalk could not be started on the adapter.\r\n


Message:
Unable to acquire a node on adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
A seeding adapter had no network range specified for adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
A seeding adapter had no zone list specified on adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
Not used\r\nA seeding adapter had too many zones specified on adapter "%2". The limit on zones is 255.\r\n


Message:
Not used\r\nEither the default zone was null or the zone list was empty on a LocalTalk\r\nadapter "%2".\r\n


Message:
Not used\r\nThere was more than one zone specified in the zone list for a LocalTalk adapter "%2".\r\n


Message:
Not used\r\nUnable to open the AppleTalk key in the registry.\r\n


Message:
Not used\r\nStarted with no bindings. The protocol must be bound to at least one adapter.\r\n


Message:
Not used\r\nUnable to start the router on adapter "%2" because a node could not be acquired.\r\n


Message:
Not used\r\nUnable to start ZIP/RTMP processes on adapter "%2".\r\n


Message:
Not used\r\nUnable to release a node acquired on adapter "%2".\r\n


Message:
An invalid AARP packet was received on adapter "%2".\r\n


Message:
An AARP packet could not be sent on adapter "%2".\r\n


Message:
The Zone Information Socket could not be opened on a new node being\r\nacquired, and the acquired node is being released on adapter "%2".\r\n


Message:
The Address Mapping Table for adapter "%2" was not updated because the incoming\r\npacket contained an invalid source address\r\n


Message:
Unable to open RTMP/NBP/EP sockets on a node created on adapter "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
Not used\r\nUnable to close sockets on a node on adapter "%2" and so the\r\nnode may not be released properly\r\n


Message:
Unable to create the device "%2". \r\nAppleTalk protocol could not be started.\r\nThe error is in the data.\r\n


Message:
Unable to register with the NDIS wrapper.\r\nAppletalk could not be started on the adapter.\r\n


Message:
Unable to deregister with the NDIS wrapper.\r\nAppletalk protocol may be in an unstable state on the adapter.\r\n


Message:
Unable to open the adapter (bind to the mac) "%2".\r\nAppletalk could not be started on the adapter.\r\n


Message:
AppleTalk is not bound to the adapter "%2". \r\nRequest for the adapter was ignored.\r\n


Message:
Unable to allocate resources from the NDIS wrapper.\r\nSystem may be low on resources.\r\n


Message:
Unable to allocate resources from the NDIS wrapper.\r\nAppletalk could not be started on the adapter.\r\nSystem may be low on resources.\r\n


Message:
Appletalk protocol stack was unable to allocate memory. \r\nSystem may be low on memory.\r\n


Message:
Not used\r\nA fatal internal error was detected in the AppleTalk stack.\r\n


Message:
Not used\r\nA uniprocessor driver was loaded a multiprocessor system. The driver could not load.\r\n


Message:
An extensible counter has opened the Event Log for SFMCTRS.DLL\r\n


Message:
An extensible counter has closed the Event Log for SFMCTRS.DLL\r\n


Message:
The message has been sent, but not all of the connected workstations have\r\nreceived it. Some workstations are running an unsupported version of\r\nsystem software.\r\n


Message:
The File Server is in an invalid state for the operation being performed.\r\nCheck the status of the File Server for Macintosh service and retry the \r\noperation.\r\n


Message:
Cannot create a Macintosh-Accessible volume within another volume.\r\nChoose a directory that is not within a volume.\r\n


Message:
The target server is not setup to accept Remote Procedure Calls.\r\n


Message:
The selected Creator/Type item already exists.\r\n


Message:
The selected Creator/Type item no longer exists.\r\nThis item may have been deleted by another administrator.\r\n


Message:
The default Creator/Type item cannot be deleted.\r\n


Message:
The default Creator/Type item may not be edited.\r\n


Message:
The Creator/Type item is invalid and will not be use by the File Server\r\nfor Macintosh service.\r\nThe invalid Creator/Type item is in the data.\r\n


Message:
Too many Extension/Type Creator mappings than the system can handle.\r\nSystem limit is 2147483647 mappings.\r\n


Message:
The password specified is invalid.\r\nSpecify a valid password less than 8 characters.\r\n


Message:
The selected Macintosh-Accessible volume no longer exists.\r\nAnother administrator may have removed the selected volume.\r\n


Message:
The memory range for adapter %2 could not be translated to something the memory management system could understand.\r\n


Message:
Port %2(%3) was unable to initialize properly.\r\n


Message:
The memory window for adapter %2 failed to open.\r\n


Message:
The Miniport driver %2 version is incorrect.  Please make certain that all Digi Intelligent Async products have been updated to the same driver version.\r\n


Message:
dmio: Cannot open disk %2: kernel error %3\r\n


Message:
dmio: Disk %2: Unexpected status on close: %3\r\n


Message:
dmio: read error on object %2 of mirror %3 in volume %4 (start %5, length %6) corrected\r\n


Message:
dmio: Reassigning bad block number %2 on disk %3\r\n


Message:
dmio: Reassign bad block(s) on disk %2 succeeded\r\n


Message:
dmio: Found a bad block on disk %2 at block number %3\r\n


Message:
dmio: Corrected a read error during RAID5 initialization on %2\r\n


Message:
dmio: %2 read error at block %3: status 0x%4\r\n


Message:
dmio: %2 write error at block %3: status 0x%4\r\n


Message:
dmio: %2 write error at block %3 due to disk removal\r\n


Message:
dmio: %2 read error at block %3 due to disk removal\r\n


Message:
dmio: Device %2,%3: Received spurious close\r\n


Message:
dmio: Failed to log the detach of the DRL volume %2\r\n


Message:
dmio: %2 error on %3 %4 of volume %5 offset %6 length %7\r\n


Message:
dmio: Overlapping mirror %2 %3 detached from volume %4\r\n


Message:
dmio: Kernel log full: %2 %3 detached\r\n


Message:
dmio: Kernel log update failed: %2 %3 detached\r\n


Message:
dmio: object %2 detached from RAID-5 %3 at column %4 offset %5\r\n


Message:
dmio: RAID-5 %2 entering degraded mode operation\r\n


Message:
dmio: Double failure condition detected on RAID-5 %2\r\n


Message:
dmio: Failure in RAID-5 logging operation\r\n


Message:
dmio: log object %2 detached from RAID-5 %3\r\n


Message:
dmio: check_ilocks: stranded ilock on %2 start %3 len %4\r\n


Message:
dmio: check_ilocks: overlapping ilocks: %2 for %3, %4 for %5\r\n


Message:
dmio: %2 %3 block %4: Uncorrectable %5 error\r\n


Message:
dmio: %2 %3 block %4:\r\n        Uncorrectable %5 error on %6 %7 block %8\r\n


Message:
dmio: Fail to reassign bad block(s) on disk %2: error 0x%3\r\n


Message:
dmio: Failed to recover a read error during RAID5 initialization on %2: error %3\r\n


Message:
dmio: Disk %2 block %3 (mountpoint %4): Uncorrectable read error\r\n


Message:
dmio: %2 %3 block %4 (mountpoint %5): Uncorrectable read error\r\n


Message:
dmio: Disk %2 block %3 (mountpoint %4): Uncorrectable write error\r\n


Message:
dmio: %2 %3 block %4 (mountpoint %5): Uncorrectable write error\r\n


Message:
Starting Microsoft DNS Server (NT4.0 ServicePack6 October 1999).\r\n


Message:
Starting Microsoft DNS Server (Windows2000 RC2 August 1999).\r\n


Message:
The DNS server did not detect any zones of either primary or secondary type.\r\nIt will run as a caching-only server but will not be authoritative for any\r\nzones.  For more information, see the online Help.\r\n


Message:
The DNS server wrote version %1 of zone %2 to file %3.\r\n


Message:
An extensible counter has opened the Event Log for ATKCTRS.DLL\r\n


Message:
An extensible counter has closed the Event Log for ATKCTRS.DLL\r\n


Message:
A request for data from a foreign computer was received by the ATK Collection routine. This request was ignored and no data was returned.\r\n


Message:
A request for a counter object not provided by the ATK Collection routine was received.\r\n


Message:
Successful data request from the ATK device.\r\n


Message:
ATK counters are requesting Event Log access to close.\r\n


Message:
A Null ATK device handle was encountered in the Collect routine. The ATK file was probably not opened in the Open routine.\r\n


Message:
Unable to open driver containing Appletalk performance data.\r\n  To view the AppleTalk counters from Perfmon.exe, make sure the Appletalk driver has been started.\r\n


Message:
Unable to perform ioctl to device driver containing Appletalk performance data.\r\n  To view the Appletalk counters from Perfmon.exe, make sure the Appletalk driver has been started.\r\n


Message:
Unable open "Performance" key of Appletalk driver in registry. Status code is returned in data.\r\n


Message:
Unable to read the "First Counter" value under the AppleTalk\\Performance Key. Status codes returned in data.\r\n


Message:
An exception occurred while performing Windows 3.1 migration.  Some data\r\nmay not have been migrated.\r\n


Message:
The entire contents of %1 was migrated into the Windows NT registry.\r\n


Message:
The entire contents of the %1 section of %2 was migrated into the\r\nWindows NT registry.\r\n


Message:
The value of the %1 variable in the %2 section of %3 was migrated into\r\nthe Windows NT registry.\r\n


Message:
The entire contents of the %1 Program Manager group was migrated into the\r\nWindows NT registry.\r\n


Message:
The contents of the Windows 3.X Program Manager group file %1 was not\r\nmigrated into the Windows NT registry, as a group of that name, %2,\r\nalready existed.\r\n


Message:
Unable to migrate all or part of the %1 file into the Windows NT registry.\r\n


Message:
Unable to migrate all or part of the %1 section of %2 into the Windows\r\nNT registry.\r\n


Message:
Unable to migrate the value of the %1 variable in the %2 section of %3\r\ninto the Windows NT registry.\r\n


Message:
Unable to migrate the contents of the %1 Program Manager group into\r\nthe Windows NT registry.\r\n


Message:
Unable to load the contents of the Windows 3.1 Program Manager group file %1.\r\nError Code was %2.  Group not migrated to the Windows NT registry.\r\n


Message:
Unable to read the value of %1 from the %2 file.  Group not migrated to\r\nthe Windows NT registry.\r\n


Message:
Unable to convert the contents of the Windows 3.1 Program Manager group\r\nfile %1.  into the Windows NT format.  Error Code was %2.  Group not\r\nmigrated to the Windows NT registry.\r\n


Message:
Unable to migrate all or part of %1 to the Windows NT registry.\r\n


Message:
Did not migrate the contents of the %1 Program Manager group into\r\nthe Windows NT registry.  It is incompatible with Windows NT.\r\n


Message:
Unable to read the "First Help" value under the AppleTalk\\Performance Key. Status codes returned in data.\r\n


Message:
Unable to open ATK device for R access. Returning IO Status Block in Data.\r\n


Message:
Unable to read data from the ATK device.\r\n


Message:
The request for data from the ATK Device IO Control failed. Returning the IO Status Block.\r\n


Message:
The buffer passed to CollectATKPerformanceData was too small to receive the data. No data was returned. The message data shows the available and the required buffer size.\r\n


Message:
%1: ACPI Name Space Object %2 reports an _ADR (%3) that is already in use.\r\nSuch conflicts are not legal. Please contact your system vendor for\r\ntechnical assistance.\r\n


Message:
%1: ACPI Name Space Object %2 reports an _HID (%3) that is already in use.\r\nSuch conflicts are not legal. Please contact your system vendor for\r\ntechnical assistance.\r\n


Message:
%1: ACPI Bios claims that the machine has suffered a fatal error and needs to\r\nbe shutdown as quickly as possible. Please contact your system vendor for\r\ntechnical assistance.


Message:
No more rows to be obatained by the search result.\r\n


Message:
No more columns to be obatained for the current row.\r\n


Message:
An invalid Active Directory pathname was passed\r\n


Message:
An unknown Active Directory domain object was requested\r\n


Message:
An unknown Active Directory user object was requested\r\n


Message:
An unknown Active Directory computer object was requested\r\n


Message:
An unknown Active Directory object was requested\r\n


Message:
The specified Active Directory property was not set\r\n


Message:
The specified Active Directory property is not supported\r\n


Message:
The specified Active Directory property is invalid\r\n


Message:
One or more input parameters are invalid\r\n


Message:
The specified Active Directory object is not bound to a remote resource\r\n


Message:
The specified Active Directory object has not been modified\r\n


Message:
The Active Directory datatype cannot be converted to/from a native DS datatype\r\n


Message:
The Active Directory property cannot be found in the cache.\r\n


Message:
The attempted action violates the DS schema rules.\r\n


Message:
The specified column in the Active Directory was not set.\r\n


Message:
The search filter specified is invalid\r\n


Message:
The assignment of application %1 from policy %2 failed.  The error was %%%3.\r\n


Message:
The install of application %1 from policy %2 failed.  The error was %%%3.\r\n


Message:
The removal of the assignment of application %1 from policy %2 failed.  The error was %%%3.\r\n


Message:
The removal of application %1 from policy %2 failed.  The error was %%%3.\r\n


Message:
The reinstall of application %1 from policy %2 failed.  The error was %%%3.\r\n


Message:
Application %1 from policy %2 was configured to upgrade application %3 from policy %4.  The removal\r\nof application %3 from policy %4 failed with error %%%5.  The upgrade will be aborted.\r\n


Message:
The execution of the setup program for application %1 from policy %2 failed.  The setup\r\npath was %3 and the error was %%%4.\r\n


Message:
Failed to apply changes to software installation settings.  %1  The error was %%%2.\r\n


Message:
A network error occurred accessing software installation data in the active directory.  The error was %%%1.\r\n


Message:
Application %1 from policy %2 is an upgrade of application %3 from policy %4 and\r\nwill force application %3 to be removed.\r\n


Message:
Application %1 from policy %2 is an upgrade of application %3 from policy %4 and\r\nwill cause the assignment of application %3 to be removed.\r\n


Message:
The assignment of application %1 from policy %2 succeeded.\r\n


Message:
The install of application %1 from policy %2 succeeded.\r\n


Message:
The removal of the assignment of application %1 from policy %2 succeeded.\r\n


Message:
The removal of application %1 from policy %2 succeeded.\r\n


Message:
The reinstall of application %1 from policy %2 succeeded.\r\n


Message:
Application %1 from policy %2 successfully upgraded application %3 from policy %4.\r\n


Message:
The launch of the setup command for application %1 from policy %2 succeeded.\r\n


Message:
Changes to software installation settings were applied successfully.\r\n


Message:
Warning: %1.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Warning: %1, %2.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Warning: %1, %2, %3.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Warning: %1, %2, %3, %4.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Invalid ProgID.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Error: %1.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Error: %1, %2.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Error: %1, %2, %3.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Error: %1, %2, %3, %4.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
The ATIOEM registry entry was found but was not used to configure the adapter.\r\nThe registry entry is either obsolete or invalid.\r\n


Message:
LFB Aperture conflict, disabling aperture.\r\n


Message:
Insufficient buffer size, unable to proceed.\r\n


Message:
Unable to map required address ranges for graphics card.\r\n


Message:
Unable to obtain configuration information for graphics card.\r\n


Message:
The bus mouse does not exist or was not detected.\r\n


Message:
The Enrollee was not able to successfully authenticate to the Certificate Service.  Please check your security settings.\r\n


Message:
The request was for certificate template (%1) that is not supported by the Certificate Services policy.\r\n


Message:
The request does not contain a certificate template extension or the %1 request attribute.\r\n


Message:
The Certificate Services Policy has changed.\r\n


Message:
The Certificate Services Policy contains no valid Certificate Templates. \r\n


Message:
The Enrollee (%1) has no DNS name registered in the Active Directory. The certificate cannot be generated.\r\n


Message:
The Enrollee (%1) has no E-Mail name registered in the Active Directory.  The E-Mail name will not be included in the certificate.\r\n


Message:
Certificate Services configuration information is corrupted.\r\n


Message:
The Issuing Certificate could not be found.  The Certificate Services may need to be reinstalled.\r\n


Message:
Certificate Services could not find required Active Directory information.\r\n


Message:
The Active Directory containing the Certification Authority no longer exists.\r\n


Message:
Certificate Services issued a certificate for request %1 for %2.\r\n


Message:
Certificate Services left request %1 pending in the queue for %2.\r\n


Message:
The DHCP service failed to initialize the database. \r\nThe following error occurred: %n%1\r\n


Message:
The DHCP service failed to initialize Winsock startup. \r\nThe following error occurred: %n%1\r\n


Message:
The DHCP service failed to start as a RPC server. \r\nThe following error occurred : %n%1\r\n


Message:
The DHCP service failed to initialize Winsock data. \r\nThe following error occurred: %n%1\r\n


Message:
The DHCP service is shutting down due to the following error: %n%1\r\n


Message:
The DHCP service encountered the following error while cleaning \r\nup the pending client records: %n%1\r\n


Message:
The DHCP service issued a NACK (negative acknowledgement message)\r\nto the client, %2, for the address, %1.\r\n


Message:
The DHCP client, %2, declined the address %1.\r\n


Message:
The DHCP Client, %2, released the address %1.\r\n


Message:
The JET Database call returned the following warning : %1.\r\n\r\nAdditional Debug Information: %2.\r\n


Message:
The DHCP service encountered the following error when \r\nbacking up the registry configuration: %n%1\r\n


Message:
The DHCP service failed to restore the database. \r\nThe following error occurred: %n%1\r\n


Message:
The DHCP service failed to restore the DHCP registry configuration. \r\nThe following error occurred: %n%1\r\n


Message:
Scope, %1, is %2 percent full with only %3 IP addresses remaining.\r\n


Message:
The DHCP service could not load the JET database library successfully.\r\n


Message:
The DHCP service could not use the database. If this service\r\nwas started for the first time after the upgrade from NT 3.51 \r\nor earlier, you need to run the utility, upg351db.exe, on the \r\nDHCP database to convert it to the new JET database format. \r\nRestart the DHCP service after you have upgraded the database.\r\n


Message:
The DHCP service will now terminate because the existing database\r\nneeds conversion to Windows 2000 format.  The conversion via the \r\njetconv process, has initiated.  Do not reboot or stop the jetconv\r\nprocess.  \r\n\r\nThe conversion may take up to 10 minutes depending on the size of \r\nthe database.  Terminate DHCP now by clicking OK. This is required \r\nfor the database conversion to succeed.\r\n\r\nNOTE: The DHCP service will be restarted automatically when the \r\nconversion is completed.  To check conversion status, look at the\r\nApplication event log for the jetconv process.\r\n


Message:
The DHCP service has initialized and is ready\r\n


Message:
The DHCP service was unable to read the BOOTP file table from \r\nthe registry.  The DHCP service will be unable to respond to \r\nBOOTP requests that specify the boot file name.\r\n


Message:
The DHCP service was unable to read the global BOOTP file name \r\nfrom the registry.\r\n


Message:
The audit log file cannot be appended.\r\n


Message:
The DHCP service failed to initialize the audit log. \r\nThe following error occurred: %n%1\r\n


Message:
The DHCP service was unable to ping for a new IP address. \r\nThe address was leased to the client.\r\n


Message:
The audit log file could not be backed up.  The following error\r\noccurred: %n%1\r\n


Message:
The installed server callout .dll file has caused an exception.\r\nThe exception was: %n%1.  The server has ignored this exception. \r\nAll further exceptions will be ignored.\r\n


Message:
The installed server callout .dll file has caused an exception.\r\nThe exception was: %n%1.  The server has ignored this exception \r\nand the .dll file could not be loaded.\r\n


Message:
The DHCP service has successfully loaded one or more callout DLLs.\r\n


Message:
The DHCP service has failed to load one or more callout DLLs.  \r\nThe following error occured: %n%1\r\n


Message:
\r\nThe DHCP service was unable to create or lookup the DHCP Users\r\nlocal group on this computer.  The error code is in the data.\r\n


Message:
\r\nThe DHCP server was unable to create or lookup the DHCP Administrators \r\nlocal group on this computer.  The error code is in the data.\r\n


Message:
\r\nThe DHCP service has started to clean up the database.\r\n


Message:
\r\nThe DHCP service has cleaned up the database for unicast \r\nIP addresses -- %1 leases have been recovered and %2 records \r\nhave been removed from the database.\r\n


Message:
\r\nThe DHCP service has cleaned up the database for multicast \r\nIP addresses -- %1 leases have expired (been marked for deletion)\r\nand %2 records have been removed from the database.\r\n


Message:
The DHCP service successfully restored the database.\r\n


Message:
Certificate Services unrevoked the certificate for request %1 for %2.\r\n


Message:
Certificate Services denied request %1.  The request was for %2.\r\n


Message:
Certificate Services denied request %1.  The request was for %2.  Additional information: %3\r\n


Message:
Could not get subject name for a new certificate.\r\n


Message:
Certificate Services denied request %1 because %2.  The request was for %3.\r\n


Message:
Revocation status for a certificate in the CA certificate chain for %1 could not be verified because a server is currently unavailable.  %2.\r\n


Message:
A certificate in the CA certificate chain for %1 could not be verified because no information is available describing how to check the revocation status.  %2.\r\n


Message:
Certificate Services denied request %1 because %2.  The request was for %3.  Additional information: %4\r\n


Message:
Certificate Services could not find required registry information.  The Certificate Services may need to be reinstalled.\r\n


Message:
The Certificate Services did not start: Unable to load an external policy module.\r\n


Message:
Certificate Services were unable to build a new certificate or certificate chain: %1.\r\n


Message:
Certificate Services did not start: Unable to open the certificate store for %%1.  %2.\r\n


Message:
Certificate Services did not start: Unable to find the CA certificate in the certificate store for %1.  %2.\r\n


Message:
Certificate Services did not start: Unable to extract key provider information from the CA certificate for %1.  %2.\r\n


Message:
Certificate Services did not start: Unable to set up a cryptographic context for the CA certificate for %1.  %2.\r\n


Message:
Certificate Services did not start: Version does not match certif.dll.\r\n


Message:
Certificate Services did not start: Unable to initialize OLE: %1.\r\n


Message:
Certificate Services did not start: Unable to initialize the database connection for %1.  %2.\r\n


Message:
Certificate Services did not start: The signature algorithm is unrecognized in the registry value HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CertSvc\\Configuration\\%1\\SignatureAlgorithm.  %2.\r\n


Message:
Certificate Services did not start: The Subject Name Template string in the registry value HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CertSvc\\Configuration\\%1\\SubjectTemplate is invalid.  An example of a valid string is:\r\nCommonName\r\nOrganizationalUnit\r\nOrganization\r\nLocality\r\nState\r\nCountry\r\n


Message:
Certificate Services did not start: The Certificate Date Validity Period string in the registry value HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CertSvc\\Configuration\\%1\\ValidityPeriod is invalid.  Valid strings are "Seconds", "Minutes", "Hours", "Days", "Weeks", "Months" and "Years".\r\n


Message:
Certificate Services could not process request %1 due to an error: %2.  The request was for %3.\r\n


Message:
Certificate Services could not process request %1 due to an error: %2.  The request was for %3.  Additional information: %4\r\n


Message:
Certificate Services could not process request %1 due to an error: %2.  The request was for %3.  The certificate would contain an encoded length that is potentially incompatible with older enrollment software.  Submit a new request using different length input data for the following field: %4\r\n


Message:
Certificate Services did not start: Unable to get certificate server CSP information from registry for %1.  %2.\r\n


Message:
Certificate Services did not start: Hierarchical setup is incomplete.  Use the request file in %1.req to obtain a certificate for this Certificate Server, place it in %1.crt, and run the Certificate Server Hierarchy Configuration tool to complete the installation.\r\n


Message:
The "%1" Exit Module "%2" method caused an exception at address %4.  The exception code is %3.\r\n


Message:
The "%1" Exit Module "%2" method returned an error.  The returned status code is %3.  %4\r\n


Message:
Certificate Services did not start: Unable to acquire a cryptographic context for %1.  %2.\r\n


Message:
Certificate Services did not start: A certificate in the CA certificate chain for %1 has been revoked.  %2.\r\n


Message:
Certificate Services did not start: A certificate in the CA certificate chain for %1 has expired.  %2.\r\n


Message:
A new certificate requested by %2 was issued for%1%3%1\r\nCertificate Type: %4%1\r\nSerial Number: %5%1\r\nCertification Authority: %6 on Server %7%1\r\n


Message:
The Certification Authority was unable to publish the certificate for %1 to the Directory Service.  %2 (%3)\r\n


Message:
The Certification Authority was unable to publish the CRL to the Directory Service.  Publishing will be retried at a later time. %1 (%2)\r\nMicrosoft Corporation


Message:
A specified metaobject path was not found. The metaobject and associated metadata was ignored.\r\n


Message:
A metaobject or metadata was specified more than once. The duplicate ignored.\r\n


Message:
Invalid metadata was specified. The invalid metadata was ignored.\r\n


Message:
The path was not inserted into the string as requested. The probable cause is that the data is at an object at a higher level than the handle.\r\n


Message:
The metadata save prior to backup failed. The previous version of the data was backed up.\r\n


Message:
The specified metadata was not found.\r\n


Message:
The version specified in metadata storage was not recognized.\r\n


Message:
A secure communications channel could not be established with the target server.\r\n


Message:
The DHCP server initialization parameters are incorrect.\r\n


Message:
The DHCP server was unable to open the DHCP client database.\r\n


Message:
The primary host information for the specified subnet was not found.\r\n


Message:
The specified option already exists.\r\n


Message:
The specified option does not exist.\r\n


Message:
The specified address is not available.\r\n


Message:
The specified IP address range is full.\r\n


Message:
An error occurred while accessing the DHCP database. Look at the\r\nDHCP server event log for more information on this error.\r\n


Message:
The specified client already exists in the database.\r\n


Message:
The DHCP server received a message that is not valid.\r\n


Message:
The DHCP server received a message from a client that is not valid.\r\n


Message:
The specified DHCP client is not a reserved client.\r\n


Message:
The specified DHCP client is a reserved client.\r\n


Message:
The specified IP address range is too small.\r\n


Message:
The specified IP address range already exists.\r\n


Message:
The specified IP address is being used by another client.\r\n


Message:
The specified range either overlaps an existing range or is\r\nnot valid.\r\n


Message:
The specified range is an extension of an existing range.\r\n


Message:
The range extension specified is too small.  The range must be\r\nextended by multiples of 32 addresses.\r\n


Message:
The range was extended less than the specified backward extension.\r\nExtend the range by multiples of 32 addresses.\r\n


Message:
DHCP database needs to be upgraded to a newer format.  Look at the\r\nDHCP server event log for more information.\r\n


Message:
An unknown value %2 was returned while waiting for log processing routine thread %1 termination.\r\nThread state is unknown.\r\n


Message:
Error reading log event record.\r\nHandle specified is %1. Return code from ReadEventLog is %2.\r\n


Message:
Error opening event log file %1. Log will not be processed.\r\nReturn code from OpenEventLog is %2.\r\n


Message:
Error pulsing event for log processing routine shutdown event %1.\r\nReturn code from PulseEvent is %2.\r\n


Message:
The trap size of the requested event log exceeds the maximum length of an SNMP trap.\r\n


Message:
Error allocating memory for event log buffer.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the buffer for the trap to be processed.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the storage for the event type string.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the storage for the event category string.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the storage for the computer name string.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the buffer for the varbind queue entry structure.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the buffer for the varbind list.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the buffer for the enterprise OID.\r\nTrap will not be sent.\r\n


Message:
No memory was available to allocate the integer array for the enterprise OID.\r\nTrap will not be sent.\r\n


Message:
An attempt was made to convert a string to an OID, but the string contained non-numeric values.\r\nThe OID cannot be created. Trap will not be sent.\r\n


Message:
Unable to open the registry key for event source for %1. RegOpenKeyEx returned %2.\r\nTrap will not be sent.\r\n


Message:
Unable to locate EventMessageFile for event source for %1. RegOpenKeyEx returned %2.\r\nTrap will not be sent.\r\n


Message:
Unable to expand file name in EventMessageFile for %1. Size needed is %2.\r\nTrap will not be sent.\r\n


Message:
Unable to load file name in EventMessageFile for %1. LoadLibraryEx returned %2.\r\nTrap will not be sent.\r\n


Message:
Principal name is not a valid MSSTD name.\r\n


Message:
Unable to obtain server's security context\r\n


Message:
Unable to open the access token of the current thread\r\n


Message:
Unable to obtain user info from an access token\r\n


Message:
The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method\r\n


Message:
Unable to obtain the client's security blanket\r\n


Message:
Unable to set a discretionary ACL into a security descriptor\r\n


Message:
The system function, AccessCheck, returned false\r\n


Message:
Either NetAccessDel or NetAccessAdd returned an error code.\r\n


Message:
One of the trustee strings provided by the user did not conform to the <Domain>\\<Name> syntax and it was not the "*" string\r\n


Message:
One of the security identifiers provided by the user was invalid\r\n


Message:
Unable to convert a wide character trustee string to a multibyte trustee string\r\n


Message:
Unable to find a security identifier that corresponds to a trustee string provided by the user\r\n


Message:
The system function, LookupAccountSID, failed\r\n


Message:
The File Server for Macintosh service failed to start. \r\nThe Registry contains an invalid value for the maximum sessions parameter.\r\nVerify the value of this parameter through the Computer Managerment Console \r\nand in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters Registry key.\r\n


Message:
The File Server for Macintosh service failed to start. \r\nThe Registry contains an invalid value for the logon message parameter.\r\nVerify the value of this parameter through the Computer Managerment Console \r\nand in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters Registry key.\r\n


Message:
Obsolete:\r\nThe File Server for Macintosh service failed to start. \r\nThe Registry contains an invalid value for the maximum paged memory.\r\nChange the value of this parameter in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters Registry key.\r\n


Message:
Obsolete:\r\nThe File Server for Macintosh service failed to start. \r\nThe Registry contains an invalid value for the maximum non-paged memory\r\nparameter.\r\nChange the value of this parameter in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters Registry key.\r\n


Message:
The File Server for Macintosh service failed to start.\r\nAn error occurred while trying to initialize the AppleTalk Filing Protocol \r\ndriver (SfmSrv.sys) with server parameters.\r\n


Message:
The File Server for Macintosh service failed to start.\r\nAn error occurred while trying to initialize Macintosh-Accessible volumes.\r\nThe error code is in the data.\r\n


Message:
Failed to register volume "%1" with the File Server for Macintosh service.\r\nThis volume may be removed from the Registry by using the Server Manager or\r\nFile Manager tools.\r\n


Message:
The File Server for Macintosh service failed to start. \r\nAn error occurred while trying to initialize the AppleTalk Filing \r\nProtocol driver (SfmSrv.sys) with the extension/creator/type associations.\r\n


Message:
The File Server for Macintosh service failed to start.\r\nAn error occurred while trying to initialize the AppleTalk Filing Protocol \r\ndriver (SfmSrv.sys) with the server icons.\r\n


Message:
Failed to register icon "%1" with the File Server for Macintosh service.\r\nThis icon can no longer be used by the service.\r\n


Message:
A system resouce could not be allocated for the File Server for Macintosh service.\r\nUnable to create a Server Helper thread.\r\nThe error code is in the data.\r\n


Message:
The File Server for Macintosh service was unable to open a handle to the \r\nAppleTalk Filing Protocol file system driver (Sfmsrv.sys).\r\n


Message:
The File Server for Macintosh service was unable to open a handle to the \r\nLocal Security Authority.\r\n


Message:
The File Server for Macintosh service was unable to contact a \r\ndomain controller to obtain domain information.\r\n


Message:
The File Server for Macintosh service was unable to send domain information \r\nto the AppleTalk Filing Protocol file system driver.\r\n


Message:
An error occured while checking user's credentials.\r\nOperation was not completed.\r\n


Message:
A corrupt extension "%1" was detected in the Registry.\r\nThis value was ignored and processing was continued.\r\nChange the value for this extension in the \r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters\\Extensions Registry key.\r\nRestart the service if the corrected extension is to be used.\r\n


Message:
Unable to stop the File Server for Macintosh service.\r\nA system specific error has occured.\r\nThe error code is in the data.\r\n


Message:
Not used\r\nThe Registry contains an invalid value for the path to the Macintosh\r\ncode-page file.\r\n


Message:
An error occurred while initializing the File Server for Macintosh service.\r\nA Server Helper thread could not be initialized.\r\nThe specific error code is in the data.\r\n


Message:
The File Server for Macintosh service failed to start.\r\nUnable to load the AppleTalk Filing Protocol file system driver.\r\nThe specific error code is in the data.\r\n


Message:
The Registry contains invalid information for the volume "%1". \r\nThe value was ignored and processing was continued.\r\nChange the value for this volume in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters\\Volumes Registry key.\r\nRestart the service if the corrected information is to be used\r\nfor the volume.\r\n


Message:
The File Server for Macintosh service was unable to load resource\r\nstrings.\r\n


Message:
A corrupt Creator/Type pair with creator "%2" and type "%1" was detected\r\nin the Registry. This value was ignored and processing was continued.\r\nChange the value for this Creator/Type pair in the\r\nSYSTEM\\CurrentControlSet\\Services\\MacFile\\Parameters\\Type_Creators Registry key.\r\nRestart the service if the corrected information is to be used\r\nfor the Creator/Type pair.\r\n


Message:
The File Server for Macintosh service was unable to contact a domain controler.\r\nThe service will continue to retry periodically until it succeeds or\r\nuntil the service is manually stopped.\r\n


Message:
The File Server for Macintosh service started successfully.\r\n


Message:
Unable to delete the directory "Network Trash Folder" from volume "%1".\r\n


Message:
Unable to create the directory "Network Trash Folder" on volume "%1".\r\n


Message:
Unable to read internal server information from file "%1".\r\n


Message:
Unable to write internal server information to file "%1".\r\n


Message:
Not used.\r\nUnable to lock a range of bytes for "%1".\r\n


Message:
Unable to unlock a range of bytes for "%1".\r\n


Message:
Unable to query the file size for "%1".\r\n


Message:
Unable to set the file size for "%1".\r\n


Message:
Unable to query time/date information for "%1".\r\n


Message:
Unable to set time/date information for ""%1".\r\n


Message:
Unable to query alternate data stream names for "%1".\r\n


Message:
Unable to query the short ( MS-DOS compatible) filename for "%1".\r\n


Message:
Not used.\r\nUnable to obtain security information.\r\n


Message:
Unable to query the file system type for directory "%1".\r\n


Message:
Desktop database for volume "%1" could not be loaded. Reconstructing the database.\r\n


Message:
Not used.\r\nUnable to load the MSV1_0 authentication package.\r\n


Message:
Unable to load the Macintosh character set.\r\n


Message:
Unable to register the server name with the network. Make sure no other server is using this name.\r\n


Message:
Not used.\r\nAn error occurred on the network.\r\n


Message:
Unable to process requests due to insufficient resources.\r\n


Message:
Unable to send attention to a connected user.\r\n


Message:
Unable to allocate a system resource (IRP).\r\nSystem may be low on memory.\r\n


Message:
Unable to allocate a system resouces (Memory Descriptor List - MDL).\r\nSystem may be low on memory.\r\n


Message:
An internal error occurred.\r\nError occured while waiting on single object to change state.\r\n


Message:
Not used.\r\nUnable to create a process.\r\n


Message:
Unable to query contents of directory "%1".\r\n


Message:
Error in creating File object for current Appletalk address.\r\n


Message:
Not used.\r\nAn error occured on the network.\r\n


Message:
An error occured while setting the File Server status block during initialization. The File Server was not started.\r\n


Message:
Volume %1 is being reindexed.\r\nThe volume will be available for use after indexing is over.\r\n


Message:
An error occured while creating the system-level process token during\r\nthe File Server driver initialization.\r\nThe File Server could not be started.\r\n


Message:
Not used.\r\nUnable to register with the Local Security Authority.\r\n


Message:
Not used.\r\nUnable to create a device object.\r\n


Message:
Unable to query group membership for the user.\r\n


Message:
Unable to translate Macintosh used ANSI characters into Unicode characters.\r\nThe specfic error is in the data.\r\n


Message:
Unable to translate Unicode characters into Macintosh used ANSI characters.\r\nThe specfic error is in the data.\r\n


Message:
Internal server information for file "%1" was corrupted. Setting default information.\r\n


Message:
Unable to update the Desktop database for volume "%1". There may not be enough disk space.\r\n


Message:
Not used.\r\nUnable to impersonate a client.\r\n


Message:
Not used.\r\nUnable to revert from impersonating a client.\r\n


Message:
Unable to allocate paged memory resource.\r\n


Message:
Unable to allocate nonpaged memory resources.\r\n


Message:
Not used.\r\nUnable to authenticate user.\r\n


Message:
Unable to logon user "%1".\r\n


Message:
The maximum directory ID has been reached on volume "%1". No more files or directories can be created on this volume.\r\n


Message:
Unable to update the index database for the Macintosh-Accessible volume "%1". There may not be enough disk space.\r\n


Message:
A directory change notification was missed on volume "%1".\r\n


Message:
Session from user "%2" was timed out and disconnected by the server.\r\nThe AppleTalk address of the Macintosh workstation is in the data.\r\n


Message:
Guest session was timed out and disconnected by the server.\r\nThe AppleTalk address of the Macintosh workstation is in the data.\r\n


Message:
Not used.\r\nA uniprocessor driver was loaded on a multiprocessor system. \r\nThe driver could not load.\r\n


Message:
Updating the Desktop database version for volume "%1".\r\n


Message:
Number of files and folders in volume "%1" is greater than 65535.\r\nOlder Macintosh clients may not function correctly in this situation due\r\nto Macintosh volume limitation.\r\n


Message:
Unable to activate volume "%1".  The available non-paged memory in the system * is not adequate to handle the large number of folders within this volume.  \r\nReducing the number of folders can help.\r\n


Message:
Unable to allocate virtual memory.  \r\nReducing the number of folders can help.\r\n


Message:
Session from user "%2" was timed out and disconnected by the server.\r\nThe IP address of the Macintosh workstation is in the data.\r\n


Message:
Guest session was timed out and disconnected by the server.\r\nThe IP address of the Macintosh workstation is in the data.\r\n


Message:
Index database for volume %1 is being updated because the server detected an older\r\nversion.  The volume will be visible on the network after indexing is complete.  For\r\nvery large volumes, this can take several minutes.\r\n


Message:
Not used\r\nThe MacPrint Service has started.\r\n


Message:
The TrueImage Interpreter was unable to retrieve the default printer\r\ncharacteristics. The error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to allocate memory.\r\n


Message:
The TrueImage Interpreter was unable to generate the Error Page. The\r\nerror code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to retrieve data from the print\r\nspooler. The error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to render the print job.\r\nThe error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to initialize the required information to begin processing the job.\r\nThe error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to query the font list correctly to begin processing the job.\r\n


Message:
The TrueImage Interpreter has reached its limit for internal fonts. No more\r\nfonts can be defined.\r\n


Message:
The TrueImage Interpreter failed to allocate memory required to process a job. The job will not print.\r\n


Message:
The TrueImage Interpreter process was unable to start succesfully.\r\nThe error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to set the correct security privilege\r\nand cannot print the job. The error code returned from the system was %1.\r\n


Message:
The printer %1 could not be registered on the AppleTalk network.\r\n


Message:
The printer %1 could not be registered because another printer by the same name\r\nalready exists on this AppleTalk network.\r\n


Message:
Not more than 127 printers can be shared out by the MacPrint service.\r\nPlease enable printer sharing on not more than 127 printers connected to the\r\nWindows 2000 server. Otherwise, printer jobs will be lost and shared printers \r\nmay not be able to be seen from Macintosh clients. Current printer count \r\nin hexadecimal is in the data.\r\n\r\n


Message:
Unique name required.  A log or alert with name '%s' already exists.


Message:
At least one provider is no longer active in the system.\r\nWould you like to remove all inactive providers from the %1 settings?%r\r\nInactive providers:\r\n


Message:
The %1 log or alert has not started.\r\nRefresh the log or alert list to view current status,\r\nor see the application event log for any errors. \r\n


Message:
To view existing log sessions and alert scans on %1, you must have read access to the\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\SysmonLog\\Log Queries\r\nregistry subkey and its subkeys on that system. Administrators can use Regedt32.exe\r\nto grant the required permissions. See the Registry Editor Help file for details on how\r\nto change the security on a subkey.\r\n


Message:
To complete this task, you must have full control access to the\r\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\SysmonLog\\Log Queries\r\nregistry subkey on %1. In general, administrators have this access by default.\r\nAdministrators can grant access to users using the Security menu in Regedt32.exe.%r\r\nYou must also have the right to start or otherwise configure services on the\r\nsystem. Administrators have this right by default and can grant it to users with\r\nGroup Policy Editor in the Computer Management snap-in.\r\n


Message:
The Performance Logs and Alerts service has not been installed on %1. The service will\r\nbe installed the first time that an Administrator opens\r\nPerformance Logs and Alerts to view log sessions and alert scans.\r\n


Message:
Unable to access computer bootup state on %1. The trace logs node will not be opened. System message is:  \r\n


Message:
Modifications are not allowed for default logs and alerts.\r\nYou can start or stop the session from the context menu\r\nStart or Stop items or from the associated toolbar buttons.\r\n


Message:
Unable to access registered trace providers on %1. The %2 properties will not be opened. System message is:\r\n


Message:
The boot mode for %1 is a fail-safe mode. Trace providers\r\nare available only in normal mode. The trace logs node\r\nwill not be opened.\r\n


Message:
The settings do not contain any complete HTML System Monitor objects.\r\n


Message:
The %1 log or alert has not stopped.\r\nRefresh the list to update current status,\r\nor view the application event log for any errors. \r\n


Message:
Unable to complete the current operation on the %1 log or alert. System message is:. \r\n


Message:
Unable to read the Last Modified value of the %1 log or alert configuration.\r\nThis log or alert will not be started.\r\nThe error code returned is in the data.\r\n


Message:
Unable to allocate a data block for the %1 log or alert configuration.\r\nThis log or alert will not be started.\r\nThe error code returned is in the data.\r\n


Message:
Unable to start the thread for the %1 log or alert configuration.\r\nThis log or alert will not be started.\r\nThe error code returned is in the data.\r\n


Message:
Unable to start the trace session for the %1 trace log configuration.\r\nOnly one instance of each trace provider can be enabled at any given time.\r\n


Message:
Unable to enable any trace providers for the %1 trace log configuration.\r\nThis log will not be started.\r\n


Message:
The database code page is not valid for this NT installation CodePage=%1\r\n


Message:
Partitioning wizard unable to load setupstr.dll.  Please verify that setupstr.dll is present and registered.\r\n


Message:
Partitioning wizard unable to setup tables, stored procedures, indices, and data on target db (%1).  Verify target db is valid, stable, and empty.\r\n


Message:
Partitioning wizard unable to load dscomobj.dll.  Please verify that %1 exists or refresh your install.\r\n


Message:
Partitioning wizard: %1 appears to be invalid or out of date.  Please refresh your install.\r\n


Message:
Partitioning wizard has lost database integrity.  Partition may be invalid.\r\n


Message:
Partitioning setup failed and the DSOGRID table could not be restored to its previous state.  System unstable, consult documentation.\r\n


Message:
Partitioning setup failed and the SUBREFS table could not be restored to its previous state.  System unstable, consult documentation.\r\n


Message:
Deleted a partitioned container but was unable to remove partition info from the DSOGRID table.  System unstable, consult documentation.\r\n


Message:
Add Db Server admin call made with an invalid value partition id for container %1.  Most likely cause is attempt to configure more value partition db's than were specified in initial partitioning configuration.\r\n


Message:
Query failed attempting to determine the value partition count for container %1.  Verify parameters being passed to the AddDbServer interface and target database state, and check event log for SQL errors."\r\n


Message:
Could not find value partition count for container %1.  Verify parameters being passed to the AddDbServer interface and admin interface call sequence."\r\n


Message:
Out of sync stored procedure indicates that a database for this server may not have been updated with the current mcis2upd.sql script.  Please run this script from your Site Server 3.0 Update for MCIS 2.0 installation site.\r\n


Message:
IISADMIN service recreated an account %1.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
IISADMIN service found that account %1 is disabled. Some IIS functions can fail because of that reason.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
The MS Telnet Service has started successfully.\r\n


Message:
Windows cannot set the timer. %s Return value  (%d).


Message:
The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible.\r\n


Message:
The local WINS requested a remote WINS to update the version number of\r\na database record owned by the remote WINS. The remote WINS could not do the \r\nupdate and reported an error.\r\n


Message:
WINS received an error while registering replicas. It will not register any\r\nadditional replicas of this WINS at this time (the address is in the data section \r\n4th-8th byte). Check a previous log entry to determine the reason for this.\r\nIf you get the same error during subsequent replication with the above \r\npartner WINS, you may want to restore the WINS database from the backup.\r\n


Message:
WINS received an error while trying to register a group's replica with name, %1.\r\nThe replica is owned by the WINS with the address given in the data section.\r\n


Message:
WINS received an error while trying to register the unique entry with the \r\nname, %1.\r\n


Message:
WINS received an error while trying to register the group entry with the \r\nname, %1.\r\n


Message:
WINS received an error while trying to update the version number of a record in\r\nthe WINS database.\r\n


Message:
WINS received an error while trying to release a record in the WINS database.\r\n


Message:
WINS received an error while trying to query a record in the WINS database.\r\n


Message:
WINS received a replica whose state is incorrect. For example, the state may\r\nbe RELEASED or the replica might be an Internet group that does not have any\r\nmembers but the state is not TOMBSTONE.\r\n


Message:
The Scavenger thread was unable to change its priority level.\r\n


Message:
***A name release request was received for a record that didn't match the\r\nunique or group type indicated in the request. The request has been ignored.\r\n


Message:
A name release request was received for the record name, %2, that did not\r\nhave the same address as the requestor. The request has been ignored.\r\n


Message:
An error was encountered while trying send a push trigger notification to a\r\nremote WINS. The exception code is the second DWORD of the data section.\r\n


Message:
An error was encountered while trying to service a pull range request from a\r\nremote WINS. The exception code is the second DWORD of the data section.\r\n


Message:
WINS was either provided a bad command code or it became corrupt.\r\n


Message:
The static data file that is used to initialize the WINS database is too big.\r\n


Message:
An error was encountered during an operation on the static data file, %1.\r\n


Message:
The name of the file, after expansion, is bigger than WINS can handle. \r\nThe condensed string is, %1.\r\n


Message:
The shell stopped unexpectedly and %1 was restarted.\r\n


Message:
\r\nThe automatically enrolled certificate of type %1 is being renewed for the following reason(s):\r\n%2\r\n


Message:
The automatically enrolled certificate of type %1 is being re-enrolled for the following reason(s):\r\n%2\r\n


Message:
Automatic enrollment against the certification authority %4 for a certificate of type %3 has\r\nfailed.  (%1) %2.   Another certification authority will be tried.\r\n


Message:
The certificate returned from an auto-enrollment is incorrect.  Subsequent auto-enrollment cycles\r\nwill ignore reasons for failure.  Please contact your system administrator.  The reasons for failure are\r\nlisted below:\r\n%2\r\n


Message:
The certificate does not fulfill the intended usage requirements specified by the certificate template:\r\nCertificate: %1\r\nCertificate Template: %2\r\n\r\n


Message:
The certificate does not fulfill the key usage requirements specified by the certificate template:\r\nCertificate: %1\r\nCertificate Template: %2\r\n\r\n


Message:
The certificate does not fulfill the basic constraints requirements specified by the certificate template:\r\nCertificate: %1\r\nCertificate Template: %2\r\n\r\n


Message:
The certificate does not contain the template name specified by the certificate template:\\n\r\nCertificate: %1\\n\r\nCertificate Template: %2\r\n\r\n


Message:
The certificate does not contain the any of the principal names specified for this user:\r\nPrincipal Name(s): %1\r\n\r\n


Message:
The subject name of this certificate does not contain the e-mail name for this user:\r\nUser e-mail name(s): %1\r\n\r\n


Message:
The alternate subject name of this certificate does not contain the e-mail name for this user:\r\nUser e-mail name(s): %1\r\n\r\n


Message:
This certificate does not contain the e-mail name for this user:\r\nUser e-mail name(s): %1\r\n\r\n


Message:
The certificate does not contain the DNS name of the machine:\r\nDNS Name(s): %1\r\n\r\n


Message:
This certificate does not contain the Directory Name of the user or machine:\r\nDirectory Name(s): %1\r\n\r\n


Message:
This certificate does not contain the Active Directory object identifier of the user or machine.\r\n\r\n


Message:
This certificate contains an Active Directory object identifier, but should not.\r\n\r\n


Message:
The certificate is no longer trusted for the following reason (%1) %2.\r\n\r\n


Message:
The certificate's issuer is no longer allowed by the autoenrollment object.\r\n\r\n


Message:
The certificate will expire soon.\r\n\r\n


Message:
The Scavenger thread encountered an error while cleaning up the owner-address\r\ntable. It will try again after the Verify interval has elapsed.\r\n


Message:
WINS is trying to update the version number of a database record that it\r\ndoes not own. This is a serious error if the WINS server is updating the\r\nrecord after a conflict. It is not a serious error if the WINS server is\r\nupdating the record as a result of a request to do so from a remote WINS\r\nserver (When a remote WINS server notices a conflict between an active owned\r\nentry and a replica it informs the owner of the replica to update the version\r\nnumber of the record. It is possible that the replica is no longer owned by\r\nthe remote WINS).\r\n\r\nCheck a previous log entry to determine which situation applies here.\r\n


Message:
The special group mask specified is not valid. It has either a non-hexadecimal \r\ncharacter or is less than 32 characters in length. A hexadecimal character is \r\nin the range 0-F (or 0-f).\r\n


Message:
WINS tried to get its addresses but failed. WINS will recover when the \r\nIP address comes back.\r\n


Message:
WINS did not get back any names from NetBIOS over TCP/IP (NetBT) when it did an \r\nadapter status.\r\n


Message:
WINS could not initialize properly with the security subsystem.\r\nAt initialization, WINS creates a security object and attaches an \r\nAccess Control List (ACL) to it. This security object is then used to \r\nauthenticate Remote Procedure Call (RPC) calls made to WINS. WINS could not \r\ncreate the above security object.\r\n


Message:
The client application does not have the permissions required to execute the \r\nfunction.\r\n


Message:
When WINS replicated with its partners, one of the partners showed there was more data that actually existed. WINS adjusted its counter so that new registrations and updates are seen by its partners. This means that recovery did not work properly. You may want to check which of the partners has the highest 
version number orresponding to the local WINS. Shut down WINS and restart after specifying this number in the registry.


Message:
Too many concurrent static initializations are occurring. The number of such initializations currently active is given in the data section. This could be caused by reinitialization or imports from the WINS Manager tool. Try to initialize again.


Message:
WINS encountered a low memory condition. Check to see if the system is running \r\nout of virtual memory.\r\n


Message:
WINS has initialized its log for this invocation.\r\n


Message:
WINS initialized properly and is now fully operational.\r\n


Message:
WINS was terminated by the service controller. WINS will gracefully terminate.\r\n


Message:
WINS is being gracefully terminated by the administrator. The address of the administrator is %1.\r\n


Message:
WINS is being abruptly terminated by the administrator. The address of the administrator is %1.\r\n


Message:
WINS received a Name Request with an invalid operation code. The request is being thrown away.\r\n


Message:
The connection was aborted by the remote WINS. Remote WINS may not be configured to replicate with the server.\r\n


Message:
***There are no records in the registry for the key.\r\n


Message:
The WINS database of name-to-address mappings is empty. It could mean that a\r\nprevious invocation of WINS created the database and then went down before\r\nany registration could be done.\r\n


Message:
The WINS database of owner-to-address mappings is empty. It could mean that\r\na previous invocation of WINS created the table and then went down before\r\nits own entry could be added. The WINS server went down very fast\r\n(even before all its threads could become fully operational).\r\n


Message:
***WINS could not read the InitTimeReplication field of the pull/push key.\r\n


Message:
WINS could not read the Refresh interval from the registry\r\n


Message:
WINS could not read the Tombstone interval from the registry\r\n


Message:
WINS could not read the Verify interval from the registry\r\n


Message:
***WINS could not read the retry count for retrying communication with a remote WINS.\r\n


Message:
WINS could not read the Tombstone Timeout from the registry.\r\n


Message:
WINS could not read the ConsistencyCheck value (type DWORD) from the\r\nParameters\\ConsistencyCheck subkey in the registry. The first consistency \r\ncheck is done at the time specified in the SpTime entry under the \r\nConsistencyCheck subkey and is limited by the MaxRecsAtATime value. If the \r\ntime is not specified, the check is done at 2 am.\r\n\r\nTo correct the problem, open the registry and verify that the ConsistencyCheck \r\nsubkey has been correctly sent up and all required values have been set. Correct the values, as needed.\r\n


Message:
WINS could not read the MaxRecsAtATime value (type DWORD) in the\r\nWins\\Parameters\\ConsistencyCheck subkey of the registry. Set this value \r\nif you do not want WINS to replicate more than a set number of records in \r\none cycle while doing periodic consistency checks of the WINS database. \r\nWhen doing a consistency check, WINS replicates all records of an owner WINS \r\nby either going to that WINS or to a replication partner. At the end of doing \r\na consistency check for an owner's records, it checks to see if it has \r\nreplicated more than the specified value in the current consistency check \r\ncycle. If the value has been exceeded, the consistency check stops, otherwise \r\nit continues. In the next cycle, it starts from where it left off and wraps \r\naround to the first owner if required.\r\n


Message:
WINS could not read the UseRplPnrs value of the Wins\\Parameters\\ConsistencyCheck \r\nkey. If this value is set to a non-zero (DWORD) value, WINS will do a \r\nconsistency check of the owners in its database by going to one or more of \r\nits replication partners. If the owner of the records happens to be a \r\nreplication partner, WINS will go to it, otherwise it will pick one at \r\nrandom. Set this value if you have a large number of WINSs in your \r\nconfiguration and/or if you do not want the local WINS to go to any WINS that\r\nis not a replication partner.\r\n


Message:
WINS just did a consistency check on the records owned by the WINS with the address, %1.\r\nThe number of records inserted, updated, and deleted are in the data section\r\n(second, third, fourth DWORDS).\r\n


Message:
WINS could not do a consistency check on the records. This could be because WINS\r\nwas directed to do the consistency check only with replication partners and\r\nit currently does not have any pull replication partners. To get around this\r\nproblem, you should either allow WINS to do consistency check with owner WINSs\r\nor configure the WINS with one or more pull partners.\r\n


Message:
***WINS received a packet that has the wrong format. For example, a label may be \r\nMore than 63 octets.\r\n


Message:
***No records meeting the %1 criteria were found in the WINS database.\r\n


Message:
WINS could not find any records in the WINS database.\r\nThis means there are no active or tombstone records in the database.\r\nIt could be that the records being requested by a remote WINS server have\r\neither been released or do not exist.\r\n


Message:
***The special group has reached its limit. WINS cannot add any more members.\r\n


Message:
***The address database already has reached the limit of owners. This is 100.\r\nThis error was noticed while attempting to add the address given in the data section.\r\n


Message:
The WINS server received an update notification from the non-configured WINS \r\nserver at the address, %1. The WINS server rejected it. This means the remote\r\nWINS server is not in the list of Push partners (WINS servers under the Pull \r\nkey) and the administrator has prohibited (using the registry) replication with\r\nnon-configured WINS servers. If you want this WINS server to accept update\r\nnotifications from non-configured WINS servers, then set the\r\nWins\\Paramaters\\RplOnlyWCnfPnrs value in the registry to 0.\r\n


Message:
WINS received an update notification from the WINS with the address, %1. \r\nWINS accepted it.\r\n


Message:
The WINS server received a pull request from the non-configured WINS server \r\nwith the address, %1. The WINS server rejected it since the remote WINS server \r\nis not in the list of Pull partners (WINS servers under the Pull key) and the \r\nadministrator has prohibited (using the registry) replication with \r\nnon-configured partners. If you want this WINS server to accept update\r\nnotifications from WINS servers not in the "pull partner" list, then set the \r\n"replication only with configured partners" value in the registry to 0.\r\n


Message:
The datafiles key could not be opened.\r\n


Message:
The NetBios over TCP/IP (NetBT) key could not be opened.\r\n


Message:
The NetBios over TCP/IP (NetBT) key could not be queried.\r\n


Message:
A worker thread was created by the administrator.\r\n


Message:
A worker thread was terminated by the administrator.\r\n


Message:
The owner-address mapping table had an entry with a non-zero owner ID and \r\nan address the same as the local WINS address. The entry has been marked as \r\ndeleted in the in-memory table.\r\n


Message:
An error occurred while trying to inform a remote WINS to update\r\nthe version number.\r\n


Message:
The local WINS is going to inform a remote WINS to update the version number of\r\na record. This is because the local WINS encountered a conflict between an \r\nactive owned name and an active replica that it pulled from a replication \r\npartner.\r\n


Message:
The local WINS has been informed by a remote WINS with address, %1, to update\r\nthe version number of a record. This is because the remote WINS encountered a \r\nconflict between an active owned name and an active replica that it pulled from \r\na replication partner.\r\n


Message:
A remote WINS requested the update of the version stamp of a record, but the \r\nrecord could not be found. Check to see if the record was deleted or updated.\r\n


Message:
***A name mismatch was noticed while verifying the validity of old replicas.\r\nThe local record has the name %1 while the replica pulled in from the WINS\r\nthat owns this record has the name %2.  This could mean that the remote\r\nWINS was brought down and then up again but its version counter value was\r\nnot set to its previous value before termination.\r\n


Message:
WINS adjusted the Maximum Records at a time parameter of the ConsistencyCheck key. The value specified, %2, was changed to the minimum value, %1. These are the maximum number of records that will be replicated at any one time for a consistency check.


Message:
WINS has encountered an error that caused it to shut down.


Message:
The replication Pull thread is shutting down due to an error. Restart WINS.


Message:
The replication Push thread is shutting down due to an error. Restart WINS.


Message:
The Name Challenge thread is shutting down due to an error. Restart WINS.


Message:
The worker thread is shutting down due to an error. Restart WINS.


Message:
An abnormal error occurred during the WINS initialization. Check the \r\napplication and system logs for information on the cause. WINS may need \r\nto be restarted.\r\n


Message:
WINS could not properly set up the WINS database. Look at the application log \r\nfor errors from the Exchange component, ESENT.\r\n


Message:
A worker thread could not be created. The computer may be low on resources.\r\n


Message:
A thread could not be created. The computer may be low on resources.\r\n


Message:
An error occurred from which WINS will try to recover. If the recovery fails, check previous event log entries to determine what prevented a successful recovery. Take the appropriate action to solve the error that prevented recovery.


Message:
WINS could not create the notification socket. Make sure the TCP/IP driver is installed and running properly.


Message:
WINS could not create the User Datagram Protocol (UDP) socket to listen for Connection notification messages sent by another Pull thread in the local WINS.


Message:
WINS could not create the TCP socket for listening to TCP connections. Make sure the TCP/IP driver is installed and running properly.


Message:
WINS could not create the TCP socket for making a TCP connection. Make sure the TCP/IP stack is installed and running properly.


Message:
An address could not bind to a socket. Make sure the TCP/IP stack is installed and running properly.

This event might mean that the 'nameserver' port (specified in the services file) which is used as the default by WINS for replication and discovering 
other WINSs has been taken by another process or service running on this computer. You have two options - either bring down that other process or service or direct WINS to use another port. If you choose the second option, set the 
value 'PortNo' (REG_DWORD) under the Wins\Parameters subkey in the registry to 1512. 

NOTE: Changing the port number this way will prevent this WINS from replicating or discovering other WINSs unless they too are directed to use the same port number as this WINS.


Message:
WINS could not listen on the Winsock socket.


Message:
Winsock Select returned with an error.\r\n


Message:
***%1 returned with an error code of %2.


Message:
WINS created a socket and called the 'bind' WinSock API to bind a handle to it. On calling 'getsockname' to determine the address bound, WINS received an error.


Message:
An attempt to connect to the remote WINS server with address %1 returned with\r\nan error. Check to see that the remote WINS server is running and available,\r\nand that WINS is running on that server.\r\n


Message:
WINS could not read from the User Datagram Protocol (UDP) socket.


Message:
WINS could not read from NetBIOS over TCP/IP (NetBT).


Message:
***A Winsock Sendto message could not send all the bytes.\r\n


Message:
WINS could not send a User Datagram Protocol (UDP) message to a WINS client.\r\n


Message:
A Winsock Sendto message returned with an error.\r\n


Message:
***The Winsock receive function returned with an unexpected error.\r\n


Message:
The WinSock send function returned with an unexpected error.\r\n


Message:
A message was received on an association. The association is in a bad state.\r\nThis indicates a bug in the WINS code. Restart WINS.\r\n


Message:
WINS could not allocate a responder association. Check to see if the system is low on resources.\r\n


Message:
***WINS could not allocate an initiator association. Check to see if the system is low on resources.\r\n


Message:
***WINS could not allocate an implicit dialogue. Check to see if the system is low on resources.\r\n


Message:
WINS could not get information about the DATAFILES key. Check to see if the \r\npermissions on the key are set properly, system resources are low, or the \r\nregistry is having a problem.\r\n


Message:
WINS could not get information about the SPEC_GRP_MASKS key. Check to see if the \r\npermissions on the key are set properly, system resources are low, or the \r\nregistry is having a problem.\r\n


Message:
WINS could not open a Pull subkey. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.\r\n


Message:
WINS could not open a Push subkey. Check to see if the permissions on the key \r\nare set properly, system resources are low, or the registry is having a problem.\r\n


Message:
WINS could not get the time interval from a Pull record.\r\n


Message:
***WINS could not get the time interval from a Push record.\r\n


Message:
WINS could not get the update count from a Push record. No default will be used. \r\n


Message:
WINS could not close an open key. Check to see if the permissions on the \r\nkey are set properly, system resources are low, or the registry is having a problem.\r\n


Message:
WINS Timer thread encountered an exception.\r\n


Message:
WINS Push thread encountered an exception. A recovery will be attempted.\r\n


Message:
WINS Pull thread encountered an error during the process of sending a push \r\nnotification to another WINS. The error code is given in the data section.\r\n


Message:
A WINS Remote Procedure Call (RPC) thread encountered an error.\r\n


Message:
The WINS TCP Listener thread encountered an error.\r\n


Message:
The WINS User Datagram Protocol (UDP) Listener thread encountered an error.\r\n


Message:
The WINS Scavenger thread encountered an error.\r\n


Message:
The WINS Challenger thread encountered an error.\r\n


Message:
A WINS worker thread encountered an error.\r\n


Message:
The WINS Scavenger thread could not scavenge a record. This record will \r\nbe ignored. The Scavenger will continue on to the next available record.\r\nCheck the application log for the Exchange component, ESENT.\r\n


Message:
The WINS Replication Pull Handler could not connect to a WINS server.\r\nAll retries failed. WINS will try again after a set number of replication \r\ntime intervals have elapsed.\r\n


Message:
WINS did not find any subkeys under the Pull key.


Message:
WINS did not find any subkeys under the Push key.


Message:
An error has prevented WINS from updating the WINS database. The database may be\r\ncorrupt.\r\n


Message:
***WINS has been asked to pull entries from itself. Check all the Pull subkeys of this WINS.\r\n


Message:
WINS was unable to propagate the push trigger.


Message:
WINS sent a name query or a name release with a certain transaction ID.\r\nIt received a response to the request that differed either in the name that it \r\ncontained or in the operation code. WINS has thrown the response away.\r\n


Message:
The WINS database is inconsistent. The number of owners found in the \r\nname-address mapping table are different from the number found in the \r\nowner-address mapping table.\r\n


Message:
WINS could not do a static initialization.\r\n


Message:
An error occurred during the configuration or reconfiguration of WINS.\r\nIf this was encountered during boot time, WINS will come up with default\r\nparameters. You may want to research the cause of this initialization failure\r\nand then reboot WINS.\r\n


Message:
An error occurred during the configuration or reconfiguration of WINS.\r\n


Message:
A lock error has occurred. This could happen if the WINS is trying to send a\r\nresponse on a dialogue that is no longer ACTIVE. An implicit dialogue can\r\ncease to exist if the association it is mapped to terminates. In this case,\r\ngetting a lock error is normal.\r\n


Message:
WINS could not import static mappings from the file, %1.\r\nVerify that the file exists and is readable.\r\n


Message:
WINS encountered an error while processing a push trigger or update \r\nnotification. The error code is given in the data section. If it indicates a \r\ncommunication failure, check to see if the remote WINS that sent the trigger \r\nwent down. If the remote WINS is on a different subnet, then maybe the router \r\nis down.\r\n


Message:
WINS encountered an exception while processing a pull trigger.\r\n


Message:
WINS encountered an exception while retrieving data records.\r\n


Message:
WINS found some database corruption. The record named, %1, is corrupt.\r\nIt could be that recovery from the last crash did not work properly. WINS will\r\ntry to recover. You may decide, however, to restore the WINS database from the \r\nbackup.\r\n


Message:
The following name, %1, is too long. It has been entered in the WINS database.\r\nIf you want the name to be over 15 characters, enclose it in quotes.\r\n


Message:
The computer running the WINS server does not have a valid address.\r\nWhen WINS requested an address, it received 0.0.0.0 as the address.\r\n\r\nNOTE: WINS binds to the first adapter in a machine with more than one adapter\r\nbound to TCP/IP. Check the binding order of adapters and make sure the first\r\none has a valid IP address for the WINS server.\r\n


Message:
WINS encountered an error doing a database backup to directory %1.\r\n


Message:
WINS encountered an error while deleting the file, %1.


Message:
WINS encountered an error while deleting one or more records of a WINS.\r\nThe WINS address is in the second DWORD in data section. Check a previous log\r\nentry to determine what went wrong.


Message:
WINS encountered an error while getting the browser names for a client.


Message:
The length of the message sent by another WINS indicates a very big message.\r\nThere may have been corruption of the data. WINS will ignore this message,\r\nterminate the connection with the remote WINS, and continue.\r\n


Message:
The WINS replicator Pull thread encountered an error while processing a request.\r\nCheck other log entries to determine what went wrong.\r\n


Message:
***WINS does not support this functionality.\r\n


Message:
This WINS computer has %1 processors. It has %2 bytes of physical memory and \r\n%3 bytes of memory available for allocation.\r\n


Message:
The record named, %1, could not replace another record in the WINS database.\r\nThe record's version number is %2. The version number of record in the database is %3.\r\n


Message:
WINS has found some database corruption. It will try to recover.\r\nThis recovery process can take a long time. Do not kill WINS in the middle of \r\nthe recovery. If you do, you will have to restart WINS with a clean database.\r\n


Message:
WINS has exceeded the wait time for all threads to terminate. The number of\r\nthreads still active is given in the second DWORD of the data section.\r\nThe thread that could be stuck is the replicator thread. It could be because \r\nof the other WINS being slow in sending data or reading data. The latter can \r\ncontribute to back-pressure on the TCP connection on which it is trying to \r\nreplicate.\r\n\r\nCheck the partner WINSs to see if one or more is in a bad state. This WINS terminated itself abruptly.\r\n


Message:
The name, %1, is in the wrong format. It has not been put in the\r\nWINS database. Check to see if you have a space before the name. If you want \r\nthis space in the name, enclose the name within quotes.\r\n


Message:
WINS Performance Monitor Counters could not get the WINS statistics.\r\n


Message:
WINS Performance Monitor Counters could not open the event log.\r\n


Message:
***WINS could not open the log file. Check the log path specified in the registry\r\nunder WINS\\Parameters\\LogFilePath and restart WINS, if necessary. WINS is going \r\nto use the default log file path of %%SystemRoot%%\\system32\\WINS.\r\n


Message:
WINS found a name in the WINS database with a length of more than 255 \r\ncharacters. The name was truncated to 17 characters.\r\n


Message:
WINS could not start due to a missing or corrupt database.\r\nRestore the database using WINS Manager (or winscl.exe found in the Windows 2000 Resource Kit) and restart WINS. If WINS still does not start, begin with a fresh \r\ncopy of the database.\r\n\r\nTo do this:\r\n\r\n 1) Delete all the  files in the %%SystemRoot%%\\system32\\WINS directory.\r\n       NOTE: If the WINS database file (typically named wins.mdb) is not in the\r\n       above directory, check the registry for the full filepath.\r\n       Delete the .mdb file.\r\n       NOTE: If jet*.log are not in the above directory, check the registry\r\n       for the directory path. Delete all log files\r\n\r\n 2) Restart WINS.\r\n


Message:
WINS could not start because the existent database must be converted to the\r\nWindows 2000 format. If this is the first invocation of WINS after an upgrade \r\nFrom NT 3.51, you need to run the convert utility (upg351db.exe in the\r\n%%SystemRoot%%\\system32 directory) on the WINS database to convert it to the new \r\ndatabase format. Once you have done that, you should restart WINS.\r\n


Message:
WINS will not start because the existing WINS database needs to be converted \r\nto the Windows 2000 format. WINS has initiated this conversion using a \r\nprocess called JETCONV. Once the conversion is successfully completed, WINS \r\nwill be restarted. The conversion will take anywhere from a few minutes \r\nto an hour depending on the size of the databases to be converted.\r\n\r\nNOTE: Rebooting or ending the JETCONV process before it is completed could\r\ncorrupt your databases. Check the Application Log in the Event Viewer for\r\nthe status of JETCONV.\r\n


Message:
The NoOfWrkThds parameter's value is too large and cannot be supported.


Message:
WINS could not come up because the existing WINS database needs conversion to \r\nthe Windows 2000 format.\r\n\r\nIf this is the first invocation of WINS after an upgrade from NT3.51, first,\r\nyou need to run the convert utility (upg351db.exe in the %%SystemRoot%%\\system32 \r\ndirectory) on the WINS database to convert it to the NT 4.0 database format. \r\nThen, you need to run the convert utility (edbutil.exe in the \r\n%%SystemRoot%%\\system32 directory) on the converted 4.0 WINS database to convert \r\nit to the Windows 2000 database format.\r\n\r\nOnce you have done that, you should restart WINS.\r\n


Message:
WINS could not start because the existing database needs to be converted to \r\nthe Windows 2000 format.\r\n\r\nIf this is the first invocation of WINS after an upgrade from NT 4.0, you need \r\nTo run the convert utility (edbutil.exe in the %%SystemRoot%%\\system32 \r\ndirectory) on the WINS database to convert it to the Windows 2000 database \r\nformat.\r\n\r\nOnce you have done that, you should restart WINS. \r\n


Message:
WINS cannot start because the existing WINS database needs conversion to the\r\nWindows 2000 format. WINS has initiated the conversion using the JETCONV \r\nprocess. Once the conversion is complete, WINS will start automatically. Do not\r\nreboot or kill the JETCONV process. The conversion may take anywhere from a\r\nfew minutes to approximately two hours depending on the size of the databases.\r\n\r\nNOTE: Check the application log to see the status of the WINS database conversion.\r\n


Message:
The WINS Server could not initialize security to allow the read-only operations.


Message:
SMTP service has been started, Version: %1.%2.%3.%4.%5.%6.%7.


Message:
SMTP service instance %1 has been started.


Message:
The CI daemon was hung and subsequently restarted.


Message:
The local WINS server received a request from a remote WINS server that is not the same version. Because the WINS servers are not compatible, the connection was terminated. The version number of the remote WINS server is given in the data section.


Message:
Winsock Send could not send all the bytes. The connection could have been aborted by the remote client.


Message:
***The Name Registration Response could not be sent due to an error. This error was encountered by a NetBT request thread.


Message:
The record with the name, %1, has bad address. It has not been entered in the \r\nWINS database.\r\n


Message:
The WINS server started the burst handling of incoming requests. WINS does this to handle a sudden increase of incoming requests. WINS will also log an event indicating when the burst handling stops. If you see this event frequently, you may want to upgrade the WINS server to a faster computer. You can also try to adjust the burst handling count using the WINS Manager tool.


Message:
The WINS server completed the burst handling of incoming requests because the queue length became a quarter of what it was when burst handling began.


Message:
Members who have view-only access to the WINS Server%0


Message:
Error (%1) encountered while writing to accounting file. MSIDLPM will stop writing to the accounting file, due to the error, and will restart after the next policy cache timeout.


Message:
Contents of %1 migrated to the Windows NT registry.


Message:
The system failed to update and remove host (A) resource records (RRs)
for network adapter%nwith settings:%n%n
  Adapter Name : %1%n
  Host Name : %2%n
  Primary Domain Suffix : %3%n
  DNS server list :%n
    %4%n
  Sent update to server : %5%n
  IP Address(es) :%n
    %6%n%n
The request to remove these records failed because the DNS server refused the update request. The cause of this might be that either (a) this computer is not allowed to update the DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol.


Message:
The system failed to update and remove host (A) resource records (RRs)
for network adapter%nwith settings:%n%n
  Adapter Name : %1%n
  Host Name : %2%n
  Primary Domain Suffix : %3%n
  DNS server list :%n
    %4%n
  Sent update to server : %5%n
  IP Address(es) :%n
    %6%n%n
The reason for this failure was because of a security related problem.
The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. For specific error code, see the record data displayed below.


Message:
The system failed to update and remove host (A) resource records (RRs)
for network adapter%nwith settings:%n%n
  Adapter Name : %1%n
  Host Name : %2%n
  Primary Domain Suffix : %3%n
  DNS server list :%n
    %4%n
  Sent update to server : %5%n
  IP Address(es) :%n
    %6%n%n
The reason the update request failed was because of a system problem. For specific error code, see the record data displayed below.


Message:
The File Replication Service is unable to add this computer to the following
replica set:
%n    "%1"
%n
%nThis could be caused by a number of problems such as:
%n  --  an invalid root path,
%n  --  a missing directory,
%n  --  a missing disk volume,
%n  --  a file system on the volume that does not support NTFS 5.0
%n
%nThe information below may help to resolve the problem:
%nComputer DNS name is "%2"
%nReplica set member name is "%3"
%nReplica set root path is "%4"
%nReplica staging directory path is "%5"
%nReplica working directory path is "%6"
%nWindows error status code is %7
%nFRS error status code is %8
%n
%nOther event log messages may also help determine the problem.  Correct the
problem and the service will attempt to restart replication automatically at
a later time.


Message:
The File Replication Service successfully added this computer to the following
replica set:
%n    "%1"
%n
%nInformation related to this event is shown below:
%nComputer DNS name is "%2"
%nReplica set member name is "%3"
%nReplica set root path is "%4"
%nReplica staging directory path is "%5"
%nReplica working directory path is "%6"


Message:
The File Replication Service successfully added the connections shown below
to the replica set:
%n    "%1"
%n
%n    %2
%n    %3
%n    %4
%n    %5
%n    %6
%n    %7
%n    %8
%n    %9
%n
%nMore information may appear in subsequent event log messages.


Message:
The File Replication Service is in an error state. Files will not replicate
to or from one or all of the replica sets on his computer until the
following recovery steps are performed:
%n
%n Recovery Steps:
%n
%n [1] The error state may clear itself if you stop and restart the FRS service.
This can be done by performing the following in a command window:
%n
%n    net stop ntfrs
%n    net start ntfrs
%n
%nIf this fails to clear up the problem then proceed as follows.
%n
%n [2] For Active Directory Domain Controllers that DO NOT host any DFS
alternates or other replica sets with replication enabled:
%n
%nIf there is at least one other Domain Controller in this domain then
restore the "system state" of this DC from backup (using ntbackup or other
backup-restore utility) and make it non-authoritative.
%n
%nIf there are NO other Domain Controllers in this domain then restore
the "system state" of this DC from backup (using ntbackup or other
backup-restore utility) and choose the Advanced option which marks
the sysvols as primary.
%n
%nIf there are other Domain Controllers in this domain but ALL of
them have this event log message then restore one of them as primary
(data files from primary will replicate everywhere) and the others as
non-authoritative.
%n
%n
%n [3] For Active Directory Domain Controllers that host DFS alternates
or other replica sets with replication enabled:
%n
%n (3-a) If the Dfs alternates on this DC do not have any other replication
partners then copy the data under that Dfs share to a safe location.
%n (3-b) If this server is the only Active Directory Domain Controller for this
domain then, before going to (3-c),  make sure this server does not have any
inbound or outbound connections to other servers that were formerly Domain
Controllers for this domain but are now off the net (and will never be
coming back online) or have been fresh installed without being demoted.
To delete connections use the Sites and Services snapin and look for
%nSites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
%n (3-c) Restore the "system state" of this DC from backup (using ntbackup
or other backup-restore utility) and make it non-authoritative.
%n (3-d) Copy the data from step (3-a) above to the original location
after the sysvol share is published.
%n
%n
%n [4] For other Windows 2000 servers:
%n
%n (4-a)  If any of the DFS alternates or other replica sets hosted by
this server do not have any other replication partners then copy the
data under its share or replica tree root to a safe location.
%n (4-b)  net stop ntfrs
%n (4-c)  rd /s /q  %1
%n (4-d)  net start ntfrs
%n (4-e)  Copy the data from step (4-a) above to the original location after
the service has initialized (5 minutes is a safe waiting time).
%n
%nNote: If this error message is in the eventlog of all the members of a
particular replica set then perform steps (4-a) and (4-e) above on only
one of the members.


Message:
The File Replication Service has detected what appears to be an attempt
to change the root path for the following replica set:
%n    "%1"
%n
%nThis is not allowed.  To perform this operation you must remove this member
from the replica set and add the member back with the new root path.
%n
%nIt is possible that this is a transient error due to Active Directory
replication delays associated with updating FRS configuration objects.  If
file replication does not take place after an appropriate waiting time,
which could be several hours if cross site Active Directory replication
is required, you must delete and re-add this member to the replica set.
%n
%nInformation related to this event is shown below:
%nComputer DNS name is "%2"
%nReplica set member name is "%3"
%nThe current Replica set root path is "%4"
%nThe desired new Replica set root path is "%5"
%nReplica staging directory path is "%6"


Message:
The File Replication Service has detected a duplicate connection object between
this computer "%6" and a computer named "%1".
%nThis was detected for the following replica set:
%n    "%2"
%n
%nThis is not allowed and replication will not occur between these two
computers until the duplicate connection objects are removed.
%n
%nIt is possible that this is a transient error due to Active Directory
replication delays associated with updating FRS configuration objects.  If
file replication does not take place after an appropriate waiting time,
which could be several hours if cross site Active Directory replication
is required, you must manually delete the duplicate connection objects by
following the steps below:
%n
%n [1] Start the Active Directory Sites and Services Snapin.
%n [2] Click on "%3, %4, %5, %6, %7".
%n [3] Look for duplicate connections from "%1" in site "%8".
%n [4] Delete all but one of the connections.


Message:
The File Replication Service has detected a duplicate connection object between
this computer "%7" and a computer named "%1".
%nThis was detected for the following replica set:
%n    "%2"
%n
%nThis is not allowed and replication will not occur between these two
computers until the duplicate connection objects are removed.
%n
%nIt is possible that this is a transient error due to Active Directory
replication delays associated with updating FRS configuration objects.  If
file replication does not take place after an appropriate waiting time,
which could be several hours if cross site Active Directory replication
is required, you must manually delete the duplicate connection objects by
following the steps below:
%n
%n [1] Start the Active Directory Users and Computers Snapin.
%n [2] Click the view button and advanced features to display the system node.
%n [3] Click on "%3, %4, %5".
%n [4] Under "%5" you will see one or more DFS related replica set objects.
Look for the FRS member object "%6" under the subtree for replica set "%2".
%n [5] Under "%6" look for duplicate connections from "%1".
%n [6] Delete all but one of the connections.


Message:
The system failed to update and remove host (A) resource records (RRs)
for network adapter%nwith settings:%n%n
  Adapter Name : %1%n
  Host Name : %2%n
  Primary Domain Suffix : %3%n
  DNS server list :%n
    %4%n
  Sent update to server : %5%n
  IP Address(es) :%n
    %6%n%n
The reason for this failure is because the DNS server sent the update
either (a) does not support the DNS dynamic update protocol, or (b) the
authoritative zone for the DNS domain name specified in these A RRs does
not currently accept DNS dynamic updates.


Message:
The system failed to update and remove host (A) resource records (RRs)
for network adapter%nwith settings:%n%n
  Adapter Name : %1%n
  Host Name : %2%n
  Primary Domain Suffix : %3%n
  DNS server list :%n
    %4%n
  Sent update to server : %5%n
  IP Address(es) :%n
    %6%n%n
The request to remove these records failed because the DNS server refused
the update request. The cause of this might be that either (a) this
computer is not allowed to update the DNS domain name specified by these
settings, or (b) because the DNS server authorized to perform updates for
the zone that contains these RRs does not support the DNS dynamic update
protocol.


Message:
The Certification Authority was unable to publish a certificate to the file %1.


Message:
IISADMIN service was unable to update the activation identity for all IIS COM+ applications. Some IIS applications may fail to function.
%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.


Message:
The account %1 cannot be converted to be a domain controller account as
its object class attribute in the directory is not computer or is not 
derived from computer.If this is caused by an attempt to install a pre windows 
2000 domain controller in a windows 2000 domain, then you should precreate the 
account for the domain controller with the correct object class.


Message:
The SNMP Service has encountered a fatal error.


Message:
The SNMP Service is ignoring trap destination %1 because it is invalid.


Message:
The SNMP Service is not designed for this operating system.


Message:
The SNMP Service registry key %1 is missing or misconfigured.


Message:
During the installation of the Directory Service, this server's machine account was deleted hence preventing this Domain Controller from starting up.


Message:
QoS RSVP has failed to find any interfaces with traffic control enabled. Install QoS traffic control services via network and dial-up connections.


Message:
Error loading map file %1, error %2.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Logon failed for user %1 : %2.\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Digest authentication: invalid authentication for user "%1", realm "%2".\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


Message:
Digest authentication: unrecognized user "%1", realm "%2".\r\n%nFor additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.\r\n


