# Windows 2000 Events

Message:
Invalid message for a combo box because it does not have an edit control.\r\n


Message:
Cannot set nonlocal hook without a module handle.\r\n


Message:
This hook procedure can only be set globally.\r\n


Message:
The journal hook procedure is already installed.\r\n


Message:
The hook procedure is not installed.\r\n


Message:
Invalid message for single-selection list box.\r\n


Message:
LB_SETCOUNT sent to non-lazy list box.\r\n


Message:
This list box does not support tab stops.\r\n


Message:
Cannot destroy object created by another thread.\r\n


Message:
The window does not have a system menu.\r\n


Message:
The specified instance type is not valid.\r\n


Message:
The operation must be performed at a master DSA.\r\n


Message:
The object class attribute must be specified.\r\n


Message:
An attempt was made to modify an object to include an attribute that is not legal for its class.\r\n


Message:
The specified attribute is already present on the object.\r\n


Message:
The specified attribute is not present, or has no values.\r\n


Message:
An attribute's single value constraint has been violated.\r\n


Message:
An attribute's range constraint has been violated.\r\n


Message:
The attribute cannot be removed because it is not present on the object.\r\n


Message:
The attribute value cannot be removed because it is not present on the object.\r\n


Message:
The specified root object cannot be a subref.\r\n


Message:
Chained evaluation is not permitted.\r\n


Message:
The operation could not be performed because the object's parent is either uninstantiated or deleted.\r\n


Message:
Having a parent that is an alias is not permitted. Aliases are leaf objects.\r\n


Message:
The object and parent must be of the same type, either both masters or\r\nboth replicas.\r\n


Message:
The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object.\r\n


Message:
The format of the bootstrap protocol file table is incorrect.  \r\nThe correct format is:\r\n<requested boot file name1>,<boot file server name1>,<boot file name1>\r\n<requested boot file name2>,<boot file server name2>,<boot file name2>\r\netc...\r\n


Message:
The specified superscope name is too long.\r\n


Message:
The DHCP audit-log file path is too long.\r\n


Message:
The DHCP service received a request for a valid IP address \r\nthat is not administered by this server.\r\n


Message:
The DHCP Server failed to receive a notification of interface \r\nlist changes.  Some of the interfaces will not be enabled in\r\nthe DHCP service.\r\n


Message:
The DHCP database needs to be upgraded to the current Jet format.  \r\nLook at the DHCP service event log for more information.\r\n


Message:
The DHCP Server is not servicing any clients on the network \r\nbecause it could not determine if it is authorized to run.  \r\nThis might be due to network problems or insufficient resources.\r\n


Message:
The DHCP service is shutting down because another DHCP server \r\nwith the IP address %1 is active on the network.\r\n


Message:
The DHCP service is not servicing any clients on the network \r\nbecause it has determined that it is not authorized to run.\r\n


Message:
The DHCP service is unable to contact the directory service \r\nfor domain %1.  The DHCP service will continue to attempt \r\nto contact the directory service.  During this time, no clients \r\non the network will be serviced.\r\n


Message:
The DHCP service is not servicing any clients on the network \r\nbecause its authorization information conflicts with another \r\nDHCP server whose IP address is %1 and is active on domain %2.\r\n


Message:
The authentication request was dropped because it contained an unexpected packet.\r\n


Message:
The context handle changed during a remote procedure call.\r\n


Message:
The binding handles passed to a remote procedure call do not match.\r\n


Message:
The stub is unable to get the remote procedure call handle.\r\n


Message:
The account used is a computer account. Use your global user account or local user account to access this server.\r\n


Message:
The account used is a server trust account. Use your global user account or local user account to access this server.\r\n


Message:
The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.\r\n


Message:
The server is in use and cannot be unloaded.\r\n


Message:
The specified image file did not contain a resource section.\r\n


Message:
The specified resource type cannot be found in the image file.\r\n


Message:
The specified resource name cannot be found in the image file.\r\n


Message:
The specified resource language ID cannot be found in the image file.\r\n


Message:
Not enough quota is available to process this command.\r\n


Message:
The remote procedure call was cancelled.\r\n


Message:
The binding handle does not contain all required information.\r\n


Message:
A communications failure occurred during a remote procedure call.\r\n


Message:
The requested authentication level is not supported.\r\n


Message:
The error specified is not a valid Windows RPC error code.\r\n


Message:
A UUID that is valid only on this computer has been allocated.\r\n


Message:
A security package specific error occurred.\r\n


Message:
The user tried to dial-in outside of permitted hours.\r\n


Message:
The user tried to connect using an unauthorized phone number.\r\n


Message:
The user tried to connect using an unauthorized dial-in media.\r\n


Message:
A constraint defined in the Remote Access Policy failed. \r\n


Message:
The service was unable to write the authentication or accounting record. Make sure the drive is not full and is connected to the server.\r\n


Message:
The authentication request was dropped because the session timed out.\r\n


Message:
%1 (%2) File system error %4 during IO on database %3. Please restore the databases from a previous backup.\r\n


Message:
%1 (%2) IO size mismatch on database %3. IO size %4 expected while returned size is %5.\r\n


Message:
%1 (%2) File system error %4 during IO on log file %3.\r\n


Message:
%1 (%2) IO size mismatch on log file %3. IO size %4 expected while returned size is %5.\r\n


Message:
%1 (%2) Must install language support for language id 0x%3.\r\n


Message:
%1 (%2) The database engine %3.%4.%5.%6 started.\r\n


Message:
%1 (%2) The database engine is initiating recovery steps.\r\n


Message:
%1 (%2) The database engine is replaying log file %3.\r\n


Message:
%1 (%2) The database engine has successfully completed recovery steps.\r\n


Message:
%1 (%2) Direct read found corrupted page %3 with error %4. Please restore the databases from a previous backup.\r\n


Message:
%1 (%2) The database engine is initiating index cleanup of database '%3' as a result of an NT version upgrade from %4.%5.%6 SP%7 to %8.%9.%10 SP%11.\r\n


Message:
%1 (%2) The database engine has successfully completed index cleanup on database '%3'.\r\n


Message:
Unable to locate ParameterMessageFile for %1. RegOpenKeyEx returned %2.\r\n


Message:
RegNotifyChangeKeyValue failed with a return code of %1.\r\nInitialization will continue, but registry changes will not be updated until SNMP is stopped and restarted.\r\n


Message:
SNMP Event Log Extension Agent is starting.\r\n


Message:
SNMP Event Log Extension Agent has terminated.\r\n


Message:
Performance threshold values have been reached.\r\nTrap processing is being quiesed. Further traps will not be sent without operator intervention.\r\n


Message:
Performance threshold values have been restored by operator intervention.\r\nTrap processing has been resumed.\r\n


Message:
The system cannot perform a JOIN or SUBST at this time.\r\n


Message:
The system cannot join or substitute a drive to or for a directory on the same drive.\r\n


Message:
The directory is not a subdirectory of the root directory.\r\n


Message:
The path specified is being used in a substitute.\r\n


Message:
Not enough resources are available to process this command.\r\n


Message:
The path specified cannot be used at this time.\r\n


Message:
An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute.\r\n


Message:
System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.\r\n


Message:
The number of specified semaphore events for DosMuxSemWait is not correct.\r\n


Message:
DosMuxSemWait did not execute; too many semaphores are already set.\r\n


Message:
The DosMuxSemWait list is not correct.\r\n


Message:
The volume label you entered exceeds the label character\r\nlimit of the target file system.\r\n


Message:
The recipient process has refused the signal.\r\n


Message:
The segment is already discarded and cannot be locked.\r\n


Message:
The address for the thread ID is not correct.\r\n


Message:
The argument string passed to DosExecPgm is not correct.\r\n


Message:
No more threads can be created in the system.\r\n


Message:
A directory service error has occurred.\r\n


Message:
The operation can only be performed on an internal master DSA object.\r\n


Message:
Insufficient access rights to perform the operation.\r\n


Message:
The object cannot be added because the parent is not on the list of possible superiors.\r\n


Message:
Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM).\r\n


Message:
The directory service encountered an error parsing a name.\r\n


Message:
The directory service cannot get the attribute type for a name.\r\n


Message:
The name does not identify an object; the name identifies a phantom.\r\n


Message:
The security descriptor is too short.\r\n


Message:
Failed to create name for deleted object.\r\n


Message:
The parent of a new subref must exist.\r\n


Message:
The object must be a naming context.\r\n


Message:
It is not permitted to add an attribute which is owned by the system.\r\n


Message:
The driver could not create the required device object.\r\n


Message:
Failed to apply IP Security on port %1 because of error: %2. \r\nNo calls will be accepted to this port.\r\n


Message:
Interface %1 is unreachable because it is not currently connected to the network.\r\n


Message:
Security Enabled Global Group Created:%n\r\n%tNew Account Name:%t%1%n\r\n%tNew Domain:%t%2%n\r\n%tNew Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Security Enabled Global Group Changed:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Security Enabled Global Group Member Added:%n\r\n%tMember Name:%t%1%n\r\n%tMember ID:%t%2%n\r\n%tTarget Account Name:%t%3%n\r\n%tTarget Domain:%t%4%n\r\n%tTarget Account ID:%t%5%n\r\n%tCaller User Name:%t%6%n\r\n%tCaller Domain:%t%7%n\r\n%tCaller Logon ID:%t%8%n\r\n%tPrivileges:%t%9%n\r\n


Message:
Security Enabled Global Group Member Removed:%n\r\n%tMember Name:%t%1%n\r\n%tMember ID:%t%2%n\r\n%tTarget Account Name:%t%3%n\r\n%tTarget Domain:%t%4%n\r\n%tTarget Account ID:%t%5%n\r\n%tCaller User Name:%t%6%n\r\n%tCaller Domain:%t%7%n\r\n%tCaller Logon ID:%t%8%n\r\n%tPrivileges:%t%9%n\r\n


Message:
Security Enabled Global Group Deleted:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Windows NT is shutting down.\r\nAll logon sessions will be terminated by this shutdown.\r\n


Message:
An authentication package has been loaded by the Local Security Authority.\r\nThis authentication package will be used to authenticate logon attempts.\r\n%n\r\nAuthentication Package Name:%t%1\r\n


Message:
A trusted logon process has registered with the Local Security Authority.\r\nThis logon process will be trusted to submit logon requests.\r\n%n\r\n%n\r\nLogon Process Name:%t%1\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation client is not recognized.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. No other information is available.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation client has not provided sufficient information to allow assignment to an Emulated LAN.\r\n


Message:
The Local ATM address (%2) can not be used because it is already registered by another node in the network.\r\n


Message:
The File Replication Service stopped without cleaning up.\r\n


Message:
The File Replication Service has stopped after taking an assertion failure.\r\n


Message:
The File Replication Service failed a consistency check (%3) in "%1" at line %2.\r\n%n\r\n%nThe File Replication Service will restart automatically at a later time.\r\nFor more information about the automatic restart right click on\r\nMy Computer and then click on Manage, System Tools, Services,\r\nFile Replication Service, and Recovery.\r\n


Message:
The File Replication Service cannot start replica set %1 on computer %2\r\nfor directory %3 because the type of volume %4 is not NTFS 5.0 or later.\r\n%n\r\n%nThe volume's type can be found by typing "chkdsk %4".\r\n%n\r\n%nThe volume can be upgraded to NTFS 5.0 or later by typing "chkntfs /E %4".\r\n


Message:
The File Replication Service on the computer %1 cannot communicate with\r\nthe File Replication Service on the computer %2.\r\n%n\r\n%nVerify that the computer %2 is up and running.\r\n%n\r\n%nVerify that the File Replication Service is running on %2 by\r\ntyping "net start ntfrs" on %2.\r\n%n\r\n%nVerify that the network is functioning between %1 and %2 by\r\ntyping "ping %1" on %2 and "ping %2" on %1.\r\nIf the pings succeed then retry the failed operation.\r\nIf the pings fail then there may be problems with the DNS server.\r\n%n\r\n%nThe DNS server is responsible for mapping computer names to IP addresses.\r\nThe commands "ipconfig" and "nslookup" help diagnose problems with the\r\nDNS server.\r\n%n\r\n%nTyping "ipconfig /all" will list the computer's IP address and the IP\r\naddress of the computer's DNS servers. Type "ping <DNS server's IP address>"\r\nto verify that a DNS server is available. The DNS mapping for %2 or %1\r\ncan be verified by typing "nslookup" and then typing "%2" and then "%1"\r\non %1 and %2. Be sure to check out the DNS server on both %1 and %2;\r\na DNS problem on either computer will prevent proper communication.\r\n%n\r\n%nSome network problems between %1 and %2 can be cleared up by flushing\r\nthe DNS Resolver Cache. Type "ipconfig /flushdns".\r\n%n\r\n%nSome network problems between %1 and %2 can be cleared up by renewing\r\nthe IP address. Type "ipconfig /release" followed by "ipconfig /renew".\r\n%n\r\n%nSome network problems between %1 and %2 can be cleared up by resetting\r\nthe computer's DNS entry. Type "net stop NetLogon" followed by\r\n"net start NetLogon".\r\n%n\r\n%nSome problems between %1 and %2 can be cleared up by restarting\r\nthe File Replication Service. Type "net stop ntfrs" followed by\r\n"net start ntfrs".\r\n%n\r\n%nSome problems between %1 and %2 can be cleared up by restarting\r\nthe computers %1 and %2 AFTER CLOSING RUNNING APPLIATIONS,\r\nespecially dcpromo. Click on Start, Shutdown, select Restart, and\r\nclick on OK.\r\n%n\r\n%nOther network and computer problems are beyond the scope of\r\nthis event log message.\r\n


Message:
The File Replication Service is stopping on computer %1 because there is no free\r\nspace on the volume containing %2.\r\n%n\r\n%nThe available space on the volume can be found by typing\r\n"dir %2".\r\n%n\r\n%nOnce free space is made available on the volume containing %2,\r\nthe File Replication Service can be restarted immediately by typing\r\n"net start ntfrs". Otherwise, the File Replication Service will\r\nrestart automatically at a later time.\r\n%n\r\n%nFor more information about the automatic restart right click on\r\nMy Computer and then click on Manage, System Tools, Services, File\r\nReplication Service, and Recovery.\r\n%n\r\n%nFor more information about managing space on a volume type "copy /?",\r\n"rename /?", "del /?", "rmdir /?", and "dir /?".\r\n


Message:
The File Replication Service on computer %1 is stopping because the\r\ndatabase %2 is corrupted.\r\n%n\r\n%nThe database can be recovered by typing "esentutl /d %2 /l%3 /s%4".\r\n%n\r\n%nOnce the database has been successfully recovered the\r\nFile Replication Service can be restarted by typing "net start ntfrs".\r\n


Message:
The File Replication Service could not grant an unknown user access to the\r\nAPI "%1".\r\n%n\r\n%nAccess checks can be disabled for "%1" by running regedt32.\r\n%n\r\n%nClick on Start, Run, and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,\r\nCurrentControlSet, Services, NtFrs, Parameters, Access Checks, "%1", and "%2".\r\nChange the string to Disabled.\r\n%n\r\n%nPermissions can be changed by highlighting "%1" and then clicking on the\r\ntoolbar option Security and then Permissions...\r\n


Message:
Server Message Blocks (SMBs) received%0\r\n


Message:
Server Message Blocks (SMBs) transmitted%0\r\n


Message:
Initialization of automatic certificate enrollment has failed.  There is possible corruption\r\nof system DLL's required for auto-enrollment.  (%1) %2\r\n


Message:
Windows 2000 could not be started as configured.\r\nA previous working configuration was used instead.\r\n


Message:
The exception 0x%1 occurred in the application %2 at location 0x%3.\r\n


Message:
The servers %1 and  %3 both claim to be an NT Domain Controller for\r\nthe %2 domain. One of the servers should be removed from the\r\ndomain because the servers have different security identifiers\r\n(SID).\r\n


Message:
The server %1 and %2 both claim to be the primary domain\r\ncontroller for the %3 domain. One of the servers should be\r\ndemoted or removed from the domain.\r\n


Message:
The computer %1 tried to connect to the server %2 using\r\nthe trust relationship established by the %3 domain. However, the\r\ncomputer lost the correct security identifier (SID)\r\nwhen the domain was reconfigured. Reestablish the trust\r\nrelationship.\r\n


Message:
The computer has rebooted from a bugcheck.  The bugcheck was:\r\n%1.\r\n%2\r\nA full dump was not saved.\r\n


Message:
The computer has rebooted from a bugcheck.  The bugcheck was:\r\n%1.\r\n%2\r\nA dump was saved in: %3.\r\n


Message:
The computer or domain %1 trusts domain %2.  (This may be an indirect\r\ntrust.)  However, %1 and %2 have the same machine security identifier\r\n(SID).  NT should be re-installed on either %1 or %2.\r\n


Message:
The computer or domain %1 trusts domain %2.  (This may be an indirect\r\ntrust.)  However, %2 is not a valid name for a trusted domain.\r\nThe name of the trusted domain should be changed to a valid name.\r\n


Message:
Could not share the User or Script path.\r\n


Message:
The password for this computer is not found in the local security\r\ndatabase.\r\n


Message:
An internal error occurred while accessing the computer's\r\nlocal or network security database.\r\n


Message:
The Netlogon service could not initialize the replication data\r\nstructures successfully. The service was terminated.  The following\r\nerror occurred: %n%1\r\n


Message:
The Netlogon service failed to update the domain trust list.  The\r\nfollowing error occurred: %n%1\r\n


Message:
The Netlogon service could not add the RPC interface.  The\r\nservice was terminated. The following error occurred: %n%1\r\n


Message:
The Netlogon service could not read a mailslot message from %1 due\r\nto the following error: %n%2\r\n


Message:
Invalid operation on the encoding/decoding handle.\r\n


Message:
Incompatible version of the serializing package.\r\n


Message:
Incompatible version of the RPC stub.\r\n


Message:
The previous certificate or CRL context was deleted.\r\n


Message:
The certificate does not have a property that references a private key.\r\n


Message:
Cannot find the certificate and private key for decryption.\r\n


Message:
Cannot find the certificate and private key to use for decryption.\r\n


Message:
Not a cryptographic message or the cryptographic message is not formatted correctly.\r\n


Message:
The signed cryptographic message does not have a signer for the specified signer index.\r\n


Message:
Final closure is pending until additional frees or closes.\r\n


Message:
No Dll or exported function was found to verify revocation.\r\n


Message:
The revocation function was unable to check revocation for the certificate.\r\n


Message:
The revocation function was unable to check revocation because the revocation server was offline.\r\n


Message:
The certificate is not in the revocation server's database.\r\n


Message:
The string contains a non-numeric character.\r\n


Message:
The string contains a non-printable character.\r\n


Message:
The string contains a character not in the 7 bit ASCII character set.\r\n


Message:
The string contains an invalid X500 name attribute key, oid, value or delimiter.\r\n


Message:
The dwValueType for the CERT_NAME_VALUE is not one of the character strings.  Most likely it is either a CERT_RDN_ENCODED_BLOB or CERT_TDN_OCTED_STRING.\r\n


Message:
The Put operation can not continue.  The file needs to be resized.  However, there is already a signature present.  A complete signing operation must be done.\r\n


Message:
The cryptographic operation failed due to a local security option setting.\r\n


Message:
No DLL or exported function was found to verify subject usage.\r\n


Message:
The called function was unable to do a usage check on the subject.\r\n


Message:
The value for the parameter %1 to the browser service was illegal.\r\n


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


Message:
%2 could not allocate a resource of type %3 due to system resource problems.\r\n


Message:
%2 could not allocate a resource of type %3 due to its configured size of %4.\r\n


Message:
%2 could not allocate a resource of type %3 due to a specifically configured limit of %4.\r\n


Message:
A SAP announcement was sent over %2 which is configured for multiple\r\nnetworks, but no internal network is configured. This may prevent\r\nmachines on some networks from locating the advertised service.\r\n


Message:
The value for the %2 parameter %3 was illegal.\r\n


Message:
The DNS Client service failed to reach DNS server at address %1. It will\r\nnot use this DNS server for %2 seconds.\r\n


Message:
The system failed to register network adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS Server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe cause of this DNS registration failure was because the DNS update\r\nrequest timed out after being sent to the specified DNS Server. This is\r\nprobably because the authoritative DNS server for the name being updated\r\nis not running.%n%n You can manually retry registration of the network\r\nadapter and its settings by typing "ipconfig /registerdns" at the command\r\nprompt. If problems still  persist, contact your network systems\r\nadministrator to verify network conditions.\r\n


Message:
The system failed to register network adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe cause of this DNS registration failure was because of DNS server failure.\r\nThis may be due to a zone transfer that has locked the DNS server for the\r\napplicable zone that your computer needs to register itself with.%n%n\r\n(The applicable zone should typically correspond to the Adapter-specific\r\nDomain Suffix that was indicated above.) You can manually retry registration\r\nof the network adapter and its settings by typing "ipconfig /registerdns"\r\nat the command prompt. If problems still persist, contact your network\r\nsystems administrator to verify network conditions.\r\n


Message:
The system failed to register network adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason it could not register was because either: (a) the DNS server\r\ndoes not support the DNS dynamic update protocol, or (b) the primary zone\r\nauthoritative for the registering names does not currently accept dynamic\r\nupdates.%n%n To add or register a DNS host (A) resource record using the\r\nspecific DNS name for this adapter, contact your DNS server or network\r\nsystems administrator.\r\n


Message:
The system failed to register network adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason it could not register was because the DNS server refused the\r\ndynamic update request. This could happen for the following reasons:\r\n(a) current DNS update policies do not allow this computer to update\r\nthe DNS domain name configured for this adapter, or (b) the authoritative\r\nDNS server for this DNS domain name does not support the DNS dynamic update\r\nprotocol.%n%n\r\nTo register a DNS host (A) resource record using the specific DNS domain\r\nname for this adapter, contact your DNS server or network systems\r\nadministrator.\r\n


Message:
The system failed to register network adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe system could not register the DNS update request because of a\r\nsecurity related problem. This could happen for the following reasons:\r\n(a) the DNS domain name that your computer is trying to register could\r\nnot be updated because your computer does not have the right permissions,\r\nor (b) there might have been a problem negotiating valid credentials\r\nwith the DNS server to update.%n%n\r\nYou can manually retry DNS registration of the network adapter and its\r\nsettings by typing "ipconfig /registerdns" at the command prompt. If\r\nproblems still persist, contact your DNS server or network systems\r\nadministrator. For specific error code information, click the Record\r\nData tab.\r\n


Message:
The system failed to register network adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the DNS update request could not be completed was because\r\nof a system problem. You can manually retry DNS registration of the\r\nnetwork adapter and its settings by typing "ipconfig /registerdns"\r\nat the command prompt. If problems still persist, contact your DNS\r\nserver or network systems administrator. For specific error code\r\ninformation, click the Record Data tab.\r\n


Message:
The system failed to register pointer (PTR) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe reason that the system could not register these RRs was because the\r\nupdate request that was sent to the specified DNS server timed out. This\r\nis probably because the authoritative DNS server for the name being\r\nregistered is not running.%n%n You can manually retry DNS registration\r\nof the network adapter and its settings by typing "ipconfig /registerdns"\r\nat the command prompt. If problems still persist, contact your DNS\r\nserver or network systems administrator. For specific error code\r\ninformation, click the Record Data tab.\r\n


Message:
Force user logoff how long after time expires?:%0\r\n\r\n


Message:
Lock out account after how many bad passwords?:%0\r\n\r\n


Message:
Length of password history maintained:%0\r\n


Message:
Primary Domain controller for workstation domain:%0.\r\n


Message:
Unable to find a trustee name that corresponds to a security identifier provided by the user\r\n


Message:
The system function, LookupAccountName, failed\r\n


Message:
Unable to set or reset a serialization handle\r\n


Message:
Unable to obtain the Windows directory\r\n


Message:
Unable to close a serialization handle or a file handle.\r\n


Message:
The number of ACEs in an ACL exceeds the system limit.\r\n


Message:
Not all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream.\r\n


Message:
The version of ACL format in the stream is not supported by this implementation of IAccessControl\r\n


Message:
Insufficient quota to complete the requested service.\r\n


Message:
The paging file is too small for this operation to complete.\r\n


Message:
This operation requires an interactive window station.\r\n


Message:
This operation returned because the timeout period expired.\r\n


Message:
No event log file could be opened, so the event logging service did not start.\r\n


Message:
The event log file has changed between read operations.\r\n


Message:
The Windows Installer service could not be accessed.  Contact your support personnel to verify that the Windows Installer service is properly registered.\r\n


Message:
This action is only valid for products that are currently installed.\r\n


Message:
The configuration data for this product is corrupt.  Contact your support personnel.\r\n


Message:
The installation source for this product is not available.  Verify that the source exists and that you can access it.\r\n


Message:
This installation package cannot be installed by the Windows Installer service.  You must install a Windows service pack that contains a newer version of the Windows Installer service.\r\n


Message:
An attempt was made to add an object using an RDN that is not the RDN defined in the schema.\r\n


Message:
None of the requested attributes were found on the objects.\r\n


Message:
The attribute specified in the operation is not present on the object.\r\n


Message:
Illegal modify operation. Some aspect of the modification is not permitted.\r\n


Message:
The specified server cannot perform the requested operation.\r\n


Message:
An unexpected network error occurred.\r\n


Message:
The remote adapter is not compatible.\r\n


Message:
Space to store the file waiting to be printed is not available on the server.\r\n


Message:
Your file waiting to be printed was deleted.\r\n


Message:
The specified network name is no longer available.\r\n


Message:
The network resource type is not correct.\r\n


Message:
The name limit for the local computer network adapter card was exceeded.\r\n


Message:
The network BIOS session limit was exceeded.\r\n


Message:
The remote server has been paused or is in the process of being started.\r\n


Message:
No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.\r\n


Message:
The specified printer or disk device has been paused.\r\n


Message:
The directory or file cannot be created.\r\n


Message:
Storage to process this request is not available.\r\n


Message:
The local device name is already in use.\r\n


Message:
The specified network password is not correct.\r\n


Message:
A write fault occurred on the network.\r\n


Message:
The system cannot start another process at this time.\r\n


Message:
Cannot create another system semaphore.\r\n


Message:
The exclusive semaphore is owned by another process.\r\n


Message:
The semaphore is set and cannot be closed.\r\n


Message:
Cannot request exclusive semaphores at interrupt time.\r\n


Message:
The previous ownership of this semaphore has ended.\r\n


Message:
The program stopped because an alternate diskette was not inserted.\r\n


Message:
The disk is in use or locked by\r\nanother process.\r\n


Message:
The system cannot open the\r\ndevice or file specified.\r\n


Message:
There is not enough space on the disk.\r\n


Message:
No more internal file identifiers available.\r\n


Message:
The target internal file identifier is incorrect.\r\n


Message:
The IOCTL call made by the application program is not correct.\r\n


Message:
The list box identifier was not found.\r\n


Message:
Thread does not have a clipboard open.\r\n


Message:
The window is not a valid dialog window.\r\n


Message:
%1 (%2) The database engine %3.%4.%5 started.\r\n


Message:
%1 (%2) The database engine stopped.\r\n


Message:
%1 (%2) The database engine is starting a full backup.\r\n


Message:
%1 (%2) The database engine is starting an incremental backup.\r\n


Message:
%1 (%2) The database engine has completed the backup successfully.\r\n


Message:
%1 (%2) The database engine has stopped the backup with error %3.\r\n


Message:
%1 (%2) The database engine is restoring from backup directory %3.\r\n


Message:
%1 (%2) The database engine has stopped restoring.\r\n


Message:
%1 (%2) The database is running recovery steps.\r\n


Message:
%1 (%2) Database engine error %3 occurred.\r\n


Message:
%1 (%2) Asynchronous overlapped read page error %3 occurred. Please restore the databases from a previous backup.\r\n


Message:
%1 (%2) Synchronous overlapped write page issue error %3 occurred.\r\n


Message:
%1 (%2) Synchronous overlapped write page error %3 occurred.\r\n


Message:
%1 (%2) Synchronous overlapped patch file write page error %3 occurred.\r\n


Message:
%1 (%2) Asynchronous read page time error %3 occurred. Please restore the databases from a previous backup.\r\n


Message:
%1 (%2) Direct read found corrupted page error %3. Please restore the databases from a previous backup.\r\n


Message:
%1 (%2) Buffer I/O thread termination error %3 occurred.\r\n


Message:
%1 (%2) Unable to write to the log. Error %3.\r\n


Message:
%1 (%2) Unable to write to the log header. Error %3.\r\n


Message:
%1 (%2) Unable to read the log. Error %3.\r\n


Message:
%1 (%2) Log version stamp does not match database engine version stamp.\r\n


Message:
%1 (%2) Unable to read the log header. Error %3.\r\n


Message:
The cluster node is not the owner of the resource.\r\n


Message:
The cluster node is not the owner of the group.\r\n


Message:
The cluster resource could not be created in the specified resource monitor.\r\n


Message:
The cluster resource could not be brought online by the resource monitor.\r\n


Message:
The operation could not be completed because the cluster resource is online.\r\n


Message:
The cluster resource could not be deleted or brought offline because it is the quorum resource.\r\n


Message:
The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.\r\n


Message:
The cluster software is shutting down.\r\n


Message:
The group or resource is not in the correct state to perform the requested operation.\r\n


Message:
The properties were stored but not all changes will take effect until the next time the resource is brought online.\r\n


Message:
The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.\r\n


Message:
The cluster resource could not be deleted since it is a core resource.\r\n


Message:
The quorum resource failed to come online.\r\n


Message:
The quorum log could not be created or mounted successfully.\r\n


Message:
The record could not be written to the cluster log since it exceeds the maximum size.\r\n


Message:
The cluster log exceeds its maximum size.\r\n


Message:
No checkpoint record was found in the cluster log.\r\n


Message:
The minimum required disk space needed for logging is not available.\r\n


Message:
The cluster node failed to take control of the quorum resource because the resource is owned by another active node.\r\n


Message:
A cluster network is not available for this operation.\r\n


Message:
A cluster node is not available for this operation.\r\n


Message:
All cluster nodes must be running to perform this operation.\r\n


Message:
A node is in the process of joining the cluster.\r\n


Message:
The cluster local node information was not found.\r\n


Message:
The cluster network interface already exists.\r\n


Message:
The cluster network interface was not found.\r\n


Message:
The cluster request is not valid for this object.\r\n


Message:
The cluster network provider is not valid.\r\n


Message:
OSS ASN.1 Error: Multi-threading conflict.\r\n


Message:
OSS ASN.1 Error: Encode/Decode function not implemented.\r\n


Message:
OSS ASN.1 Error: Function not implemented.\r\n


Message:
OSS ASN.1 Error: Program link error.\r\n


Message:
The signature of the certificate can not be verified.\r\n


Message:
The timestamp signature and/or certificate could not be verified or is malformed.\r\n


Message:
The digital signature of the object did not verify.\r\n


Message:
A certificate's basic constraint extension has not been observed.\r\n


Message:
The certificate does not meet or contain the Authenticode financial extensions.\r\n


Message:
Tried to reference a part of the file outside the proper range.\r\n


Message:
Could not retrieve an object from the file.\r\n


Message:
Could not find the head table in the file.\r\n


Message:
The magic number in the head table is incorrect.\r\n


Message:
The offset table has incorrect values.\r\n


Message:
Duplicate table tags or tags out of alphabetical order.\r\n


Message:
A table does not start on a long word boundary.\r\n


Message:
First table does not appear after header information.\r\n


Message:
Too many pad bytes between tables or pad bytes are not 0.\r\n


Message:
File is too small to contain the last table.\r\n


Message:
The signature does not have the correct attributes for the policy.\r\n


Message:
The file did not pass the hints check.\r\n


Message:
User Account password set:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n


Message:
User Account Disabled:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n


Message:
User Account Deleted:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
General Account Database Change:%n\r\n%tType of change:%t%1%n\r\n%tObject Type:%t%2%n\r\n%tObject Name:%t%3%n\r\n%tObject ID:%t%4%n\r\n%tCaller User Name:%t%5%n\r\n%tCaller Domain:%t%6%n\r\n%tCaller Logon ID:%t%7%n\r\n


Message:
User Account Changed:%n\r\n%t%1%n\r\n%tTarget Account Name:%t%2%n\r\n%tTarget Domain:%t%3%n\r\n%tTarget Account ID:%t%4%n\r\n%tCaller User Name:%t%5%n\r\n%tCaller Domain:%t%6%n\r\n%tCaller Logon ID:%t%7%n\r\n%tPrivileges:%t%8%n\r\n


Message:
Domain Policy Changed:%n\r\n%tDomain:%t%t%1%n\r\n%tDomain ID:%t%2%n\r\n%tCaller User Name:%t%3%n\r\n%tCaller Domain:%t%4%n\r\n%tCaller Logon ID:%t%5%n\r\n%tPrivileges:%t%6%n\r\n


Message:
User Account Locked Out:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller Machine Name:%t%2%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n


Message:
Authentication Ticket Granted:%n\r\n%tUser Name:%t%t%1%n\r\n%tSupplied Realm Name:%t%2%n\r\n%tUser ID:%t%3%n\r\n%tService Name:%t%t%4%n\r\n%tService ID:%t%t%5%n\r\n%tTicket Options:%t%t%6%n\r\n%tTicket Encryption Type:%t%7%n\r\n%tPre-Authentication Type:%t%8%n\r\n%tClient Address:%t%t%9%n\r\n


Message:
Service Ticket Granted:%n\r\n%tUser Name:%t%t%1%n\r\n%tUser Domain:%t%t%2%n\r\n%tService Name:%t%t%3%n\r\n%tService ID:%t%t%4%n\r\n%tTicket Options:%t%t%5%n\r\n%tTicket Encryption Type:%t%6%n\r\n%tClient Address:%t%t%7%n\r\n


Message:
Ticket Granted Renewed:%n\r\n%tUser Name:%t%1%n\r\n%tUser Domain:%t%2%n\r\n%tService Name:%t%3%n\r\n%tService ID:%t%4%n\r\n%tTicket Options:%t%5%n\r\n%tTicket Encryption Type:%t%6%n\r\n%tClient Address:%t%7%n\r\n


Message:
All handles to windows in a multiple-window position structure must have the same parent.\r\n


Message:
Cannot process a message from a window that is not a multiple document interface (MDI) window.\r\n


Message:
The window does not have scroll bars.\r\n


Message:
Scroll bar range cannot be greater than 0x7FFF.\r\n


Message:
Cannot show or remove the window in the way specified.\r\n


Message:
Insufficient system resources exist to complete the requested service.\r\n


Message:
The DHCP service is ignoring a request from another DHCP \r\nservice because it is on a different directory service \r\nenterprise (Directory Service Enterprise root = %1)\r\n


Message:
The DHCP service has detected a directory service environment\r\non the network.  If there is directory service on the network, \r\nDHCP service can only run on a server which is part of the directory\r\nservice.  Since this server belongs to a workgroup, the DHCP service \r\nis terminating.\r\n


Message:
The class name being used is unknown or inconrrect.\r\n


Message:
The class name is already in use or the class information \r\nis already in use.\r\n


Message:
The specified scope name is too long.  The name is limited to\r\na maximum of 256 characters.\r\n


Message:
There is already a default scope configured on the server.\r\n


Message:
The Dynamic BOOTP attribute cannot be turned on or off.\r\n


Message:
Conversion of a scope to a DHCP Only scope or to a BOOTP Only scope \r\nis not allowed when DHCP and BOOTP clients both exist in the scope.\r\nManually delete either the DHCP or the BOOTP clients from the scope,\r\nas appropriate for the type of scope being created.\r\n


Message:
The DHCP service could not contact Active Directory.\r\n


Message:
The DHCP service root could not be found in the Active Directory.\r\n


Message:
An unexpected error occurred while accessing the Active Directory.\r\n\r\n


Message:
There were too many errors to proceed.\r\n


Message:
The specified options are already present in the directory service.\r\n


Message:
The specified options are not present in the directory service.\r\n


Message:
The specified classes already exist in the directory service.\r\n


Message:
The specified classes do not exist in the directory service.\r\n


Message:
The specified servers are already present in the directory service.\r\n


Message:
The specified servers are not present in the directory service.\r\n


Message:
The specified server address does not belong to the identified \r\nserver name.\r\n


Message:
The specified subnets already exist in the directory service.\r\n


Message:
The specified subnet belongs to a different superscope.\r\n


Message:
The specified subnet is not present in the directory service.\r\n


Message:
The specified reservation is not present in the directory service.\r\n


Message:
The reservation specified conflicts with an existing reservation\r\nin the directory service.\r\n


Message:
The specified IP range conflicts with some existing IP range in the\r\ndirectory service.\r\n


Message:
The specified IP range is not present in the directory service.\r\n


Message:
The DHCP service encountered the following error while cleaning \r\nup the database: %n%1\r\n


Message:
The JET Database call returned the following error : %1.\r\n\r\nAdditional Debug Information: %2.\r\n


Message:
The DHCP service encountered the following error when \r\nbacking up the database: %n%1\r\n


Message:
The DHCP/BINL service on the local machine has determined that it is\r\nauthorized to start.  It is servicing clients now.\r\n


Message:
The DHCP/BINL service on the local machine, belonging to the Windows\r\nAdministrative domain %2, has determined that it is authorized to start.\r\nIt is servicing clients now.\r\n


Message:
The DHCP/BINL service on the local machine has determined that it is\r\nnot authorized to start.  It has stopped servicing clients.  The\r\nfollowing are some possible reasons for this: \r\n%n%tThis machine belongs to a workgroup and has encountered another DHCP \r\nServer (belonging to a Windows Administrative Domain) servicing \r\nthe same network.\r\n%n%n%tAn unexpected network error occurred.\r\n


Message:
The DHCP/BINL service on the local machine, belonging to the Windows\r\nAdministrative domain %2, has determined that it is not authorized\r\nto start.  It has stopped servicing clients.  The following are\r\nsome possible reasons for this:\r\n%n%tThis machine is part of a directory service enterprise and is \r\nnot authorized in the same domain.  (See help on the DHCP Service \r\nManagement Tool for additional information).\r\n%n%n%tThis machine cannot reach its directory service enterprise and \r\nit has encountered an other DHCP service on the network belonging to \r\na directory service enterprise on which the local machine is not authorized.\r\n%n%n%tSome undexpected network error occurred.\r\n


Message:
The DHCP/BINL service on the local machine has determined that it is\r\nauthorized to start.  It is servicing clients now.\r\n%nThe DHCP/BINL service has determined that the machine was recently \r\nupgraded.  If the machine is intended to belong to a directory service \r\nenterprise, the DHCP service must be authorized in the directory service\r\nfor it to start servicing clients.  (See help on DHCP Service Management \r\nTool for authorizing the server).\r\n


Message:
The DHCP/BINL Service on the local machine, belonging to Windows Domain\r\n%2, has determined that it is authorized to start.  \r\n\r\nIt is servicing clients now.\r\n\r\nIt has determined that the computer was recently upgraded.  It has also \r\ndetermined that either there is no directory service enterprise for the \r\ndomain or that the computer is not authorized in the directory service. \r\n\r\nAll DHCP services that belong to a directory service enterprise should \r\nbe authorized in the directory service to service clients.   (See help\r\non the DHCP Service Management Tool for authorizing a DHCP service in\r\nthe directory service).\r\n


Message:
The DHCP/BINL service on the local machine encountered an error while\r\ntrying to find the domain of the local machine.  The error was: %3.\r\n


Message:
The DHCP/BINL service on the local machine encountered a network error.\r\nThe error was: %3.\r\n


Message:
The DHCP/BINL service has determined that it is not authorized to\r\nservice clients on this network for the Windows domain: %2.\r\n


Message:
The DHCP/BINL service on this workgroup server has encountered another\r\nserver with IP Address, %1, belonging to the domain %2.\r\n


Message:
The DHCP/BINL service on this Small Business Server\r\nhas encountered another server on this network with \r\nIP Address, %1, belonging to the domain: %2.\r\n


Message:
The DHCP/BINL service on this computer is shutting down. \r\nSee the previous event log messages for reasons.\r\n


Message:
Unable to create the symbolic link from %2 -> %3.\r\n


Message:
Unable to add registry key and/or value to HARDWARE\\DEVICEMAP\\%2.\r\n


Message:
Transmit buffer on port %2 isn't drained!  (%3)\r\n


Message:
Not enough memory was available to allocate internal storage needed for the device %1.\r\n


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


Message:
Registry key %2 could not be opened.  Check current configuration.\r\n


Message:
DigiBoard adapter %2 was unable to initialize properly.\r\n


Message:
Unable to access device name %2.  Check current configuration.\r\n


Message:
A domain controller with the specified name already exists.\r\n


Message:
This operation is supported only when you are connected to the server.\r\n


Message:
The group policy framework should call the extension even if there are no changes.\r\n


Message:
The specified user does not have a valid profile.\r\n


Message:
This operation is not supported on a Microsoft Small Business Server\r\n


Message:
Not all privileges referenced are assigned to the caller.\r\n


Message:
Some mapping between account names and security IDs was not done.\r\n


Message:
No system quota limits are specifically set for this account.\r\n


Message:
No encryption key is available. A well-known encryption key was returned.\r\n


Message:
The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.\r\n


Message:
Indicates two revision levels are incompatible.\r\n


Message:
This security ID may not be assigned as the owner of this object.\r\n


Message:
This security ID may not be assigned as the primary group of an object.\r\n


Message:
An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.\r\n


Message:
There are currently no logon servers available to service the logon request.\r\n


Message:
A specified logon session does not exist. It may already have been terminated.\r\n


Message:
A specified privilege does not exist.\r\n


Message:
A required privilege is not held by the client.\r\n


Message:
A Remote activation was necessary but the server name provided was invalid\r\n


Message:
The class is configured to run as a security id different from the caller\r\n


Message:
Use of Ole1 services requiring DDE windows is disabled\r\n


Message:
A RunAs specification must be <domain name>\\<user name> or simply <user name>\r\n


Message:
The server process could not be started.  The pathname may be incorrect.\r\n


Message:
The server process could not be started as the configured identity.  The pathname may be incorrect or unavailable.\r\n


Message:
The server process could not be started because the configured identity is incorrect.  Check the username and password.\r\n


Message:
The client is not allowed to launch this server.\r\n


Message:
The service providing this server could not be started.\r\n


Message:
This computer was unable to communicate with the computer providing the server.\r\n


Message:
The server did not respond after being launched.\r\n


Message:
The registration information for this server is inconsistent or incomplete.\r\n


Message:
The registration information for this interface is inconsistent or incomplete.\r\n


Message:
The operation attempted is not supported.\r\n


Message:
A Microsoft Software Installer error was encountered.\r\n


Message:
The specified activation could not occur in the client context as specified.\r\n


Message:
Call was canceled by the message filter.\r\n


Message:
The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage.\r\n


Message:
The specified status flag was neither DBCOLUMNSTATUS_OK nor\r\nDBCOLUMNSTATUS_ISNULL\r\n


Message:
The specified set of rows was not contiguous to or overlapping the\r\nrows in the specified watch region\r\n


Message:
A transition from ALL* to MOVE* or EXTEND* was specified\r\n


Message:
The specified region is not a proper subregion of the region\r\nidentified by the given watch region handle\r\n


Message:
The provider does not support multi-statement commands\r\n


Message:
A specified value violated the integrity constraints for a column or\r\ntable\r\n


Message:
The given type name was unrecognized\r\n


Message:
Execution aborted because a resource limit has been reached; no\r\nresults have been returned\r\n


Message:
Cannot clone a command object whose command tree contains a rowset\r\nor rowsets\r\n


Message:
Cannot represent the current tree as text\r\n


Message:
The number of rows with pending changes has exceeded the set limit\r\n


Message:
There are pending changes on a row with a reference count of zero\r\n


Message:
A literal value in the command overflowed the range of the type of\r\nthe associated column\r\n


Message:
The supplied DynamicErrorID was invalid\r\n


Message:
Unable to get visible data for a newly-inserted row that has not\r\nyet been updated\r\n


Message:
The server was unable to allocate from the system paged pool because the server reached the configured limit for paged pool allocations.\r\n


Message:
The server was unable to allocate from the system nonpaged pool because the pool was empty.\r\n


Message:
The server was unable to allocate from the system paged pool because the pool was empty.\r\n


Message:
The server's Registry key %1 was not present.  The server could not start.\r\n


Message:
The server's Registry key %1 was not present and could not be created.  The server could not start.\r\n


Message:
The server did not bind to any transports.  The server could not start.\r\n


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


Message:
Unable to create device object %2. Initialization failed.\r\n


Message:
Unable to allocate required resources. Initialization failed.\r\n


Message:
IP has been bound to more than the maximum number of supported interfaces.\r\nSome interfaces on adapter %2 will not be initialized.\r\n


Message:
No subnet mask was specified for interface %2. This interface and\r\nall subsequent interfaces on adapter %3 cannot be initialized.\r\n


Message:
Invalid address %2 was specified for adapter %3. This interface\r\ncannot be initialized.\r\n


Message:
Invalid subnet mask %2 was specified for address %3 on adapter %4.\r\nThis interface cannot be initialized.\r\n


Message:
IP could not allocate some resources required to configure adapter %2.\r\nSome interfaces on this adapter will not be initialized.\r\n


Message:
IP could not open the registry key for adapter %2.\r\nInterfaces on this adapter will not be initialized.\r\n


Message:
Unable to read the configured IP addresses for adapter %2.\r\nIP interfaces will not be initialized on this adapter.\r\n


Message:
Unable to read the configured subnet masks for adapter %2.\r\nIP interfaces will not be initialized on this adapter.\r\n


Message:
IP was unable to read its bindings from the registry. No network interfaces\r\nwere configured.\r\n


Message:
The system detected an address conflict for IP address %2 with the system\r\nhaving network hardware address %3. The local interface has been disabled.\r\n


Message:
The system detected an address conflict for IP address %2 with the system\r\nhaving network hardware address %3. Network operations on this system may\r\nbe disrupted as a result.\r\n


Message:
Unable to read or write the NTE Context list for adapter %2.\r\nIP interfaces on this adapter may not be initialized completely.\r\n


Message:
Received %2 packet(s) with a bad Security Parameters Index from %3.\r\nThis could be a temporary glitch; if it persists please flush the Security Associations on this machine.\r\n


Message:
Received %2 packet(s) in the clear from %3 which should have been secured.\r\nThis could be a temporary glitch; if it persists please flush the Security Associations on this machine.\r\n


Message:
Failed to authenticate the hash for %2 packet(s) received from %3.\r\nThis could be a temporary glitch; if it persists please flush the Security Associations on this machine.\r\n


Message:
Received %2 packet(s) from %3 with invalid packet syntax.\r\nThis could be a temporary glitch; if it persists please flush the Security Associations on this machine.\r\n


Message:
Received %2 packet(s) from %3 with inproper protocol identifier.\r\nThis could be a temporary glitch; if it persists please flush the Security Associations on this machine.\r\n


Message:
Received %2 packet(s) from %3 that failed the IPSec processing for an unknown reason.\r\nThis could be a temporary glitch; if it persists please flush the Security Associations on this machine.\r\n


Message:
The IPSec driver failed the oakley negotiation with %2 since no filter\r\nexists to protect packets to that destination.\r\nPlease check the configuration on this machine to ensure at least one\r\nfilter matches the destination.\r\n


Message:
Unable to open the Registry Parameters to read configuration information.\r\n


Message:
Unable to configure the addresses of the WINS servers.\r\n


Message:
Initialization failed because the transport refused to open initial Addresses.\r\n


Message:
The full synchronization request from the server %1 failed with\r\nthe following error: %n%2\r\n


Message:
The partial synchronization replication of the %1 database from the\r\nprimary domain controller %2 completed successfully. %3 change(s) is(are)\r\napplied to the database.\r\n


Message:
The partial synchronization replication of the %1 database from the\r\nprimary domain controller %2 failed with the following error: %n%3\r\n


Message:
The full synchronization replication of the %1 database from the\r\nprimary domain controller %2 completed successfully.\r\n


Message:
The full synchronization replication of the %1 database from the\r\nprimary domain controller %2 failed with the following error: %n%3\r\n


Message:
No Windows NT or Windows 2000 Domain Controller is available for domain %1.\r\nThe following error occurred:%n%2\r\n


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


Message:
The workstation driver is not installed.\r\n


Message:
An internal error occurred.  The network cannot access a shared memory segment.\r\n


Message:
A network resource shortage occurred .\r\n


Message:
This operation is not supported on workstations.\r\n


Message:
The device or directory does not exist.\r\n


Message:
The operation is invalid on a redirected resource.\r\n


Message:
The server is currently out of the requested resource.\r\n


Message:
Requested addition of items exceeds the maximum allowed.\r\n


Message:
The Peer service supports only two simultaneous users.\r\n


Message:
An error occurred when opening or reading the configuration file.\r\n


Message:
The Workstation service is in an inconsistent state. Restart the computer before restarting the Workstation service.\r\n


Message:
The Workstation service has not been started.\r\n


Message:
The requested information is not available.\r\n


Message:
An internal Windows 2000 error occurred.\r\n


Message:
The server is not configured for transactions.\r\n


Message:
The requested API is not supported on the remote server.\r\n


Message:
The computer name already exists on the network. Change it and restart the computer.\r\n


Message:
The specified component could not be found in the configuration information.\r\n


Message:
The specified parameter could not be found in the configuration information.\r\n


Message:
A line in the configuration file is too long.\r\n


Message:
The printer destination cannot be found.\r\n


Message:
The printer destination already exists.\r\n


Message:
No more printer destinations can be added.\r\n


Message:
This printer destination is idle and cannot accept control operations.\r\n


Message:
This printer destination request contains an invalid control function.\r\n


Message:
The print processor is not responding.\r\n


Message:
The DNS server machine currently has no DNS domain name.  Its DNS name is a single\r\nlabel hostname with no domain (example:  "host" rather than "host.mycompany.com").\r\n%n\r\n%nYou might have forgotten to configure a primary DNS domain for the server computer.\r\nFor more information, see either "DNS server log reference" or "To configure the\r\nprimary DNS suffix for a client computer" in the online Help.\r\n%n\r\n%nWhile the DNS server has only a single label name, all zones created will have\r\ndefault records (SOA and NS) created using only this single label name for the\r\nserver's hostname.  This can lead to incorrect and failed referrals when clients\r\nand other DNS servers use these records to locate this server by name.\r\n%n\r\n%nTo correct this problem:\r\n%n  1) open ControlPanel\r\n%n  2) open System applet\r\n%n  3) select NetworkIdentification tab\r\n%n  4) click the "Properties" button and enter a domain name or workgroup name;  this name will be used as your DNS domain name\r\n%n  5) reboot to initialize with new domain name\r\n%n\r\n%nAfter reboot, the DNS server will attempt to fix up default records, substituting\r\nnew DNS name of this server, for old single label name.  However, you should\r\nreview to make sure zone's SOA and NS records now properly use correct\r\ndomain name of this server.\r\n


Message:
The DNS server could not create a thread.  System may be out of resources.\r\nYou might close applications not in use, restart the DNS server or\r\nreboot your computer.  For the specific error code, see the Record Data page.\r\n


Message:
The DNS server could not initialize a recursion thread.  The system may be\r\nout of resources.  You might close applications not in use, restart\r\nthe DNS server or reboot your computer.  For the specific error code, see\r\nthe Record Data page.\r\n


Message:
The DNS server could not initialize WINS lookup.  The system may be out\r\nof resources.  You might close applications not in use, restart the\r\nDNS server or reboot your computer.  For the specific error code, see the\r\nRecord Data page.\r\n


Message:
The DNS server failed to initialize WINSR reverse lookup, through NetBIOS\r\nadapter status lookup.  The server will continue to run but will not\r\nattempt to perform WINS reverse lookups.  This may be due to an incorrect\r\nconfiguration.\r\nIf WINSR lookup is not required, remove WINSR records from zone data\r\nfiles and reload modified zones or restart the DNS server.\r\nIf the DNS server should support WINSR reverse lookup, restart the\r\nserver computer and verify that the WINS/NetBT configuration for TCP/IP\r\nclient properties on the computer are correctly set.\r\n


Message:
The DNS server could not initialize the remote procedure call (RPC) service.\r\nIf it is not running, start the RPC service or reboot the computer.  For\r\nspecific error code, see the Record Data page.\r\n


Message:
The DNS server could not create a Transmission Control Protocol (TCP) socket.\r\nRestart the DNS server or reboot the computer.  For the specific error code, see\r\nthe Record Data page.\r\n


Message:
The DNS server could not bind a Transmission Control Protocol (TCP) socket\r\nto address %1.  Restart the DNS server or reboot the computer.  For specific\r\nerror code, see the Record Data page.  An IP address of 0.0.0.0 can indicate\r\na valid "any address" configuration in which all configured IP addresses on\r\nthe computer are available for use.\r\n


Message:
The DNS server could not listen on Transmission Control Protocol (TCP)\r\nsocket for address %1.  Restart the DNS server or reboot your computer.\r\nFor the specific error code, see the Record Data page.  An IP address of 0.0.0.0\r\ncan indicate a valid "any address" configuration in which all configured\r\nIP addresses on the computer are available for use.\r\n


Message:
The DNS server could not create a User Datagram Protocol (UDP) socket.\r\nRestart the DNS server or reboot your computer.  For the specific error code,\r\nsee the Record Data page.\r\n


Message:
The DNS server could not bind a User Datagram Protocol (UDP) socket to %1.\r\nRestart the DNS server or reboot your computer.  For the specific error code,\r\nsee the Record Data page.\r\n


Message:
The DNS server could not open socket for address %1.\r\n%nVerify that this is a valid IP address for the server computer.  If it is NOT valid\r\nuse the Interfaces dialog under Server Properties in the DNS Manager to remove\r\nit from the list of IP interfaces.  Then stop and restart the DNS server.\r\n(If this was the only IP interface on this machine and the DNS server may not\r\nhave started as a result of this error.  In that case remove the DNS\\Parmeters\\\r\nListenAddress value in the services section of the registry and restart.)\r\n%n\r\n%nIf this is a valid IP address for this machine, make sure that no other\r\napplication (e.g. another DNS server) is running that would attempt to use\r\nthe DNS port.\r\n%n\r\n%nFor more information, see "DNS server log reference" in the online Help.\r\n


Message:
The DNS server list of restricted interfaces does not contain a valid IP address\r\nfor the server computer.\r\nThe DNS server will use all IP interfaces on the machine.\r\n%nUse the DNS manager server properties, interfaces dialog, to verify and reset\r\nthe IP addresses the DNS server should listen on.  For more information, see\r\n"To restrict a DNS server to listen only on selected addresses" in the online Help.\r\n


Message:
The DNS server did not bind to all IP addresses available on this server.\r\n%nPlease use the DnsManger server properties interfaces tab to edit the list of\r\nIP addresses on which DNS is running.  Add any missing IP addresses to the\r\nlist.  After adding any additional IP addresses to the interfaces list, you\r\nMUST stop and restart the DNS service for the new interfaces to receive DNS\r\nservice. For more information, see "To restrict a DNS server to listen only\r\non selected addresses" in the online Help.\r\n%n\r\n%nNote that each additional IP interface does consume system resources and adds a\r\nsmall performance overhead to query reception.  There is no benefit in DNS to\r\nadditional addresses beyond those necessary to support the available network\r\ncards.  Even if the DNS server is handling multiple zones registered with the\r\nInternic, it is NOT necessary to have different IPs registered for each zone.\r\nHence, though the individual effect if small, since a very large number of IP\r\ninterfaces may degrade performance, you are encouraged to remove from the\r\nmachine any IP addresses that are unnecessary.\r\n


Message:
The DNS server has detected that the zone %1 has invalid or corrupted\r\nregistry data. To correct the problem, you can delete the applicable zone\r\nsubkey, located under DNS server parameters in the Windows 2000 registry.\r\nYou can then recreate the zone using the DNS console. For more information,\r\nsee "Tuning advanced server parameters" and "Add and Remove Zones" in the\r\nonline Help.\r\n


Message:
The file extension is invalid.\r\nThe invalid file extension is in the data.\r\n


Message:
The given aixs was not valid for this Dataset


Message:
One or more of the given cell ordinals was invalid


Message:
The supplied command does not have a DBID


Message:
The maximum number of Sessions supported by the provider has 
already been created. The consumer must release one or more currently held Sessions before obtaining a new Session Object


Message:
The initialization string specified does not conform to specificiation


Message:
The OLE DB root enumerator did not return any providers that matched any of the SOURCES_TYPEs requested


Message:
The initialization string specifies a provider which does not match the currently active provider


Message:
The trustee is not for the current data source


Message:
The trustee does not support memberships/collections


Message:
The object is invalid or unknown to the provider


Message:
The access entry list supplied is invalid


Message:
The trustee supplied as owner is invalid or unknown to the provider


Message:
The permission supplied in the access entry list is invalid


Message:
The reconciliation is only partially complete.


Message:
Reconciliation aborted via abort callback.


Message:
The implementation does not support generation of residues.


Message:
Callee is not the same version as that which created the difference.


Message:
The document versions are too dissimilar to reconcile.


Message:
The objects are identical - i.e. further reconciliation would not result in any changes to either object.


Message:
A control failure has occured because a system resource could not be obtained


Message:
This control panel does not target the required type of profile.


Message:
The profile data dropped on a control panel cannot be read.  The data is either corrupt or was not read back properly by a controller that wrote part of the data.


Message:
A controller that can only operate on the local machine was asked to operate on a remote machine.


Message:
Software Management does not support this version of the PDF.


Message:
An internal error has occurred in Software Management.


Message:
Creation of the %1 log or alert is not complete.
This log will not be started.


Message:
The open operation on log file: %1 for log %2 generated a warning.
The log will continue.
The warning returned is: %3.


Message:
Send Failed. The call was not answered by a fax device.
This fax will not be sent, as the maximum number of retries has been reached.
Sender: %1.
Billing code: %2.
Sender company: %3.
Sender dept: %4.
Recipient name: %5.
Recipient number: %6.
Device name: %7.


Message:
The DNS server was unable to open Active Directory.  This DNS server\r\nis configured to obtain and use information from the directory for\r\nthis zone and is unable to load the zone without it.  Check that the\r\nActive Directory is functioning properly and reload the zone.  The\r\nrecord data contains the error status.  For more information,\r\nclick the Record Data tab.\r\n


Message:
The application, %1!s!, generated an application error\r\nThe error occurred on %2!s!/%3!s!/%4!s! @ %5!s!:%6!s!:%7!s!.%8!s!\r\nThe exception generated was %9!s! at address %10!s! (%11!s!)\r\n


Message:
%1 (%2) Unable to create the log. The drive may be read-only or out of disk space. Error %3.\r\n


Message:
%1 (%2) Unable to write to section 0 while flushing the log. Error %3.\r\n


Message:
%1 (%2) Unable to write to section 1 while flushing the log. Error %3.\r\n


Message:
%1 (%2) Unable to write to section 2 while flushing the log. Error %3.\r\n


Message:
%1 (%2) Unable to write to section 3 while flushing the log. Error %3.\r\n


Message:
%1 (%2) Error %3 occurred while opening a newly created log file.\r\n


Message:
%1 (%2) Unable to read page %4 of database %3. Error %5.\r\n


Message:
%1 (%2) Unable to read header of database %3. Error %4.\r\n


Message:
%1 (%2) The database %3 created at %4 was not recovered. The recovered database was created at %5.\r\n


Message:
%1 (%2) The database %3 created at %4 was not recovered.\r\n


Message:
%1 (%2) The database engine found a bad page.\r\n


Message:
%1 (%2) The database engine lost one page of bad data.\r\n


Message:
%1 (%2) The database engine repaired one page link.\r\n


Message:
%1 (%2) The database engine lost one or more bad columns of data in one record.\r\n


Message:
%1 (%2) The database engine lost one table called %3.\r\n


Message:
%1 (%2) The database signature does not match the log signature for database %3.\r\n


Message:
%1 (%2) The database engine could not find the file or directory called %3.\r\n


Message:
%1 (%2) The database engine could not access the file called %3.\r\n


Message:
%1 (%2) The database engine is rejecting update operations due to low free disk space on the log disk.\r\n


Message:
%1 (%2) The database engine log disk is full. Free up some disk space and restart database engine.\r\n


Message:
%1 (%2) Database %3 and its patch file do not match.\r\n


Message:
%1 (%2) The starting log 0x%3 is too high. It should start from 0x%4.\r\n


Message:
%1 (%2) The ending log 0x%3 is too low. It should end with 0x%4.\r\n


Message:
%1 (%2) The restore log file 0x%3 is damaged.\r\n


Message:
%1 (%2) The time stamp for restore log file 0x%3 does not match previous log.\r\n


Message:
%1 (%2) The restore log file 0x%3 is missing.\r\n


Message:
%1 (%2) The existing log file 0x%3 is damaged. Log files 0x%4 to 0x%5 have been deleted.\r\n


Message:
%1 (%2) The existing log file 0x%3 is not in a valid sequence. Log files 0x%4 to 0x%5 have been deleted.\r\n


Message:
%1 (%2) Database %3 needs a full backup before incremental backup.\r\n


Message:
%1 (%2) The backup database %3 must be a multiple of 4 KB.\r\n


Message:
%1 (%2) Unable to write a shadowed header for file %3.\r\n


Message:
%1 (%2) Background clean up skipped pages. Database may benefit from defragmentation.\r\n


Message:
Performance threshold values have been set by operator intervention.\r\nCurrent settings indicate performance thresholds have been reached.\r\nTrap processing is being quiesed. Further traps will not be sent without operator intervention.\r\n


Message:
The event log time could not be converted from UCT to local time.\r\nGetTimeZoneInformation returned a value of %1. UCT time will be used in this trap.\r\n


Message:
Unable to locate ParameterMessageFile for event source for %1. RegOpenKeyEx returned %2.\r\n


Message:
Unable to expand file name in ParameterMessageFile for %1. Size needed is %2.\r\n


Message:
Unable to load file name in ParameterMessageFile for %1. LoadLibraryEx returned %2.\r\n


Message:
An error occurred freeing message DLL. FreeLibrary returned %1.\r\n


Message:
Account name could not be located for this event. Unknown will be used.\r\nLookupAccountSid returned %1.\r\n


Message:
Local storage for buffer could not be freed. LocalFree returned %1. Potential memory leak.\r\n


Message:
ParameterMessageFile did not contain a substitution string for %1. Error code was %2.\r\n


Message:
PrimaryModule did not contain a substitution string for %1. Error code was %2.\r\nThis secondary parameter will be removed.\r\n


Message:
Too many insertion strings. First %1 used.\r\n


Message:
Error opening registry for Parameter information; defaults used for all parameters.\r\nReturn code from RegOpenKeyEx is %1.\r\n


Message:
TraceFileName parameter not located in registry;\r\nDefault trace file used is %1.\r\n


Message:
TrimFlag parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
TrimMessage parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
MaxTrapSize parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
ThresholdEnabled parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
Threshold parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
ThresholdCount parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
ThresholdCount parameter is an invalid value in the registry;\r\nDefault value used is %1.\r\n


Message:
ThresholdTime parameter not located in registry;\r\nDefault value used is %1.\r\n


Message:
ThresholdTime parameter is an invalid value in the registry;\r\nDefault value used is %1.\r\n


Message:
TraceFileName parameter is of the wrong type in the registry;\r\nDefault trace file used is %1.\r\n


Message:
TraceLevel parameter is of the wrong type in the registry;\r\nDefault trace level used is %1.\r\n


Message:
TraceLevel parameter not located in registry;\r\nDefault trace level used is %1.\r\n


Message:
Unable to set Threshold key in registry. Processing will continue.\r\nReturn code from RegSetValueEx is %1.\r\n


Message:
Error creating the registry key change notify event.\r\nReturn code from CreateEvent is %1.\r\nInitialization will continue, but registry changes will not be updated until SNMP is stopped and restarted.\r\n


Message:
Error closing the stop agent event handle %1.\r\nReturn code from CloseHandle is %2.\r\n


Message:
Error closing the stop log processing routine event handle %1.\r\nReturn code from CloseHandle is %2.\r\n


Message:
Error closing the registry key changed event handle %1.\r\nReturn code from CloseHandle is %2.\r\n


Message:
Error closing the registry Parameter key handle %1.\r\nReturn code from RegCloseKey is %2.\r\n


Message:
Error closing the stop log processing routine thread handle %1.\r\nReturn code from CloseHandle is %2.\r\n


Message:
Error waiting for the log processing routine thread %1 to terminate.\r\nReturn code from WaitForSingleObject is %2.\r\n


Message:
The log processing routine thread %1 failed to terminate within 30 seconds.\r\nThread will be terminated.\r\n


Message:
Unable to format message %1. FormatMessage returned %2.\r\nTrap will not be sent.\r\n


Message:
Unable to post event completion to handle %1. SetEvent returned %2.\r\nTrap may not be sent.\r\n


Message:
OpenMutex failed for object %1, reason code %2.\r\nTrap will not be sent.\r\n


Message:
Mutex object has been abandoned.\r\nTrap will not be sent.\r\n


Message:
Mutex object could not be released. Reason code is %1.\r\nTrap may not be sent.\r\n


Message:
WaitForMultipleObjects returned an unknown error condition.\r\nTrap will not be sent.\r\n


Message:
GetExitCodeThread returned FALSE, reason code is %1.\r\n


Message:
Error allocating storage for Count/Time table entry.\r\nTrap will not be sent.\r\n


Message:
Error allocating storage for variable bindings.\r\nTrap will not be sent.\r\n


Message:
Error allocating storage for message DLL insertion string array.\r\nTrap will not be sent.\r\n


Message:
Error allocating storage for message DLL insertion string length array.\r\nTrap will not be sent.\r\n


Message:
Error allocating storage for message DLL insertion strings.\r\nTrap will not be sent.\r\n


Message:
Cannot specify SNMP Event Log Extension Agent DLL events as trap generators.\r\nThis trap is ignored.\r\n


Message:
Unable to copy varbind entry during trap buffer trimming.\r\nTrap will not be sent.\r\n


Message:
Attempt to reduce trap buffer size failed.\r\nTrap will not be sent.\r\n


Message:
The amount of data required to be trimmed is larger than the entire trap.\r\nTrap will not be sent.\r\n


Message:
Error opening registry for EventLogFiles information. Extension agent cannot run.\r\nReturn code from RegOpenKeyEx is %1.\r\n


Message:
No Event Logs were specified for event scanning.\r\nExtension agent is terminating.\r\n


Message:
Error reading Parameter key information from the registry.\r\nReturn code from RegEnumValue is %1. Index value is %2.\r\nExtension agent terminating.\r\n


Message:
Error reading EventLogFiles key information from the registry.\r\nReturn code from RegEnumValue is %1. Index value is %2.\r\nExtension agent terminating.\r\n


Message:
No BaseEnterpriseOID parameter found in registry.\r\nExtension agent terminating.\r\n


Message:
No SupportedView parameter found in registry.\r\nExtension agent terminating.\r\n


Message:
Error processing registry parameters.\r\nExtension agent terminating.\r\n


Message:
Unable to convert BaseEnterpriseOID from string to ASN.1 OID.\r\nExtension agent terminating.\r\n


Message:
Unable to convert EnterpriseOID from string to ASN.1 OID.\r\nTrap cannot be sent.\r\n


Message:
Unable to convert SupportedView from string to ASN.1 OID.\r\nExtension agent terminating.\r\n


Message:
Unable to load PrimaryModule %1. LoadLibraryEx returned %2.\r\n


Message:
Error creating the stop extension agent event.\r\nReturn code from CreateEvent is %1.\r\n


Message:
Error creating the stop log processing routine termination event.\r\nReturn code from CreateEvent is %1.\r\n


Message:
Error creating the log event notification event.\r\nReturn code from CreateEvent is %1.\r\n


Message:
Error creating the log processing routine service thread.\r\nReturn code from CreateThread is %1.\r\n


Message:
Error waiting for extension agent shutdown request event %1.\r\nReturn code from WaitForSingleObject is %2.\r\nExtension agent did not initialize.\r\n


Message:
Error setting the extension agent shutdown event %1.\r\nReturn code from SetEvent is %2.\r\n


Message:
Error setting the log processing routine shutdown event %1.\r\nReturn code from SetEvent is %2.\r\n


Message:
Error terminating the log processing routine %1.\r\nReturn code from TerminateThread is %2.\r\n


Message:
SNMP Event Log Extension Agent did not initialize correctly.\r\n


Message:
Error positioning to end of log file -- handle is invalid.\r\nHandle specified is %1.\r\n


Message:
Error positioning to end of log file -- log buffer allocation failed.\r\nHandle specified is %1.\r\n


Message:
Error positioning to end of log file -- can't get oldest log record.\r\nHandle specified is %1. Return code from GetOldestEventLogRecord is %2.\r\n


Message:
Error positioning to end of log file -- can't get number of log records.\r\nHandle specified is %1. Return code from GetNumberOfEventLogRecords is %2.\r\n


Message:
Error positioning to end of log file -- seek to end of log failed.\r\nHandle specified is %1. Return code from ReadEventLog is %2.\r\n


Message:
Insufficient memory available to allocate the wait event array.\r\n


Message:
Insufficient memory available to reallocate the log event array.\r\n


Message:
Insufficient memory available to allocate dynamic variable.\r\n


Message:
Insufficient memory available to reallocate the log name array.\r\n


Message:
Insufficient memory available to reallocate the PrimaryModule handle array.\r\n


Message:
Insufficient memory available to reallocate the insertion strings for secondary parameters.\r\nFurther secondary substitution has been terminated. Message will be formatted with strings as is.\r\n


Message:
Error creating event for log event notification.\r\nReturn code from CreateEvent is %1.\r\n


Message:
Error requesting notification of change in log event %1.\r\nReturn code from ElfChangeNotify is %2.\r\n


Message:
Error waiting on event array in log processing event routine.\r\nReturn code from WaitForMultipleObjects is %1.\r\nExtension agent is terminating.\r\n


Message:
Error closing an event log wait event handle.\r\nEvent handle is %1. Return code from CloseHandle is %2.\r\n


Message:
Received %1 routed to local inbox: %2.\r\n


Message:
%1 received.\r\nFrom: %2.\r\nCallerId: %3.\r\nTo: %4.\r\nPages: %5.\r\nTransmission time: %6.\r\nDevice Name: %7.\r\n


Message:
Fax Sent.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nReceiver CSID: %7.\r\nPages: %8.\r\nTransmission time: %9.\r\nDevice name: %10.\r\n


Message:
Send Failed. The number was busy. Another attempt\r\nwill be made to send this fax.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. There was no answer. Another attempt\r\nwill be made to send this fax.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. The call was not answered by a fax device.\r\nAnother attempt will be made to send this fax.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
An error was encountered while sending a fax.  Please wait a minute and then try to send the fax again.  If difficulties persist, please check that the following items are working : Phone line, Sending Fax Device and Receiving Fax device.  If problems persist, contact product support.  \r\nAnother attempt will be made to send this fax.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Cancelled.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. There was no dial tone. Another attempt\r\nwill be made to send this fax.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Unable to route %1 to local inbox: %2.\r\nThe following error occurred: MAPI error.\r\n


Message:
Send Failed. The number was busy. This fax will not be sent,\r\nas the maximum number of retries has been reached.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. There was no answer. This fax will not be sent,\r\nas the maximum number of retries has been reached.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. The call was not answered by a fax device.\r\nThis fax will not be sent, as the maximum number of retries has been reached.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. The fax transmission was interrupted.\r\nThis fax will not be sent, as the maximum number of retries has been reached.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. The fax transmission was interrupted.\r\nAnother attempt will be made to send this fax.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Unable to archive %1 to %2.\r\nThe following error occurred: %3.\r\n


Message:
Cannot print %1 to fax printer %2.  The fax service cannot print incoming faxes to fax printers.\r\n


Message:
An error was encountered while receiving a fax.  Please wait a minute and have the sender try again.  If difficulties persist, please check that the following items are working : Phone line, Sending Fax Device and Receiving Fax device.  If problems persist, contact product support.\r\n


Message:
Unable to receive fax. Fax receive directory %1 does not exist or is not writable.\r\n


Message:
Unable to receive fax. Cannot create receive fax file %1.\r\n


Message:
The spooler service cannot process requests from the fax service.\r\n


Message:
An error was encountered while sending a fax.  Please wait a minute and then try to send the fax again.  If difficulties persist, please check that the following items are working : Phone line, Sending Fax Device and Receiving Fax device.  If problems persist, contact product support.  \r\nThis fax will not be sent, as the maximum number of retries has been reached.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
Send Failed. There was no dial tone. This fax will not be sent,\r\nas the maximum number of retries has been reached.\r\nSender: %1.\r\nBilling code: %2.\r\nSender company: %3.\r\nSender dept: %4.\r\nRecipient name: %5.\r\nRecipient number: %6.\r\nDevice name: %7.\r\n


Message:
You have violated the license agreement for the Small Business Server by installing Fax Server on a computer not running the Small Business Server\r\n


Message:
Receive failed due to a transmission error.  \r\nThe Fax Service was able to recover a portion of the received fax.\r\nFile Name: %1.\r\nFrom: %2.\r\nCallerId: %3.\r\nTo: %4.\r\nRecovered Pages: %5.\r\nTotal Pages: %6.\r\nTransmission time: %7.\r\nDevice Name: %8.\r\n\r\n


Message:
The Fax Service had problems restoring the fax queue.\r\n\r\nIf you are unsure if a fax job was transmitted, you should retransmit\r\nthat job.\r\n


Message:
The Fax Service had problems initializing the routing module "%1" .\r\n\r\nLocation:%2.\r\n\r\nPlease contact your system administrator.\r\n


Message:
The Fax Service had problems initializing the virtual devices for %1.\r\n\r\nPlease contact your system administrator.\r\n


Message:
The Fax Service had problems initializing the fax service provider module "%1".\r\n\r\nLocation: %2.\r\n\r\nPlease contact your system administrator.\r\n


Message:
Anonymous logon request received from %1 at host %2.\r\n


Message:
User logon request received from %1 at host %2.\r\n


Message:
User %1 at host %2 has timed-out after %3 seconds of inactivity.\r\n


Message:
User %1 failed to log on, could not access the home directory %2.\r\n


Message:
User %1 denied access to the current directory %2 due to a security change.\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:
FTP Server could not initialize its security.  The data is the error.\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:
FTP Server could not initialize the socket library.  The data is the error.\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:
FTP Server was unable to initialize due to a shortage of available memory.  The data is the error.\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:
FTP Server could not locate the FTP/TCP service.  The data is the error.\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:
FTP Server could not create the main connection socket.  The data is the error.\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:
FTP Server could not create the main connection thread.  The data is the error.\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:
FTP Server could not create a client worker thread for user at host %1.  The connection to this user is terminated.  The data is the error.\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:
A call to a system service failed unexpectedly.  The data is the error.\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 server was unable to load ODBC32.DLL for sql logging due to the following error: %1 The data is the error code.\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:
Some firmware configuration information was incomplete, so defaults were used.\r\n


Message:
User configuration data is overriding firmware configuration data.\r\n


Message:
The ring buffer that stores incoming keyboard data has overflowed (buffer size is configurable via the registry).\r\n


Message:
The ring buffer that stores incoming mouse data has overflowed (buffer size is configurable via the registry).\r\n


Message:
Could not successfully write the Controller Command Byte for the i8042.\r\n


Message:
An unexpected ACKNOWLEDGE was received from the device.\r\n


Message:
No mouse port ("PS/2 compatible") mouse device was detected on the i8042 auxiliary port (not a problem unless this type of mouse really is connected).\r\n


Message:
An unexpected RESET was detected from the mouse device.\r\n


Message:
Unable to create the device map entry for %1.\r\n


Message:
Unable to delete the device map entry for %1.\r\n


Message:
The device sent an incorrect response(s) following a keyboard reset.\r\n


Message:
The device sent an incorrect response(s) following a mouse reset.\r\n


Message:
Unable to create the symbolic link for %1.\r\n


Message:
An unexpected RESEND was received from the device.\r\n


Message:
The keyboard device does not exist or was not detected.\r\n


Message:
The keyboard and mouse devices do not exist or were not detected.\r\n


Message:
An unexpected RESET was detected from the mouse device.  The wheel has been deactivated.\r\n


Message:
A bogus RESET was detected from the mouse device.\r\n


Message:
A wheel mouse was detected after a device reset. The wheel has been reactivated.\r\n


Message:
A protocol error has occured. Resetting the mouse to known state.\r\n


Message:
Not enough memory was available to allocate the ring buffer that holds incoming data for %1.\r\n


Message:
The hardware locations for %1 could not be translated to something the memory management system understands.\r\n


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


Message:
Could not connect the interrupt for %1.\r\n


Message:
The Start I/O procedure has detected an internal error in the driver for %1.\r\n


Message:
The Initiate I/O procedure has detected an internal state error in the driver for %1.\r\n


Message:
Could not set the keyboard typematic rate and delay.\r\n


Message:
Could not set the keyboard indicator lights.\r\n


Message:
Could not tell the hardware to send keyboard scan codes in the set expected by the driver.\r\n


Message:
Could not set the mouse sample rate.\r\n


Message:
Could not enable transmissions from the mouse.\r\n


Message:
Exceeded the allowable number of retries (configurable via the registry) on device %1.\r\n


Message:
The operation on %1 timed out (time out is configurable via the registry).\r\n


Message:
An error occurred while trying to determine the number of mouse buttons.\r\n


Message:
An internal error occurred. Check the event log for additional information on what might have caused this error.\r\n


Message:
The service does not have sufficient access rights to process the request.\r\n


Message:
The service could not access the Active Directory Global Catalog.\r\n


Message:
The user's account domain is not accessible.\r\n


Message:
The specified domain does not exist.\r\n


Message:
There was an authentication failure because of an unknown user name or a bad password.\r\n


Message:
A user could not change their password because the new password did not meet the requirements for this network.\r\n


Message:
The specified authentication type is not supported on this system.\r\n


Message:
The current configuration only supports local user accounts.\r\n


Message:
The user must change their password.\r\n


Message:
The log on failed because the account is currently disabled. The person with administrative rights for the computer must enable the account.\r\n


Message:
The user's account has expired. The person with administrative rights for the computer must re-establish the account.\r\n


Message:
The user's account is currently locked out and may not be logged on to. Only the person with administrative rights for the computer can unlock a user account.\r\n


Message:
The log on failed because of an account logon time restriction violation.\r\n


Message:
The log on failed because of a user account restriction.\r\n


Message:
The user's information did not match a Remote Access Policy.\r\n


Message:
The user has exceeded the dial-in lockout count.\r\n


Message:
The user is not allowed dial-in access to the network.\r\n


Message:
The user attempted to use an unauthorized authentication method.\r\n


Message:
The user tried to connect from an unauthorized calling station.\r\n


Message:
A null reference pointer was passed to the stub.\r\n


Message:
The enumeration value is out of range.\r\n


Message:
The supplied user buffer is not valid for the requested operation.\r\n


Message:
The disk media is not recognized. It may not be formatted.\r\n


Message:
The workstation does not have a trust secret.\r\n


Message:
The security database on the server does not have a computer account for this workstation trust relationship.\r\n


Message:
The trust relationship between the primary domain and the trusted domain failed.\r\n


Message:
The trust relationship between this workstation and the primary domain failed.\r\n


Message:
A remote procedure call is already in progress for this thread.\r\n


Message:
An attempt was made to logon, but the network logon service was not started.\r\n


Message:
The redirector is in use and cannot be unloaded.\r\n


Message:
The specified printer driver is already installed.\r\n


Message:
The specified separator file is invalid.\r\n


Message:
The environment specified is invalid.\r\n


Message:
The account used is an interdomain trust account. Use your global user account or local user account to access this server.\r\n


Message:
The object invoked has disconnected from its clients.\r\n


Message:
The object invoked chose not to process the call now.  Try again later.\r\n


Message:
The message filter indicated that the application is busy.\r\n


Message:
The message filter rejected the call.\r\n


Message:
A call control interfaces was called with invalid data.\r\n


Message:
An outgoing call cannot be made since the application is dispatching an input-synchronous call.\r\n


Message:
The application called an interface that was marshalled for a different thread.\r\n


Message:
CoInitialize has not been called on the current thread.\r\n


Message:
The version of OLE on the client and server machines does not match.\r\n


Message:
OLE received a packet with an invalid header.\r\n


Message:
OLE received a packet with an invalid extension.\r\n


Message:
The requested object or interface does not exist.\r\n


Message:
The requested object does not exist.\r\n


Message:
OLE has sent a request and is waiting for a reply.\r\n


Message:
OLE is waiting before retrying a request.\r\n


Message:
Call context cannot be accessed after call completed.\r\n


Message:
Impersonate on unsecure calls is not supported.\r\n


Message:
Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized.\r\n


Message:
No security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server.\r\n


Message:
Remote calls are not allowed for this process.\r\n


Message:
The marshaled interface data packet (OBJREF) has an invalid or unknown format.\r\n


Message:
No context is associated with this call. This happens for some custom marshalled calls and on the client side of the call.\r\n


Message:
There are no synchronize objects to wait on.\r\n


Message:
Full subject issuer chain SSL principal name expected from the server.\r\n


Message:
The share name entered may not be accessible from some MS-DOS workstations.\r\nAre you sure you want to use this share name? %1: %0\r\n


Message:
ID         Path                                    User name            # Locks\r\n


Message:
Computer               User name            Client Type       Opens Idle time\r\n


Message:
Offline cache enabled: manual restore%0\r\n


Message:
Offline cache enabled: automatic restore%0\r\n


Message:
Offline cache enabled: no sharing among users%0\r\n


Message:
Net Send has been interrupted by a Ctrl+Break from the user.\r\n


Message:
Name                         Job #      Size            Status\r\n


Message:
The profile for user %1 was loaded successfully.\r\n


Message:
The profile for user %1 was unloaded successfully.\r\n


Message:
The profile for user %1 is mandatory.\r\n


Message:
The default profile was used for user %1.\r\n


Message:
The central profile %1 for user %2 is not updated. No central profile updates are allowed from this computer.\r\n


Message:
The central profile %1 was copied over the user's cached profile.\r\n


Message:
The user's cached profile was copied over the central profile %1.\r\n


Message:
The mandatory profile %1 was not found, error = %2.\r\n


Message:
The user %1 does not have access to the mandatory profile located at %2.\r\n


Message:
The user %1 does not have read permissions on the keys in the profile %2.\r\n


Message:
The profile for user %1 is already loaded due to a previous unload failure. The profile will appear in the state in was during the last logon session.\r\n


Message:
The central profile %1 for user %2 is not available. See error code below.\r\n


Message:
Failed to load the local cached profile for user %1.\r\n


Message:
Failed to copy the central profile %1 over the user's cached profile.\r\n


Message:
Failed to copy the user's cached profile over the central profile %1.\r\n


Message:
Failed to load the profile %1 for user %2.\r\n


Message:
Failed to unload the profile for user %1.\r\n


Message:
Failed to copy the profile for user %1 back to %2.\r\n


Message:
Failed to set the user's home directory %1.\r\n


Message:
Failed to load the profile %1 for user %2. See below for error code.\r\n


Message:
Failed to copy the user default profile to a local copy for user %1.\r\n


Message:
Failed to save the system default profile to a local profile for user %1.\r\n


Message:
Failed to set the proper security in user's copy of the default profile for user %1. The profile can not be loaded.\r\n


Message:
The user %1 was given a copy of the default profile but loading the profile failed.\r\n


Message:
DCOM got error "%%%1" attempting to start the service %2 with arguments "%3"\r\nin order to run the server:%n%4\r\n


Message:
DCOM got error "%%%1" from the computer %2 when attempting to\r\nactivate the server:%n%3\r\n


Message:
DCOM got error "%%%1" when attempting to\r\nactivate the server:%n%2\r\n


Message:
DCOM got error "%%%1" from the computer %2 when attempting to\r\nthe server:%n%3 with file %4.\r\n


Message:
DCOM was unable to communicate with the computer %1 using any of the configured\r\nprotocols.\r\n


Message:
The system failed to update and remove registration for the\r\nnetwork adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason for this failure is because the DNS server it sent the update\r\nrequest to timed out. The most likely cause of this failure is that the\r\nDNS server authoritative for the zone where the registration was originally\r\nmade is either not running or unreachable through the network at this time.\r\n


Message:
The system failed to update and remove registration for the\r\nnetwork adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason for this failure is because the DNS server it sent the update\r\nto failed the update request. A possible cause of this failure is that\r\nthe DNS server required to process this update request has a lock in place\r\non the zone, probably because a zone transfer is in progress.%n%n\r\n


Message:
The system failed to update and remove registration for the network\r\nadapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason for this failure is because the DNS server sent the update\r\neither (a) does not support the DNS dynamic update protocol, or (b) the\r\nauthoritative zone for the specified DNS domain name does not currently\r\naccept DNS dynamic updates.\r\n


Message:
The system failed to update and remove registration for the network\r\nadapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not perform the update request was the\r\nDNS server contacted refused update request. The cause of this is\r\n(a) this computer is not allowed to update the specified DNS domain\r\nname, or (b) because the DNS server authoritative for the zone that\r\nrequires updating does not support the DNS dynamic update protocol.\r\n


Message:
The system failed to update and remove registration for the network\r\nadapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not perform the update request was because\r\nof a security related problem. The cause of this could be (a) your computer\r\ndoes not have permissions to register and update the specific DNS domain\r\nname set for this adapter, or (b) there might have been a problem negotiating\r\nvalid credentials with the DNS server during the processing of the update\r\nrequest.%n%n\r\nFor specific error code, click the Record Data tab.\r\n


Message:
The system failed to update and remove the DNS registration for the\r\nnetwork adapter with settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe system could not update to remove this DNS registration because of\r\na system problem. For specific error code, click the Record Data tab.\r\n


Message:
The system failed to update and remove pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe system could not remove these PTR RRs because the update request\r\ntimed out while awaiting a response from the DNS server. This is probably\r\nbecause the DNS server authoritative for the zone that requires update\r\nis not running.\r\n


Message:
The system failed to update and remove pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe system could not remove these PTR RRs because the DNS server failed the\r\nupdate request. A possible cause is that a zone transfer is in progress,\r\ncausing a lock for the zone at the DNS server authorized to perform the\r\nupdates for these RRs.\r\n


Message:
The system failed to update and remove pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe system could not remove these PTR RRs because either the DNS server\r\ndoes not support the DNS dynamic update protocol or the authoritative zone\r\nthat contains these RRs does not accept dynamic updates.\r\n


Message:
The system failed to update and remove pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe system could not remove these PTR RRs because the DNS server refused the\r\nupdate request. The cause of this might be (a) this computer is not allowed\r\nto update the specified DNS domain name specified by these settings, or\r\n(b) because the DNS server authorized to perform updates for the zone that\r\ncontains these RRs does not support the DNS dynamic update protocol.\r\n


Message:
The system failed to update and remove pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe system could not remove these PTR RRs because of a security related\r\nproblem. The cause of this could be that (a) your computer does not have\r\npermissions to remove and update the specific DNS domain name or IP addresses\r\nconfigured for this adapter, or (b) there might have been a problem negotiating\r\nvalid credentials with the DNS server during the processing of the update\r\nrequest. For specific error code, click the Record Data tab.\r\n


Message:
The system failed to update and remove pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe system could not remove these PTR RRs because because of a system\r\nproblem. For specific error code, click the Record Data tab.\r\n


Message:
User %1 was granted access.%n\r\nFully-Qualified-User-Name = %2%n\r\nNAS-IP-Address = %3%n\r\nNAS-Identifier = %4%n\r\nClient-Friendly-Name = %5%n\r\nClient-IP-Address = %6%n\r\nNAS-Port-Type = %7%n\r\nNAS-Port = %8%n\r\nPolicy-Name = %9%n\r\nAuthentication-Type = %10%n\r\nEAP-Type = %11\r\n


Message:
User %1 was denied access.%n\r\nFully-Qualified-User-Name = %2%n\r\nNAS-IP-Address = %3%n\r\nNAS-Identifier = %4%n\r\nCalled-Station-Identifier = %5%n\r\nCalling-Station-Identifier = %6%n\r\nClient-Friendly-Name = %7%n\r\nClient-IP-Address = %8%n\r\nNAS-Port-Type = %9%n\r\nNAS-Port = %10%n\r\nPolicy-Name = %11%n\r\nAuthentication-Type = %12%n\r\nEAP-Type = %13%n\r\nReason-Code = %14%n\r\nReason = %15\r\n


Message:
Access request for user %1 was discarded.%n\r\nFully-Qualified-User-Name = %2%n\r\nNAS-IP-Address = %3%n\r\nNAS-Identifier = %4%n\r\nCalled-Station-Identifier = %5%n\r\nCalling-Station-Identifier = %6%n\r\nClient-Friendly-Name = %7%n\r\nClient-IP-Address = %8%n\r\nNAS-Port-Type = %9%n\r\nNAS-Port = %10%n\r\nReason-Code = %11%n\r\nReason = %12\r\n


Message:
The address, %1, of client, %2, could not be resolved. The data is the error code generated by Winsock.\r\n


Message:
The address, %1, of client, %2, is not a valid IP address.\r\n


Message:
An internal error occurred while processing a request. The data is the error code.\r\n


Message:
A request was received from the invalid client IP Address %1.\r\n


Message:
A request was received with an authenticator that is not valid from client %1.\r\n


Message:
A malformed request was received from client %1. The data is the packet.\r\n


Message:
A packet with type %1, which is not valid, was received on port %2 from client %3.\r\n


Message:
A signature attribute is required in Access-Requests from client %1.\r\n


Message:
An Access-Request was received from client %1 with a signature attribute that is not valid.\r\n


Message:
An Access-Request from client %1 contained an Extensible Authentication Protocol (EAP) message but no signature.\r\n


Message:
An attribute in the response exceeds the maximum RADIUS attribute length. The data is the attribute ID.\r\n


Message:
The response exceeds the maximum RADIUS packet length.\r\n


Message:
The Internet Authentication Service (IAS) could not send a response due to a network error. The data is the error code generated by Winsock.\r\n


Message:
The cleaner cartridge has performed the maximum number of drive cleanings.\r\n


Message:
The last remaining item in this group or resource cannot be deleted.\r\n


Message:
The message provided exceeds the maximum size allowed for this parameter.\r\n


Message:
The volume contains system or paging files.\r\n


Message:
The media type cannot be removed from this library since at least one drive in the library reports it can support this media type.\r\n


Message:
This offline media cannot be mounted on this system since no enabled drives are present which can be used.\r\n


Message:
The remote storage service was not able to recall the file.\r\n


Message:
The remote storage service is not operational at this time.\r\n


Message:
The remote storage service encountered a media error.\r\n


Message:
The file or directory is not a reparse point.\r\n


Message:
The reparse point attribute cannot be set because it conflicts with an existing attribute.\r\n


Message:
The data present in the reparse point buffer is invalid.\r\n


Message:
The tag present in the reparse point buffer is invalid.\r\n


Message:
There is a mismatch between the tag specified in the request and the tag present in the reparse point.\r\n\r\n


Message:
Single Instance Storage is not available on this volume.\r\n


Message:
The cluster resource cannot be moved to another group because other resources are dependent on it.\r\n


Message:
The cluster resource dependency cannot be found.\r\n


Message:
The cluster resource cannot be made dependent on the specified resource because it is already dependent.\r\n


Message:
The cluster resource is not available.\r\n


Message:
The cluster resource could not be found.\r\n


Message:
A cluster node cannot be evicted from the cluster while it is online.\r\n


Message:
The cluster group is not available for any new requests.\r\n


Message:
Wrong OS or OS version for application\r\n


Message:
Application was launched but it didn't register a class factory\r\n


Message:
An event was unable to invoke any of the subscribers\r\n


Message:
A syntax error occurred trying to evaluate a query string\r\n


Message:
An invalid field name was used in a query string\r\n


Message:
An unexpected internal error was detected\r\n


Message:
The owner SID on a per-user subscription doesn't exist\r\n


Message:
A user-supplied component or subscriber raised an exception\r\n


Message:
An interface has too many methods to fire events from\r\n


Message:
A subscription cannot be stored unless its event class already exists\r\n


Message:
Not all the objects requested could be removed\r\n


Message:
COM+ is required for this operation, but is not installed\r\n


Message:
One or more of the properties that are needed to run this task have not been set.\r\n


Message:
There is no running instance of the task to terminate.\r\n


Message:
The Task Scheduler Service is not installed on this computer.\r\n


Message:
The task object could not be opened.\r\n


Message:
The object is either an invalid task object or is not a task object.\r\n


Message:
No account information could be found in the Task Scheduler security database for the task indicated.\r\n


Message:
Unable to establish existence of the account specified.\r\n


Message:
Corruption was detected in the Task Scheduler security database; the database has been reset.\r\n


Message:
Task Scheduler security services are available only on Windows NT.\r\n


Message:
The task object version is either unsupported or invalid.\r\n


Message:
The task has been configured with an unsupported combination of account settings and run time options.\r\n


Message:
The Task Scheduler Service is not running.\r\n


Message:
Digest authentication: stalled 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:
The Inport bus mouse does not exist or was not detected.\r\n


Message:
The ISR has detected an internal state error in the driver for %1.\r\n


Message:
A user hit their quota threshold on volume %2.\r\n


Message:
A user hit their quota limit on volume %2.\r\n


Message:
The system has started rebuilding the user disk quota information on\r\ndevice %1 with label "%2".\r\n


Message:
The system has successfully rebuilt the user disk quota information on\r\ndevice %1 with label "%2".\r\n


Message:
The driver has detected that device %1 has old or out-of-date firmware.\r\nReduced performance may result.\r\n


Message:
The driver detected that the device %1 has its write cache enabled. Data corruption\r\nmay occur.\r\n


Message:
Data was recovered using error correction code on device %1.\r\n


Message:
The driver disabled the write cache on device %1.\r\n


Message:
The system has encounted an error rebuilding the user disk quota\r\ninformation on device %1 with label "%2".\r\n


Message:
The driver could not allocate something necessary for the request for %1.\r\n


Message:
Driver or device is incorrectly configured for %1.\r\n


Message:
Driver detected an internal error in its data structures for %1.\r\n


Message:
The device, %1, did not respond within the timeout period.\r\n


Message:
The driver detected an unexpected sequence by the device, %1.\r\n


Message:
The driver detected a controller error on %1.\r\n


Message:
The driver detected an internal driver error on %1.\r\n


Message:
The driver was configured with an incorrect interrupt for %1.\r\n


Message:
The driver was configured with an invalid I/O base address for %1.\r\n


Message:
The device, %1, is not ready for access yet.\r\n


Message:
The request is incorrectly formatted for %1.\r\n


Message:
The wrong version of the driver has been loaded.\r\n


Message:
The driver beneath this one has failed in some way for %1.\r\n


Message:
A transport driver received a frame which violated the protocol.\r\n


Message:
A conflict has been detected between two drivers which claimed two overlapping\r\nmemory regions.\r\nDriver %2, with device <%3>, claimed a memory range with starting address\r\nin data address 0x28 and 0x2c, and length in data address 0x30.\r\n


Message:
A conflict has been detected between two drivers which claimed two overlapping\r\nIo port regions.\r\nDriver %2, with device <%3>, claimed an IO port range with starting address\r\nin data address 0x28 and 0x2c, and length in data address 0x30.\r\n


Message:
A conflict has been detected between two drivers which claimed equivalent DMA\r\nchannels.\r\nDriver %2, with device <%3>, claimed the DMA Channel in data address 0x28, with\r\noptinal port in data address 0x2c.\r\n


Message:
A conflict has been detected between two drivers which claimed equivalent IRQs.\r\nDriver %2, with device <%3>, claimed an interrupt with Level in data address\r\n0x28, vector in data address 0x2c and Affinity in data address 0x30.\r\n


Message:
The driver has detected a device with old or out-of-date firmware.  The\r\ndevice will not be used.\r\n


Message:
The device could not allocate one or more required resources due to conflicts\r\nwith other devices. The device DMA setting of '%2' could not be\r\nsatisified due to a conflict with Driver '%3'.\r\n


Message:
The device could not allocate one or more required resources due to conflicts\r\nwith other devices. The device interrupt setting of '%2' could not be\r\nsatisified due to a conflict with Driver '%3'.\r\n


Message:
The device could not allocate one or more required resources due to conflicts\r\nwith other devices. The device memory setting of '%2' could not be\r\nsatisified due to a conflict with Driver '%3'.\r\n


Message:
The device could not allocate one or more required resources due to conflicts\r\nwith other devices. The device port setting of '%2' could not be\r\nsatisified due to a conflict with Driver '%3'.\r\n


Message:
The file %2 on device %1 contains a bad disk block.\r\n


Message:
The file system structure on the disk is corrupt and unusable.\r\nPlease run the chkdsk utility on the device %1 with label "%2".\r\n


Message:
The user disk quota information is unusable.\r\nTo ensure accuracy, the file system quota information on the device %1 with label "%2" will\r\nbe rebuilt.\r\n


Message:
The system could not get file retrieval pointers for the dump file.\r\n


Message:
The system could not sucessfully load the crash dump driver.\r\n


Message:
A valid crash dump was found in the paging file while trying to configure\r\na direct dump. Direct dump is disabled! This occurs when the direct dump\r\noption is set in the registry but a stop error occured before configuration\r\ncompleted\r\n


Message:
Direct dump configuration failed. Validate the filename and make sure the target device\r\nis not a Fault Tolerant set member, remote, or floppy device. The failure may\r\nbe because there is not enough room on the dump device to create the dump file.\r\n


Message:
Configuring the Page file for crash dump failed. Make sure there is a page\r\nfile on the boot partition and that is large enough to contain all physical\r\nmemory.\r\n


Message:
The file system structure on the disk is corrupt and unusable.\r\nPlease run the chkdsk utility on the volume %2.\r\n


Message:
IPRIP was unable to create an event for synchronization.\r\nPlease try freeing some system resources.\r\n


Message:
IPRIP was unable to add a route to the system route table.\r\nThe data is the error code.\r\n


Message:
The system cannot find the file specified.\r\n


Message:
The system cannot find the path specified.\r\n


Message:
The storage control blocks were destroyed.\r\n


Message:
Not enough storage is available to process this command.\r\n


Message:
The storage control block address is invalid.\r\n


Message:
The instance name passed was not recognized as valid by a WMI data provider.\r\n


Message:
The data item ID passed was not recognized as valid by a WMI data provider.\r\n


Message:
The WMI request could not be completed and should be retried.\r\n


Message:
The WMI data provider could not be located.\r\n


Message:
The WMI data provider references an instance set that has not been registered.\r\n


Message:
The WMI data block or event notification has already been enabled.\r\n


Message:
The WMI data block is no longer available.\r\n


Message:
The WMI data service is not available.\r\n


Message:
The WMI data provider failed to carry out the request.\r\n


Message:
The WMI MOF information is not valid.\r\n


Message:
The WMI registration information is not valid.\r\n


Message:
The WMI data block or event notification has already been disabled.\r\n


Message:
The WMI data item or data block is read only.\r\n


Message:
The WMI data item or data block could not be changed.\r\n


Message:
The media identifier does not represent a valid medium.\r\n


Message:
The library identifier does not represent a valid library.\r\n


Message:
The media pool identifier does not represent a valid media pool.\r\n


Message:
The drive and medium are not compatible or exist in different libraries.\r\n


Message:
The medium currently exists in an offline library and must be online to perform this operation.\r\n


Message:
The operation cannot be performed on an offline library.\r\n


Message:
The library, drive, or media pool is empty.\r\n


Message:
OSS ASN.1 Error: System resource error.\r\n


Message:
ASN1 Certificate encode/decode error code base.\r\n\r\nThe ASN1 error values are offset by CRYPT_E_ASN1_ERROR.\r\n


Message:
ASN1 internal encode or decode error.\r\n


Message:
ASN1 function not supported for this PDU.\r\n


Message:
ASN1 bad arguments to function call.\r\n


Message:
The request subject name is invalid or too long.\r\n


Message:
The request's current status does not allow this operation.\r\n


Message:
The requested property value is empty.\r\n


Message:
The certification authority's certificate contains invalid data.\r\n


Message:
Certificate service has been suspended for a database restore operation.\r\n


Message:
The certificate contains an encoded length that is potentially incompatible with older enrollment software.\r\n


Message:
The requested certificate template is not supported by this CA.\r\n


Message:
The request contains no certificate template information.\r\n


Message:
A system-level error occurred while verifying trust.\r\n


Message:
The certificate for the signer of the message is invalid or not found.\r\n


Message:
One of the counter signatures was invalid.\r\n


Message:
IIS Logging for %1 was resumed.\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:
IIS ODBC Logging resumed logging to data source %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:
IIS Logging for %1 has been shutdown because a disk full error has been encountered.\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:
IIS Logging was unable to create the directory %1.  The data is the error.\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:
IIS Logging was unable to create the file %1.  The data is the error.\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:
IIS ODBC Logging failed to connect to data source %1. Error text is [%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:
IIS ODBC Logging failed to log data to data source %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:
An attempt was made to load a program with an incorrect format.\r\n


Message:
Not enough storage is available to complete this operation.\r\n


Message:
The system cannot find the drive specified.\r\n


Message:
The system cannot move the file to a different disk drive.\r\n


Message:
The system cannot find the device specified.\r\n


Message:
The device does not recognize the command.\r\n


Message:
Data error (cyclic redundancy check).\r\n


Message:
The program issued a command but the command length is incorrect.\r\n


Message:
The drive cannot locate a specific area or track on the disk.\r\n


Message:
The specified disk or diskette cannot be accessed.\r\n


Message:
The drive cannot find the sector requested.\r\n


Message:
The system cannot write to the specified device.\r\n


Message:
The system cannot read from the specified device.\r\n


Message:
A device attached to the system is not functioning.\r\n


Message:
The process cannot access the file because it is being used by another process.\r\n


Message:
The process cannot access the file because another process has locked a portion of the file.\r\n


Message:
The wrong diskette is in the drive.\r\nInsert %2 (Volume Serial Number: %3)\r\ninto drive %1.\r\n


Message:
The network request is not supported.\r\n


Message:
The remote computer is not available.\r\n


Message:
A duplicate name exists on the network.\r\n


Message:
The specified network resource or device is no longer available.\r\n


Message:
The network BIOS command limit has been reached.\r\n


Message:
A network adapter hardware error occurred.\r\n


Message:
The verify-on-write switch parameter value is not correct.\r\n


Message:
The system does not support the command requested.\r\n


Message:
This function is only valid in Windows NT mode.\r\n


Message:
The semaphore timeout period has expired.\r\n


Message:
The data area passed to a system call is too small.\r\n


Message:
The filename, directory name, or volume label syntax is incorrect.\r\n


Message:
The system call level is not correct.\r\n


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


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


Message:
There are no child processes to wait for.\r\n


Message:
The %1 application cannot be run in Win32 mode.\r\n


Message:
Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.\r\n


Message:
An attempt was made to move the file pointer before the beginning of the file.\r\n


Message:
The file pointer cannot be set on the specified device or file.\r\n


Message:
A JOIN or SUBST command cannot be used for a drive that contains previously joined drives.\r\n


Message:
An attempt was made to use a JOIN or SUBST command on a drive that has already been joined.\r\n


Message:
An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted.\r\n


Message:
The system tried to delete the JOIN of a drive that is not joined.\r\n


Message:
The system tried to delete the substitution of a drive that is not substituted.\r\n


Message:
The system tried to join a drive to a directory on a joined drive.\r\n


Message:
The system tried to substitute a drive to a directory on a substituted drive.\r\n


Message:
The system tried to join a drive to a directory on a substituted drive.\r\n


Message:
The system tried to SUBST a drive to a directory on a joined drive.\r\n


Message:
A lock request was not outstanding for the supplied cancel region.\r\n


Message:
The file system does not support atomic changes to the lock type.\r\n


Message:
The system detected a segment number that was not correct.\r\n


Message:
Cannot create a file when that file already exists.\r\n


Message:
The specified system semaphore name was not found.\r\n


Message:
%1 is not a valid Win32 application.\r\n


Message:
The operating system cannot run this application program.\r\n


Message:
The operating system is not presently configured to run this application.\r\n


Message:
The code segment cannot be greater than or equal to 64K.\r\n


Message:
The system could not find the environment\r\noption that was entered.\r\n


Message:
No process in the command subtree has a\r\nsignal handler.\r\n


Message:
The filename or extension is too long.\r\n


Message:
The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.\r\n


Message:
The signal being posted is not correct.\r\n


Message:
The segment is locked and cannot be reallocated.\r\n


Message:
Too many dynamic-link modules are attached to this program or dynamic-link module.\r\n


Message:
The image file %1 is valid, but is for a machine type other than the current machine.\r\n


Message:
No process is on the other end of the pipe.\r\n


Message:
The specified extended attribute name was invalid.\r\n


Message:
The extended attributes are inconsistent.\r\n


Message:
The extended attributes did not fit in the buffer.\r\n


Message:
The extended attribute file on the mounted file system is corrupt.\r\n


Message:
The extended attribute table file is full.\r\n


Message:
The specified extended attribute handle is invalid.\r\n


Message:
The mounted file system does not support extended attributes.\r\n


Message:
Attempt to release mutex not owned by caller.\r\n


Message:
Too many posts were made to a semaphore.\r\n


Message:
Only part of a ReadProcessMemory or WriteProcessMemory request was completed.\r\n


Message:
An invalid oplock acknowledgment was received by the system.\r\n


Message:
The system cannot find message text for message number 0x%1 in the message file for %2.\r\n


Message:
There is a process on other end of the pipe.\r\n


Message:
Waiting for a process to open the other end of the pipe.\r\n


Message:
Access to the extended attribute was denied.\r\n


Message:
The I/O operation has been aborted because of either a thread exit or an application request.\r\n


Message:
Overlapped I/O event is not in a signaled state.\r\n


Message:
Overlapped I/O operation is in progress.\r\n


Message:
Recursion too deep; the stack overflowed.\r\n


Message:
The window cannot act on the sent message.\r\n


Message:
The volume does not contain a recognized file system.\r\nPlease make sure that all required file system drivers are loaded and that the volume is not corrupted.\r\n


Message:
The volume for a file has been externally altered so that the opened file is no longer valid.\r\n


Message:
The requested operation cannot be performed in full-screen mode.\r\n


Message:
An attempt was made to reference a token that does not exist.\r\n


Message:
The configuration registry database is corrupt.\r\n


Message:
The configuration registry key is invalid.\r\n


Message:
The configuration registry key could not be opened.\r\n


Message:
The configuration registry key could not be read.\r\n


Message:
The configuration registry key could not be written.\r\n


Message:
One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.\r\n


Message:
The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.\r\n


Message:
An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.\r\n


Message:
The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.\r\n


Message:
Illegal operation attempted on a registry key that has been marked for deletion.\r\n


Message:
System could not allocate the required space in a registry log.\r\n


Message:
Cannot create a symbolic link in a registry key that already has subkeys or values.\r\n


Message:
Cannot create a stable subkey under a volatile parent key.\r\n


Message:
A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.\r\n


Message:
A stop control has been sent to a service that other running services are dependent on.\r\n


Message:
The requested control is not valid for this service.\r\n


Message:
The service did not respond to the start or control request in a timely fashion.\r\n


Message:
A thread could not be created for the service.\r\n


Message:
An instance of the service is already running.\r\n


Message:
The account name is invalid or does not exist, or the password is invalid for the account name specified.\r\n


Message:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.\r\n


Message:
Circular service dependency was specified.\r\n


Message:
The specified service does not exist as an installed service.\r\n


Message:
The service cannot accept control messages at this time.\r\n


Message:
The service process could not connect to the service controller.\r\n


Message:
An exception occurred in the service when handling the control request.\r\n


Message:
The database specified does not exist.\r\n


Message:
The service has returned a service-specific error code.\r\n


Message:
The dependency service or group failed to start.\r\n


Message:
The service did not start due to a logon failure.\r\n


Message:
After starting, the service hung in a start-pending state.\r\n


Message:
The specified service database lock is invalid.\r\n


Message:
The specified service has been marked for deletion.\r\n


Message:
The specified service already exists.\r\n


Message:
The system is currently running with the last-known-good configuration.\r\n


Message:
The dependency service does not exist or has been marked for deletion.\r\n


Message:
The current boot has already been accepted for use as the last-known-good control set.\r\n


Message:
No attempts to start the service have been made since the last boot.\r\n


Message:
The name is already in use as either a service name or a service display name.\r\n


Message:
The account specified for this service is different from the account specified for other services running in the same process.\r\n


Message:
Failure actions can only be set for Win32 services, not for drivers.\r\n


Message:
This service runs in the same process as the service control manager.\r\nTherefore, the service control manager cannot take action if this service's process terminates unexpectedly.\r\n


Message:
No recovery program has been configured for this service.\r\n


Message:
The executable program that this service is configured to run in does not implement the service.\r\n


Message:
The physical end of the tape has been reached.\r\n


Message:
The beginning of the tape or a partition was encountered.\r\n


Message:
A tape access reached the end of a set of files.\r\n


Message:
When accessing a new tape of a multivolume partition, the current block size is incorrect.\r\n


Message:
Tape partition information could not be found when loading a tape.\r\n


Message:
Unable to lock the media eject mechanism.\r\n


Message:
The media in the drive may have changed.\r\n


Message:
No mapping for the Unicode character exists in the target multi-byte code page.\r\n


Message:
A dynamic link library (DLL) initialization routine failed.\r\n


Message:
Unable to abort the system shutdown because no shutdown was in progress.\r\n


Message:
The request could not be performed because of an I/O device error.\r\n


Message:
No serial device was successfully initialized. The serial driver will unload.\r\n


Message:
Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened.\r\n


Message:
A serial I/O operation was completed by another write to the serial port.\r\n(The IOCTL_SERIAL_XOFF_COUNTER reached zero.)\r\n


Message:
A serial I/O operation completed because the timeout period expired.\r\n(The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)\r\n


Message:
No ID address mark was found on the floppy disk.\r\n


Message:
Mismatch between the floppy disk sector ID field and the floppy disk controller track address.\r\n


Message:
The floppy disk controller reported an error that is not recognized by the floppy disk driver.\r\n


Message:
The floppy disk controller returned inconsistent results in its registers.\r\n


Message:
While accessing the hard disk, a recalibrate operation failed, even after retries.\r\n


Message:
While accessing the hard disk, a disk operation failed even after retries.\r\n


Message:
While accessing the hard disk, a disk controller reset was needed, but even that failed.\r\n


Message:
Not enough server storage is available to process this command.\r\n


Message:
A potential deadlock condition has been detected.\r\n


Message:
The base address or the file offset specified does not have the proper alignment.\r\n


Message:
An attempt to change the system power state was vetoed by another application or driver.\r\n


Message:
The system BIOS failed an attempt to change the system power state.\r\n


Message:
An attempt was made to create more links on a file than the file system supports.\r\n


Message:
The specified program requires a newer version of Windows.\r\n


Message:
The specified program is not a Windows or MS-DOS program.\r\n


Message:
Cannot start more than one instance of the specified program.\r\n


Message:
The specified program was written for an earlier version of Windows.\r\n


Message:
One of the library files needed to run this application is damaged.\r\n


Message:
No application is associated with the specified file for this operation.\r\n


Message:
An error occurred in sending the command to the application.\r\n


Message:
One of the library files needed to run this application cannot be found.\r\n


Message:
The current process has used all of its system allowance of handles for Window Manager objects.\r\n


Message:
The message can be used only with synchronous operations.\r\n


Message:
The indicated source element has no media.\r\n


Message:
The indicated destination element already contains media.\r\n


Message:
The indicated element does not exist.\r\n


Message:
The indicated element is part of a magazine that is not present.\r\n


Message:
The indicated device requires reinitialization due to hardware errors.\r\n


Message:
The device has indicated that cleaning is required before further operations are attempted.\r\n


Message:
The device has indicated that its door is open.\r\n


Message:
There was no match for the specified key in the index.\r\n


Message:
The property set specified does not exist on the object.\r\n


Message:
The point passed to GetMouseMovePoints is not in the buffer.\r\n


Message:
The tracking (workstation) service is not running.\r\n


Message:
The specified Very Large Memory (64-bit) operation is invalid.\r\n


Message:
Unable to remove the file to be replaced.\r\n


Message:
Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name.\r\n


Message:
Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name.\r\n


Message:
The volume change journal is being deleted.\r\n


Message:
The volume change journal service is not active.\r\n


Message:
A file was found, but it may not be the correct file.\r\n


Message:
The journal entry has been deleted from the journal.\r\n


Message:
The specified device name is invalid.\r\n


Message:
The device is not currently connected but it is a remembered connection.\r\n


Message:
An attempt was made to remember a device that had previously been remembered.\r\n


Message:
No network provider accepted the given network path.\r\n


Message:
The specified network provider name is invalid.\r\n


Message:
Unable to open the network connection profile.\r\n


Message:
The network connection profile is corrupted.\r\n


Message:
The format of the specified group name is invalid.\r\n


Message:
The format of the specified computer name is invalid.\r\n


Message:
The format of the specified event name is invalid.\r\n


Message:
The format of the specified domain name is invalid.\r\n


Message:
The format of the specified service name is invalid.\r\n


Message:
The format of the specified network name is invalid.\r\n


Message:
The format of the specified share name is invalid.\r\n


Message:
The format of the specified password is invalid.\r\n


Message:
The format of the specified message name is invalid.\r\n


Message:
The format of the specified message destination is invalid.\r\n


Message:
The credentials supplied conflict with an existing set of credentials.\r\n


Message:
An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.\r\n


Message:
The workgroup or domain name is already in use by another computer on the network.\r\n


Message:
The network is not present or not started.\r\n


Message:
The operation was canceled by the user.\r\n


Message:
The requested operation cannot be performed on a file with a user-mapped section open.\r\n


Message:
The remote system refused the network connection.\r\n


Message:
The network connection was gracefully closed.\r\n


Message:
The network transport endpoint already has an address associated with it.\r\n


Message:
An address has not yet been associated with the network endpoint.\r\n


Message:
An operation was attempted on a nonexistent network connection.\r\n


Message:
An invalid operation was attempted on an active network connection.\r\n


Message:
The network location cannot be reached. For information about network troubleshooting, see Windows Help.\r\n


Message:
No service is operating at the destination network endpoint on the remote system.\r\n


Message:
The network connection was aborted by the local system.\r\n


Message:
The operation could not be completed. A retry should be performed.\r\n


Message:
A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.\r\n


Message:
Attempting to log in during an unauthorized time of day for this account.\r\n


Message:
The account is not authorized to log in from this station.\r\n


Message:
The network address could not be used for the operation requested.\r\n


Message:
The specified service does not exist.\r\n


Message:
The operation being requested was not performed because the user has not been authenticated.\r\n


Message:
The operation being requested was not performed because the user has not logged on to the network.\r\nThe specified service does not exist.\r\n


Message:
An attempt was made to perform an initialization operation when initialization has already been completed.\r\n


Message:
The name provided is not a properly formed account name.\r\n


Message:
Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.\r\n


Message:
The specified user account is not a member of the specified group account.\r\n


Message:
The last remaining administration account cannot be disabled or deleted.\r\n


Message:
Unable to update the password. The value provided as the current password is incorrect.\r\n


Message:
Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.\r\n


Message:
Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirement of the domain.\r\n


Message:
Logon failure: unknown user name or bad password.\r\n


Message:
Logon failure: user account restriction.\r\n


Message:
Logon failure: account logon time restriction violation.\r\n


Message:
Logon failure: user not allowed to log on to this computer.\r\n


Message:
Logon failure: the specified account password has expired.\r\n


Message:
Logon failure: account currently disabled.\r\n


Message:
No mapping between account names and security IDs was done.\r\n


Message:
Too many local user identifiers (LUIDs) were requested at one time.\r\n


Message:
No more local user identifiers (LUIDs) are available.\r\n


Message:
The subauthority part of a security ID is invalid for this particular use.\r\n


Message:
The access control list (ACL) structure is invalid.\r\n


Message:
The security ID structure is invalid.\r\n


Message:
The security descriptor structure is invalid.\r\n


Message:
The inherited access control list (ACL) or access control entry (ACE) could not be built.\r\n


Message:
The value provided was an invalid value for an identifier authority.\r\n


Message:
No more memory is available for security information updates.\r\n


Message:
The specified attributes are invalid, or incompatible with the attributes for the group as a whole.\r\n


Message:
Either a required impersonation level was not provided, or the provided impersonation level is invalid.\r\n


Message:
Cannot open an anonymous level security token.\r\n


Message:
The validation information class requested was invalid.\r\n


Message:
The type of the token is inappropriate for its attempted use.\r\n


Message:
Unable to perform a security operation on an object that has no associated security.\r\n


Message:
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.\r\n


Message:
The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.\r\n


Message:
The domain was in the wrong state to perform the security operation.\r\n


Message:
This operation is only allowed for the Primary Domain Controller of the domain.\r\n


Message:
The specified domain either does not exist or could not be contacted.\r\n


Message:
The specified domain already exists.\r\n


Message:
An attempt was made to exceed the limit on the number of domains per server.\r\n


Message:
Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.\r\n


Message:
Generic access types were contained in an access mask which should already be mapped to nongeneric types.\r\n


Message:
A security descriptor is not in the right format (absolute or self-relative).\r\n


Message:
The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.\r\n


Message:
Cannot start a new logon session with an ID that is already in use.\r\n


Message:
A specified authentication package is unknown.\r\n


Message:
The logon session is not in a state that is consistent with the requested operation.\r\n


Message:
The logon session ID is already in use.\r\n


Message:
A logon request contained an invalid logon type value.\r\n


Message:
Unable to impersonate using a named pipe until data has been read from that pipe.\r\n


Message:
The transaction state of a registry subtree is incompatible with the requested operation.\r\n


Message:
An internal security database corruption has been encountered.\r\n


Message:
Cannot perform this operation on built-in accounts.\r\n


Message:
Cannot perform this operation on this built-in special group.\r\n


Message:
Cannot perform this operation on this built-in special user.\r\n


Message:
The user cannot be removed from a group because the group is currently the user's primary group.\r\n


Message:
The token is already in use as a primary token.\r\n


Message:
The specified local group does not exist.\r\n


Message:
The specified account name is not a member of the local group.\r\n


Message:
The specified account name is already a member of the local group.\r\n


Message:
The specified local group already exists.\r\n


Message:
Logon failure: the user has not been granted the requested logon type at this computer.\r\n


Message:
The maximum number of secrets that may be stored in a single system has been exceeded.\r\n


Message:
The length of a secret exceeds the maximum length allowed.\r\n


Message:
The local security authority database contains an internal inconsistency.\r\n


Message:
During a logon attempt, the user's security context accumulated too many security IDs.\r\n


Message:
A cross-encrypted password is necessary to change a user password.\r\n


Message:
A member could not be added to or removed from the local group because the member does not exist.\r\n


Message:
A new member could not be added to a local group because the member has the wrong account type.\r\n


Message:
Too many security IDs have been specified.\r\n


Message:
A cross-encrypted password is necessary to change this user password.\r\n


Message:
Indicates an ACL contains no inheritable components.\r\n


Message:
The file or directory is corrupted and unreadable.\r\n


Message:
The disk structure is corrupted and unreadable.\r\n


Message:
There is no user session key for the specified logon session.\r\n


Message:
The service being accessed is licensed for a particular number of connections.\r\nNo more connections can be made to the service at this time because there are already as many connections as the service can accept.\r\n


Message:
Logon Failure: The target account name is incorrect.\r\n


Message:
Mutual Authentication failed. The server's password is out of date at the domain controller.\r\n


Message:
There is a time difference between the client and server.\r\n


Message:
Invalid handle to a multiple-window position structure.\r\n


Message:
Cannot create a top-level child window.\r\n


Message:
Invalid window; it belongs to other thread.\r\n


Message:
SQL query syntax invalid or unsupported.\r\n


Message:
An error occurred while sending a message to %1.\r\n


Message:
The password or user name is invalid for %1.\r\n


Message:
An error occurred when the share was deleted.\r\n


Message:
Your persistent connections were not all restored.\r\n


Message:
This is not a valid computer name or domain name.\r\n


Message:
Default permissions cannot be set for that resource.\r\n


Message:
The resource named cannot be shared.\r\n


Message:
The permissions string contains invalid permissions.\r\n


Message:
You can only perform this operation on printers and communication devices.\r\n


Message:
%1 is an invalid user or group name.\r\n


Message:
The server is not configured for remote administration.\r\n


Message:
No users have sessions with this server.\r\n


Message:
User %1 is not a member of group %2.\r\n


Message:
User %1 is already a member of group %2.\r\n


Message:
The destination list provided does not match the destination list of the printer queue.\r\n


Message:
Your password cannot be changed until %1.\r\n


Message:
The current local clock is %1\r\nDo you want to set the local computer's time to match the\r\ntime at %2? %3: %0\r\n


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


Message:
The user's home directory could not be determined.\r\n


Message:
The user's home directory has not been specified.\r\n


Message:
The name specified for the user's home directory (%1) is not a universal naming convention (UNC) name.\r\n


Message:
Drive %1 is now connected to %2. Your home directory is %3\\%4.\r\n


Message:
There are no available drive letters left.\r\n


Message:
%1 is not a valid domain or workgroup name.\r\n


Message:
This computer is not currently configured to use a specific SNTP server.\r\n


Message:
This current autoconfigured SNTP value is: %1\r\n


Message:
You specified too many values for the %1 option.\r\n


Message:
You entered an invalid value for the %1 option.\r\n


Message:
You specified an invalid file number.\r\n


Message:
You specified an invalid print job number.\r\n


Message:
The user or group account specified cannot be found.\r\n


Message:
The user was added but could not be enabled for File and Print\r\nServices for NetWare.\r\n


Message:
File and Print Services for NetWare is not installed.\r\n


Message:
Cannot set user properties for File and Print Services for NetWare.\r\n


Message:
The file replication service detected an invalid parameter.\r\n


Message:
An error occurred while installing the directory service. For more information, see the event log.\r\n


Message:
The directory service evaluated group memberships locally.\r\n


Message:
The specified directory service attribute or value does not exist.\r\n


Message:
The attribute syntax specified to the directory service is invalid.\r\n


Message:
The attribute type specified to the directory service is not defined.\r\n


Message:
The specified directory service attribute or value already exists.\r\n


Message:
The directory service is unavailable.\r\n


Message:
The directory service was unable to allocate a relative identifier.\r\n


Message:
The directory service has exhausted the pool of relative identifiers.\r\n


Message:
The requested operation could not be performed because the directory service is not the master for that type of operation.\r\n


Message:
The directory service was unable to initialize the subsystem that allocates relative identifiers.\r\n


Message:
The requested operation did not satisfy one or more constraints associated with the class of the object.\r\n


Message:
The directory service can perform the requested operation only on a leaf object.\r\n


Message:
The search filter cannot be recognized.\r\n


Message:
The specified method is not supported.\r\n


Message:
The specified control is not supported by the server.\r\n


Message:
A referral loop was detected by the client.\r\n


Message:
The preset referral limit was exceeded.\r\n


Message:
The root object must be the head of a naming context. The root object cannot have an instantiated parent.\r\n


Message:
The add replica operation cannot be performed. The naming context must be writable in order to create the replica.\r\n


Message:
A reference to an attribute that is not defined in the schema occurred.\r\n


Message:
The maximum size of an object has been exceeded.\r\n


Message:
An attempt was made to add an object to the directory with a name that is already in use.\r\n


Message:
An attempt was made to add an object of a class that does not have an RDN defined in the schema.\r\n


Message:
It is not permitted for an alias to refer to another alias.\r\n


Message:
The class of the object must be structural; you cannot instantiate an abstract class.\r\n


Message:
The schema object could not be found.\r\n


Message:
A local object with this GUID (dead or alive) already exists.\r\n


Message:
The operation cannot be performed on a back link.\r\n


Message:
The cross reference for the specified naming context could not be found.\r\n


Message:
The operation could not be performed because the directory service is shutting down.\r\n


Message:
The directory service request is invalid.\r\n


Message:
The role owner attribute could not be read.\r\n


Message:
The requested FSMO operation failed. The current FSMO holder could not be contacted.\r\n


Message:
Modification of a DN across a naming context is not permitted.\r\n


Message:
The attribute cannot be modified because it is owned by the system.\r\n


Message:
Only the replicator can perform this function.\r\n


Message:
The specified class is not a subclass.\r\n


Message:
It is not permitted to delete a master cross reference.\r\n


Message:
Subtree notifications are only supported on NC heads.\r\n


Message:
Schema update failed: duplicate RDN.\r\n


Message:
Schema update failed: duplicate OID.\r\n


Message:
Schema update failed: duplicate MAPI identifier.\r\n


Message:
Schema update failed: duplicate schema-id GUID.\r\n


Message:
Schema update failed: duplicate LDAP display name.\r\n


Message:
Schema update failed: range-lower less than range upper.\r\n


Message:
Schema update failed: syntax mismatch.\r\n


Message:
Schema deletion failed: attribute is used in must-contain.\r\n


Message:
Schema deletion failed: attribute is used in may-contain.\r\n


Message:
Schema update failed: attribute in may-contain does not exist.\r\n


Message:
Request for data from a DSIS foreign computer received.\r\n


Message:
Information from the foriegn computer was retrieved successfully\r\n


Message:
Copying data from network requests to perfmon buffer.\r\n


Message:
Data contains return value of WSAIsBlocking() call just before call to SnmpMgrRequest(ASN_RFC1157_GETREQUEST) was made.\r\n


Message:
Current Status of the Process Heap. Data is: Allocated Entries, Allocated Bytes, Free Entries, Free Bytes, Module Line Number.\r\n


Message:
Allocating the internal data structure for a foriegn CPU.\r\n


Message:
Initializing data in foreign CPU data structure.\r\n


Message:
Attempting to open an SNMP link to foreign computer.\r\n


Message:
SNMP link to foreign computer established.\r\n


Message:
Using previously opened SNMP Link to Foreign Computer.\r\n


Message:
Data successfully retrieved from foreign computer\r\n


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


Message:
No SPX Devices are currently open or the NWLink SPX/SPXII service has\r\nnot been started. SPX performance data cannot be collected.\r\n


Message:
No objects were returned by the foreign computer.\r\n


Message:
No SNMP Mgr Session was established in the OpenTcpIpPerformanceData routine.\r\n


Message:
Not enough room in buffer to store Network Interface data. Available and\r\nrequired buffer size is returned in data.\r\n


Message:
Not enough room in buffer to store Network Protocol (IP, ICMP, TCP & UDP) data. Available and required buffer size is returned in data.\r\n


Message:
SNMP socket is busy. Subsequent calls to SNMP services may fail.\r\n


Message:
A NULL ICMP data buffer was returned by SNMP. No ICMP data will be returned. This may be caused by a problem with the SNMP service. \r\n


Message:
A NULL TCP data buffer was returned by SNMP. No ICMP data will be returned. This may be caused by a problem with the SNMP service. \r\n


Message:
A NULL buffer was returned by SNMP in response to a request for Network performance information. this may indicate a problem with the SNMP service.\r\n


Message:
Buffer passed to receive data from foreign computer was not large enough.\r\n


Message:
Unable to create an event for subsequent SNMP calls. NtStatus and WIN32 Error are returned in the data.\r\n


Message:
The CollectDsisPerformanceData routine returned an error.\r\n


Message:
CollectNbtPerformanceData routine returned an error.\r\n


Message:
Insufficient memory was available to allocate an SNMP request buffer.\r\n


Message:
SnmpMgrRequest call requesting the TCP, IP, UDP and Interface Counters returned an error. ErrorStatus and ErrorIndex values are shown in Data.\r\n


Message:
SnmpMgrRequest call requesting the Net Interface Counters returned an error. ErrorStatus and ErrorIndex values are shown in Data.\r\n


Message:
SnmpMgrRequest call requesting ICMP Counters returned an error. ErrorStatus and ErrorIndex values are shown in Data.\r\n


Message:
Error returned by SnmpGet (GETNEXT) request while processing Net Interface instances. ErrorStatus and ErrorIndex\r\nreturned in Data.\r\n


Message:
Error returned by SNMP while trying to close session.\r\n


Message:
Error returned by Heap Status routine. Data is returned status value.\r\n


Message:
Error converting a DSIS MIB string to it's corresponding ObjectId. This error is usually caused by the system's MIB not supporting the DSIS MIB inforamation.\r\n


Message:
Unable to convert Unicode CPU name to ASCII.\r\n


Message:
Unable to allocate internal storage for this foreign CPU.\r\n


Message:
Unable to establish SNMP link to foreign computer.\r\n


Message:
Unable to get data from foreign computer. SNMP Error Status and Error Index are returned in the Data.\r\n


Message:
The Open Procedure for service "%1!s!" in DLL "%2!s!" failed. \r\nPerformance data for this service will not be available. Status code \r\nreturned is data DWORD 0.\r\n


Message:
The end of the list has been reached.%0\r\n


Message:
An attempt to add a filter with a duplicate name succeeded with a modified name.%0\r\n


Message:
The state transition has not completed.%0\r\n


Message:
Some of the streams in this movie are in an unsupported format.%0\r\n


Message:
The file contained some property settings that were not used.%0\r\n


Message:
Some connections have failed and have been deferred.%0\r\n


Message:
The resource specified is no longer needed.%0\r\n


Message:
A connection could not be made with the media type in the persistent graph,%0\r\nbut has been made with a negotiated media type.%0\r\n


Message:
Cannot play back the video stream: no suitable decompressor could be found.%0\r\n


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


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


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


Message:
Unable to enable trace provider %1 for the %2 trace log configuration.\r\nOnly one instance of each trace provider can be enabled at any given time.\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\nAnother trace session for this provider is currently enabled.\r\nOnly one instance of each trace provider can be enabled at any given time.\r\n


Message:
Unable to create the exit event 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\nThe maximum number of active logs and alerts has been reached.\r\nRestart the log or alert when fewer logs and alerts are active.\r\n


Message:
Unable to read the list of counters from 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 read the list of trace providers to log for the %1 trace log configuration.\r\nThis log will not be started.\r\nThe error code returned is in the data.\r\n


Message:
Unable to allocate the memory for the counter list 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:
An error occurred while trying to update the log file with the current data\r\nfor the %1 log session.  This log session will be stopped.\r\nThe Pdh error returned is : %2.\r\n


Message:
An error occurred while trying to reset the current state of the %1 log or alert to Stopped.\r\nThe service will continue, but the configuration of that log or alert might\r\nbe incorrect.\r\n


Message:
An error occurred while trying to reset the current manual start state\r\nof the %1 log or alert to match its current stopped state.  The service\r\nwill continue, but the configuration of that log or alert might be incorrect.\r\n


Message:
The service was unable to add the counter '%1' to the %2 log or alert.  This log or alert\r\nwill continue, but data for that counter will not be collected.\r\nThe error returned is: %3.\r\n


Message:
The service was unable to add any counters to the %1 log or alert.  \r\nThis log or alert will not be started.\r\n


Message:
The service was unable to parse the alert info for the %2 alert so this counter\r\nwill not be monitored.\r\nThe path string in error is: %1\r\n


Message:
An error occurred while trying to reset the current manual stop state\r\nof the %1 log or alert to match the its current stopped state.  The service\r\nwill continue, but the configuration of that log or alert might be incorrect.\r\n


Message:
Unable to create the reconfigure event 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:
An error occurred while trying to collect data for the %1 alert scan.\r\nThe service will continue, but that alert scan will be stopped.\r\nThe error returned is: %2.\r\n


Message:
The addition of counter '%1' to the %2 log or alert generated a warning.\r\nData for that counter might not be collected.\r\nThe error returned is: %3.\r\n


Message:
Unable to create the %1 folder for the %2 log configuration.\r\nThis log will not be started.\r\nThe error returned is: %3.\r\n


Message:
Unable to execute command '%1' for the %2 alert.  \r\nThe alert will continue as scheduled.\r\nThe error code returned is in the data.\r\n


Message:
Unable to execute command '%1' for the %2 log.  \r\nThe log will continue as scheduled.\r\nThe error returned is: %3.\r\n


Message:
The service was unable to open the command or program file: %1. The %2 log or alert will\r\ncontinue as scheduled.  Check the file for existence, spelling and permissions or reenter\r\nthe file name using the configuration program.\r\nThe error returned is: %3.\r\n


Message:
Unable to allocate memory while starting the %1 log. \r\nThis log will not be started.\r\nThe error code returned is in the data.\r\n


Message:
The service was unable to send a message for alert %1 to machine %2. The alert will\r\ncontinue as scheduled.\r\nThe error returned is: %3.\r\n


Message:
Unable to read the configuration of the %1 log, started in response to the %2 alert trigger.  The alert will\r\ncontinue as scheduled.\r\n


Message:
Unable to start the %1 log in response to the %2 alert trigger.  The alert will\r\ncontinue as scheduled.\r\nThe error code returned is in the data.\r\n


Message:
Unable to create the %1 log file. The log will not be started.\r\nError returned is: %2.\r\n


Message:
The service was unable to add the counter '%1' to the %2 log or alert.\r\nThis log or alert will continue, but data for that counter will not be collected.\r\nTo collect data from a remote computer, the Performance Logs and Alerts service\r\nmust run under an account that has access to the remote system.\r\n


Message:
Unable to initialize the service. Win32 error code returned is in the data.\r\n


Message:
Unable to register the Service Control Handler function. Win32 error code returned\r\nis in the data.\r\n


Message:
Unable to create the configuration event. Win32 error code returned is in the data.\r\n


Message:
Unable to open the Performance Logs and Alerts configuration.\r\nThis configuration is initialized when you use the Performance\r\nLogs and Alerts Management Console snapin to create a Log or\r\nAlert session.\r\n


Message:
The SNMP Service has started successfully.\r\n


Message:
The SNMP Service has stopped successfully.\r\n


Message:
The SNMP Service configuration has been updated successfully.\r\n


Message:
The SNMP Service is ignoring the manager %1 because its name could not be resolved.\r\n


Message:
The SNMP Service is ignoring extension agent key %1 because it is missing or misconfigured.\r\n


Message:
The SNMP Service is ignoring extension agent dll %1 because it is missing or misconfigured.\r\n


Message:
The SNMP Service has reset the registry parameter sysObjectID to a default value.\r\nThis is caused either by an invalid type or by an invalid string format of the registry value.\r\n


Message:
The SNMP Service encountered an error while accessing the registry key %1.\r\n


Message:
The SNMP Service encountered an error while setting up the incoming transports.\\n\r\nThe %1 transport has been dropped out.\r\n


Message:
The SNMP Service encountered an error while registering for registry notifications.\\n\r\nChanges in the service's configuration will not be considered.\r\n


Message:
Microsoft LDAP Static Store DLL Loaded\r\n


Message:
Succeeded backing out group membership for Rdn: %1\r\n


Message:
LDAP Administrative Max Connections to database exceeded 100 times for %1\r\n


Message:
Failed to modify subref object.  If namespace partition root objects appear inconsistent, run modify operation again.\r\n


Message:
Partitioning setup failed to delete some objects from the source partition.  This should not affect functionality.\r\n


Message:
Attempted to partition a non-existent container %1.  Please create the container before trying to partition it.\r\n


Message:
Attempted to partition a non-empty container %1.  Please target an empty container.\r\n


Message:
Attempted to partition a partitioned container %1.  Please target an non-partitioned container.\r\n


Message:
Consecutive DB connect failures exceed threshold with connect string %1.  Putting DB in recovery mode.\r\n


Message:
DB recovery timeout overridden on connect string %1.  Verify system integrity.\r\n


Message:
Missing timestamp stored procedure indicates that the master database for this server may not have been updated with the mcis2upd.sql script.  Please run this script from your Site Server 3.0 Update for MCIS 2.0 installation site.\r\n


Message:
Microsoft LDAP Static Store DLL Load Failed\r\n


Message:
Memory Allocation Failed.  Additional Info: %1\r\n


Message:
Unable to connect to DB server with connect string: %1.  Validate login and verify database is running with TCP/IP support.\r\n


Message:
Failed to backout group membership for Rdn: %1\r\n


Message:
Maximum number of partitions exceeded.\r\n


Message:
Only one writeable database is allowed on a given value partition.  Remove write capability from %1.\r\n


Message:
You have exceeded the maximum of %1 subscribers for a given value partition.\r\n


Message:
The Code Page for the Database could not be determined.  %1\r\n


Message:
Another installation is already in progress.  Complete that installation before proceeding with this install.\r\n


Message:
This installation package could not be opened.  Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.\r\n


Message:
This installation package could not be opened.  Contact the application vendor to verify that this is a valid Windows Installer package.\r\n


Message:
There was an error starting the Windows Installer service user interface.  Contact your support personnel.\r\n


Message:
Error opening installation log file. Verify that the specified log file location exists and that you can write to it.\r\n


Message:
The language of this installation package is not supported by your system.\r\n


Message:
Error applying transforms.  Verify that the specified transform paths are valid.\r\n


Message:
This installation is forbidden by system policy.  Contact your system administrator.\r\n


Message:
The directory service cannot perform the requested operation on the RDN attribute of an object.\r\n


Message:
The directory service detected an attempt to modify the object class of an object.\r\n


Message:
The requested cross-domain move operation could not be performed.\r\n


Message:
Unable to contact the global catalog server.\r\n


Message:
The policy object is shared and can only be modified at the root.\r\n


Message:
The requested policy information is only in the directory service.\r\n


Message:
A domain controller promotion is currently active.\r\n


Message:
A domain controller promotion is not currently active\r\n


Message:
The time limit for this request was exceeded.\r\n


Message:
The size limit for this request was exceeded.\r\n


Message:
The administrative limit for this request was exceeded.\r\n


Message:
The requested authentication method is not supported by the server.\r\n


Message:
A more secure authentication method is required for this server.\r\n


Message:
The authentication mechanism is unknown.\r\n


Message:
A referral was returned from the server.\r\n


Message:
The server does not support the requested critical extension.\r\n


Message:
This request requires a secure connection.\r\n


Message:
There is no such object on the server.\r\n


Message:
An invalid dn syntax has been specified.\r\n


Message:
There is an alias dereferencing problem.\r\n


Message:
The server is unwilling to process the request.\r\n


Message:
The %1 service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.\r\n


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


Message:
The Service Control Manager tried to take a corrective action (%2) after the unexpected termination of the %3 service, but this action failed with the following error: %n%4\r\n


Message:
The Service Control Manager is not initialized successfully therefore the\r\nsystem is shutting down. Security configuration server (scesrv.dll) failed\r\nto initialize with error %1\r\n


Message:
The %1 command is marked as an interactive command.  However, the system is\r\nconfigured to not allow interactive command execution.  This command may not\r\nfunction properly.\r\n


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


Message:
The master browser has received a server announcement from the computer %2\r\nthat believes that it is the master browser for the domain on transport %3.\r\nThe master browser is stopping or an election is being forced.\r\n


Message:
The browser was unable to update the service status bits.  The data is the error.\r\n


Message:
The browser was unable to update its role.  The data is the error.\r\n


Message:
The browser was unable to promote itself to master browser.  The computer that currently\r\nbelieves it is the master browser is %1.\r\n


Message:
The browser driver was unable to convert a character string to a unicode string.\r\n


Message:
The browser was unable to add the configuration parameter %1.\r\n


Message:
The browser driver has received too many illegal datagrams from the remote computer %2 to name %3 on transport %4.  The data is the datagram.\r\nNo more events will be generated until the reset frequency has expired.\r\n


Message:
%1 is not a recognized day of the week.\r\n


Message:
The time range specified ends before it starts.\r\n


Message:
%1 is not a valid specification for minutes.\r\n


Message:
Time supplied is not exactly on the hour.\r\n


Message:
12 and 24 hour time formats may not be mixed.\r\n


Message:
An illegal date format has been supplied.\r\n


Message:
An illegal day range has been supplied.\r\n


Message:
An illegal time range has been supplied.\r\n


Message:
Arguments to NET USER are invalid. Check the minimum password\r\nlength and/or arguments supplied.\r\n


Message:
The value for ENABLESCRIPT must be YES.\r\n


Message:
An illegal country code has been supplied.\r\n


Message:
The user was successfully created but could not be added\r\nto the USERS local group.\r\n


Message:
The user context supplied is invalid.\r\n


Message:
The dynamic-link library %1 could not be loaded, or an error\r\noccurred while trying to use it.\r\n


Message:
Sending files is no longer supported.\r\n


Message:
You may not specify paths for ADMIN$ and IPC$ shares.\r\n


Message:
User or group %1 is already a member of local group %2.\r\n


Message:
There is no such global user or group: %1.\r\n


Message:
Only disk shares can be marked as cacheable\r\n


Message:
The system could not find message: %1.\r\n


Message:
The LANMAN root directory is unavailable.\r\n


Message:
The SCHED.LOG file could not be opened.\r\n


Message:
The Server service has not been started.\r\n


Message:
The delete failed due to a problem with the AT schedule file.\r\n


Message:
The command line cannot exceed 259 characters.\r\n


Message:
The AT schedule file could not be updated because the disk is full.\r\n


Message:
The AT schedule file is invalid.  Please delete the file and create a new one.\r\n


Message:
The syntax of this command is:\r\n\r\nAT [id] [/DELETE]\r\nAT time [/EVERY:date | /NEXT:date] command\r\n\r\nThe AT command schedules a program command to run at a\r\nlater date and time on a server.  It also displays the\r\nlist of programs and commands scheduled to be run.\r\n\r\nYou can specify the date as M,T,W,Th,F,Sa,Su or 1-31\r\nfor the day of the month.\r\n\r\nYou can specify the time in the 24 hour HH:MM format.\r\n


Message:
The AT command has timed-out.\r\nPlease try again later.\r\n


Message:
The minimum password age for user accounts cannot be greater\r\nthan the maximum password age.\r\n


Message:
You have specified a value that is incompatible\r\nwith servers with down-level software. Please specify a lower value.\r\n


Message:
%1 is not a valid Windows 2000 network message number.\r\n


Message:
The value returned had to be estimated.  It's accuracy can not be guaranteed.%0\r\n


Message:
This success code is reserved for internal purposes within ActiveMovie.%0\r\n


Message:
The graph can't be cued because of lack of or corrupt data.%0\r\n


Message:
The stop time for the sample was not set.%0\r\n


Message:
There was no preview pin available, so the capture pin output is being split to provide both capture and preview.%0\r\n


Message:
Could not change formats dynamically.%0\r\n


Message:
Current pin connection is not using the IOverlay transport.%0\r\n


Message:
Current pin connection is not using the IMemInputPin transport.%0\r\n


Message:
Setting a color key would conflict with the palette already set.%0\r\n


Message:
Setting a palette would conflict with the color key already set.%0\r\n


Message:
No matching color key is available.%0\r\n


Message:
Too many colors for the current display settings.%0\r\n


Message:
The state changed while waiting to process the sample.%0\r\n


Message:
The operation could not be performed because the filter is not stopped.%0\r\n


Message:
The operation could not be performed because the filter is not paused.%0\r\n


Message:
The operation could not be performed because the filter is not running.%0\r\n


Message:
The operation could not be performed because the filter is in the wrong state.%0\r\n


Message:
The sample start time is after the sample end time.%0\r\n


Message:
The supplied rectangle is invalid.%0\r\n


Message:
This pin cannot use the supplied media type.%0\r\n


Message:
This sample cannot be rendered because the end of the stream has been reached.%0\r\n


Message:
An attempt to add a filter with a duplicate name failed.%0\r\n


Message:
The list has already been exhausted.%0\r\n


Message:
Updates are not allowed in this state.%0\r\n


Message:
An attempt was made to queue a command for a time in the past.%0\r\n


Message:
The queued command has already been canceled.%0\r\n


Message:
Cannot render the file because it is corrupt.%0\r\n


Message:
An overlay advise link already exists.%0\r\n


Message:
No full-screen modes are available.%0\r\n


Message:
This Advise cannot be canceled because it was not successfully set.%0\r\n


Message:
A full-screen mode is not available.%0\r\n


Message:
Cannot call IVideoWindow methods while in full-screen mode.%0\r\n


Message:
The media type of this file is not recognized.%0\r\n


Message:
The source filter for this file could not be loaded.%0\r\n


Message:
The version number of the file is invalid.%0\r\n


Message:
The Windows Installer service failed to start.  Contact your support personnel.\r\n


Message:
The temp folder is either full or inaccessible.  Verify that the temp folder exists and that you can write to it.\r\n


Message:
This installation package is not supported by this processor type. Contact your product vendor.\r\n


Message:
Component not used on this computer.\r\n


Message:
This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.\r\n


Message:
This patch package could not be opened.  Contact the application vendor to verify that this is a valid Windows Installer patch package.\r\n


Message:
This patch package cannot be processed by the Windows Installer service.  You must install a Windows service pack that contains a newer version of the Windows Installer service.\r\n


Message:
Another version of this product is already installed.  Installation of this version cannot continue.  To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.\r\n


Message:
Invalid command line argument.  Consult the Windows Installer SDK for detailed command line help.\r\n


Message:
Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.\r\n


Message:
The requested operation completed successfully.  The system will be restarted so the changes can take effect.\r\n


Message:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.\r\n


Message:
The binding handle is not the correct type.\r\n


Message:
The RPC protocol sequence is not supported.\r\n


Message:
The RPC protocol sequence is invalid.\r\n


Message:
The string universal unique identifier (UUID) is invalid.\r\n


Message:
The object universal unique identifier (UUID) was not found.\r\n


Message:
The object universal unique identifier (UUID) has already been registered.\r\n


Message:
The type universal unique identifier (UUID) has already been registered.\r\n


Message:
The RPC server is already listening.\r\n


Message:
No protocol sequences have been registered.\r\n


Message:
Not enough resources are available to complete this operation.\r\n


Message:
The RPC server is too busy to complete this operation.\r\n


Message:
There are no remote procedure calls active on this thread.\r\n


Message:
The remote procedure call failed and did not execute.\r\n


Message:
A remote procedure call (RPC) protocol error occurred.\r\n


Message:
The transfer syntax is not supported by the RPC server.\r\n


Message:
The universal unique identifier (UUID) type is not supported.\r\n


Message:
The binding does not contain an entry name.\r\n


Message:
No network address is available to use to construct a universal unique identifier (UUID).\r\n


Message:
The maximum number of calls is too small.\r\n


Message:
The RPC protocol sequence was not found.\r\n


Message:
The procedure number is out of range.\r\n


Message:
The binding does not contain any authentication information.\r\n


Message:
The authentication service is unknown.\r\n


Message:
The authentication level is unknown.\r\n


Message:
The authorization service is unknown.\r\n


Message:
The server endpoint cannot perform the operation.\r\n


Message:
There are no more endpoints available from the endpoint mapper.\r\n


Message:
The network address family is invalid.\r\n


Message:
The requested operation is not supported.\r\n


Message:
No security context is available to allow impersonation.\r\n


Message:
An internal error occurred in a remote procedure call (RPC).\r\n


Message:
The RPC server attempted an integer division by zero.\r\n


Message:
An addressing error occurred in the RPC server.\r\n


Message:
A floating-point operation at the RPC server caused a division by zero.\r\n


Message:
A floating-point underflow occurred at the RPC server.\r\n


Message:
A floating-point overflow occurred at the RPC server.\r\n


Message:
The list of RPC servers available for the binding of auto handles has been exhausted.\r\n


Message:
Unable to open the character translation table file.\r\n


Message:
The file containing the character translation table has fewer than 512 bytes.\r\n


Message:
A null context handle was passed from the client to the host during a remote procedure call.\r\n


Message:
The RPC pipe object is invalid or corrupted.\r\n


Message:
An invalid operation was attempted on an RPC pipe object.\r\n


Message:
The endpoint mapper database entry could not be created.\r\n


Message:
The object universal unique identifier (UUID) is the nil UUID.\r\n


Message:
The specified printer handle is already being waited on\r\n


Message:
The specified printer has been deleted.\r\n


Message:
The state of the printer is invalid.\r\n


Message:
The user's password must be changed before logging on the first time.\r\n


Message:
Could not find the domain controller for this domain.\r\n


Message:
The referenced account is currently locked out and may not be logged on to.\r\n


Message:
The object exporter specified was not found.\r\n


Message:
The object resolver set specified was not found.\r\n


Message:
Some data remains to be sent in the request buffer.\r\n


Message:
Invalid asynchronous remote procedure call handle.\r\n


Message:
Invalid asynchronous RPC call handle for this operation.\r\n


Message:
The RPC pipe object has already been closed.\r\n


Message:
The RPC call completed before all pipes were processed.\r\n


Message:
No more data is available from the RPC pipe.\r\n


Message:
No site name is available for this machine.\r\n


Message:
The file can not be accessed by the system.\r\n


Message:
The name of the file cannot be resolved by the system.\r\n


Message:
The entry is not of the expected type.\r\n


Message:
Not all object UUIDs could be exported to the specified entry.\r\n


Message:
Interface could not be exported to the specified entry.\r\n


Message:
The specified profile entry could not be added.\r\n


Message:
The specified profile element could not be added.\r\n


Message:
The specified profile element could not be removed.\r\n


Message:
The group element could not be added.\r\n


Message:
The group element could not be removed.\r\n


Message:
The window style or class attribute is invalid for this operation.\r\n


Message:
The requested metafile operation is not supported.\r\n


Message:
The requested transformation operation is not supported.\r\n


Message:
The requested clipping operation is not supported.\r\n


Message:
The specified color management module is invalid.\r\n


Message:
The specified color profile is invalid.\r\n


Message:
The specified tag is already present.\r\n


Message:
The specified color profile is not associated with any device.\r\n


Message:
The specified color profile was not found.\r\n


Message:
The specified color space is invalid.\r\n


Message:
Image Color Management is not enabled.\r\n


Message:
There was an error while deleting the color transform.\r\n


Message:
The specified color transform is invalid.\r\n


Message:
The specified transform does not match the bitmap's color space.\r\n


Message:
The specified named color index is not present in the profile.\r\n


Message:
The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified.\r\n


Message:
This network connection does not exist.\r\n


Message:
This network connection has files open or requests pending.\r\n


Message:
The device is in use by an active process and cannot be disconnected.\r\n


Message:
The specified print monitor is unknown.\r\n


Message:
The specified printer driver is currently in use.\r\n


Message:
A StartDocPrinter call was not issued.\r\n


Message:
The specified print processor has already been installed.\r\n


Message:
The specified print monitor has already been installed.\r\n


Message:
The specified print monitor does not have the required functions.\r\n


Message:
The specified print monitor is currently in use.\r\n


Message:
The requested operation is not allowed when there are jobs queued to the printer.\r\n


Message:
The requested operation is successful. Changes will not be effective until the system is rebooted.\r\n


Message:
The requested operation is successful. Changes will not be effective until the service is restarted.\r\n


Message:
WINS encountered an error while processing the command.\r\n


Message:
The importation from the file failed.\r\n


Message:
The backup failed. Was a full backup done before?\r\n


Message:
The backup failed. Check the directory to which you are backing the database.\r\n


Message:
The name does not exist in the WINS database.\r\n


Message:
Replication with a nonconfigured partner is not allowed.\r\n


Message:
The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.\r\n


Message:
The GUID passed was not recognized as valid by a WMI data provider.\r\n


Message:
The library, drive, or media pool must be empty to perform this operation.\r\n


Message:
No media is currently available in this media pool or library.\r\n


Message:
A resource required for this operation is disabled.\r\n


Message:
The media identifier does not represent a valid cleaner.\r\n


Message:
The drive cannot be cleaned or does not support cleaning.\r\n


Message:
The object identifier does not represent a valid object.\r\n


Message:
Unable to read from or write to the database.\r\n


Message:
The medium is not compatible with the device or media pool.\r\n


Message:
The resource required for this operation does not exist.\r\n


Message:
The operation identifier is not valid.\r\n


Message:
The media is not mounted or ready for use.\r\n


Message:
The operator or administrator has refused the request.\r\n


Message:
The drive identifier does not represent a valid drive.\r\n


Message:
Library is full.  No slot is available for use.\r\n


Message:
The transport cannot access the medium.\r\n


Message:
Unable to load the medium into the drive.\r\n


Message:
Unable to retrieve the drive status.\r\n


Message:
Unable to retrieve status about the transport.\r\n


Message:
Cannot use the transport because it is already in use.\r\n


Message:
Unable to open or close the inject/eject port.\r\n


Message:
Unable to eject the medium because it is in a drive.\r\n


Message:
The cluster group could not be found.\r\n


Message:
The operation could not be completed because the cluster group is not online.\r\n


Message:
The cluster node is not a member of the cluster.\r\n


Message:
A cluster join operation is not in progress.\r\n


Message:
The cluster IP address is already in use.\r\n


Message:
No cluster security context is available.\r\n


Message:
The cluster network is not configured for internal cluster communication.\r\n


Message:
The cluster network is already online.\r\n


Message:
The cluster network is already offline.\r\n


Message:
The cluster node is already a member of the cluster.\r\n


Message:
The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.\r\n


Message:
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.\r\n


Message:
This operation cannot be performed on the cluster resource as it the quorum resource. You may not bring the quorum resource offline or modify its possible owners list.\r\n


Message:
The cluster quorum resource is not allowed to have any dependencies.\r\n


Message:
The cluster resource cannot be brought online. The owner node cannot run this resource.\r\n


Message:
The cluster node is not ready to perform the requested operation.\r\n


Message:
The cluster join operation was aborted.\r\n


Message:
The cluster join operation failed due to incompatible software versions between the joining node and its sponsor.\r\n


Message:
This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.\r\n


Message:
The system configuration changed during the cluster join or form operation. The join or form operation was aborted.\r\n


Message:
The specified resource type was not found.\r\n


Message:
The specified node does not support a resource of this type.  This may be due to version inconsistencies or due to the absence of the resource DLL on this node.\r\n


Message:
The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.\r\n


Message:
No authentication package could be registered with the RPC server.\r\n


Message:
You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.\r\n


Message:
The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.\r\n


Message:
The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.\r\n


Message:
A non locker code got a request to reserve the lock for making global updates.\r\n


Message:
The quorum disk could not be located by the cluster service.\r\n


Message:
The backed up cluster database is possibly corrupt.\r\n


Message:
A DFS root already exists in this cluster node.\r\n


Message:
An attempt to modify a resource property failed because it conflicts with another existing property.\r\n


Message:
The specified file could not be encrypted.\r\n


Message:
The specified file could not be decrypted.\r\n


Message:
The specified file is encrypted and the user does not have the ability to decrypt it.\r\n


Message:
There is no valid encryption recovery policy configured for this system.\r\n


Message:
The required encryption driver is not loaded for this system.\r\n


Message:
The file was encrypted with a different encryption driver than is currently loaded.\r\n


Message:
There are no EFS keys defined for the user.\r\n


Message:
The specified file is not encrypted.\r\n


Message:
The specified file is not in the defined EFS export format.\r\n


Message:
The directory has been disabled for encryption.\r\n


Message:
The server is not trusted for remote encryption operation.\r\n


Message:
The list of servers for this workgroup is not currently available\r\n


Message:
The specified session name is invalid.\r\n


Message:
The specified protocol driver is invalid.\r\n


Message:
The specified protocol driver was not found in the system path.\r\n


Message:
The specified terminal connection driver was not found in the system path.\r\n


Message:
A registry key for event logging could not be created for this session.\r\n


Message:
A service with the same name already exists on the system.\r\n


Message:
A close operation is pending on the session.\r\n


Message:
There are no free output buffers available.\r\n


Message:
The modem name was not found in MODEM.INF.\r\n


Message:
The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.\r\n


Message:
The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.\r\n


Message:
Carrier detect has failed or carrier has been dropped due to disconnect.\r\n


Message:
Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.\r\n


Message:
Busy signal detected at remote site on callback.\r\n


Message:
Voice detected at remote site on callback.\r\n


Message:
The specified session cannot be found.\r\n


Message:
The specified session name is already in use.\r\n


Message:
The requested operation cannot be completed because the terminal connection is currently busy processing a connect, disconnect, reset, or delete operation.\r\n


Message:
An attempt has been made to connect to a session whose video mode is not supported by the current client.\r\n


Message:
The application attempted to enable DOS graphics mode.\r\nDOS graphics mode is not supported.\r\n


Message:
Your interactive logon privilege has been disabled.\r\nPlease contact your administrator.\r\n


Message:
The requested operation can be performed only on the system console.\r\nThis is most often the result of a driver or system DLL requiring direct console access.\r\n


Message:
The client failed to respond to the server connect message.\r\n


Message:
Disconnecting the console session is not supported.\r\n


Message:
Reconnecting a disconnected session to the console is not supported.\r\n


Message:
The request to control another session remotely was denied.\r\n


Message:
The requested session access is denied.\r\n


Message:
The specified terminal connection driver is invalid.\r\n


Message:
The requested session cannot be controlled remotely.\r\nThis may be because the session is disconnected or does not currently have a user logged on. Also, you cannot control a session remotely from the system console or control the system console remotely. And you cannot remote control your own current session.\r\n


Message:
The requested session is not configured to allow remote control.\r\n


Message:
Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user.\r\nPlease call your system administrator to obtain a new copy of the Terminal Server client with a valid, unique license number.\r\n


Message:
Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client.\r\nPlease call your system administrator for help in entering a valid, unique license number for this Terminal Server client.\r\n


Message:
The system has reached its licensed logon limit.\r\nPlease try again later.\r\n


Message:
The client you are using is not licensed to use this system.  Your logon request is denied.\r\n


Message:
The system license has expired.  Your logon request is denied.\r\n


Message:
The file replication service API was called incorrectly.\r\n


Message:
The file replication service cannot be started.\r\n


Message:
The file replication service cannot be stopped.\r\n


Message:
The file replication service API terminated the request.\r\nThe event log may have more information.\r\n


Message:
The file replication service terminated the request.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot be contacted.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot satisfy the request because the user has insufficient privileges.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot satisfy the request because authenticated RPC is not available.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot communicate with the file replication service on the domain controller.\r\nThe event log may have more information.\r\n


Message:
The file replication service on the domain controller cannot communicate with the file replication service on this computer.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot populate the system volume because of an internal error.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot populate the system volume because of an internal timeout.\r\nThe event log may have more information.\r\n


Message:
The file replication service cannot process the request. The system volume is busy with a previous request.\r\n


Message:
The file replication service cannot stop replicating the system volume because of an internal error.\r\nThe event log may have more information.\r\n


Message:
Schema update failed: attribute in must-contain does not exist.\r\n


Message:
Schema update failed: class in aux-class list does not exist or is not an auxiliary class.\r\n


Message:
Schema update failed: class in poss-superiors does not exist.\r\n


Message:
Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules.\r\n


Message:
Schema update failed: Rdn-Att-Id has wrong syntax.\r\n


Message:
Schema deletion failed: class is used as auxiliary class.\r\n


Message:
Schema deletion failed: class is used as sub class.\r\n


Message:
Schema deletion failed: class is used as poss superior.\r\n


Message:
Schema update failed in recalculating validation cache.\r\n


Message:
The tree deletion is not finished.  The request must be made again to continue deleting the tree.\r\n


Message:
The requested delete operation could not be performed.\r\n


Message:
Cannot read the governs class identifier for the schema record.\r\n


Message:
The attribute schema has bad syntax.\r\n


Message:
The attribute could not be removed from the cache.\r\n


Message:
The class could not be removed from the cache.\r\n


Message:
The distinguished name attribute could not be read.\r\n


Message:
The instance type attribute could not be retrieved.\r\n


Message:
The specified naming context is missing a cross reference.\r\n


Message:
A security checking error has occurred.\r\n


Message:
Schema allocation failed. Please check if the machine is running low on memory.\r\n


Message:
Failed to obtain the required syntax for the attribute schema.\r\n


Message:
The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.\r\n


Message:
The replication operation failed because of a schema mismatch between the servers involved.\r\n


Message:
The naming context could not be found.\r\n


Message:
The naming context could not be found in the cache.\r\n


Message:
The child object could not be retrieved.\r\n


Message:
The modification was not permitted for security reasons.\r\n


Message:
The operation cannot replace the hidden record.\r\n


Message:
The attempt to build the hierarchy table failed.\r\n


Message:
The directory configuration parameter is missing from the registry.\r\n


Message:
The attempt to count the address book indices failed.\r\n


Message:
The allocation of the hierarchy table failed.\r\n


Message:
The directory service encountered an internal failure.\r\n


Message:
The directory service encountered an unknown failure.\r\n


Message:
A root object requires a class of 'top'.\r\n


Message:
This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.\r\n


Message:
The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.\r\n


Message:
The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.\r\n


Message:
An invalid parameter was specified for this replication operation.\r\n


Message:
The directory service is too busy to complete the replication operation at this time.\r\n


Message:
The distinguished name specified for this replication operation is invalid.\r\n


Message:
The naming context specified for this replication operation is invalid.\r\n


Message:
The distinguished name specified for this replication operation already exists.\r\n


Message:
The replication system encountered an internal error.\r\n


Message:
The replication operation encountered a database inconsistency.\r\n


Message:
The server specified for this replication operation could not be contacted.\r\n


Message:
The replication operation encountered an object with an invalid instance type.\r\n


Message:
The replication operation failed to allocate memory.\r\n


Message:
The replication operation encountered an error with the mail system.\r\n


Message:
The replication reference information for the target server already exists.\r\n


Message:
The replication reference information for the target server does not exist.\r\n


Message:
The naming context cannot be removed because it is replicated to another server.\r\n


Message:
The replication operation encountered a database error.\r\n


Message:
The naming context is in the process of being removed or is not replicated from the specified server.\r\n


Message:
The requested operation is not supported by this version of the directory service.\r\n


Message:
The replication remote procedure call was cancelled.\r\n


Message:
The source server is currently rejecting replication requests.\r\n


Message:
The destination server is currently rejecting replication requests.\r\n


Message:
The replication operation failed due to a collision of object names.\r\n


Message:
The replication source has been reinstalled.\r\n


Message:
The replication operation failed because a required parent object is missing.\r\n


Message:
The replication operation was preempted.\r\n


Message:
The replication synchronization attempt was abandoned because of a lack of updates.\r\n


Message:
The replication operation was terminated because the system is shutting down.\r\n


Message:
The replication synchronization attempt failed as the destination partial attribute set is not a subset of source partial attribute set.\r\n


Message:
The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.\r\n


Message:
The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.\r\n


Message:
A schema mismatch is detected between the source and the build used during a replica install. The replica cannot be installed.\r\n


Message:
Schema update failed: An attribute with the same link identifier already exists.\r\n


Message:
Name translation: Generic processing error.\r\n


Message:
Name translation: Could not find the name or insufficient right to see name.\r\n


Message:
Name translation: Input name mapped to more than one output name.\r\n


Message:
Name translation: Input name found, but not the associated output format.\r\n


Message:
Name translation: Unable to resolve completely, only the domain was found.\r\n


Message:
Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.\r\n


Message:
Modification of a constructed att is not allowed.\r\n


Message:
The OM-Object-Class specified is incorrect for an attribute with the specified syntax.\r\n


Message:
The replication request has been posted; waiting for reply.\r\n


Message:
The requested operation requires a directory service, and none was available.\r\n


Message:
The LDAP display name of the class or attribute contains non-ASCII characters.\r\n


Message:
The requested search operation is only supported for base searches.\r\n


Message:
The search failed to retrieve attributes from the database.\r\n


Message:
The schema update operation tried to add a backward link attribute that has no corresponding forward link.\r\n


Message:
Source and destination of a cross-domain move do not agree on the object's epoch number.  Either source or destination does not have the latest version of the object.\r\n


Message:
Source and destination of a cross-domain move do not agree on the object's current name.  Either source or destination does not have the latest version of the object.\r\n


Message:
Source and destination for the cross-domain move operation are identical.  Caller should use local move operation instead of cross-domain move operation.\r\n


Message:
Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest.  Either source or destination does not have the latest version of the Partitions container.\r\n


Message:
Destination of a cross-domain move is not authoritative for the destination naming context.\r\n


Message:
Source and destination of a cross-domain move do not agree on the identity of the source object.  Either source or destination does not have the latest version of the source object.\r\n


Message:
Object being moved across-domains is already known to be deleted by the destination server.  The source server does not have the latest version of the source object.\r\n


Message:
Another operation which requires exclusive access to the PDC FSMO is already in progress.\r\n


Message:
A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains.  The destination object needs to be removed to restore the system to a consistent state.\r\n


Message:
This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, eg: trust account or restricted RID, which prevent its move.\r\n


Message:
Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group.  Remove the object from any account group memberships and retry.\r\n


Message:
A naming context head must be the immediate child of another naming context head, not of an interior node.\r\n


Message:
The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context.  Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners.\r\n


Message:
Destination domain must be in native mode.\r\n


Message:
The operation can not be performed because the server does not have an infrastructure container in the domain of interest.\r\n


Message:
Cross-domain move of account groups is not allowed.\r\n


Message:
Cross-domain move of resource groups is not allowed.\r\n


Message:
The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.\r\n


Message:
Tree deletions starting at an object which has an NC head as a descendant are not allowed.\r\n


Message:
The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.\r\n


Message:
The directory service failed to identify the list of objects to delete while attempting a tree deletion.\r\n


Message:
Security Accounts Manager initialization failed because of the following error: %1.\r\nError Status: 0x%2. Click OK to shut down the system and reboot into Directory Services Restore Mode. Check the event log for detailed information.\r\n


Message:
Only an administrator can modify the membership list of an administrative group.\r\n


Message:
Cannot change the primary group ID of a domain controller account.\r\n


Message:
An attempt is made to modify the base schema.\r\n


Message:
An attempt was made to add a new Must-Contain attribute or delete an existing Must-Contain/May-Contain/Poss-Superiors attribute from an existing class (directly or through inheritance, for example, by adding or deleting an auxiliary class).\r\n


Message:
Schema update is not allowed on this DC. Either the registry key is not set or the DC is not the schema FSMO Role Owner.\r\n


Message:
An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.\r\n


Message:
The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.\r\n


Message:
The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.\r\n


Message:
The specified group type is invalid.\r\n


Message:
You cannot nest global groups in a mixed domain if the group is security-enabled.\r\n


Message:
You cannot nest local groups in a mixed domain if the group is security-enabled.\r\n


Message:
A global group cannot have a local group as a member.\r\n


Message:
A global group cannot have a universal group as a member.\r\n


Message:
A universal group cannot have a local group as a member.\r\n


Message:
A global group cannot have a cross-domain member.\r\n


Message:
A local group cannot have another cross domain local group as a member.\r\n


Message:
A group with primary members cannot change to a security-disabled group.\r\n


Message:
The schema cache load failed to convert the string default SD on a class-schema object.\r\n


Message:
Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role.\r\n


Message:
The DSA operation is unable to proceed because of a DNS lookup failure.\r\n


Message:
While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.\r\n


Message:
The Security Descriptor attribute could not be read.\r\n


Message:
The object requested was not found, but an object with that key was found.\r\n


Message:
The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1\r\n


Message:
Security Account Manager needs to get the boot password.\r\n


Message:
Security Account Manager needs to get the boot key from floppy disk.\r\n


Message:
The connection between client and server requires packet privacy or better.\r\n


Message:
The source domain may not be in the same forest as destination.\r\n


Message:
The destination domain must be in the forest.\r\n


Message:
The operation requires that destination domain auditing be enabled.\r\n


Message:
The operation couldn't locate a DC for the source domain.\r\n


Message:
The source object must be a group or user.\r\n


Message:
The source object's SID already exists in destination forest.\r\n


Message:
The source and destination object must be of the same type.\r\n


Message:
Security Accounts Manager initialization failed because of the following error: %1.\r\nError Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information.\r\n


Message:
Schema information could not be included in the replication request.\r\n


Message:
The replication operation could not be completed due to a schema\r\nincompatibility.\r\n


Message:
The replication operation could not be completed due to a previous schema incompatibility.\r\n


Message:
The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.\r\n


Message:
The requested domain could not be deleted because there exist domain controllers that still host this domain.\r\n


Message:
The requested operation can be performed only on a global catalog server.\r\n


Message:
A local group can only be a member of other local groups in the same domain.\r\n


Message:
Foreign security principals cannot be members of universal groups.\r\n


Message:
The attribute is not allowed to be replicated to the GC because of security reasons.\r\n


Message:
The checkpoint with the PDC could not be taken because there too many modifications being processed currently.\r\n


Message:
The operation requires that source domain auditing be enabled.\r\n


Message:
Security principal objects can only be created inside domain naming contexts.\r\n


Message:
A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.\r\n


Message:
A Filter was passed that uses constructed attributes.\r\n


Message:
The unicodePwd attribute value must be enclosed in double quotes.\r\n


Message:
DNS server unable to interpret format.\r\n


Message:
DNS request not supported by name server.\r\n


Message:
DNS name that ought not exist, does exist.\r\n


Message:
DNS RR set that ought not exist, does exist.\r\n


Message:
DNS RR set that ought to exist, does not exist.\r\n


Message:
DNS server not authoritative for zone.\r\n


Message:
DNS name in update or prereq is not in zone.\r\n


Message:
No records found for given DNS query.\r\n


Message:
Record for given name and type is not unique.\r\n


Message:
DNS name does not comply with RFC specifications.\r\n


Message:
DNS name is a fully-qualified DNS name.\r\n


Message:
DNS name contains an invalid character.\r\n


Message:
DNS zone has no start of authority (SOA) record.\r\n


Message:
DNS zone has no Name Server (NS) record.\r\n


Message:
Secondary DNS zone requires master IP address.\r\n


Message:
Invalid delete of start of authority (SOA)\r\n


Message:
Failed to open datafile for DNS zone.\r\n


Message:
Failed to write datafile for DNS zone.\r\n


Message:
Failure while reading datafile for DNS zone.\r\n


Message:
A CNAME record already exists for given name.\r\n


Message:
Could not create pointer (PTR) record.\r\n


Message:
DNS zone already exists in the directory service.\r\n


Message:
DNS server not creating or reading the boot file for the directory service integrated DNS zone.\r\n


Message:
Secure update call needs to continue update request.\r\n


Message:
TCP/IP network protocol not installed.\r\n


Message:
No DNS servers configured for local system.\r\n


Message:
A blocking operation was interrupted by a call to WSACancelBlockingCall.\r\n


Message:
The file handle supplied is not valid.\r\n


Message:
An attempt was made to access a socket in a way forbidden by its access permissions.\r\n


Message:
The system detected an invalid pointer address in attempting to use a pointer argument in a call.\r\n


Message:
A non-blocking socket operation could not be completed immediately.\r\n


Message:
A blocking operation is currently executing.\r\n


Message:
An operation was attempted on a non-blocking socket that already had an operation in progress.\r\n


Message:
An operation was attempted on something that is not a socket.\r\n


Message:
A required address was omitted from an operation on a socket.\r\n


Message:
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.\r\n


Message:
A protocol was specified in the socket function call that does not support the semantics of the socket type requested.\r\n


Message:
An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.\r\n


Message:
The requested protocol has not been configured into the system, or no implementation for it exists.\r\n


Message:
The support for the specified socket type does not exist in this address family.\r\n


Message:
The attempted operation is not supported for the type of object referenced.\r\n


Message:
The protocol family has not been configured into the system or no implementation for it exists.\r\n


Message:
An address incompatible with the requested protocol was used.\r\n


Message:
Only one usage of each socket address (protocol/network address/port)\r\nis normally permitted.\r\n


Message:
The requested address is not valid in its context.\r\n


Message:
A socket operation encountered a dead network.\r\n


Message:
A socket operation was attempted to an unreachable network.\r\n


Message:
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.\r\n


Message:
An established connection was aborted by the software in your host machine.\r\n


Message:
An existing connection was forcibly closed by the remote host.\r\n


Message:
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.\r\n


Message:
A connect request was made on an already connected socket.\r\n


Message:
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.\r\n


Message:
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.\r\n


Message:
Too many references to some kernel object.\r\n


Message:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.\r\n


Message:
No connection could be made because the target machine actively refused it.\r\n


Message:
Name component or name was too long.\r\n


Message:
A socket operation failed because the destination host was down.\r\n


Message:
A socket operation was attempted to an unreachable host.\r\n


Message:
Cannot remove a directory that is not empty.\r\n


Message:
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.\r\n


Message:
File handle reference is no longer available.\r\n


Message:
WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.\r\n


Message:
The Windows Sockets version requested is not supported.\r\n


Message:
Either the application has not called WSAStartup, or WSAStartup failed.\r\n


Message:
Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.\r\n


Message:
No more results can be returned by WSALookupServiceNext.\r\n


Message:
A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.\r\n


Message:
The procedure call table is invalid.\r\n


Message:
The requested service provider is invalid.\r\n


Message:
The requested service provider could not be loaded or initialized.\r\n


Message:
A system call that should never fail has failed.\r\n


Message:
No such service is known. The service cannot be found in the specified name space.\r\n


Message:
A database query failed because it was actively refused.\r\n


Message:
This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.\r\n


Message:
A non-recoverable error occurred during a database lookup.\r\n


Message:
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.\r\n


Message:
Rejected for administrative reasons - bad credentials.\r\n


Message:
Problem with some part of the filterspec or providerspecific buffer in general.\r\n


Message:
Problem with some part of the flowspec.\r\n


Message:
An invalid or unrecognized service type was found in the flowspec.\r\n


Message:
An invalid or inconsistent flowspec was found in the QOS structure.\r\n


Message:
An invalid QOS filter style was used.\r\n


Message:
An invalid QOS filter type was used.\r\n


Message:
An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR.\r\n


Message:
An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer.\r\n


Message:
An incorrect number of flow descriptors was specified in the QOS structure.\r\n


Message:
An unrecognized object was found in the QOS provider-specific buffer.\r\n


Message:
An invalid policy object was found in the QOS provider-specific buffer.\r\n


Message:
An invalid QOS flow descriptor was found in the flow descriptor list.\r\n


Message:
An invalid or inconsistent flowspec was found in the QOS provider specific buffer.\r\n


Message:
An invalid FILTERSPEC was found in the QOS provider-specific buffer.\r\n


Message:
An invalid shape discard mode object was found in the QOS provider specific buffer.\r\n


Message:
An invalid shaping rate object was found in the QOS provider-specific buffer.\r\n


Message:
A reserved policy element was found in the QOS provider-specific buffer.\r\n


Message:
The underlying file was converted to compound file format.\r\n


Message:
The storage operation should block until more data is available.\r\n


Message:
The storage operation should retry immediately.\r\n


Message:
The notified event sink will not influence the storage operation.\r\n


Message:
Multiple opens prevent consolidated. (commit succeeded).\r\n


Message:
Consolidation of the storage file failed. (commit succeeded).\r\n


Message:
Consolidation of the storage file is inappropriate. (commit succeeded).\r\n


Message:
Use the registry database to provide the requested information\r\n


Message:
Verb number is valid but verb cannot be done now\r\n


Message:
Message is too long; some of it had to be truncated before displaying\r\n


Message:
Unable to convert OLESTREAM to IStorage\r\n


Message:
Moniker is already registered in running object table\r\n


Message:
An event was able to invoke some but not all of the subscribers\r\n


Message:
An event was delivered but there were no subscribers\r\n


Message:
The task is ready to run at its next scheduled time.\r\n


Message:
The task will not run at the scheduled times because it has been disabled.\r\n


Message:
There are no more runs scheduled for this task.\r\n


Message:
One or more of the properties that are needed to run this task on a schedule have not been set.\r\n


Message:
The last run of the task was terminated by the user.\r\n


Message:
Either the task has no triggers or the existing triggers are disabled or not set.\r\n


Message:
Event triggers don't have set run times.\r\n


Message:
Not all the requested interfaces were available\r\n


Message:
The function completed successfully, but must be called again to complete the context\r\n


Message:
The function completed successfully, but CompleteToken must be called\r\n


Message:
The function completed successfully, but both CompleteToken and this function must be called to complete the context\r\n


Message:
The logon was completed, but no network authority was available. The logon was made using locally known information\r\n


Message:
The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context.\r\n


Message:
The context data must be renegotiated with the peer.\r\n


Message:
There is no LSA mode context associated with this context.\r\n


Message:
The data necessary to complete this operation is not yet available.\r\n


Message:
Cannot set thread local storage channel control\r\n


Message:
Could not allocate thread local storage channel control\r\n


Message:
The user supplied memory allocator is unacceptable\r\n


Message:
The rowset was using optimistic concurrency and the value of a\r\ncolumn has been changed since it was last read\r\n


Message:
Errors were detected during the copy\r\n


Message:
A column ID was occurred more than once in the specification\r\n


Message:
The specified locale ID was not supported\r\n


Message:
The specified record number is invalid\r\n


Message:
Although the bookmark was validly formed, no row could be found to\r\nmatch it\r\n


Message:
By-ref accessors are not supported by this provider\r\n


Message:
Null accessors are not supported by this provider\r\n


Message:
The specified accessor was not a parameter accessor\r\n


Message:
The change was canceled during notification; no columns are changed\r\n


Message:
The rowset was single-chaptered and the chapter was not released\r\n


Message:
The provider cannot derive parameter info and SetParameterInfo has\r\nnot been called\r\n


Message:
The data source object is already initialized\r\n


Message:
The provider does not support this method\r\n


Message:
The system failed to update and remove host (A) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe system could not remove these A RRs because the update request timed\r\nout while awaiting a response from the DNS server. This is probably because\r\nthe DNS server authoritative for the zone where these RRs need to be updated\r\nis either not currently running or reachable on the network.\r\n


Message:
The system failed to update and remove host (A) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe system could not remove these A RRs because the DNS server failed the\r\nupdate request. A possible cause is that a zone transfer is in progress,\r\ncausing a lock for the zone at the DNS server authorized to perform the\r\nupdates for these RRs.\r\n


Message:
The system failed to update and remove host (A) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason for this failure is because the DNS server sent the update\r\neither (a) does not support the DNS dynamic update protocol, or (b) the\r\nauthoritative zone for the DNS domain name specified in these A RRs does\r\nnot currently accept DNS dynamic updates.\r\n


Message:
The system failed to update and remove host (A) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe request to remove these records failed because the DNS server refused\r\nthe update request. The cause of this might be that either (a) this\r\ncomputer is not allowed to update the DNS domain name specified by these\r\nsettings, or (b) because the DNS server authorized to perform updates for\r\nthe zone that contains these RRs does not support the DNS dynamic update\r\nprotocol.\r\n


Message:
The system failed to update and remove host (A) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason for this failure was because of a security related problem.\r\nThe cause of this could be that (a) your computer does not have permissions\r\nto remove and update the specific DNS domain name or IP addresses\r\nconfigured for this adapter, or (b) there might have been a problem\r\nnegotiating valid credentials with the DNS server during the processing of\r\nthe update request. For specific error code, click the Record Data tab.\r\n


Message:
The system failed to update and remove host (A) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the update request failed was because of a system problem.\r\nFor specific error code, click the Record Data tab.\r\n


Message:
The binary MOF in the resource named %1 in the image file %2 is not valid.\r\n


Message:
The binary MOF in the resource named %1 in the image file %2 could not be loaded.\r\n


Message:
The registration information for the image file %1 is not valid.\r\n


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


Message:
An event was fired specifying a static instance name that could not be resolved.\r\n


Message:
An error occured while attempting to query for the event data referenced by a fired event.\r\n


Message:
The Distributed Link Tracking volume ID quota on this machine has been exceeded.  As a result, it is not possible to create new volume IDs.  Distributed Link Tracking normally uses these volume IDs to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.\r\n


Message:
The move table quota for Distributed Link Tracking in this domain has been exceeded.  This table is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.  While this quota is exceeded, it may not be possible to automatically repair some such broken links.\r\n


Message:
The File Replication Service is having trouble enabling replication\r\nfrom %1 to %2 for %3; retrying.\r\n


Message:
The server failed to start. Either all three chdev\r\nparameters must be zero or all three must be nonzero.\r\n


Message:
A remote API request was halted due to the following\r\ninvalid description string: %1.\r\n


Message:
The network %1 ran out of network control blocks (NCBs).  You may need to increase NCBs\r\nfor this network.  The following information includes the\r\nnumber of NCBs submitted by the server when this error occurred:\r\n


Message:
The server cannot create the %1 mailslot needed to send\r\nthe ReleaseMemory alert message.  The error received is:\r\n


Message:
The server failed to register for the ReleaseMemory alert,\r\nwith recipient %1. The error code from\r\nNetAlertStart is the data.\r\n


Message:
The server cannot update the AT schedule file. The file\r\nis corrupted.\r\n


Message:
The server encountered an error when calling\r\nNetIMakeLMFileName. The error code is the data.\r\n


Message:
Initialization failed because of a system execution failure on\r\npath %1. There is not enough memory to start the process.\r\nThe system error code is the data.\r\n


Message:
Longterm lock of the server buffers failed.\r\nCheck swap disk's free space and restart the system to start the server.\r\n


Message:
The service has stopped due to repeated consecutive\r\noccurrences of a network control block (NCB) error.  The last bad NCB follows\r\nin raw data.\r\n


Message:
The Message server has stopped due to a lock on the\r\nMessage server shared data segment.\r\n


Message:
A file system error occurred while opening or writing to the\r\nsystem message log file %1. Message logging has been\r\nswitched off due to the error. The error code is the data.\r\n


Message:
Unable to display message POPUP due to system VIO call error.\r\nThe error code is the data.\r\n


Message:
An illegal server message block (SMB) was received.  The SMB is the data.\r\n


Message:
The workstation information segment is bigger than 64K.\r\nThe size follows, in DWORD format:\r\n


Message:
The workstation was unable to get the name-number of the computer.\r\n


Message:
The workstation could not initialize the Async NetBIOS Thread.\r\nThe error code is the data.\r\n


Message:
The workstation could not open the initial shared segment.\r\nThe error code is the data.\r\n


Message:
A bad mailslot server message block (SMB) was received.  The SMB is the data.\r\n


Message:
The workstation encountered an error while trying to start the user accounts database.\r\nThe error code is the data.\r\n


Message:
A Macintosh workstation has submitted a job using a version of the\r\nLaserWriter driver that is not supported. This workstation should\r\nbe upgraded to Apple system software version 7.5.1 or above.\r\n


Message:
A Macintosh workstation submitted a job with Adobe Document Structuring\r\nConvention (newer than v2.0) comments that could not be processed.  \r\nThe job from %1 was canceled.\r\n


Message:
An internal error occurred while MacPrint service was trying to log an event. \r\nThe error returned was: %1\r\n


Message:
The TrueImage Interpreter was unable to reset page-level information, such\r\nas paper size or number of copies. The job printing may not be correct.\r\nThe error code returned from the system was %1.\r\n


Message:
The TrueImage Interpreter was unable to set its priority correctly.\r\nThe error code returned from the system was %1.\r\n


Message:
Unable to allocate a system resource required for the MacPrint Service.\r\n


Message:
The MacPrint service could not register with the Windows 2000 Service Controller.\r\nMacPrint service will be stopped.\r\n


Message:
The MacPrint Service does not have access to the Registry.\r\nUse the Registry Editor to ensure that the MacPrint account has full\r\naccess to the MacPrint service key and all its subkeys.\r\n


Message:
The MacPrint Service was unable to access its Registry key (SYSTEM\\CurrentControlSet\\Services\\MacPrint\\Parameters).\r\nMacPrint service was started without using registry parameters.\r\n


Message:
Unable to allocate memory.  Use the System icon in Control Panel\r\nto increase the size of the Windows 2000 virtual memory specified in the \r\nPerformance options.\r\n


Message:
Unable to create or open the file %1.\r\n


Message:
The Windows 2000 Print System is not responding.\r\nMacPrint Service is stopping.\r\n


Message:
Not used\r\nAn error occurred on the AppleTalk network, which made a Windows 2000\r\nprinter no longer available to Macintosh users. Try stopping and \r\nrestarting the Appletalk service.\r\n


Message:
The TrueImage Interpreter initialization failed.\r\n(Document Name: %1)\r\nProcessing continued\r\n


Message:
TrueImage Interpreter - internal error occurred during job processing. \r\nThe job will not print.\r\n(Document Name: %1)\r\n


Message:
TrueImage Interpreter - internal error occurred during string processing. \r\nThe job will not print.\r\n(Document Name: %1)\r\n


Message:
A TrueImage Interpreter frame buffer memory allocation failed.\r\n(Document Name: %1)\r\n


Message:
A TrueImage Interpreter error occurred for which no error string is defined.\r\n(Document Name: %1), Error Code: %2\r\n


Message:
The WINS server has started a consistency check operation.\r\n


Message:
The WINS server has completed the consistency check operation.\r\n


Message:
Adminstrator '%1' has initiated the delete owner function of the WINS \r\npartner, %2.\r\n


Message:
The WINS server has initiated the delete owner function of the WINS partner, %2.\r\n


Message:
The WINS server has completed the delete owner function of the WINS partner, %2.


Message:
WINS adjusted the scavenging related time interval, %1, so that it is compatible with the replication time intervals. The adjusted value for this scavenging parameter is given in the data section (second DWORD). This value was computed by WINS using an algorithm that may use the maximum replication time interval specified. The current value achieves a good balance between consistency of databases across the network of WINS servers and the performance of the WINS servers.


Message:
WINS adjusted the scavenging related time interval, %1. The adjusted value for this scavenging parameter is given in the data section (second DWORD). This value was computed by WINS using an algorithm that tries to achieve a good balance between consistency of databases across the network of WINS servers and the performance of the WINS servers.


Message:
The timeout period has expired on a call to another WINS server. Assuming that the network and routers are working properly, either the remote WINS server is overloaded, or its TCP listener thread has terminated.


Message:
***The Scavenger thread found active replicas that needed to be verified with the owner WINS server since they were older than the verify time interval. The
table of owner-to-address mappings indicated the WINS was not active.


Message:
The name registration packet that was just received has too many addresses. The maximum number of addresses for a multi-homed client is 25. The number of addresses found in the packet is given in the data section.


Message:
A replica clashed with the static record, %1, in the WINS database. The replica was rejected.


Message:
WINS could not initialize the administrator interface because of a problem with the Remote Procedure Call (RPC) service. You may not be able to administer WINS. Make sure that the RPC service is running.


Message:
WINS did not send a notification message to the WINS server whose address is given in the data section. There were a number of communications failures with that server in the past few minutes.


Message:
WINS received a release for the non-owned name, %1. This name is owned by the WINS whose owner ID is given in the data section. Run winscl.exe to get the owner ID to address mapping.


Message:
The administrator deleted a record with the name, %1.


Message:
WINS could not start because of a database error. WINS restored the old database from the backup directory and will come up using this database.


Message:
A non-zero replication type applies for this partner. This means only a subset of records will be replicated between the local WINS and this partner. If later you want to get records that did not replicate, you can either pull 
them using winscl.exe in the Windows 2000 Resource Kit, or delete all owners acquired only through this partner and initiate replication after that to reacquire all their records. The partner's address is given in the second DWORD 
of the data section.


Message:
***A partner has requested only a subset of records. This means we won't replicate all the records in the range requested.  Check the partner's
registry to see what replication type applies to it. The partner's address is
given in the second DWORD of the data section.


Message:
The OLE service mutex already exists\r\n


Message:
The OLE service file mapping already exists\r\n


Message:
Unable to map view of file for OLE service\r\n


Message:
Failure attempting to launch OLE service\r\n


Message:
There was an attempt to call CoInitialize a second time while single threaded\r\n


Message:
A Remote activation was necessary but was not allowed\r\n


Message:
The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call.\r\n


Message:
It is illegal to call out while inside message filter.\r\n


Message:
The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid.\r\n


Message:
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed.\r\n


Message:
The caller (client) disappeared while the callee (server) was processing a call.\r\n


Message:
The data packet with the marshalled parameter data is incorrect.\r\n


Message:
The call was not transmitted properly; the message queue was full and was not emptied after yielding.\r\n


Message:
The client (caller) cannot marshall the parameter data - low memory, etc.\r\n


Message:
The client (caller) cannot unmarshall the return data - low memory, etc.\r\n


Message:
The server (callee) cannot marshall the return data - low memory, etc.\r\n


Message:
The server (callee) cannot unmarshall the parameter data - low memory, etc.\r\n


Message:
Received data is invalid; could be server or client data.\r\n


Message:
A particular parameter is invalid and cannot be (un)marshalled.\r\n


Message:
There is no second outgoing call on same channel in DDE conversation.\r\n


Message:
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute.\r\n


Message:
Could not allocate some required resource (memory, events, ...)\r\n


Message:
Attempted to make calls on more than one thread in single threaded mode.\r\n


Message:
The requested interface is not registered on the server object.\r\n


Message:
RPC could not call the server or could not return the results of calling the server.\r\n


Message:
Cannot change thread mode after it is set.\r\n


Message:
The method called does not exist on the server.\r\n


Message:
Unable to open the access token of the server process\r\n


Message:
Unable to decode the ACL in the stream provided by the user\r\n


Message:
The COM IAccessControl object is not initialized\r\n


Message:
Field name not defined in the record.\r\n


Message:
Invalid forward reference, or reference to uncompiled type.\r\n


Message:
Function not defined in specified DLL.\r\n


Message:
Wrong module kind for the operation.\r\n


Message:
Duplicate ID in inheritance hierarchy.\r\n


Message:
Incorrect inheritance depth in standard OLE hmember.\r\n


Message:
Unable to perform requested operation.\r\n


Message:
There are insufficient resources to open another file.\r\n


Message:
Attempted an operation on an invalid object.\r\n


Message:
There is insufficient memory available to complete operation.\r\n


Message:
There are no more entries to return.\r\n


Message:
An error occurred during a seek operation.\r\n


Message:
A disk error occurred during a write operation.\r\n


Message:
A disk error occurred during a read operation.\r\n


Message:
There is insufficient disk space to complete operation.\r\n


Message:
Illegal write of non-simple property to simple property set.\r\n


Message:
The file %1 is not a valid compound file.\r\n


Message:
Attempted to use an object that is busy.\r\n


Message:
The storage has been changed since the last commit.\r\n


Message:
Attempted to use an object that has ceased to exist.\r\n


Message:
The compound file %1 was produced with an incompatible version of storage.\r\n


Message:
The compound file %1 was produced with a newer version of storage.\r\n


Message:
Share.exe or equivalent is required for operation.\r\n


Message:
Illegal operation called on non-file based storage.\r\n


Message:
Illegal operation called on object with extant marshallings.\r\n


Message:
OLE32.DLL has been loaded at the wrong address.\r\n


Message:
The compound file is too large for the current implementation\r\n


Message:
The compound file was not created with the STGM_SIMPLE flag\r\n


Message:
The file download was aborted abnormally.  The file is incomplete.\r\n


Message:
The file download has been terminated.\r\n


Message:
Can't enumerate any more, because the associated data is missing\r\n


Message:
This implementation doesn't take advises\r\n


Message:
There is no connection for this connection ID\r\n


Message:
Need to run the object to perform this operation\r\n


Message:
Linked object's source class has changed\r\n


Message:
Not able to get the moniker of the object\r\n


Message:
Object is static; operation not allowed\r\n


Message:
compobj.dll is too old for the ole2.dll initialized\r\n


Message:
Object is not in any of the inplace active states\r\n


Message:
Not able to perform the operation because object is not given storage yet\r\n


Message:
tdSize parameter of the DVTARGETDEVICE structure is invalid\r\n


Message:
Object doesn't support IViewObject interface\r\n


Message:
Trying to revoke a drop target that has not been registered\r\n


Message:
This window has already been registered as a drop target\r\n


Message:
Class does not support aggregation (or class object is remote)\r\n


Message:
ClassFactory cannot supply requested class\r\n


Message:
Could not find the key in the registry\r\n


Message:
No package in the software installation data in the Active Directory meets this criteria.\r\n


Message:
Deleting this will break the referential integrity of the software installation data in the Active Directory.\r\n


Message:
The CLSID was not found in the software installation data in the Active Directory.\r\n


Message:
The software installation data in the Active Directory is corrupt.\r\n


Message:
There is no software installation data in the Active Directory.\r\n


Message:
There is no software installation data object in the Active Directory.\r\n


Message:
The software installation data object in the Active Directory already exists.\r\n


Message:
The path to the software installation data in the Active Directory is not correct.\r\n


Message:
A network error interrupted the operation.\r\n


Message:
The size of this object exceeds the maximum size set by the Administrator.\r\n


Message:
The schema for the software installation data in the Active Directory does not match the required schema.\r\n


Message:
An error occurred in the software installation data in the Active Directory.\r\n


Message:
Contents of the OLESTREAM not in correct format\r\n


Message:
There was an error in a Windows GDI call while converting the bitmap to a DIB\r\n


Message:
Contents of the IStorage not in correct format\r\n


Message:
Contents of IStorage is missing one of the standard streams\r\n


Message:
There was an error in a Windows GDI call while converting the DIB to a bitmap.\r\n\r\n


Message:
Moniker needs to be connected manually\r\n


Message:
User input required for operation to succeed\r\n


Message:
CoInitialize has already been called.\r\n


Message:
Class of object cannot be determined\r\n


Message:
Application cannot be run more than once\r\n


Message:
The Task Scheduler service must be configured to run in the System account to function properly.  Individual tasks may be configured to run in other accounts.\r\n


Message:
The root transaction wanted to commit, but transaction aborted\r\n


Message:
You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting.\r\n


Message:
The component is configured to use synchronization and a thread has timed out waiting to enter the context.\r\n


Message:
You made a method call on a COM+ component that has a transaction that has already committed or aborted.\r\n


Message:
The specified role was not configured for the application\r\n


Message:
COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator\r\n


Message:
An unexpected error occurred during COM+ Activation.\r\n


Message:
COM+ Activation failed. Check the event log for more information\r\n


Message:
COM+ Activation failed due to a catalog or configuration error.\r\n


Message:
COM+ activation failed because the activation could not be completed in the specified amount of time.\r\n


Message:
COM+ Activation failed because an initialization function failed.  Check the event log for more information.\r\n


Message:
The requested operation requires that JIT be in the current context and it is not\r\n


Message:
The requested operation requires that the current context have a Transaction, and it does not\r\n


Message:
The components threading model has changed after install into a COM+ Application.  Please re-install component.\r\n


Message:
Attempt to create a class object failed\r\n


Message:
RPC communication failed with OLE service\r\n


Message:
OLE service could not communicate with the object server\r\n


Message:
Moniker path could not be normalized\r\n


Message:
Object server is stopping when OLE service contacts it\r\n


Message:
An invalid root block pointer was specified\r\n


Message:
An allocation chain contained an invalid link pointer\r\n


Message:
The requested allocation size was too large\r\n


Message:
Key not valid for use in specified state.\r\n


Message:
Hash not valid for use in specified state.\r\n


Message:
Insufficient memory available for the operation.\r\n


Message:
Provider type as registered is invalid.\r\n


Message:
Provider type does not match registered value.\r\n


Message:
The digital signature file is corrupt.\r\n


Message:
Provider DLL failed to initialize correctly.\r\n


Message:
Provider could not perform the action since the context was acquired as silent.\r\n


Message:
The security token does not have storage space available for an additional container.\r\n


Message:
The profile for the user is a temporary profile.\r\n


Message:
The key parameters could not be set because the CSP uses fixed parameters.\r\n


Message:
Not enough memory is available to complete this request\r\n


Message:
The function requested is not supported\r\n


Message:
The specified target is unknown or unreachable\r\n


Message:
The Local Security Authority cannot be contacted\r\n


Message:
The requested security package does not exist\r\n


Message:
The caller is not the owner of the desired credentials\r\n


Message:
The security package failed to initialize, and cannot be installed\r\n


Message:
The token supplied to the function is invalid\r\n


Message:
The security package is not able to marshall the logon buffer, so the logon attempt has failed\r\n


Message:
The per-message Quality of Protection is not supported by the security package\r\n


Message:
The security context does not allow impersonation of the client\r\n


Message:
The credentials supplied to the package were not recognized\r\n


Message:
No credentials are available in the security package\r\n


Message:
The message or signature supplied for verification has been altered\r\n


Message:
The message supplied for verification is out of sequence\r\n


Message:
No authority could be contacted for authentication.\r\n


Message:
The context has expired and can no longer be used.\r\n


Message:
The supplied message is incomplete.  The signature was not verified.\r\n


Message:
The credentials supplied were not complete, and could not be verified. The context could not be initialized.\r\n


Message:
The buffers supplied to a function was too small.\r\n


Message:
The target principal name is incorrect.\r\n


Message:
The clocks on the client and server machines are skewed.\r\n


Message:
The certificate chain was issued by an untrusted authority.\r\n


Message:
The message received was unexpected or badly formatted.\r\n


Message:
An unknown error occurred while processing the certificate.\r\n


Message:
The received certificate has expired.\r\n


Message:
The specified data could not be encrypted.\r\n


Message:
The specified data could not be decrypted.\r\n\r\n


Message:
The client and server cannot communicate, because they do not possess a common algorithm.\r\n


Message:
The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation).\r\n


Message:
An error occurred while performing an operation on a cryptographic message.\r\n


Message:
The object identifier is poorly formatted.\r\n


Message:
The cryptographic message does not contain an expected authenticated attribute.\r\n


Message:
The content of the cryptographic message has already been decrypted.\r\n


Message:
The content of the cryptographic message has not been decrypted yet.\r\n


Message:
The enveloped-data message does not contain the specified recipient.\r\n


Message:
Invalid issuer and/or serial number.\r\n


Message:
The cryptographic message does not contain all of the requested attributes.\r\n


Message:
The streamed cryptographic message is not ready to return data.\r\n


Message:
The streamed cryptographic message requires more data to complete the decode operation.\r\n


Message:
The length specified for the output data was insufficient.\r\n


Message:
An error occurred during encode or decode operation.\r\n


Message:
An error occurred while reading or writing to a file.\r\n


Message:
The object or property already exists.\r\n


Message:
No provider was specified for the store or object.\r\n


Message:
The specified certificate is self signed.\r\n


Message:
Since the server was offline, the called function was unable to complete the usage check.\r\n


Message:
The subject was not found in a Certificate Trust List (CTL).\r\n


Message:
None of the signers of the cryptographic message or certificate trust list is trusted.\r\n


Message:
The public key's algorithm parameters are missing.\r\n


Message:
OSS Certificate encode/decode error code base\r\n\r\nSee asn1code.h for a definition of the OSS runtime errors. The OSS\r\nerror values are offset by CRYPT_E_OSS_ERROR.\r\n


Message:
OSS ASN.1 Error: Output Buffer is too small.\r\n


Message:
OSS ASN.1 Error: Signed integer is encoded as a unsigned integer.\r\n


Message:
OSS ASN.1 Error: Unknown ASN.1 data type.\r\n


Message:
OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated.\r\n


Message:
OSS ASN.1 Error: Encode/Decode version mismatch.\r\n


Message:
OSS ASN.1 Error: Encode/Decode Error.\r\n


Message:
OSS ASN.1 Error: Unsupported BER indefinite-length encoding.\r\n


Message:
Failed on a file operation (open, map, read, write).\r\n


Message:
A call to a CryptoAPI function failed.\r\n


Message:
There is a bad version number in the file.\r\n


Message:
The structure of the DSIG table is incorrect.\r\n


Message:
A check failed in a partially constant table.\r\n


Message:
The trust verification action specified is not supported by the specified trust provider.\r\n


Message:
The form specified for the subject is not one supported or known by the specified trust provider.\r\n


Message:
The subject is not trusted for the specified action.\r\n


Message:
Error due to problem in ASN.1 encoding process.\r\n


Message:
Error due to problem in ASN.1 decoding process.\r\n


Message:
Reading / writing Extensions where Attributes are appropriate, and visa versa.\r\n


Message:
The size of the data could not be determined.\r\n


Message:
The size of the indefinite-sized data could not be determined.\r\n


Message:
This object does not read and write self-sizing data.\r\n


Message:
No signature was present in the subject.\r\n


Message:
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.\r\n


Message:
The validity periods of the certification chain do not nest correctly.\r\n


Message:
A certificate that can only be used as an end-entity is being used as a CA or visa versa.\r\n


Message:
A path length constraint in the certification chain has been violated.\r\n


Message:
A certificate contains an unknown extension that is marked 'critical'.\r\n


Message:
A certificate being used for a purpose other than the ones specified by its CA.\r\n


Message:
A parent of a given certificate in fact did not issue that child certificate.\r\n


Message:
A certificate is missing or has an empty value for an important field, such as a subject or issuer name.\r\n


Message:
A certificate chain processed correctly, but terminated in a root certificate which is not trusted by the trust provider.\r\n


Message:
An internal certificate chaining error has occurred.\r\n


Message:
A certificate was explicitly revoked by its issuer.\r\n


Message:
The certification path terminates with the test root which is not trusted with the current policy settings.\r\n


Message:
The revocation process could not continue - the certificate(s) could not be checked.\r\n


Message:
The certificate's CN name does not match the passed value.\r\n


Message:
The certificate is not valid for the requested usage.\r\n


Message:
The certificate was explicitly marked as untrusted by the user.\r\n


Message:
A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.\r\n


Message:
A non-empty line was encountered in the INF before the start of a section.\r\n


Message:
A section name marker in the INF is not complete, or does not exist on a line by itself.\r\n


Message:
An INF section was encountered whose name exceeds the maximum section name length.\r\n


Message:
The style of the INF is different than what was requested.\r\n


Message:
The required section was not found in the INF.\r\n


Message:
The required line was not found in the INF.\r\n


Message:
The files affected by the installation of this file queue have not been backed up for uninstall.\r\n


Message:
The INF or the device information set or element does not have an associated install class.\r\n


Message:
The INF or the device information set or element does not match the specified install class.\r\n


Message:
An existing device was found that is a duplicate of the device being manually installed.\r\n


Message:
There is no driver selected for the device information set or element.\r\n


Message:
The requested device registry key does not exist.\r\n


Message:
The device instance name is invalid.\r\n


Message:
The install class is not present or is invalid.\r\n


Message:
The device instance cannot be created because it already exists.\r\n


Message:
The operation cannot be performed on a device information element that has not been registered.\r\n


Message:
The device property code is invalid.\r\n


Message:
The INF from which a driver list is to be built does not exist.\r\n


Message:
The device instance does not exist in the hardware tree.\r\n


Message:
The icon representing this install class cannot be loaded.\r\n


Message:
The class installer registry entry is invalid.\r\n


Message:
The class installer has indicated that the default action should be performed for this installation request.\r\n


Message:
The operation does not require any files to be copied.\r\n


Message:
The specified hardware profile does not exist.\r\n


Message:
There is no device information element currently selected for this device information set.\r\n


Message:
The operation cannot be performed because the device information set is locked.\r\n


Message:
The operation cannot be performed because the device information element is locked.\r\n


Message:
The specified path does not contain any applicable device INFs.\r\n


Message:
No class installer parameters have been set for the device information set or element.\r\n


Message:
The operation cannot be performed because the file queue is locked.\r\n


Message:
A service installation section in this INF is invalid.\r\n


Message:
There is no class driver list for the device information element.\r\n


Message:
The installation failed because a function driver was not specified for this device instance.\r\n


Message:
There is presently no default device interface designated for this interface class.\r\n


Message:
The operation cannot be performed because the device interface is currently active.\r\n


Message:
The operation cannot be performed because the device interface has been removed from the system.\r\n


Message:
An interface installation section in this INF is invalid.\r\n


Message:
This interface class does not exist in the system.\r\n


Message:
The reference string supplied for this interface device is invalid.\r\n


Message:
The specified machine name does not conform to UNC naming conventions.\r\n


Message:
A general remote communication error occurred.\r\n


Message:
The machine selected for remote communication is not available at this time.\r\n


Message:
The Plug and Play service is not available on the remote machine.\r\n


Message:
The property page provider registry entry is invalid.\r\n


Message:
The requested device interface is not present in the system.\r\n


Message:
The device's co-installer has additional work to perform after installation is complete.\r\n


Message:
The device's co-installer is invalid.\r\n


Message:
There are no compatible drivers for this device.\r\n


Message:
There is no icon that represents this device or device type.\r\n


Message:
A logical configuration specified in this INF is invalid.\r\n


Message:
The class installer has denied the request to install or upgrade this device.\r\n


Message:
One of the filter drivers installed for this device is invalid.\r\n


Message:
The driver selected for this device does not support Windows 2000.\r\n


Message:
The driver selected for this device does not support Windows.\r\n


Message:
The third-party INF does not contain digital signature information.\r\n


Message:
An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms.\r\n


Message:
The device could not be dynamically removed.\r\n


Message:
No installed components were detected.\r\n


Message:
An internal consistency check failed.\r\n


Message:
The action was cancelled by an SCardCancel request.\r\n


Message:
One or more of the supplied parameters could not be properly interpreted.\r\n


Message:
Registry startup information is missing or invalid.\r\n


Message:
Not enough memory available to complete this command.\r\n


Message:
An internal consistency timer has expired.\r\n


Message:
The data buffer to receive returned data is too small for the returned data.\r\n


Message:
The specified reader name is not recognized.\r\n


Message:
The user-specified timeout value has expired.\r\n


Message:
The smart card cannot be accessed because of other connections outstanding.\r\n


Message:
The operation requires a Smart Card, but no Smart Card is currently in the device.\r\n


Message:
The specified smart card name is not recognized.\r\n


Message:
The system could not dispose of the media in the requested manner.\r\n


Message:
The requested protocols are incompatible with the protocol currently in use with the smart card.\r\n


Message:
The reader or smart card is not ready to accept commands.\r\n


Message:
One or more of the supplied parameters values could not be properly interpreted.\r\n


Message:
The action was cancelled by the system, presumably to log off or shut down.\r\n


Message:
An internal communications error has been detected.\r\n


Message:
An internal error has been detected, but the source is unknown.\r\n


Message:
An ATR obtained from the registry is not a valid ATR string.\r\n


Message:
An attempt was made to end a non-existent transaction.\r\n


Message:
The specified reader is not currently available for use.\r\n


Message:
The operation has been aborted to allow the server application to exit.\r\n


Message:
The PCI Receive buffer was too small.\r\n


Message:
The reader driver does not meet minimal requirements for support.\r\n


Message:
The reader driver did not produce a unique reader name.\r\n


Message:
The smart card does not meet minimal requirements for support.\r\n


Message:
The Smart card resource manager is not running.\r\n


Message:
The Smart card resource manager has shut down.\r\n


Message:
An unexpected card error has occurred.\r\n


Message:
No Primary Provider can be found for the smart card.\r\n


Message:
The requested order of object creation is not supported.\r\n


Message:
This smart card does not support the requested feature.\r\n


Message:
The identified directory does not exist in the smart card.\r\n


Message:
The identified file does not exist in the smart card.\r\n


Message:
The supplied path does not represent a smart card directory.\r\n


Message:
The supplied path does not represent a smart card file.\r\n


Message:
An attempt was made to write more data than would fit in the target object.\r\n


Message:
There was an error trying to set the smart card file object pointer.\r\n


Message:
An unrecognized error code was returned from a layered component.\r\n


Message:
The requested certificate does not exist.\r\n


Message:
The requested certificate could not be obtained.\r\n


Message:
A communications error with the smart card has been detected.  Retry the operation.\r\n


Message:
The reader cannot communicate with the smart card, due to ATR configuration conflicts.\r\n


Message:
The smart card is not responding to a reset.\r\n


Message:
Power has been removed from the smart card, so that further communication is not possible.\r\n


Message:
The smart card has been reset, so any shared state information is invalid.\r\n


Message:
The smart card has been removed, so that further communication is not possible.\r\n


Message:
Access was denied because of a security violation.\r\n


Message:
The card cannot be accessed because the wrong PIN was presented.\r\n


Message:
The card cannot be accessed because the maximum number of PIN entry attempts has been reached.\r\n


Message:
The end of the smart card file has been reached.\r\n


Message:
The action was cancelled by the user.\r\n


Message:
Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail\r\n


Message:
One or more of the object's properties are missing or invalid\r\n


Message:
The object was not found in the catalog\r\n


Message:
Error occurred writing to the application file\r\n


Message:
Error occurred reading the application file\r\n


Message:
Invalid version number in application file\r\n


Message:
The application is already installed\r\n


Message:
One or more users in the application file are not valid\r\n


Message:
The component's CLSID is missing or corrupt\r\n


Message:
The component's progID is missing or corrupt\r\n


Message:
Unable to set required authentication level for update request\r\n


Message:
The identity or password set on the application is not valid\r\n


Message:
Application file CLSIDs or IIDs do not match corresponding DLLs\r\n


Message:
Interface information is either missing or changed\r\n


Message:
DllRegisterServer failed on component install\r\n


Message:
The registered TypeLib ID is not valid\r\n


Message:
Application install directory not found\r\n


Message:
Errors occurred while in the component registrar\r\n


Message:
The DLL does not support the components listed in the TypeLib\r\n


Message:
The file does not contain components or component information\r\n


Message:
Changes to this object and its sub-objects have been disabled\r\n


Message:
The delete function has been disabled for this object\r\n


Message:
The server catalog version is not supported\r\n


Message:
The component move was disallowed, because the source or destination application is either a system application or currently locked against changes\r\n


Message:
The component move failed because the destination application no longer exists\r\n


Message:
The system was unable to register the TypeLib\r\n


Message:
This operation can not be performed on the system application\r\n


Message:
The component registrar referenced in this file is not available\r\n


Message:
A component in the same DLL is already installed\r\n


Message:
One or more property settings are either invalid or in conflict with each other\r\n


Message:
The object you are attempting to add or rename already exists\r\n


Message:
A CLSID with the same GUID as the new application ID is already installed on this machine\r\n


Message:
A role assigned to a component, interface, or method did not exist in the application\r\n


Message:
You must have components in an application in order to start the application\r\n


Message:
This operation is not enabled on this platform\r\n


Message:
Failed to start application because it is either a library application or an application proxy\r\n


Message:
System application is not exportable\r\n


Message:
Can not subscribe to this component (the component may have been imported)\r\n


Message:
Only COM+ applications marked "queued" can be created using the "queue" moniker.\r\n


Message:
At least one interface must be marked 'queued" in order to create a queued component instance with the "queue" moniker.\r\n


Message:
MSMQ, which is required for the requested operation, is not installed.\r\n


Message:
One of the objects being inserted or updated does not belong to a valid parent collection\r\n


Message:
One of the specified objects cannot be found\r\n


Message:
Site Server LDAP Service could not establish Secure Sockets Layer (SSL) channel.  Verify that a proper certificate is installed correctly.  The data area, shown below, contains the return error code.\r\n


Message:
Cannot allocate %1 because there is not enough memory available.\r\n


Message:
Cannot allocate %1 because the preallocated limit has been reached.\r\n


Message:
Site Server LDAP Service rejected the connection attempt because there are too many users connected.\r\n


Message:
The evaluation period for this product has expired and could no longer be started.\r\n


Message:
Site Server LDAP Service cannot initialize the socket library. Check the TCP/IP configuration.\r\n


Message:
Printer Driver %1 for %2 %3 was added or updated. Files:- %4.\r\n


Message:
Replication of license information failed because the License Logging Service on server %1 could not be contacted.\r\n


Message:
Performance counters for the %1!s! service were loaded successfully.\r\nThe Record Data contains the new index values assigned\r\nto this service.\r\n


Message:
Performance counters for the %1!s! service were removed successfully.\r\nThe Record Data contains the new values of the system Last Counter and \r\nLast Help registry entries.\r\n


Message:
No object list was found in the installation file. Adding an object \r\nlist to the installation file will \r\nimprove performance of the system when measuring performance counters.\r\n


Message:
Installing the performance counter strings for %1!s! failed. The\r\nError code is DWORD 0 of the Record Data.\r\n


Message:
The driver could not obtain resources required to create a propper WaitWake IRP.\r\n


Message:
Could not locate the device object for one or more pointer port devices.\r\n


Message:
Could not connect to port device %1.\r\n


Message:
Could not enable interrupts on connected port device %1.\r\n


Message:
Could not disable interrupts on connected port device %1.\r\n


Message:
The driver for device %1 encountered an internal driver error.\r\n


Message:
Internal resources allocated for the queuing of audit messages have been exhausted,\r\nleading to the loss of some audits.\r\n%n\r\n%tNumber of audit messages discarded:%t%1\r\n


Message:
The audit log was cleared\r\n%n\r\n%tPrimary User Name:%t%1%n\r\n%tPrimary Domain:%t%2%n\r\n%tPrimary Logon ID:%t%3%n\r\n%tClient User Name:%t%4%n\r\n%tClient Domain:%t%5%n\r\n%tClient Logon ID:%t%6%n\r\n


Message:
An notification package has been loaded by the Security Account Manager.\r\nThis package will be notified of any account or password changes.\r\n%n\r\nNotification Package Name:%t%1\r\n


Message:
Successful Logon:%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon ID:%t%t%3%n\r\n%tLogon Type:%t%4%n\r\n%tLogon Process:%t%5%n\r\n%tAuthentication Package:%t%6%n\r\n%tWorkstation Name:%t%7\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tUnknown user name or bad password%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tAccount logon time restriction violation%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tAccount currently disabled%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tThe specified user account has expired%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tUser not allowed to logon at this computer%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%tThe user has not been granted the requested%n\r\n%t%tlogon type at this machine%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tThe specified account's password has expired%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tThe NetLogon component is not active%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tAn unexpected error occurred during logon%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
User Logoff:%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon ID:%t%t%3%n\r\n%tLogon Type:%t%4%n\r\n


Message:
Logon Failure:%n\r\n%tReason:%t%tAccount locked out%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%2%n\r\n%tLogon Type:%t%3%n\r\n%tLogon Process:%t%4%n\r\n%tAuthentication Package:%t%5%n\r\n%tWorkstation Name:%t%6\r\n


Message:
Successful Network Logon:%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon ID:%t%t%3%n\r\n%tLogon Type:%t%4%n\r\n%tLogon Process:%t%5%n\r\n%tAuthentication Package:%t%6%n\r\n%tWorkstation Name:%t%7\r\n


Message:
IKE security association established.%n\r\nMode: %n%1%n\r\nPeer Identity: %n%2%n\r\nFilter: %n%3%n\r\nParameters: %n%4%n\r\n


Message:
IKE security association ended.%n\r\nMode: Data Protection (Quick mode)\r\nFilter: %n%1%n\r\nInbound SPI: %n%2%n\r\nOutbound SPI: %n%3%n\r\n


Message:
IKE security association ended.%n\r\nMode: Key Exchange (Main mode)%n\r\nFilter: %n%1%n\r\n


Message:
IKE security association establishment failed because peer could not authenticate.\r\nThe certificate trust could not be established.%n\r\nPeer Identity: %n%1%n\r\nFilter: %n%2%n\r\n


Message:
IKE peer authentication failed.%n\r\nPeer Identity: %n%1%n\r\nFilter: %n%2%n\r\n


Message:
IKE security association establishment failed because peer\r\nsent invalid proposal.%n\r\nMode: %n%1%n\r\nFilter: %n%2%n\r\nAttribute: %n%3%n\r\nExpected value: %n%4%n\r\nReceived value: %n%5%n\r\n


Message:
IKE security association negotiation failed.%n\r\nMode: %n%1%n\r\nFilter: %n%2%n\r\nFailure Point: %n%3%n\r\nFailure Reason: %n%4%n\r\n


Message:
Object Open:%n\r\n%tObject Server:%t%1%n\r\n%tObject Type:%t%2%n\r\n%tObject Name:%t%3%n\r\n%tNew Handle ID:%t%4%n\r\n%tOperation ID:%t{%5,%6}%n\r\n%tProcess ID:%t%7%n\r\n%tPrimary User Name:%t%8%n\r\n%tPrimary Domain:%t%9%n\r\n%tPrimary Logon ID:%t%10%n\r\n%tClient User Name:%t%11%n\r\n%tClient Domain:%t%12%n\r\n%tClient Logon ID:%t%13%n\r\n%tAccesses%t%t%14%n\r\n%tPrivileges%t%t%15%n\r\n


Message:
Handle Allocated:%n\r\n%tHandle ID:%t%1%n\r\n%tOperation ID:%t{%2,%3}%n\r\n%tProcess ID:%t%4%n\r\n


Message:
Handle Closed:%n\r\n%tObject Server:%t%1%n\r\n%tHandle ID:%t%2%n\r\n%tProcess ID:%t%3%n\r\n


Message:
Object Open for Delete:%n\r\n%tObject Server:%t%1%n\r\n%tObject Type:%t%2%n\r\n%tObject Name:%t%3%n\r\n%tNew Handle ID:%t%4%n\r\n%tOperation ID:%t{%5,%6}%n\r\n%tProcess ID:%t%7%n\r\n%tPrimary User Name:%t%8%n\r\n%tPrimary Domain:%t%9%n\r\n%tPrimary Logon ID:%t%10%n\r\n%tClient User Name:%t%11%n\r\n%tClient Domain:%t%12%n\r\n%tClient Logon ID:%t%13%n\r\n%tAccesses%t%t%14%n\r\n%tPrivileges%t%t%15%n\r\n


Message:
Object Deleted:%n\r\n%tObject Server:%t%1%n\r\n%tHandle ID:%t%2%n\r\n%tProcess ID:%t%3%n\r\n


Message:
Object Open:%n\r\n%tObject Server:%t%1%n\r\n%tObject Type:%t%2%n\r\n%tObject Name:%t%3%n\r\n%tNew Handle ID:%t%4%n\r\n%tOperation ID:%t{%5,%6}%n\r\n%tProcess ID:%t%7%n\r\n%tPrimary User Name:%t%8%n\r\n%tPrimary Domain:%t%9%n\r\n%tPrimary Logon ID:%t%10%n\r\n%tClient User Name:%t%11%n\r\n%tClient Domain:%t%12%n\r\n%tClient Logon ID:%t%13%n\r\n%tAccesses%t%t%14%n\r\n%tPrivileges%t%t%15%n%n\r\nProperties:%n%16%17%18%19%20%21%22%23%24%25%n\r\n


Message:
Special privileges assigned to new logon:%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon ID:%t%t%3%n\r\n%tAssigned:%t%t%4\r\n


Message:
Privileged Service Called:%n\r\n%tServer:%t%t%1%n\r\n%tService:%t%t%2%n\r\n%tPrimary User Name:%t%3%n\r\n%tPrimary Domain:%t%4%n\r\n%tPrimary Logon ID:%t%5%n\r\n%tClient User Name:%t%6%n\r\n%tClient Domain:%t%7%n\r\n%tClient Logon ID:%t%8%n\r\n%tPrivileges:%t%9\r\n


Message:
Privileged object operation:%n\r\n%tObject Server:%t%1%n\r\n%tObject Handle:%t%2%n\r\n%tProcess ID:%t%3%n\r\n%tPrimary User Name:%t%4%n\r\n%tPrimary Domain:%t%5%n\r\n%tPrimary Logon ID:%t%6%n\r\n%tClient User Name:%t%7%n\r\n%tClient Domain:%t%8%n\r\n%tClient Logon ID:%t%9%n\r\n%tPrivileges:%t%10\r\n


Message:
A new process has been created:%n\r\n%tNew Process ID:%t%1%n\r\n%tImage File Name:%t%2%n\r\n%tCreator Process ID:%t%3%n\r\n%tUser Name:%t%4%n\r\n%tDomain:%t%t%5%n\r\n%tLogon ID:%t%t%6%n\r\n


Message:
A process has exited:%n\r\n%tProcess ID:%t%1%n\r\n%tUser Name:%t%2%n\r\n%tDomain:%t%t%3%n\r\n%tLogon ID:%t%t%4%n\r\n


Message:
A handle to an object has been duplicated:%n\r\n%tSource Handle ID:%t%1%n\r\n%tSource Process ID:%t%2%n\r\n%tTarget Handle ID:%t%3%n\r\n%tTarget Process ID:%t%4%n\r\n


Message:
Indirect access to an object has been obtained:%n\r\n%tObject Type:%t%1%n\r\n%tObject Name:%t%2%n\r\n%tProcess ID:%t%3%n\r\n%tPrimary User Name:%t%4%n\r\n%tPrimary Domain:%t%5%n\r\n%tPrimary Logon ID:%t%6%n\r\n%tClient User Name:%t%7%n\r\n%tClient Domain:%t%8%n\r\n%tClient Logon ID:%t%9%n\r\n%tAccesses:%t%10%n\r\n


Message:
User Right Assigned:%n\r\n%tUser Right:%t%1%n\r\n%tAssigned To:%t%2%n\r\n%tAssigned By:%n\r\n%tUser Name:%t%3%n\r\n%tDomain:%t%t%4%n\r\n%tLogon ID:%t%t%5%n\r\n


Message:
User Right Removed:%n\r\n%tUser Right:%t%1%n\r\n%tRemoved From:%t%2%n\r\n%tRemoved By:%n\r\n%tUser Name:%t%3%n\r\n%tDomain:%t%t%4%n\r\n%tLogon ID:%t%t%5%n\r\n


Message:
New Trusted Domain:%n\r\n%tDomain Name:%t%1%n\r\n%tDomain ID:%t%2%n\r\n%tEstablished By:%n\r\n%tUser Name:%t%3%n\r\n%tDomain:%t%t%4%n\r\n%tLogon ID:%t%t%5%n\r\n


Message:
Removing Trusted Domain:%n\r\n%tDomain Name:%t%1%n\r\n%tDomain ID:%t%2%n\r\n%tRemoved By:%n\r\n%tUser Name:%t%3%n\r\n%tDomain:%t%t%4%n\r\n%tLogon ID:%t%t%5%n\r\n


Message:
Audit Policy Change:%n\r\nNew Policy:%n\r\n%tSuccess%tFailure%n\r\n%t    %3%t    %4%tLogon/Logoff%n\r\n%t    %5%t    %6%tObject Access%n\r\n%t    %7%t    %8%tPrivilege Use%n\r\n%t    %13%t    %14%tAccount Management%n\r\n%t    %11%t    %12%tPolicy Change%n\r\n%t    %1%t    %2%tSystem%n\r\n%t    %9%t    %10%tDetailed Tracking%n\r\n%t    %15%t    %16%tDirectory Service Access%n\r\n%t    %17%t    %18%tAccount Logon%n%n\r\nChanged By:%n\r\n%tUser Name:%t%19%n\r\n%tDomain Name:%t%20%n\r\n%tLogon ID:%t%t%21\r\n


Message:
IPSec policy agent started: %t%1%n\r\nPolicy Source: %t%2%n\r\n%3%n\r\n


Message:
IPSec policy agent disabled: %t%1%n\r\n%2%n\r\n


Message:
IPSec policy agent changed: %t%1%n\r\nPolicySource: %t%2%n\r\n%3%n\r\n


Message:
IPSec policy agent encountered a potentially serious failure.%n\r\n%1%n\r\n


Message:
User Account Created:%n\r\n%tNew Account Name:%t%1%n\r\n%tNew Domain:%t%2%n\r\n%tNew Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges%t%t%7%n\r\n


Message:
User Account Type Change:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tNew Type:%t%4%n\r\n%tCaller User Name:%t%5%n\r\n%tCaller Domain:%t%6%n\r\n%tCaller Logon ID:%t%7%n\r\n


Message:
User Account Enabled:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n


Message:
Change Password Attempt:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Pre-authentication failed:%n\r\n%tUser Name:%t%t%1%n\r\n%tUser ID:%t%t%2%n\r\n%tService Name:%t%t%3%n\r\n%tPre-Authentication Type:%t%4%n\r\n%tFailure Code:%t%t%5%n\r\n%tClient Address:%t%t%6%n\r\n


Message:
Authentication Ticket Request Failed:%n\r\n%tUser Name:%t%1%n\r\n%tSupplied Realm Name:%t%2%n\r\n%tService Name:%t%3%n\r\n%tTicket Options:%t%4%n\r\n%tFailure Code:%t%5%n\r\n%tClient Address:%t%6%n\r\n


Message:
Service Ticket Request Failed:%n\r\n%tUser Name:%t%1%n\r\n%tUser Domain:%t%2%n\r\n%tService Name:%t%3%n\r\n%tTicket Options:%t%4%n\r\n%tFailure Code:%t%5%n\r\n%tClient Address:%t%6%n\r\n


Message:
Account Mapped for Logon by: %1%n\r\nClient Name:%n\r\n%t%2%n\r\n%tMapped Name:%m\r\n%t%3%n\r\n


Message:
The name:%n\r\n%t%2%n\r\ncould not be mapped for logon by:\r\n%t%1%n\r\n


Message:
Account Used for Logon by: %1%n\r\nAccount Name:%n\r\n%t%2%n\r\nWorkstation: %n\r\n%t%3%n\r\n


Message:
The logon to account: %2%n\r\nby: %1%n\r\nfrom workstation: %3%n\r\nfailed. The error code was: %4%n\r\n


Message:
Session reconnected to winstation:%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon ID:%t%t%3%n\r\n%tSession Name:%t%4%n\r\n%tClient Name:%t%5%n\r\n%tClient Address:%t%6\r\n


Message:
Session disconnected from winstation:%n\r\n%tUser Name:%t%1%n\r\n%tDomain:%t%t%2%n\r\n%tLogon ID:%t%t%3%n\r\n%tSession Name:%t%4%n\r\n%tClient Name:%t%5%n\r\n%tClient Address:%t%6\r\n


Message:
Security Enabled Local Group Changed:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Security Enabled Local Group Member Added:%n\r\n%tMember Name:%t%1%n\r\n%tMember ID:%t%2%n\r\n%tTarget Account Name:%t%3%n\r\n%tTarget Domain:%t%4%n\r\n%tTarget Account ID:%t%5%n\r\n%tCaller User Name:%t%6%n\r\n%tCaller Domain:%t%7%n\r\n%tCaller Logon ID:%t%8%n\r\n%tPrivileges:%t%9%n\r\n


Message:
Security Enabled Local Group Member Removed:%n\r\n%tMember Name:%t%1%n\r\n%tMember ID:%t%2%n\r\n%tTarget Account Name:%t%3%n\r\n%tTarget Domain:%t%4%n\r\n%tTarget Account ID:%t%5%n\r\n%tCaller User Name:%t%6%n\r\n%tCaller Domain:%t%7%n\r\n%tCaller Logon ID:%t%8%n\r\n%tPrivileges:%t%9%n\r\n


Message:
Security Enabled Local Group Deleted:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Security Disabled Local Group Created:%n\r\n%tTarget Account Name:%t%1%n\r\n%tTarget Domain:%t%2%n\r\n%tTarget Account ID:%t%3%n\r\n%tCaller User Name:%t%4%n\r\n%tCaller Domain:%t%5%n\r\n%tCaller Logon ID:%t%6%n\r\n%tPrivileges:%t%7%n\r\n


Message:
Fetching requested number of rows would have exceeded total number\r\nof active rows supported by the rowset\r\n


Message:
One or more column types are incompatible; conversion errors will\r\noccur during copying\r\n


Message:
Parameter type information has been overridden by caller\r\n


Message:
Skipped bookmark for deleted or non-member row\r\n


Message:
Reached start or end of rowset or chapter\r\n


Message:
The provider re-executed the command\r\n


Message:
Server cannot release or downgrade a lock until the end of the\r\ntransaction\r\n


Message:
Specified weight was not supported or exceeded the supported limit\r\nand was set to 0 or the supported limit\r\n


Message:
Consumer is uninterested in receiving further notification calls for\r\nthis reason\r\n


Message:
Input dialect was ignored and text was returned in different\r\ndialect\r\n


Message:
Consumer is uninterested in receiving further notification calls for\r\nthis phase\r\n


Message:
The operation is being processed asynchronously\r\n


Message:
In order to reposition to the start of the rowset, the provider had\r\nto reexecute the query; either the order of the columns changed or\r\ncolumns were added to or removed from the rowset\r\n


Message:
The method had some errors; errors have been returned in the error\r\narray\r\n


Message:
A given HROW referred to a hard-deleted row\r\n


Message:
The provider was unable to keep track of all the changes; the client\r\nmust refetch the data associated with the watch region using another\r\nmethod\r\n


Message:
Execution stopped because a resource limit has been reached; results\r\nobtained so far have been returned but execution cannot be resumed\r\n


Message:
A lock was upgraded from the value specified\r\n


Message:
One or more properties were changed as allowed by provider\r\n


Message:
Updating this row caused more than one row to be updated in the\r\ndata source\r\n


Message:
Creating another row would have exceeded the total number of active\r\nrows supported by the rowset\r\n


Message:
Unable to write with a read-only accessor\r\n


Message:
Given values violate the database schema\r\n


Message:
A literal value in the command could not be converted to the\r\ncorrect type due to a reason other than data overflow\r\n


Message:
Specified column does not contain bookmarks or chapters\r\n


Message:
No command has been set for the command object\r\n


Message:
Unable to find a query plan within the given cost limit\r\n


Message:
No value given for one or more required parameters\r\n


Message:
The command contained one or more errors\r\n


Message:
The executing command cannot be canceled\r\n


Message:
The provider does not support the specified dialect\r\n


Message:
A data source with the specified name already exists\r\n


Message:
The rowset was built over a live data feed and cannot be restarted\r\n


Message:
No key matching the described characteristics could be found within\r\nthe current range\r\n


Message:
Ownership of this tree has been given to the provider\r\n


Message:
The provider is unable to determine identity for newly inserted\r\nrows\r\n


Message:
No nonzero weights specified for any goals supported, so goal was\r\nrejected; current goal was not changed\r\n


Message:
Requested conversion is not supported\r\n


Message:
lRowsOffset would position you past either end of the rowset,\r\nregardless of the cRows value specified; cRowsObtained is 0\r\n


Message:
Information was requested for a query, and the query was not set\r\n


Message:
Provider called a method from IRowsetNotify in the consumer and\tthe\r\nmethod has not yet returned\r\n


Message:
A non-NULL controlling IUnknown was specified and the object being\r\ncreated does not support aggregation\r\n


Message:
A given HROW referred to a hard- or soft-deleted row\r\n


Message:
The rowset does not support fetching backwards\r\n


Message:
All HROWs must be released before new ones can be obtained\r\n


Message:
One of the specified storage flags was not supported\r\n


Message:
The given parameter name was unrecognized\r\n


Message:
Multiple storage objects can not be open simultaneously\r\n


Message:
The requested filter could not be opened\r\n


Message:
The requested order could not be opened\r\n


Message:
The Microsoft Distributed Transaction Coordinator service was successfully installed.%0\r\n


Message:
Failed to initialize the MS DTC TIP Gateway. \r\nMS DTC is being started but the TIP feature will be disabled.%0\r\n


Message:
The server %1 did not register with DCOM within the required timeout.\r\n


Message:
The server %1 could not be contacted to establish the connection to the client\r\n


Message:
There is an assertion failure in DCOM.  Context follows:\r\n%1\r\n%2\r\n%3\r\n


Message:
DCOM server attempted to listen on an invalid endpoint.\r\nProtseq:  %1\r\nEndpoint: %2\r\nFlags:    %3\r\n


Message:
Unable to start DNS Client Service.\r\nFailed to load DLL %2, Error: %1.\r\nPlease reinstall this DLL from installation CD.\r\n


Message:
Unable to start DNS Client service. Can not find entry %3 in DLL %2.\r\nPlease reinstall this DLL from installation CD. For specific error\r\ncode, click the Record Data tab.\r\n


Message:
Unable to start the DNS Client service. The system could not register a\r\nservice control handler and could be out of resources. Close any\r\napplications not in use or reboot the computer. For specific error\r\ncode, click the Record Data tab.\r\n


Message:
Unable to start DNS Client service. The system could\r\nnot create a termination event for this service and\r\ncould be out of resources. Close any applications not\r\nin use or reboot the computer. For specific error code,\r\nclick the Record Data tab.\r\n


Message:
Unable to start DNS Client service. Could not start the\r\nRemote Procedure Call (RPC) interface for this service.\r\nTo correct the problem, you may restart the RPC and DNS\r\nClient services. To do so, use the following commands at a command\r\nprompt: (1) type "net start rpc" to start the RPC service, and (2)\r\ntype "net start dnscache" to start the DNS Client service. For\r\nspecific error code information, click the Record Data tab.\r\n


Message:
Unable to start DNS Client service. The system could not register\r\nshutdown notification for this service and could be out of resources.\r\nTry closing any applications not in use or reboot the computer.\r\n


Message:
Unable to start DNS Client service. Could not update status with\r\nService Control Manager. To correct the problem, you may restart\r\nthe RPC and DNS Client services. To do so, use the following commands\r\nat a command prompt: (1) type "net start rpc" to start the RPC service,\r\nand (2) type "net start dnscache" to start the DNS Client service. For\r\nspecific error code information, click the Record Data tab.\r\n


Message:
Unable to start DNS Client service because the system failed to allocate\r\nmemory and may be out of available memory. Try closing any applications not\r\nin use or reboot the computer. For specific error code, click the Record\r\nData tab.\r\n


Message:
The WMI service was unable to open the WMI service device. The status code is in the additional data.\r\n


Message:
The File Replication Service moved the preexisting files in %1 to %2.\r\n%n\r\n%nThe File Replication Service may delete the files in %2 at any time.\r\nFiles can be saved from deletion by copying them out of %2. Copying\r\nthe files into %1 may lead to name conflicts if the files already exist\r\non some other replicating partner.\r\n%n\r\n%nIn some cases, the File Replication Service may copy a file\r\nfrom %2 into %1 instead of replicating the file from some other\r\nreplicating partner.\r\n%n\r\n%nSpace can be recovered at any time by deleting the files in %2.\r\n


Message:
The File Replication Service paused because the staging area is full.\r\nReplication will resume if staging space becomes available or if the\r\nstaging space limit is increased.\r\n%n\r\n%nThe current value of the staging space limit is %1 KB.\r\n%n\r\n%nTo change the staging space limit, run regedt32.\r\n%n\r\n%nClick on Start, Run and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,\r\nCurrentControlSet, Services, NtFrs, Parameters, and the value\r\n"Staging Space Limit in KB".\r\n


Message:
The File Replication Service paused because the size of a file exceeds the\r\nstaging space limit. Replication will resume only if the staging space limit\r\nis increased.\r\n%n\r\n%nThe staging space limit is %1 KB and the file size is %2 KB.\r\n%n\r\n%nTo change the staging space limit, run regedt32.\r\n%n\r\n%nClick on Start, Run and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,\r\nCurrentControlSet, Services, NtFrs, Parameters, and the value\r\n"Staging Space Limit in KB".\r\n


Message:
The File Replication Service cannot find the DNS name for the computer %1\r\nbecause the "%2" attribute could not be read from the distinguished\r\nname "%3".\r\n%n\r\n%nThe File Replication Service will try using the name "%1" until the\r\ncomputer's DNS name appears.\r\n


Message:
The File Replication Service detected an invalid parameter value in the\r\nregistry.  %1.\r\n%n\r\n%nThe expected registry key name is "%2".\r\n%nThe expected value name is "%3".\r\n%nThe expected registry data type is %4.\r\n%nThe allowed range for this parameter is %5\r\n%nThe data units for this parameter value are %6.\r\n%nThe File Replication Service is using a default value of "%7".\r\n%n\r\n%nTo change this parameter, run regedt32.\r\n%n\r\n%nClick on Start, Run and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE.\r\n%nClick down the key path: "%8"\r\n%nDouble click on the value name -\r\n%n    "%9"\r\n%nand update the value.\r\n%nIf the value name is not present you may add it with the Add Value function\r\nunder the Edit Menu item. Type the value name exactly as shown above using the\r\nabove registry data type.  Make sure you observe the data units and allowed range\r\nwhen entering the value.\r\n


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


Message:
Qos [Adapter %2]:%nThe registry entry for BestEffortLimit is not supported over WAN links. Defaulting to Unlimited BestEffort mode.\r\n


Message:
QoS [Adapter %2]:%nTotal bandwidth allocated to flows exceeds the NonBestEffortLimit. This is because of a reduction in the LinkSpeed or because of a change to the NonBestEffortLimit registry key.\r\n


Message:
The server's call to a system service failed unexpectedly.\r\n


Message:
The server was unable to perform an operation due to a shortage of available resources.\r\n


Message:
The server could not create its device.  The server could not be started.\r\n


Message:
The server could not create a process.  The server could not be started.\r\n


Message:
The browser driver has received an election packet from computer %2 on network %3.  The data is the packet received.\r\n


Message:
The browser has retrieved a list of servers from remote computer %1 on transport %2.%n\r\nThere were %3 entries read, and %4 total entries.\r\n


Message:
The browser has retrieved a list of domains from remote computer %1 on transport %2.%n\r\nThere were %3 entries read, and %4 total entries.\r\n


Message:
The system detected that network adapter %2 was connected to the network,\r\nand has initiated normal operation over the network adapter.\r\n


Message:
The system detected that network adapter %2 was disconnected from the network,\r\nand the adapter's network configuration has been released. If the network\r\nadapter was not disconnected, this may indicate that it has malfunctioned.\r\nPlease contact your vendor for updated drivers.\r\n


Message:
%2 : The adapter is configured such that the receive space is smaller than\r\nthe maximum packet size.  Some packets may be lost.\r\n


Message:
%2 : The adapter has successfully reinserted back into the ring.\r\n


Message:
The browser driver has forced an election on network %2 because it was unable to find a master browser to retrieve a backup list on that network.\r\n


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


Message:
The browser has forced an election on network %1 because a Windows 2000 Server (or domain master) browser is started.\r\n


Message:
The backup browser server %2 is out-of-date.  Consider upgrading this computer.\r\n


Message:
The browser running on the Domain Controller has lost an election.  The computer that won the election is %2, on the transport %3.%n\r\nThe data contains the election version, election criteria, and remote computer time up, and the same information for\r\nthe current computer.\r\n


Message:
The browser running on this computer has won a browser election on network %2.\r\nThis computer is a member of a domain, so the Domain Controller should become the master\r\nbrowser.\r\n


Message:
The browser driver was unable to initialize variables from the Registry.\r\n


Message:
The browser driver has discarded too many mailslot messages.\r\n


Message:
The browser driver has discarded too many GetBrowserServerList requests.\r\n


Message:
The browser has forced an election on network %1 because a master browser was stopped.\r\n


Message:
The browser has forced an election on network %1 because the Domain Controller (or Server) has changed its role\r\n


Message:
%2 could not transfer a packet from the adapter.  The packet was dropped.\r\n


Message:
%2 could not create a link to a remote computer.  Your computer has exceeded the number of connections it can make to that remote computer.\r\n


Message:
%2 received an unexpected %3 packet from a remote computer.\r\n


Message:
The default frame type for auto-detection on %2 was changed to %3.\r\nThis type is now the default if no frame type can be detected.\r\n


Message:
The system registered network adapter with settings :%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6\r\n


Message:
The system registered pointer (PTR) resource records (RRs) for network\r\nadapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  Primary Domain Suffix : %4%n\r\n  DNS server list :%n\r\n    %5%n\r\n  Sent update to server : %6%n\r\n  IP Address : %7\r\n


Message:
The system registered host (A) resource records (RRs) for network\r\nadapter%nwith settings :%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6\r\n


Message:
A new volume ID has been assigned for %1:%n%2%n%n\r\nThis ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.  If there previously were links to files on this volume that are broken, they might not be automatically repairable.\r\n


Message:
Ownership of the volume ID for %1: has been successfully claimed.  This volume ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.\r\n


Message:
The volume ID for %1: has been reset, since it was a duplicate of that on %2:.  This volume ID is used by Distributed Link Tracking to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.\r\n


Message:
The File Replication Service is starting.\r\n


Message:
The File Replication Service is stopping.\r\n


Message:
The File Replication Service has stopped.\r\n


Message:
The File Replication Service is no longer preventing the computer %1 from\r\nbecoming a domain controller. The system volume has been successfully\r\ninitialized and the Netlogon service has been notified that the system\r\nvolume is now ready to be shared as SYSVOL.\r\n%n\r\n%nType "net share" to check for the SYSVOL share.\r\n


Message:
Dfs received a referral request for "%2".  The return code is in the data.\r\n


Message:
Dfs was unable to open the Lan Redir\r\n


Message:
Dfs was unable to open a connection to server %2.  The error returned is in the record data.\r\n


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


Message:
Dfs obtained a referral for "%2" from %3\r\n


Message:
Dfs reached its limit of attempts of resolution of "%2".\r\n


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


Message:
Dfs failed on open of %2 directed to %3.  The error returned is in the record data.\r\n


Message:
NetrDfsEnum received an enumeration.  The return code is in the record data.\r\n


Message:
NetrDfsEnumEx received an enumeration.  The return code is in the record data.\r\n


Message:
The %2 disk is at or near capacity.  You may need to delete some files.\r\n


Message:
The server was unable to allocate a work item %2 times in the last %3 seconds.\r\n


Message:
The server was unable to find a free connection %2 times in the last %3 seconds.\r\n


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


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


Message:
The server could not bind to the transport %1.\r\n


Message:
The value named %1 in the server's Registry key %2 was invalid.  The value was ignored, and processing continued.\r\n


Message:
The security descriptor stored in the Registry for the share %1 was invalid.  The share was not automatically recreated.\r\n


Message:
The server service was unable to load the server driver.\r\n


Message:
The server service was unable to unload the server driver.\r\n


Message:
The server service was unable to map error code %1.\r\n


Message:
The server service was unable to recreate the share %1 because the directory %2 no longer exists.\r\n


Message:
The server service was unable to change the domain name from %1 to %2.\r\n


Message:
The redirector was unable to allocate memory.\r\n


Message:
The redirector could not create its device.  The redirector could not be started.\r\n


Message:
The redirector could not create a system thread.\r\n


Message:
The redirector could not set the priority for a system thread.\r\n


Message:
The redirector received an incorrectly formatted response from %2.\r\n


Message:
The redirector received an SMB that was too short.\r\n


Message:
The redirector received an incorrect response from %2 to a lock request.\r\n


Message:
The redirector failed to unlock part of a file on server %2.\r\n


Message:
The redirector failed to write data to server %2 after the file was closed.\r\n


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


Message:
The redirector has timed out a request to %2.\r\n


Message:
The redirector received an invalid oplock level from %2.\r\n


Message:
The redirector dereferenced a connection through zero.\r\n


Message:
The redirector dereferenced a server through zero.\r\n


Message:
The redirector dereferenced the allocated SMB count through zero.\r\n


Message:
The redirector accessed a share-level server that indicates it encrypts passwords.\r\nThis combination is not supported.\r\n


Message:
The redirector failed to determine the connection type.\r\n


Message:
The redirector failed to allocate a multiplex table entry.  This indicates that\r\nthe MAXCMDS parameter to the redirector is insufficient for the users needs.\r\n


Message:
The redirector failed to allocate a buffer for an oplock break.\r\n


Message:
The redirector failed to map the requested file disposition (for NtCreateFile).\r\n


Message:
The redirector is allocating additional resources for input/output request packet contexts.  This is\r\nprobably caused by a resource leak in the redirector.\r\n


Message:
A write-behind operation has failed to the remote server %2.  The data contains the amount requested to write and the amount actually written.\r\n


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


Message:
The redirector was unable to initialize variables from the Registry.\r\n


Message:
The time zone bias calculated between %2 and the current workstation is too\r\nlarge.  The data specifies the number of 100ns units between the workstation\r\nand server.  Make sure that the time of day on the workstation and server are\r\ncorrect.\r\n


Message:
The redirector has failed to connect to the server %2 on the primary transport.  The data contains the error.\r\n


Message:
The redirector was unable to update the file attributes on a file located on server %2.\r\nThe data contains the name of the file.\r\n


Message:
The redirector was unable to delete the file specified on server %2 when it was closed by the application.\r\nThe data contains the name of the file.\r\n


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


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


Message:
The redirector was unable to initialize security context or query context attributes.\r\n


Message:
The redirector was unable to build SMB header.\r\n


Message:
The redirector detected a security signature mismatch. The connection has been disconnected.\r\n


Message:
Unable to allocate a %2 byte message.\r\n


Message:
%2 message allocations have failed since initialization.\r\n


Message:
Unable to allocate a %2 byte external message.\r\n


Message:
%2 external message allocations have failed since initialization.\r\n


Message:
IP was unable to initialize adapter %2 for configuration by DHCP.\r\nIf DHCP is enabled on this adapter, the primary interface may not be\r\nconfigured properly. Interfaces on this adapter not configured by\r\nDHCP will be unaffected.\r\n


Message:
Invalid default gateway address %2 was specified for adapter %3.\r\nSome remote networks may not be reachable as a result.\r\n


Message:
More than the maximum number of default gateways were specified for\r\nadapter %2. Some remote networks may not be reachable as a result.\r\n


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


Message:
The backup WINS server address is not configured in the registry.\r\n


Message:
The primary WINS server address is not configured in the registry.\r\n


Message:
The backup WINS server address is not formated correctly in the registry.\r\n


Message:
The primary WINS server address is not formated correctly in the registry.\r\n


Message:
There are no adapters configured for this protocol stack.\r\n


Message:
Unable to open the Registry to read the WINS server addresses.\r\n


Message:
The Netbios Name Scope has a component longer than 63 characters. Each label\r\nin the Scope cannot be longer than 63 bytes.  Use the Control Panel, Network\r\napplet to change the scope.\r\n


Message:
The Netbios Name Scope is too long. The scope cannot be longer than\r\n255 bytes. Use the Control Panel, Network applet to change the scope.\r\n


Message:
%2 : The adapter is disabled.  The driver cannot open the adapter.\r\n


Message:
%2 : There is an I/O port or DMA channel conflict.\r\n


Message:
%2 : There is a memory conflict at address 0x%3.\r\n


Message:
%2 : There is a interrupt conflict at interrupt number %3.\r\n


Message:
%2 : There is a resource conflict at DMA channel %3.\r\n


Message:
%2 : The specified Registry entry MaxReceives is out of range.  Using\r\ndefault value.\r\n


Message:
%2 : The specified Registry entry MaxTransmits is out of range.  Using\r\ndefault value.\r\n


Message:
%2 : The specified Registry entry MaxFrameSize is out of range.  Using\r\ndefault value.\r\n


Message:
%2 : The specified Registry entry MaxInternalBufs is out of range.  Using\r\ndefault value.\r\n


Message:
%2 : The specified Registry entry MaxMulticast is out of range.  Using\r\ndefault value.\r\n


Message:
%2 : The specified Registry entry ProductId is out of range.  Using\r\ndefault value.\r\n


Message:
%2 : A Token Ring Lobe Wire Fault has occurred.  Verify cable\r\nconnections.  The adapter will continue to try to reinsert back\r\ninto the ring.\r\n


Message:
%2 : The adapter had detected a loss of signal on the ring.  The adapter\r\nwill continue to try to reinsert back into the ring.\r\n


Message:
%2 : The adapter has received a request to deinsert from the\r\nring.  The adapter will continue to try to reinsert back into the ring.\r\n


Message:
%2 : The adapter failed to reset within a specified time.  The adapter will\r\ncontinue to try to reset.  This could be the result of a hardware failure.\r\n


Message:
%2 : The adapter has detected that the Token Ring cable is disconnected from\r\nthe adapter.  Please reconnect the Token Ring cable.  The adapter will continue\r\nto try to reset until the connection is repaired.\r\n


Message:
%2 : The adapter has successfully completed a previously failed reset.\r\n


Message:
The %1 log file is corrupted and will be cleared.\r\n


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


Message:
A driver packet received from the I/O subsystem was invalid.  The data is the\r\npacket.\r\n


Message:
The previous system shutdown at %1 on %2 was unexpected.\r\n


Message:
Microsoft (R) Windows 2000 (R) %1 %2 %3 %4.\r\n


Message:
A request has been submitted to promote the computer to backup when it is already a\r\nmaster browser.\r\n


Message:
The browser has received a server announcement indicating that the computer %2\r\nis a master browser, but this computer is not a master browser.\r\n


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


Message:
The browser was unable to retrieve a list of servers from the browser master %1 on the network %2.\r\nThe data is the error code.\r\n


Message:
The browser was unable to retrieve a list of domains from the browser master %1 on the network %2.\r\nThe data is the error code.\r\n


Message:
The system failed to register pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe reason that the system could not register these RRs was because\r\nof DNS server failure. This may be due to a zone transfer lock on\r\nthe DNS server for the zone that your computer needs to update.%n%n\r\nYou can manually retry DNS registration of the network adapter and\r\nits settings by typing "ipconfig /registerdns" at the command prompt.\r\nIf problems still persist, contact your DNS server or network systems\r\nadministrator. For specific error code information, click the Record\r\nData tab.\r\n


Message:
The system failed to register pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe reason that the system could not register these RRs was because\r\n(a) either the DNS server does not support the DNS dynamic update\r\nprotocol, or (b) the authoritative zone where these records are to\r\nbe registered does not allow dynamic updates.%n%n\r\nTo register DNS pointer (PTR) resource records using the specific\r\nDNS domain name and IP addresses for this adapter, contact your\r\nDNS server or network systems administrator.\r\n


Message:
The system failed to register pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe reason that the system could not register these RRs was because\r\nthe DNS server refused the update request. The cause of this could\r\nbe (a) your computer is not allowed to update the adapter-specified DNS\r\ndomain name, or (b) because the DNS server authoritative for the specified\r\nname does not support the DNS dynamic update protocol.%n%n\r\nTo register the DNS pointer (PTR) resource records using the specific\r\nDNS domain name and IP addresses for this adapter, contact your DNS\r\nserver or network systems administrator.\r\n


Message:
The system failed to register pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe reason that the system could not register these RRs was because\r\nof a security related problem. The cause of this could be (a) your\r\ncomputer does not have permissions to register and update the specific\r\nDNS domain name set for this adapter, or (b) there might have been a\r\nproblem negotiating valid credentials with the DNS server during the\r\nprocessing of the update request.%n%n\r\nYou can manually retry DNS registration of the network adapter and\r\nits settings by typing "ipconfig /registerdns" at the command prompt.\r\nIf problems still persist, contact your DNS server or network systems\r\nadministrator.\r\n


Message:
The system failed to register pointer (PTR) resource records (RRs)\r\nfor network adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Adapter-specific Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address : %6%n%n\r\nThe reason the system could not register these RRs during the\r\nupdate request was because of a system problem. You can manually\r\nretry DNS registration of the network adapter and its settings by\r\ntyping "ipconfig /registerdns" at the command prompt. If problems\r\nstill persist, contact your DNS server or network systems\r\nadministrator. For specific error code, click the Record Data tab.\r\n


Message:
The system failed to register host (A) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not register these RRs was because the\r\nupdate request it sent to the DNS server timed out. The most likely\r\ncause of this is that the DNS server authoritative for the name it\r\nwas attempting to register or update is not running at this time.%n%n\r\nYou can manually retry DNS registration of the network adapter and\r\nits settings by typing "ipconfig /registerdns" at the command prompt.\r\nIf problems still persist, contact your DNS server or network systems\r\nadministrator.\r\n


Message:
The system failed to register host (A) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not register these RRs was because the\r\nDNS server failed the update request. The most likely cause of this\r\nis that the authoritative DNS server required to process this update\r\nrequest has a lock in place on the zone, probably because a zone\r\ntransfer is in progress.%n%n\r\nYou can manually retry DNS registration of the network adapter and\r\nits settings by typing "ipconfig /registerdns" at the command prompt.\r\nIf problems still persist, contact your DNS server or network systems\r\nadministrator.\r\n


Message:
The system failed to register host (A) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not register these RRs was because either\r\n(a) the DNS server does not support the DNS dynamic update protocol, or\r\n(b) the authoritative zone for the specified DNS domain name does not\r\naccept dynamic updates.%n%n\r\nTo register the DNS host (A) resource records using the specific DNS\r\ndomain name and IP addresses for this adapter, contact your DNS server\r\nor network systems administrator.\r\n


Message:
The system failed to register host (A) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not register these RRs was because the\r\nDNS server contacted refused the update request. The reasons for this\r\nmight be (a) you are not allowed to update the specified DNS domain name,\r\nor (b) because the DNS server authoritative for this name does not support\r\nthe DNS dynamic update protocol.%n%n\r\nTo register the DNS host (A) resource records using the specific DNS\r\ndomain name and IP addresses for this adapter, contact your DNS server\r\nor network systems administrator.\r\n


Message:
The system failed to register host (A) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not register these RRs was because of a\r\nsecurity related problem. The cause of this could be (a) your computer\r\ndoes not have permissions to register and update the specific DNS domain\r\nname set for this adapter, or (b) there might have been a problem negotiating\r\nvalid credentials with the DNS server during the processing of the update\r\nrequest.%n%n\r\nYou can manually retry DNS registration of the network adapter and\r\nits settings by typing "ipconfig /registerdns" at the command prompt.\r\nIf problems still persist, contact your DNS server or network systems\r\nadministrator. For specific error code, click the Record Data tab.\r\n


Message:
The system failed to register host (A) resource records (RRs) for\r\nnetwork adapter%nwith settings:%n%n\r\n  Adapter Name : %1%n\r\n  Host Name : %2%n\r\n  Primary Domain Suffix : %3%n\r\n  DNS server list :%n\r\n    %4%n\r\n  Sent update to server : %5%n\r\n  IP Address(es) :%n\r\n    %6%n%n\r\nThe reason the system could not register these RRs during the\r\nupdate request was because of a system problem. You can manually\r\nretry DNS registration of the network adapter and its settings by\r\ntyping "ipconfig /registerdns" at the command prompt. If problems\r\nstill persist, contact your DNS server or network systems\r\nadministrator. For specific error code, click the Record Data tab.\r\n


Message:
The File Replication Service has enabled replication from %1 to %2 for %3\r\nafter repeated retries.\r\n


Message:
The File Replication Service has detected an enabled disk write cache\r\non the drive containing the directory %2 on the computer %1.\r\nThe File Replication Service might not recover when power to the\r\ndrive is interrupted and critical updates are lost.\r\n


Message:
The File Replication Service may be preventing the computer %1 from becoming a\r\ndomain controller while the system volume is being initialized with data\r\nfrom another domain controller and then shared as SYSVOL.\r\n%n\r\n%nType "net share" to check for the SYSVOL share. The File Replication\r\nService has stopped preventing the computer from becoming a domain\r\ncontroller once the SYSVOL share appears.\r\n%n\r\n%nThe initialization of the system volume can take some time.\r\nThe time is dependent on the amount of data in the system volume,\r\nthe availability of other domain controllers, and the replication\r\ninterval between domain controllers.\r\n%n\r\n%nThe initialization of the system volume can be bypassed by first typing\r\nregedt32 and setting the value of SysvolReady to 1 and then restarting\r\nthe Netlogon service.\r\n%n\r\n%nWARNING - BYPASSING THE SYSTEM VOLUME INITIALIZATION IS NOT RECOMMENDED.\r\nApplications may fail in unexpected ways.\r\n%n\r\n%nThe value SysvolReady is located by clicking on HKEY_LOCAL_MACHINE\r\nand then clicking on System, CurrentControlSet, Services, Netlogon,\r\nand Parameters.\r\n%n\r\n%nThe Netlogon service can be restarted by typing "net stop netlogon"\r\nfollowed by "net start netlogon".\r\n


Message:
The File Replication Service may be preventing the computer %1 from becoming a\r\ndomain controller while the system volume is being initialized and then\r\nshared as SYSVOL.\r\n%n\r\n%nType "net share" to check for the SYSVOL share. The File Replication\r\nService has stopped preventing the computer from becoming a domain\r\ncontroller once the SYSVOL share appears.\r\n%n\r\n%nThe initialization of the system volume can take some time.\r\nThe time is dependent on the amount of data in the system volume.\r\n%n\r\n%nThe initialization of the system volume can be bypassed by first typing\r\nregedt32 and setting the value of SysvolReady to 1 and then restarting\r\nthe Netlogon service.\r\n%n\r\n%nWARNING - BYPASSING THE SYSTEM VOLUME INITIALIZATION IS NOT RECOMMENDED.\r\nApplications may fail in unexpected ways.\r\n%n\r\n%nThe value SysvolReady is located by clicking on HKEY_LOCAL_MACHINE\r\nand then clicking on System, CurrentControlSet, Services, Netlogon,\r\nand Parameters.\r\n%n\r\n%nThe Netlogon service can be restarted by typing "net stop netlogon"\r\nfollowed by "net start netlogon".\r\n


Message:
The File Replication Service will not check access to the API "%1".\r\n%n\r\n%nAccess checks can be enabled for "%1" by running regedt32.\r\n%n\r\n%nClick on Start, Run, and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,\r\nCurrentControlSet, Services, NtFrs, Parameters, Access Checks, "%1", and "%2".\r\nChange the string to Enabled.\r\n%n\r\n%nPermissions can be changed by highlighting "%1" and then clicking on the\r\ntoolbar option Security and then Permissions...\r\n


Message:
The File Replication Service did not grant the user "%3" access to the\r\nAPI "%1".\r\n%n\r\n%nPermissions for "%1" can be changed by running regedt32.\r\n%n\r\n%nClick on Start, Run, and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,\r\nCurrentControlSet, Services, NtFrs, Parameters, Access Checks, and highlight "%1".\r\nClick on the toolbar option Security and then Permissions...\r\n%n\r\n%nAccess checks can be disabled for "%1". Double click on "%2" and\r\nchange the string to Disabled.\r\n


Message:
The server could not create a startup thread.  The server could not be started.\r\n


Message:
The server received an unexpected disconnection from a client.\r\n


Message:
The server received an incorrectly formatted request from %2.\r\n


Message:
The server could not open the named pipe file system.  Remote named pipes are disabled.\r\n


Message:
The server could not expand a table because the table reached the maximum size.\r\n


Message:
The server could not start the scavenger thread.  The server could not be started.\r\n


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


Message:
The server has encountered a network error.\r\n


Message:
The server was unable to allocate virtual memory.\r\n


Message:
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.\r\n


Message:
Initialization failed because the transport refused to open initial Connections.\r\n


Message:
Initialization failed because the timers could not be started.\r\n


Message:
Initialization failed because the driver device could not be created.\r\n


Message:
Unable to open the Registry Linkage to read configuration information.\r\n


Message:
Unable to read the driver's bindings to the transport from the registry.\r\n


Message:
Unable to read the driver's exported linkage configuration information.\r\n


Message:
A duplicate name has been detected on the TCP network.  The IP address of\r\nthe machine that sent the message is in the data. Use nbtstat -n in a\r\ncommand window to see which name is in the Conflict state.\r\n


Message:
Another machine has sent a name release message to this machine probably\r\nbecause a duplicate name has been detected on the TCP network.  The IP address\r\nof the node that sent the message is in the data. Use nbtstat -n in a\r\ncommand window to see which name is in the Conflict state.\r\n


Message:
%2 : Has encountered a conflict in resources and could not load.\r\n


Message:
%2 : Could not allocate the resources necessary for operation.\r\n


Message:
%2 : Has determined that the adapter is not functioning properly.\r\n


Message:
%2 : Could not connect to the interrupt number supplied.\r\n


Message:
%2 : Has encountered an internal error and has failed.\r\n


Message:
%2 : The version number is incorrect for this driver.\r\n


Message:
%2 : Has encountered an invalid network address.\r\n


Message:
%2 : Does not support the configuration supplied.\r\n


Message:
%2 : The adapter has returned an invalid value to the driver.\r\n


Message:
%2 : A required parameter is missing from the Registry.\r\n


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


Message:
%2 : The download file is invalid.  The driver is unable to load.\r\n


Message:
%2 : The adapter has detected an Adapter Check as a result of some\r\nunrecoverable hardware or software error.  Please contact your service provider.\r\n


Message:
The %1 service was unable to set up an event source.\r\n


Message:
A uniprocessor-specific driver was loaded on a multiprocessor system.  The driver could not load.\r\n


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


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


Message:
The %1 service depends on the %2 group and no member of this group started.\r\n


Message:
The %1 service depends on the following nonexistent service: %2\r\n


Message:
The %1 call failed with the following error: %n%2\r\n


Message:
The %1 call failed for %2 with the following error: %n%3\r\n


Message:
The system reverted to its last known good configuration.  The system is restarting....\r\n


Message:
No backslash is in the account name.\r\n


Message:
Timeout (%1 milliseconds) waiting for the %2 service to connect.\r\n


Message:
Timeout (%1 milliseconds) waiting for ReadFile.\r\n


Message:
Timeout (%1 milliseconds) waiting for a transaction response from the %2 service.\r\n


Message:
Message returned in transaction has incorrect size.\r\n


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


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


Message:
Boot-start or system-start driver (%1) must not depend on a service.\r\n


Message:
The %1 service has reported an invalid current state %2.\r\n


Message:
Detected circular dependencies demand starting %1.\r\n


Message:
Detected circular dependencies auto-starting services.\r\n


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


Message:
Circular dependency: The %1 service depends on a group which starts later.\r\n


Message:
About to revert to the last known good configuration because the %1 service failed to start.\r\n


Message:
The %1 service terminated with the following error: %n%2\r\n


Message:
The %1 service terminated with service-specific error %2.\r\n


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


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


Message:
Windows 2000 could not be started as configured.  A previous working configuration was used instead.\r\n


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


Message:
The browser has failed to start because the dependent service %1 had invalid service status %2.\r\nStatus             Meaning\r\n  1              Service Stopped%n\r\n  2              Start Pending%n\r\n  3              Stop Pending%n\r\n  4              Running%n\r\n  5              Continue Pending%n\r\n  6              Pause Pending%n\r\n  7              Paused%n\r\n


Message:
The browser was unable to promote itself to master browser.  The browser will continue\r\nto attempt to promote itself to the master browser, but will no longer log any events in the event log in Event Viewer.\r\n


Message:
The browser was unable to promote itself to master browser.  The computer that currently\r\nbelieves it is the master browser is unknown.\r\n


Message:
The browser service has failed to retrieve the backup list too many times on transport %1.\r\nThe backup browser is stopping.\r\n


Message:
The browser has received a GetBrowserServerList request when it is not the master browser.\r\n


Message:
The browser has failed to start because of an error in the DirectHostBinding parameter to the browser.\r\n


Message:
The Registry Key %1 was not present.  The Sap Agent could not start.\r\n


Message:
Winsock startup routine failed.  The Sap Agent cannot continue.\r\n


Message:
Socket create call failed for main socket. The Sap Agent cannot continue.\r\n


Message:
Setting broadcast option on socket failed.  The Sap Agent cannot continue.\r\n


Message:
Binding to SAP Socket failed.  The Sap Agent cannot continue.\r\n


Message:
Getting bound address of socket failed.  The Sap Agent cannot continue.\r\n


Message:
Setting option EXTENDED_ADDRESS failed.  The Sap Agent cannot continue.\r\n


Message:
Setting NWLink option BCASTINTADDR failed.  The Sap Agent cannot continue.\r\n


Message:
Error allocating memory to hold a card structure.  The Sap Agent cannot continue.\r\n


Message:
Enumeration of cards returned 0 cards.\r\n


Message:
Error creating thread counting event.  The Sap Agent cannot continue.\r\n


Message:
Error creating receive semaphore.  The Sap Agent cannot continue.\r\n


Message:
Error creating send event.  The Sap Agent cannot continue.\r\n


Message:
Error starting receive thread.  The Sap Agent cannot continue.\r\n


Message:
Error starting worker thread.  The Sap Agent cannot continue.\r\n


Message:
Error allocating database array.  The Sap Agent cannot continue.\r\n


Message:
Error allocating hash table.  The Sap Agent cannot continue.\r\n


Message:
Error starting LPC worker thread.  The Sap Agent cannot continue.\r\n


Message:
Error creating the LPC port.  The Sap Agent cannot continue.\r\n


Message:
Error creating the LPC thread event.  The Sap Agent cannot continue.\r\n


Message:
Error allocating memory for an LPC Client structure.  The Sap Agent cannot continue.\r\n


Message:
Error allocating buffer to hold LPC worker thread handles.  The Sap Agent cannot continue.\r\n


Message:
The value for WANFilter in the registry must be 0-2.  The Sap Agent cannot continue.\r\n


Message:
Error creating event for card list access synchronization.  The Sap Agent cannot continue.\r\n


Message:
Error creating event for database access synchronization.  The Sap Agent cannot continue.\r\n


Message:
Error creating WAN control semaphore.  The Sap Agent cannot continue.\r\n


Message:
Socket create call failed for WAN socket.  The Sap Agent cannot continue.\r\n


Message:
Binding to WAN socket failed.  The Sap Agent cannot continue.\r\n


Message:
Error starting WAN worker thread.  The Sap Agent cannot continue.\r\n


Message:
Error starting WAN check thread.  The Sap Agent cannot continue.\r\n


Message:
Error on getsockopt IPX_MAX_ADAPTER_NUM.  Data is the error code.  The Sap Agent cannot continue.\r\n


Message:
Error allocating buffer to hold WAN notify thread handles.  The Sap Agent cannot continue.\r\n


Message:
Error creating the WAN thread event.  The Sap Agent cannot continue.\r\n


Message:
%2 failed to register itself with the NDIS wrapper.\r\n


Message:
%2 failed while setting OID %3 on adapter %4.\r\n


Message:
%2 failed while querying OID %3 on adapter %4.\r\n


Message:
%2 was configured with an internal network number of %3. This network\r\nnumber conflicts with one of the attached networks. The configured\r\ninternal network number will be ignored.\r\n


Message:
%2 had no frame types configured for the binding to adapter %3.\r\n


Message:
%2 failed to initialize because the driver device could not be created.\r\n


Message:
%2 could not bind to any adapters. The transport could not start.\r\n


Message:
Unable to start a DCOM Server: %3.\r\nThe error:%n"%%%2"%nHappened while starting this command:%n%1\r\n


Message:
Unable to start a DCOM Server: %3 as %4/%5.\r\nThe error:%n"%%%2"%nHappened while starting this command:%n%1\r\n


Message:
Access denied attempting to launch a DCOM Server.\r\nThe server is:%n%1%nThe user is %2/%3, SID=%4.\r\n


Message:
Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion.\r\nThe server is:%n%1%nThe user is %2/%3, SID=%4.\r\n


Message:
DCOM got error "%%%1" and was unable to logon %2\\%3\r\nin order to run the server:%n%4\r\n


Message:
An internal error occured in Distributed Link Tracking.  The error code was %1.\r\n


Message:
Service failed to start.  Error = %1\r\n


Message:
The Distributed Link Tracking log was corrupt on volume %1: and has been re-created.  This log is used to automatically repair file links, such as Shell Shortcuts and OLE links, when for some reason those links become broken.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation Service does not support the version (1.0) supported by this LAN Emulation Client.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The LAN Emulation Service does not support the version (1.0) supported by this LAN Emulation Client.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The configuration parameters are incompatible with the desired Emulated LAN.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The join parameters are incompatible with the desired Emulated LAN.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. This LAN Emulation client attempted to register a MAC address (%3) that is already in use by another client.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. This LAN Emulation client attempted to register an ATM address (%3) that is already in use by another client.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation Service does not have sufficient resources to process the request.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The LAN Emulation Service does not have sufficient resources to process the request.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The LAN Emulation Service disallowed this request for security reasons.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The LAN Emulation Service disallowed this request for security reasons.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The supplied LAN Emulation Client ID is invalid.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The supplied LAN Emulation Client ID is invalid.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The supplied MAC Address (%3) cannot be a multicast address or, on an Ethernet/802.3 Emulated LAN, a Route Descriptor.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The supplied MAC Address (%3) cannot be a multicast address or, on an Ethernet/802.3 Emulated LAN, a Route Descriptor.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Configure Request failed. The supplied ATM Address (%3) is not in a recognizable format.\r\n


Message:
Emulated LAN (%2) - LAN Emulation Join Request failed. The supplied ATM Address (%3) is not in a recognizable format.\r\n


Message:
The File Replication Service cannot enable replication on the comptuer %1\r\nuntil a backup/restore application completes.\r\n%n\r\n%nA backup/restore application has set a registry key that\r\nprevents the File Replication Service from starting until the registry\r\nkey is deleted or the system is rebooted.\r\n%n\r\n%nThe backup/restore application may still be running. Check with your\r\nlocal administrator before proceeding further.\r\n%n\r\n%nThe computer can be rebooted by clicking on Start, Shutdown, and\r\nselecting Restart.\r\n%n\r\n%nWARNING - DELETING THE REGISTRY KEY IS NOT RECOMMENDED!\r\nApplications may fail in unexpected ways.\r\n%n\r\n%nThe registry key can be deleted by running regedt32.\r\n%n\r\n%nClick on Start, Run, and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM,\r\nCurrentControlSet, Services, NtFrs, Parameters, Backup/Restore,\r\n"Stop NtFrs from Starting". On the toolbar, click on Edit and select\r\nDelete. Be careful! Deleting a key other than "Stop NtFrs From Starting"\r\ncan have unexpected sideeffects.\r\n


Message:
The File Replication Service is stopping on the computer %1 because\r\na universally unique ID (UUID) cannot be created.\r\n%n\r\n%nThe SDK function UuidCreate() returned the error "%2".\r\n%n\r\n%nThe problem may be the lack of an Ethernet address,\r\ntoken ring address, or network address. The lack of a network\r\naddress implies an unsupported netcard.\r\n%n\r\n%nThe File Replication Service will restart automatically at a later time.\r\nFor more information about the automatic restart right click on\r\nMy Computer and then click on Manage, System Tools, Services,\r\nFile Replication Service, and Recovery.\r\n


Message:
The File Replication Service cannot replicate %1 with the computer\r\n%2 because the computer's SID cannot be determined from the distinguished\r\nname "%3".\r\n%n\r\n%nThe File Replication Service will retry later.\r\n


Message:
The RPC binding failed in the Open function of the FileReplicaSet Object. The\r\ncounter data for this object will not be available. The FileReplicaSet object\r\ncontains the performance counters of the Replica sets whose files are being\r\nreplicated by the File Replication Service.\r\n


Message:
The RPC binding failed in the Open function of the FileReplicaConn Object. The\r\ncounter data for this object will not be available. The FileReplicaConn object\r\ncontains the performance counters of the connections over which files are being\r\nreplicated by the File Replication Service.\r\n


Message:
The RPC call failed in the Open function of the FileReplicaSet Object. The\r\ncounter data for this object will not be available. The FileReplicaSet object\r\ncontains the performance counters of the Replica sets whose files are being\r\nreplicated by the File Replication Service.\r\n


Message:
The RPC call failed in the Open function of the FileReplicaConn Object. The\r\ncounter data for this object will not be available. The FileReplicaConn object\r\ncontains the performance counters of the connections over which files are being\r\nreplicated by the File Replication Service.\r\n


Message:
The RPC binding failed in the Collect function of the FileReplicaSet Object. The\r\ncounter data for this object will not be available till the binding succeeds.\r\nThe FileReplicaSet object contains the performance counters of the Replica sets\r\nwhose files are being replicated by the File Replication Service.\r\n


Message:
The RPC binding failed in the Collect function of the FileReplicaConn Object.\r\nThe counter data for this object will not be available till the binding\r\nsucceeds. The FileReplicaConn object contains the performance counters of the\r\nconnections over which files are being replicated by the File Replication\r\nService.\r\n


Message:
The RPC call failed in the Collect function of the FileReplicaSet Object. The\r\ncounter data for this object will not be available till the call succeeds. The\r\nFileReplicaSet object contains the performance counters of the Replica sets\r\nwhose files are being replicated by the File Replication Service.\r\n


Message:
The RPC call failed in the Collect function of the FileReplicaConn Object. The\r\ncounter data for this object will not be available till the call succeeds. The\r\nFileReplicaConn object contains the performance counters of the connections over\r\nwhich files are being replicated by the File Replication Service.\r\n


Message:
The call to VirtualAlloc failed in the Open function of the FileReplicaSet\r\nObject. The counter data for this object will not be available. The\r\nFileReplicaSet object contains the performance counters of the Replica sets\r\nwhose files are being replicated by the File Replication Service.\r\n


Message:
The call to VirtualAlloc failed in the Open function of the FileReplicaConn\r\nObject. The counter data for this object will not be available. The\r\nFileReplicaConn object contains the performance counters of the connections over\r\nwhich files are being replicated by the File Replication Service.\r\n


Message:
The call to the Registry failed in the Open function of the FileReplicaSet\r\nObject. The counter data for this object will not be available. The\r\nFileReplicaSet object contains the performance counters of the Replica sets\r\nwhose files are being replicated by the File Replication Service.\r\n


Message:
The call to the Registry failed in the Open function of the FileReplicaConn\r\nObject. The counter data for this object will not be available. The\r\nFileReplicaConn object contains the performance counters of the connections over\r\nwhich files are being replicated by the File Replication Service.\r\n


Message:
The File Replication Service cannot replicate %1 because the\r\npathname of the replicated directory is not the fully qualified\r\npathname of an existing, accessible local directory.\r\n


Message:
The File Replication Service cannot replicate %1 because the pathname\r\nof the customer designated staging directory:\r\n%n    %2\r\n%n is not the fully qualified pathname of an existing, accessible local directory.\r\n


Message:
The File Replication Service cannot replicate %1 because it overlaps\r\nthe File Replication Service's logging pathname %2.\r\n


Message:
The File Replication Service cannot replicate %1 because it overlaps\r\nthe File Replication Service's working directory %2.\r\n


Message:
The File Replication Service cannot replicate %1 because it overlaps\r\nthe staging directory %2.\r\n


Message:
The File Replication Service cannot replicate %1 because it overlaps\r\nthe replicating directory %2.\r\n


Message:
The File Replication Service cannot replicate %1 because it overlaps\r\nthe staging directory %2 of the replicating directory %3.\r\n


Message:
The File Replication Service could not prepare the root directory\r\n%1 for replication.  This is likely due to a problem creating the\r\nroot directory or a problem removing preexisting files in the root\r\ndirectory.\r\n%n\r\n%nCheck that the path leading up to the root directory exists and is\r\naccessible.\r\n


Message:
The File Replication Service is unable to replicate with its partner computer\r\nbecause the difference in clock times is outside the range of plus or minus\r\n%1 minutes.\r\n%n\r\n%nThe connection to the partner computer is:\r\n%n  "%2"\r\n%nThe detected time difference is:  %3 minutes.\r\n%n\r\n%nNote: If this time difference is close to a multiple of 60 minutes then it\r\nis likely that either this computer or its partner computer was set to the\r\nincorrect time zone when the computer time was initially set.  Check that\r\nthe time zone and the system time are correctly set on both computers.\r\n%n\r\n%nIf necessary, the default value used to test for computer time consistency\r\nmay be changed in the registry on this computer.  (Note: This is not recommended.)\r\n%n\r\n%nTo change this parameter, run regedt32.\r\n%n\r\n%nClick on Start, Run and type regedt32.\r\n%n\r\n%nClick on the window entitled HKEY_LOCAL_MACHINE.\r\n%nClick down the key path:\r\n%n   "System\\CurrentControlSet\\Services\\NtFrs\\Parameters"\r\n%nDouble click on the value name\r\n%n   "Partner Clock Skew In Minutes"\r\n%nand update the value.\r\n%n\r\n%nIf the value name is not present you may add it with the Add Value function\r\nunder the Edit Menu item. Type the value name exactly as shown above using the\r\nthe registry data type REG_DWORD.\r\n


Message:
The File Replication Service is unable to replicate from a partner computer\r\nbecause the event time associated with the file to be replicated is too far\r\ninto the future.  It is %1 minutes greater than the current time.  This can\r\nhappen if the system time on the partner computer was set incorrectly when\r\nthe file was created or updated.  To preserve the integrity of the replica\r\nset this file update will not be performed or propagated further.\r\n%n\r\n%nThe file name is: "%2"\r\n%nThe connection to the partner computer is:\r\n%n  "%3"\r\n%n\r\n%nNote: If this time difference is close to a multiple of 60 minutes then it\r\nis likely that this file may have been created or updated on the partner\r\ncomputer while the computer was set to the incorrect time zone when its\r\ncomputer time was initially set.  Check that the timezone and time are\r\ncorrectly set on the partner computer.\r\n


Message:
The File Replication Service is unable to open the customer designated\r\nstaging directory for replica set %1.  The path used for the staging\r\ndirectory is,\r\n%n    "%2"\r\n%nThe customer designated root path for this replica set is:\r\n%n    "%3"\r\n%n\r\nThe service is unable to start replication on this replica set.  Among the\r\npossible errors to check are:\r\n%n  --  an invalid staging path,\r\n%n  --  a missing directory,\r\n%n  --  a missing disk volume,\r\n%n  --  a file system on the volume that does not support ACLs,\r\n%n  --  a sharing conflict on the staging directory with some other application.\r\n%n\r\n%nCorrect the problem and the service will attempt to restart replication\r\nautomatically at a later time.\r\n


Message:
The File Replication Service is unable to open (or create) the pre-install\r\ndirectory under the customer designated replica tree directory for\r\nreplica set %1.  The path used for the pre-install\r\ndirectory is,\r\n%n    "%2"\r\n%nThe customer designated root path for this replica set is:\r\n%n    "%3"\r\n%n\r\nThe service is unable to start replication on this replica set.  Among the\r\npossible errors to check are:\r\n%n  --  an invalid root path,\r\n%n  --  a missing directory,\r\n%n  --  a missing disk volume,\r\n%n  --  a file system on the volume that does not support NTFS 5.0\r\n%n  --  a sharing conflict on the pre-install directory with some other application.\r\n%n\r\n%nCorrect the problem and the service will attempt to restart replication\r\nautomatically at a later time.\r\n


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


Message:
QoS: The Packet Scheduler was unable to allocate required resources for initialization.\r\n


Message:
QoS: The Packet Scheduler failed to register as a protocol with NDIS.\r\n


Message:
QoS: The Packet Scheduler failed to register as a miniport with NDIS.\r\n


Message:
QoS [Adapter %2]:%nThe netcard driver failed the query for OID_GEN_MAXIMUM_FRAME_SIZE.\r\n


Message:
QoS [Adapter %2]:%nThe netcard driver failed the query for OID_GEN_MAXIMUM_TOTAL_SIZE.\r\n


Message:
QoS [Adapter %2]:%nThe netcard driver failed the query for OID_GEN_LINK_SPEED.\r\n


Message:
QoS [Adapter %2]:%nThe Packet Scheduler failed to bind to the netcard's miniport driver.\r\n


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


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


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


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


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


Message:
QoS [Adapter %2]:%nCould not allocate non paged pool memory for storing Network Addresses.\r\n


Message:
An extra ExitPoint %2 was found at server %3\r\n


Message:
The ExitPoint %2 was missing at server %3\r\n


Message:
The Volume %2 was missing at server %3\r\n


Message:
The extra Volume %2 was found at server %3\r\n


Message:
The extra ExitPoint %2 was deleted successfully from the server %3\r\n


Message:
Unable to delete the extra ExitPoint %2 at the server %3\r\n


Message:
The missing ExitPoint %2 was created at the server %3 successfully\r\n


Message:
Unable to create the missing Exit Point %2 at the server %3\r\n


Message:
Successfully created the missing volume %2 knowledge at the server %3\r\n


Message:
Unable to create the missing Volume %2 info at server %3\r\n


Message:
The extra Volume %2 info was deleted at server %3\r\n


Message:
The extra Volume %2 info was not deleted at server %3\r\n


Message:
Since the DC %2 was unavailable could not verify volumes knowledge.\r\n


Message:
Detected Knowledge inconsistency with the volume %2 at server %3\r\n


Message:
The local Prefix %2 was represented as %3 at remote server %4\r\n


Message:
The remote Prefix %3 was corrected to %2 at remote server %4\r\n


Message:
The remote Prefix %3 was NOT corrected to %2 at remote server %4\r\n


Message:
The machine %2 has become unlinked from the domain. Re-join the machine the machine to this domain.\r\n


Message:
The server could not find an AT schedule file so it created one.\r\n


Message:
The server could not access the %1 network with NetBiosOpen.\r\n


Message:
The AT command processor could not run %1.\r\n


Message:
WARNING:  Because of a lazy-write error, drive %1 now\r\ncontains some corrupted data.  The cache is stopped.\r\n


Message:
A defective sector on drive %1 has been replaced (hotfixed).\r\nNo data was lost.  You should run CHKDSK soon to restore full\r\nperformance and replenish the volume's spare sector pool.\r\n\r\nThe hotfix occurred while processing a remote request.\r\n


Message:
A disk error occurred on the HPFS volume in drive %1.\r\nThe error occurred while processing a remote request.\r\n


Message:
The user accounts database (NET.ACC) is corrupted.  The local security\r\nsystem is replacing the corrupted NET.ACC with the backup\r\nmade at %1.\r\nAny updates made to the database after this time are lost.\r\n\r\n


Message:
The user accounts database (NET.ACC) is missing.  The local\r\nsecurity system is restoring the backup database\r\nmade at %1.\r\nAny updates made to the database made after this time are lost.\r\n\r\n


Message:
Local security could not be started because the user accounts database\r\n(NET.ACC) was missing or corrupted, and no usable backup\r\ndatabase was present.\r\n\r\nTHE SYSTEM IS NOT SECURE.\r\n


Message:
Local security could not be started because an error\r\noccurred during initialization. The error code returned is %1.\r\n\r\nTHE SYSTEM IS NOT SECURE.\r\n\r\n


Message:
A NetWksta internal error has occurred:\r\n%1\r\n


Message:
The redirector is out of a resource: %1.\r\n


Message:
A server message block (SMB) error occurred on the connection to %1.\r\nThe SMB header is the data.\r\n


Message:
A virtual circuit error occurred on the session to %1.\r\nThe network control block (NCB) command and return code is the data.\r\n


Message:
WINS scavenged its records in the WINS database. The number of records scavenged \r\nis given in the data section.\r\n


Message:
WINS scavenged replica tombstones in the WINS database. The number of records \r\nScavenged is given in the data section.\r\n


Message:
***WINS revalidated old active replicas in the WINS database.\r\n


Message:
WINS Performance Monitor Counters is closing the event log.\r\n


Message:
WINS has deleted records of a partner. The internal ID of the partner whose\r\nrecords were deleted, the minimum version number (low word, high word), and\r\nthe maximum version number (low word, high word) of the records deleted\r\nare given in the data section.\r\n


Message:
WINS was forced to scavenge replica tombstones of a WINS. The person with \r\nadministrative rights on the computer forced the scavenging using winscl.exe. \r\n\r\nWINS does not scavenge replica tombstones unless they have timed out and the \r\nWINS has been running for at least 3 days (This is to ensure that the \r\ntombstones have replicated to other WINSs). In this case, the tombstones were \r\ntimed out but the WINS had not been up for 3 days. The replica tombstones \r\nwere deleted.\r\n \r\nThis deletion does not constitute a problem unless you have WINS servers that \r\nare primary and backup to clients but not both Push and Pull partners of each \r\nother. If you do have such WINSs, there is a low probability that this action \r\nwill result in database inconsistency but if it does (as you will discover \r\neventually), you can get back to a consistent state by initiating consistency \r\nchecks usding winscl.exe. \r\n\r\nNOTE: The consistency check is a network and resource intensive operation, you \r\nshould initiate it only with a full understanding of what it does. You are \r\nbetter off creating the ConsistencyCheck subkey under Wins\\Parameters.\r\n


Message:
***WINS could not read the Initial Challenge Retry Interval from the registry.


Message:
WINS could not read the Challenge Maximum Number of Retries from the registry.


Message:
Adminstrator '%1' initiated a backup of the WINS database.


Message:
Adminstrator '%1' has initiated a scavenging operation.\r\n


Message:
The WINS server has started a scavenging operation.


Message:
The WINS server has completed the scavenging operation.


Message:
Adminstrator '%1' has initiated a consistency check operation.\r\n


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


Message:
Print job %1 has not completed printing on %2.\r\n


Message:
Print job %1 has paused printing on %2.\r\n


Message:
The attempt to remove an older version of the Directory Service performance\r\ncounters failed with the following error:%n\r\n%n\r\n%1\r\n%n\r\nThe record data is the status code.\r\n


Message:
The attempt to register the Directory Service performance counters failed with\r\nthe following error:%n\r\n%n\r\n%1\r\n%n\r\nThe record data is the status code.  This operation will be retried in %2\r\nminutes.\r\n


Message:
Unable to disable disk write cache on %1. Data might be lost during system failures.\r\n


Message:
Unable to establish connection with global catalog\r\n


Message:
Error %1(%2) has occurred (Internal ID %3).  Please contact Microsoft Product Support Services for assistance.\r\n


Message:
A thread in the directory is waiting in a remote procedure call (RPC) to\r\ndirectory %1 performing a(n) %3 operation.  The directory has attempted to\r\ncancel the call and recover thread id %2.  If this condition persists, stop\r\nand restart that Windows Domain Controller.\r\n


Message:
Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.


Message:
For security reasons, the operation must be run on the destination DC.


Message:
Critical Directory Service System objects cannot be deleted during tree delete operations.  The tree delete may have been partially performed.


Message:
An event was unable to invoke any of the subscribers


Message:
The DNS Client service could not contact any DNS servers for a repeated number of attempts. For the next %3 seconds the DNS Client service will not use the network to avoid further network performance problems. It will resume its normal behavior after that. If this problem persists, verify your TCP/IP configuration, specifically check that you have a preferred (and possibly an alternate) DNS server configured. If the problem continues, verify network conditions to these DNS servers or contact your network administrator.


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:
Unable to open driver containing SFM file server performance data.\r\n  To view the MacFile counters from Perfmon.exe, make sure the MacFile service has been started.\r\n


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


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


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


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


Message:
Not used\r\nThe AppleTalk Print Monitor has started.\r\n


Message:
An attempt was made to send a print job to an AppleTalk printer while\r\nthe AppleTalk Protocol device was stopped.  \r\n


Message:
Not used\r\nThe printer returned the following status message when an attempt was made\r\nto print a job: %1\r\n


Message:
Not used\r\nThe printer %1 cannot be found on the AppleTalk network.  The print job has\r\nbeen deleted.\r\n


Message:
Not used\r\nThere was a communication problem with the printer %1. The print job has\r\nbeen deleted.\r\n


Message:
Unable to intialize Windows Sockets for AppleTalk protocol. Ensure that AppleTalk is correctly configured.\r\n


Message:
An error was reported while attempting to initialize the monitor with the \r\nlist of port information from the registry. \r\nThe information is located in the key \r\nSYSTEM\\CurrentControlSet\\Control\\Print\\Monitors\\AppleTalk Printing Devices\r\nThe error code is in the data.\r\n


Message:
The Macintosh-Accessible volume name specified is invalid.\r\nSpecify a valid volume name without colons.\r\n


Message:
A system resource could not be accessed for the current descriptor.\r\nTry the operation again.\r\n


Message:
The parameter entered was invalid. \r\nMake the appropriate changes and retry the operation.\r\n


Message:
Error in accessing Macintosh Code Page.\r\nCheck if the Code Page file name specified in\r\nSYSTEM\\CurrentControlSet\\Control\\Nls\\CodePage\\MACCP is valid and exists.\r\nStop and restart the service if the code page information is modified.\r\n


Message:
The server name specified is invalid.\r\nSpecify a valid server name without colons.\r\n


Message:
A volume with this name already exists.\r\nSpecify another name for the new volume.\r\n


Message:
The selected Macintosh-Accessible volume is currently in use by Macintoshes.\r\nThe selected volume may be removed only when no Macintosh workstations are\r\nconnected to it.\r\n


Message:
Not used\r\nAn internal error 6008 (VolumeReadOnly) occurred.\r\n


Message:
The selected directory does not belong to a Macintosh-Accessible volume.\r\nThe Macintosh view of directory permissions is only available for\r\ndirectories that are part of a Macintosh-Accessible volume.\r\n


Message:
The Macintosh view of directory permissions is not available for directories\r\non CD-ROM disks.\r\n


Message:
Insufficient memory resources to complete the operation.\r\nTry the operation again.\r\n


Message:
This file extension is already associated with a Creator/Type item.\r\n


Message:
File Server for Macintosh service only supports NTFS partitions.\r\nChoose a directory on an NTFS partition.\r\n


Message:
Certificate Services did not start: The Certificate Revocation List Period string is invalid in the registry value HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CertSvc\\Configuration\\%1\\CRLPeriod.  Valid strings are "Seconds", "Minutes", "Hours", "Days", "Weeks", "Months" and "Years".\r\n


Message:
Certificate Services did not start: Not enough memory or other system resources.\r\n


Message:
Certificate Services did not start: The chain of Certification Authority certificates is not properly configured.\r\n


Message:
Certificate Services did not start: Could not schedule automatic Certificate Revocation List publication for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not create the Certificate Server service thread for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not initialize RPC for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not initialize OLE for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not convert the Unicode authority name to look up the Certification Authority certificate for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not decode the Certification Authority certificate for %1.  %2.\r\n


Message:
Certificate Services did not start: The Certification Authority DCOM class for %1 could not be registered.  %2.  Use the services administration tool to change the Certification Authority logon context.\r\n


Message:
Certificate Services did not start: Could not initialize DCOM class factories for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not initialize DCOM Security Context for %1.  %2.\r\n


Message:
Certificate Services did not start: Could not build CA certificate chain for %1.  %2.\r\n


Message:
The "%1" Policy Module "%2" method caused an exception at address %4.  The exception code is %3.\r\n


Message:
The "%1" Policy Module "%2" method returned an error.  The returned status code is %3.  %4\r\n


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


Message:
The Windows NT or Windows 2000 %1 logon request for the user %2\\%3 from %4 (via %5)\r\nfailed.\r\n


Message:
The Windows NT or Windows 2000 %1 logoff request for the user %2\\%3 from %4\r\nfailed.\r\n


Message:
The partial synchronization request from the server %1 completed\r\nsuccessfully. %2 changes(s) has(have) been returned to the\r\ncaller.\r\n


Message:
The partial synchronization request from the server %1 failed with\r\nthe following error: %n%2\r\n


Message:
The full synchronization request from the server %1 completed\r\nsuccessfully. %2 object(s) has(have) been returned to\r\nthe caller.\r\n


Message:
This operation cannot be performed on the print destination in its current state.\r\n


Message:
This operation cannot be performed on the printer queue in its current state.\r\n


Message:
This operation cannot be performed on the print job in its current state.\r\n


Message:
A spooler memory allocation failure occurred.\r\n


Message:
The data type is not supported by the print processor.\r\n


Message:
The print processor is not installed.\r\n


Message:
The requested service has already been started.\r\n


Message:
The service does not respond to control actions.\r\n


Message:
The service is not responding to the control function.\r\n


Message:
The configuration file contains an invalid service program name.\r\n


Message:
The service could not be controlled in its present state.\r\n


Message:
The requested pause or stop is not valid for this service.\r\n


Message:
The service control dispatcher could not find the service name in the dispatch table.\r\n


Message:
The service control dispatcher pipe read failed.\r\n


Message:
A thread for the new service could not be created.\r\n


Message:
This workstation is already logged on to the local-area network.\r\n


Message:
The workstation is not logged on to the local-area network.\r\n


Message:
The user name or group name parameter is invalid.\r\n


Message:
The logon processor did not add the message alias.\r\n


Message:
The logoff processor did not delete the message alias.\r\n


Message:
A centralized logon-server conflict occurred.\r\n


Message:
The server is configured without a valid user path.\r\n


Message:
An error occurred while loading or running the logon script.\r\n


Message:
The logon server was not specified.  Your computer will be logged on as STANDALONE.\r\n


Message:
The logon server could not be found.\r\n


Message:
There is already a logon domain for this computer.\r\n


Message:
The logon server could not validate the logon.\r\n


Message:
The security database could not be found.\r\n


Message:
The resource name could not be found.\r\n


Message:
The resource permission list already exists.\r\n


Message:
This operation is only allowed on the primary domain controller of the domain.\r\n


Message:
The security database has not been started.\r\n


Message:
There are too many names in the user accounts database.\r\n


Message:
The limit of 64 entries per resource was exceeded.\r\n


Message:
Deleting a user with a session is not allowed.\r\n


Message:
The parent directory could not be located.\r\n


Message:
Unable to add to the security database session cache segment.\r\n


Message:
This operation is not allowed on this special group.\r\n


Message:
This user is not cached in user accounts database session cache.\r\n


Message:
The user already belongs to this group.\r\n


Message:
The user does not belong to this group.\r\n


Message:
The user is not allowed to log on from this workstation.\r\n


Message:
The user is not allowed to log on at this time.\r\n


Message:
The password of this user has expired.\r\n


Message:
The password of this user cannot change.\r\n


Message:
The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.\r\n


Message:
The password of this user is too recent to change.\r\n


Message:
No updates are necessary to this replicant network/local security database.\r\n


Message:
This replicant database is outdated; synchronization is required.\r\n


Message:
The network connection could not be found.\r\n


Message:
This device is currently being shared.\r\n


Message:
The computer name could not be added as a message alias.  The name may already exist on the network.\r\n


Message:
The Messenger service is already started.\r\n


Message:
The Messenger service failed to start.\r\n


Message:
The message alias could not be found on the network.\r\n


Message:
This message alias has already been forwarded.\r\n


Message:
This message alias has been added but is still forwarded.\r\n


Message:
This message alias already exists locally.\r\n


Message:
The maximum number of added message aliases has been exceeded.\r\n


Message:
The computer name could not be deleted.\r\n


Message:
Messages cannot be forwarded back to the same workstation.\r\n


Message:
An error occurred in the domain message processor.\r\n


Message:
The message was sent, but the recipient has paused the Messenger service.\r\n


Message:
The message was sent but not received.\r\n


Message:
The message alias is currently in use. Try again later.\r\n


Message:
The Messenger service has not been started.\r\n


Message:
The name is not on the local computer.\r\n


Message:
The forwarded message alias could not be found on the network.\r\n


Message:
The message alias table on the remote station is full.\r\n


Message:
Messages for this alias are not currently being forwarded.\r\n


Message:
The broadcast message was truncated.\r\n


Message:
A duplicate message alias exists on the network.\r\n


Message:
This message alias will be deleted later.\r\n


Message:
The message alias was not successfully deleted from all networks.\r\n


Message:
This operation is not supported on computers with multiple networks.\r\n


Message:
This shared resource does not exist.\r\n


Message:
A session does not exist with that computer name.\r\n


Message:
There is not an open file with that identification number.\r\n


Message:
A failure occurred when executing a remote administration command.\r\n


Message:
A failure occurred when opening a remote temporary file.\r\n


Message:
The data returned from a remote administration command has been truncated to 64K.\r\n


Message:
This device cannot be shared as both a spooled and a non-spooled resource.\r\n


Message:
The information in the list of servers may be incorrect.\r\n


Message:
The computer is not active in this domain.\r\n


Message:
The share must be removed from the Distributed File System before it can be deleted.\r\n


Message:
The operation is invalid for this device.\r\n


Message:
There are no shared communication devices.\r\n


Message:
The queue you specified does not exist.\r\n


Message:
This device is already in use by the spooler.\r\n


Message:
This device is already in use as a communication device.\r\n


Message:
The string and prefix specified are too long.\r\n


Message:
Could not determine the type of input.\r\n


Message:
The buffer for types is not big enough.\r\n


Message:
The system cannot delete current connections to network resources.\r\n


Message:
The system was unable to parse the command line in this file.\r\n


Message:
An error occurred while loading the profile file.\r\n


Message:
Errors occurred while saving the profile file.  The profile was partially saved.\r\n


Message:
This log file has changed between reads.\r\n


Message:
The source path cannot be a directory.\r\n


Message:
The source and destination paths are on different servers.\r\n


Message:
The Run server you requested is paused.\r\n


Message:
An error occurred when communicating with a Run server.\r\n


Message:
An error occurred when starting a background process.\r\n


Message:
The shared resource you are connected to could not be found.\r\n


Message:
There are open files on the connection.\r\n


Message:
This share name or password is invalid.\r\n


Message:
The device is being accessed by an active process.\r\n


Message:
The specified client is already registered for the specified event.\r\n


Message:
An invalid or nonexistent alert name was raised.\r\n


Message:
A user's session with this server has been deleted\r\nbecause the user's logon hours are no longer valid.\r\n


Message:
The log file does not contain the requested record number.\r\n


Message:
The user accounts database is not configured correctly.\r\n


Message:
This operation is not permitted when the Netlogon service is running.\r\n


Message:
This operation is not allowed on the last administrative account.\r\n


Message:
Could not find domain controller for this domain.\r\n


Message:
Could not set logon information for this user.\r\n


Message:
The Netlogon service has not been started.\r\n


Message:
Unable to add to the user accounts database.\r\n


Message:
This server's clock is not synchronized with the primary domain controller's clock.\r\n


Message:
A password mismatch has been detected.\r\n


Message:
The server identification does not specify a valid server.\r\n


Message:
The session identification does not specify a valid session.\r\n


Message:
The connection identification does not specify a valid connection.\r\n


Message:
There is no space for another entry in the table of available servers.\r\n


Message:
The server has reached the maximum number of sessions it supports.\r\n


Message:
The server has reached the maximum number of connections it supports.\r\n


Message:
The server cannot open more files because it has reached its maximum number.\r\n


Message:
There are no alternate servers registered on this server.\r\n


Message:
Try down-level (remote admin protocol) version of API instead.\r\n


Message:
The UPS driver could not be accessed by the UPS service.\r\n


Message:
The UPS service is not configured correctly.\r\n


Message:
The UPS service could not access the specified Comm Port.\r\n


Message:
The UPS indicated a line fail or low battery situation. Service not started.\r\n


Message:
The UPS service failed to perform a system shut down.\r\n


Message:
The program below returned an MS-DOS error code:\r\n


Message:
The program below needs more memory:\r\n


Message:
The program below called an unsupported MS-DOS function:\r\n


Message:
No loader is specified in the boot-block definition file.\r\n


Message:
NetBIOS returned an error: The NCB and SMB are dumped above.\r\n


Message:
Too many image parameters cross disk sector boundaries.\r\n


Message:
The image was not generated from an MS-DOS diskette formatted with /S.\r\n


Message:
Remote boot will be restarted later.\r\n


Message:
The call to the Remoteboot server failed.\r\n


Message:
Cannot connect to the Remoteboot server.\r\n


Message:
Cannot open image file on the Remoteboot server.\r\n


Message:
Connecting to the Remoteboot server...\r\n


Message:
Remote boot service was stopped; check the error log for the cause of the problem.\r\n


Message:
Remote boot startup failed; check the error log for the cause of the problem.\r\n


Message:
A second connection to a Remoteboot resource is not allowed.\r\n


Message:
The browser service was configured with MaintainServerList=No.\r\n


Message:
Service failed to start since none of the network adapters started with this service.\r\n


Message:
Service failed to start due to bad startup information in the registry.\r\n


Message:
Service failed to start because its database is absent or corrupt.\r\n


Message:
Service failed to start because RPLFILES share is absent.\r\n


Message:
Service failed to start because RPLUSER group is absent.\r\n


Message:
Workstation record information has been corrupted.\r\n


Message:
Workstation name is in use by some other workstation.\r\n


Message:
Profile record information has been corrupted.\r\n


Message:
Profile name is in use by some other profile.\r\n


Message:
There are workstations using this profile.\r\n


Message:
Configuration record information has been corrupted.\r\n


Message:
Adapter id record information has been corrupted.\r\n


Message:
An internal service error has occurred.\r\n


Message:
Vendor id record information has been corrupted.\r\n


Message:
Boot block record information has been corrupted.\r\n


Message:
The user account for this workstation record is missing.\r\n


Message:
The RPLUSER local group could not be found.\r\n


Message:
Chosen profile is incompatible with this workstation.\r\n


Message:
Chosen network adapter id is in use by some other workstation.\r\n


Message:
There are profiles using this configuration.\r\n


Message:
There are workstations, profiles or configurations using this boot block.\r\n


Message:
Service failed to backup Remoteboot database.\r\n


Message:
Vendor name is in use by some other vendor record.\r\n


Message:
(boot name, vendor id) is in use by some other boot block record.\r\n


Message:
Configuration name is in use by some other configuration.\r\n


Message:
The internal database maintained by the Dfs service is corrupt\r\n


Message:
One of the records in the internal Dfs database is corrupt\r\n


Message:
There is no volume whose entry path matches the input Entry Path\r\n


Message:
A volume with the given name already exists\r\n


Message:
The server share specified is already shared in the Dfs\r\n


Message:
The indicated server share does not support the indicated Dfs volume\r\n


Message:
The operation is not valid on a non-leaf volume\r\n


Message:
The operation is not valid on a leaf volume\r\n


Message:
The operation is ambiguous because the volume has multiple servers\r\n


Message:
The specified rename target path is invalid\r\n


Message:
The specified server is not a server for this volume\r\n


Message:
A cycle in the Dfs name was detected\r\n


Message:
The operation is not supported on a server-based Dfs\r\n


Message:
This volume is already supported by the specified server-share\r\n


Message:
Can't remove the last server-share supporting this volume\r\n


Message:
The operation is not supported for an Inter-Dfs volume\r\n


Message:
The internal state of the Dfs Service has become inconsistent\r\n


Message:
The Dfs Service has been installed on the specified server\r\n


Message:
The Dfs data being reconciled is identical\r\n


Message:
The Dfs root volume cannot be deleted - Uninstall Dfs if required\r\n


Message:
A child or parent directory of the share is already in a Dfs\r\n


Message:
This machine is already joined to a domain.\r\n


Message:
This machine is not currently joined to a domain.\r\n


Message:
This machine is a domain controller and cannot be unjoined from a domain.\r\n


Message:
The destination domain controller does not support creating machine accounts in OUs.\r\n


Message:
The specified workgroup name is invalid\r\n


Message:
The specified computer name is incompatible with the default language used on the domain controller.\r\n


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


Message:
This is the last error in NERR range.\r\n


Message:
Drive %1 is nearly full. %2 bytes are available.\r\nPlease warn users and delete unneeded files.\r\n


Message:
%1 errors were logged in the last %2 minutes.\r\nPlease review the server's error log.\r\n


Message:
%1 network errors occurred in the last %2 minutes.\r\nPlease review the server's error log.  The server and/or\r\nnetwork hardware may need service.\r\n


Message:
There were %1 bad password attempts in the last %2 minutes.\r\nPlease review the server's audit trail.\r\n


Message:
There were %1 access-denied errors in the last %2 minutes.\r\nPlease review the server's audit trail.\r\n


Message:
The error log is full.  No errors will be logged until\r\nthe file is cleared or the limit is raised.\r\n


Message:
The audit log is full.  No audit entries will be logged\r\nuntil the file is cleared or the limit is raised.\r\n


Message:
An error occurred closing file %1.\r\nPlease check the file to make sure it is not corrupted.\r\n


Message:
There were %1 access-denied errors in the last %2 minutes.\r\n


Message:
A power failure was detected at %1.  The server has been paused.\r\n


Message:
Power has been restored at %1.  The server is no longer paused.\r\n


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


Message:
There is a problem with a configuration of user specified\r\nshut down command file.  The UPS service started anyway.\r\n


Message:
The user accounts database (NET.ACC) is corrupted.  The local security\r\nsystem is replacing the corrupted NET.ACC with the backup\r\nmade on %1 at %2.\r\nAny updates made to the database after this time are lost.\r\n\r\n


Message:
The user accounts database (NET.ACC) is missing. The local\r\nsecurity system is restoring the backup database\r\nmade on %1 at %2.\r\nAny updates made to the database after this time are lost.\r\n\r\n


Message:
Local security could not be started because the user accounts database\r\n(NET.ACC) was missing or corrupted, and no usable backup\r\ndatabase was present.\r\n\r\nTHE SYSTEM IS NOT SECURE.\r\n\r\n


Message:
The server cannot export directory %1, to client %2.\r\nIt is exported from another server.\r\n


Message:
The replication server could not update directory %2 from the source\r\non %3 due to error %1.\r\n


Message:
Master %1 did not send an update notice for directory %2 at the expected\r\ntime.\r\n


Message:
User %1 has exceeded account limitation %2 on server %3.\r\n


Message:
The primary domain controller for domain %1 failed.\r\n


Message:
Failed to authenticate with %2, a Windows NT Domain Controller for\r\ndomain %1.\r\n


Message:
The replicator attempted to log on at %2 as %1 and failed.\r\n


Message:
Replicator could not access %2\r\non %3 due to system error %1.\r\n


Message:
Replicator limit for files in a directory has been exceeded.\r\n


Message:
Replicator limit for tree depth has been exceeded.\r\n


Message:
The replicator cannot update directory %1. It has tree integrity\r\nand is the current directory for some process.\r\n


Message:
Cannot log on. User is currently logged on and argument TRYUSER\r\nis set to NO.\r\n


Message:
Replicated data has changed in directory %1.\r\n


Message:
Replicator failed to update signal file in directory %2 due to\r\n%1 system error.\r\n


Message:
The Registry or the information you just typed includes an illegal\r\nvalue for "%1".\r\n


Message:
The required parameter was not provided on the command\r\nline or in the configuration file.\r\n


Message:
LAN Manager does not recognize "%1" as a valid option.\r\n


Message:
A request for resource could not be satisfied.\r\n


Message:
A problem exists with the system configuration.\r\n


Message:
An internal consistency error has occurred.\r\n


Message:
The configuration file or the command line has an ambiguous option.\r\n


Message:
The configuration file or the command line has a duplicate parameter.\r\n


Message:
The service did not respond to control and was stopped with\r\nthe DosKillProc function.\r\n


Message:
An error occurred when attempting to run the service program.\r\n


Message:
There is a conflict in the value or use of these options: %1.\r\n


Message:
Bad or missing LAN Manager root directory.\r\n


Message:
The network software is not installed.\r\n


Message:
The server cannot access the user accounts database (NET.ACC).\r\n


Message:
Incompatible files are installed in the LANMAN tree.\r\n


Message:
The domain specified could not be used.\r\n


Message:
The computer name is being used as a message alias on another computer.\r\n


Message:
The announcement of the server name failed.\r\n


Message:
The server is not running with user-level security.\r\n


Message:
The workstation is not configured properly.\r\n


Message:
ADDPAK file is corrupted.  Delete LANMAN\\NETPROG\\ADDPAK.SER\r\nand reapply all ADDPAKs.\r\n


Message:
The LM386 server cannot be started because CACHE.EXE is not running.\r\n


Message:
There is no account for this computer in the security database.\r\n


Message:
This computer is not a member of the group SERVERS.\r\n


Message:
The group SERVERS is not present in the local security database.\r\n


Message:
This Windows NT computer is configured as a member of a workgroup, not as\r\na member of a domain. The Netlogon service does not need to run in this\r\nconfiguration.\r\n


Message:
The Windows NT domain controller for this domain could not be located.\r\n


Message:
This computer is configured to be the primary domain controller of its domain.\r\nHowever, the computer %1 is currently claiming to be the primary domain controller\r\nof the domain.\r\n


Message:
The service failed to authenticate with the primary domain controller.\r\n


Message:
There is a problem with the security database creation date or serial number.\r\n


Message:
The operation failed because a network software error occurred.\r\n


Message:
The system ran out of a resource controlled by the %1 option.\r\n


Message:
The service failed to obtain a long-term lock on the\r\nsegment for network control blocks (NCBs). The error code is the data.\r\n


Message:
The service failed to release the long-term lock on the\r\nsegment for network control blocks (NCBs). The error code is the data.\r\n


Message:
There was an error stopping service %1.\r\nThe error code from NetServiceControl is the data.\r\n


Message:
Initialization failed because of a system execution failure on\r\npath %1. The system error code is the data.\r\n


Message:
An unexpected network control block (NCB) was received. The NCB is the data.\r\n


Message:
A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed.\r\nThe data shown is in this format:\r\nDWORD  approx CS:IP of call to ioctl or fsctl\r\nWORD   error code\r\nWORD   ioctl or fsctl number\r\n


Message:
Unable to create or open system semaphore %1.\r\nThe error code is the data.\r\n


Message:
Initialization failed because of an open/create error on the\r\nfile %1. The system error code is the data.\r\n


Message:
An unexpected NetBIOS error occurred.\r\nThe error code is the data.\r\n


Message:
An illegal server message block (SMB) was received.\r\nThe SMB is the data.\r\n


Message:
Initialization failed because the requested service %1\r\ncould not be started.\r\n


Message:
Some entries in the error log were lost because of a buffer\r\noverflow.\r\n


Message:
Initialization parameters controlling resource usage other\r\nthan net buffers are sized so that too much memory is needed.\r\n


Message:
The server cannot increase the size of a memory segment.\r\n


Message:
Initialization failed because account file %1 is either incorrect\r\nor not present.\r\n


Message:
Initialization failed because network %1 was not started.\r\n


Message:
The workstation encountered an error while responding to an SSI revalidation request.\r\nThe function code and the error codes are the data.\r\n


Message:
The Alerter service had a problem creating the list of\r\nalert recipients.  The error code is %1.\r\n


Message:
There was an error expanding %1 as a group name. Try\r\nsplitting the group into two or more smaller groups.\r\n


Message:
There was an error sending %2 the alert message -\r\n(\r\n%3 )\r\nThe error code is %1.\r\n


Message:
There was an error in creating or reading the alerter mailslot.\r\nThe error code is %1.\r\n


Message:
The server could not read the AT schedule file.\r\n


Message:
The server found an invalid AT schedule record.\r\n


Message:
A network control block (NCB) error occurred (%1).\r\nThe NCB is the data.\r\n


Message:
A write operation to %1 failed.\r\nData may have been lost.\r\n


Message:
Reset of driver %1 failed to complete the network control block (NCB).\r\nThe NCB is the data.\r\n


Message:
The amount of resource %1 requested was more\r\nthan the maximum. The maximum amount was allocated.\r\n


Message:
The server could not create a thread.\r\nThe THREADS parameter in the CONFIG.SYS file should be increased.\r\n


Message:
The server could not close %1.\r\nThe file is probably corrupted.\r\n


Message:
The server cannot export directory %1 to client %2.\r\nIt is exported from another server.\r\n


Message:
Failed to authenticate with %2, a Windows NT domain controller for domain %1.\r\n


Message:
Unrecognized message received in mailslot.\r\n


Message:
The primary domain controller for domain %1 has apparently failed.\r\n


Message:
Changing machine account password for account %1 failed with\r\nthe following error: %n%2\r\n


Message:
An error occurred while updating the logon or logoff information for %1.\r\n


Message:
An error occurred while synchronizing with primary domain controller %1\r\n


Message:
The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2\r\nfailed because %1 does not support signing or sealing the Netlogon\r\nsession.\r\n\r\nEither upgrade the Domain controller or set the RequireSignOrSeal\r\nregistry entry on this machine to 0.\r\n


Message:
A power failure was detected at the server.\r\n


Message:
The UPS service performed server shut down.\r\n


Message:
The UPS service did not complete execution of the\r\nuser specified shut down command file.\r\n


Message:
The UPS driver could not be opened.  The error code is\r\nthe data.\r\n


Message:
There is a problem with a configuration of user specified\r\nshut down command file.\r\n


Message:
The UPS service failed to execute a user specified shutdown\r\ncommand file %1.  The error code is the data.\r\n


Message:
Initialization failed because of an invalid or missing\r\nparameter in the configuration file %1.\r\n


Message:
Initialization failed because of an invalid line in the\r\nconfiguration file %1. The invalid line is the data.\r\n


Message:
Initialization failed because of an error in the configuration\r\nfile %1.\r\n


Message:
The file %1 has been changed after initialization.\r\nThe boot-block loading was temporarily terminated.\r\n


Message:
The files do not fit to the boot-block configuration\r\nfile %1. Change the BASE and ORG definitions or the order\r\nof the files.\r\n


Message:
Initialization failed because the dynamic-link\r\nlibrary %1 returned an incorrect version number.\r\n


Message:
There was an unrecoverable error in the dynamic-\r\nlink library of the service.\r\n


Message:
The system returned an unexpected error code.\r\nThe error code is the data.\r\n


Message:
The fault-tolerance error log file, LANROOT\\LOGS\\FT.LOG,\r\nis more than 64K.\r\n


Message:
The fault-tolerance error-log file, LANROOT\\LOGS\\FT.LOG, had the\r\nupdate in progress bit set upon opening, which means that the\r\nsystem crashed while working on the error log.\r\n


Message:
There is not enough memory to start the Workstation service.\r\n


Message:
An error occurred when reading the NETWORKS entry in the LANMAN.INI file.\r\n


Message:
The %1 NETWORKS entry in the LANMAN.INI file has a\r\nsyntax error and will be ignored.\r\n


Message:
There are too many NETWORKS entries in the LANMAN.INI file.\r\n


Message:
An error occurred when opening network\r\ndevice driver %1 = %2.\r\n


Message:
Device driver %1 sent a bad BiosLinkage response.\r\n


Message:
The program cannot be used with this operating system.\r\n


Message:
The redirector is already installed.\r\n


Message:
Installing NETWKSTA.SYS Version %1.%2.%3  (%4)\r\n\r\n


Message:
There was an error installing NETWKSTA.SYS.\r\n\r\nPress ENTER to continue.\r\n


Message:
Your logon time at %1 ends at %2.\r\nPlease clean up and log off.\r\n


Message:
You will be automatically disconnected at %1.\r\n


Message:
WARNING: You have until %1 to logoff. If you\r\nhave not logged off at this time, your session will be\r\ndisconnected, and any open files or devices you\r\nhave open may lose data.\r\n


Message:
WARNING: You must log off at %1 now.  You have\r\ntwo minutes to log off, or you will be disconnected.\r\n


Message:
You have open files or devices, and a forced\r\ndisconnection may cause you to lose data.\r\n


Message:
The command contains an invalid number of arguments.\r\n


Message:
The command completed with one or more errors.\r\n


Message:
You used an option with an invalid value.\r\n


Message:
A command was used with conflicting switches.\r\n


Message:
The software requires a newer version of the operating\r\nsystem.\r\n


Message:
More data is available than can be returned by Windows 2000.\r\n


Message:
More help is available by typing NET HELPMSG %1.\r\n


Message:
This command can be used only on a Windows 2000 Domain Controller.\r\n


Message:
This command cannot be used on a Windows 2000 Domain Controller.\r\n


Message:
These Windows 2000 services are started:\r\n


Message:
The %1 service could not be started.\r\n


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


Message:
Stopping the Workstation service also stops the Server service.\r\n


Message:
The %1 service could not be stopped.\r\n


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


Message:
The following services are dependent on the %1 service.\r\nStopping the %1 service will also stop these services.\r\n


