MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  L@.rsrc@@( @Xp   DMUIъ2#[N__L:6(k)x~;kv MUI en-USLLYZ88(  @ @@ i@k@ @@0@@8{@|@@@@@ M@O@X@X@[@_@a@a@c@c@1#@3#@%@%@ +@+@"0@0@p(0@0@(4@4@P/4@4@d04@4@27@7@7@8@G8@T88@8@<8@8@,>8@8@>8@8@4?8@8@4A8@8@XB8@8@LC8@8@0D8@8@Et@@@@FHUU Y b 8c Hk n lo ht^^``ćeeЈlmTPԢ$ХXuvhxy{}ܱtDFܵUWM!M!)#+#%%*+++++++600t0044؍4444444444X44h44x444477777788@884888888`88995:8:X>>4@@,hBhB\   Y] __LadDfhl0|pXL  80X[|]z}~ 27>>CC@GKdBPQESTdJ``$Mbb$NddN4!L!ON!U!p^,#0#\c %#%e''h-'.'t**\v0000T44t444444,4444444444D4444:66C77lF77xL 7 7$M77M88V88HY888d88f88f88i88Po88s99tl9p9}>>" to verify that a DNS server is available. The DNS mapping for %2 or %1 can be verified by typing "nslookup" and then typing "%2" and then "%1" on %1 and %2. Be sure to check out the DNS server on both %1 and %2; a DNS problem on either computer will prevent proper communication. %n %nSome network problems between %1 and %2 can be cleared up by flushing the DNS Resolver Cache. Type "ipconfig /flushdns". %n %nSome network problems between %1 and %2 can be cleared up by renewing the IP address. Type "ipconfig /release" followed by "ipconfig /renew". %n %nSome network problems between %1 and %2 can be cleared up by resetting the computer's DNS entry. Type "net stop NetLogon" followed by "net start NetLogon". %n %nSome problems between %1 and %2 can be cleared up by restarting the File Replication Service. Type "net stop ntfrs" followed by "net start ntfrs". %n %nSome problems between %1 and %2 can be cleared up by restarting the computers %1 and %2 AFTER CLOSING RUNNING APPLIATIONS, especially dcpromo. Click on Start, Shutdown, select Restart, and click on OK. %n %nOther network and computer problems are beyond the scope of this event log message. The File Replication Service is stopping on computer %1 because there is no free space on the volume containing %2. %n %nThe available space on the volume can be found by typing "dir %2". %n %nOnce free space is made available on the volume containing %2, the File Replication Service can be restarted immediately by typing "net start ntfrs". Otherwise, the File Replication Service will restart automatically at a later time. %n %nFor more information about the automatic restart right click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery. %n %nFor more information about managing space on a volume type "copy /?", "rename /?", "del /?", "rmdir /?", and "dir /?". hThe File Replication Service on computer %1 is stopping because the database %2 is corrupted. %n %nThe database can be recovered by typing "esentutl /d %2 /l%3 /s%4". %n %nOnce the database has been successfully recovered the File Replication Service can be restarted by typing "net start ntfrs". The File Replication Service could not grant an unknown user access to the API "%1". %n %nAccess checks can be disabled for "%1" by running regedt32. %n %nClick on Start, Run, and type regedt32. %n %nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Access Checks, "%1", and "%2". Change the string to Disabled. %n %nPermissions can be changed by highlighting "%1" and then clicking on the toolbar option Security and then Permissions... @The File Replication Service cannot enable replication on the comptuer %1 until a backup/restore application completes. %n %nA backup/restore application has set a registry key that prevents the File Replication Service from starting until the registry key is deleted or the system is rebooted. %n %nThe backup/restore application may still be running. Check with your local administrator before proceeding further. %n %nThe computer can be rebooted by clicking on Start, Shutdown, and selecting Restart. %n %nWARNING - DELETING THE REGISTRY KEY IS NOT RECOMMENDED! Applications may fail in unexpected ways. %n %nThe registry key can be deleted by running regedt32. %n %nClick on Start, Run, and type regedt32. %n %nClick on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Backup/Restore, "Stop NtFrs from Starting". On the toolbar, click on Edit and select Delete. Be careful! Deleting a key other than "Stop NtFrs From Starting" can have unexpected sideeffects. The File Replication Service is stopping on the computer %1 because a universally unique ID (UUID) cannot be created. %n %nThe SDK function UuidCreate() returned the error "%2". %n %nThe problem may be the lack of an Ethernet address, token ring address, or network address. The lack of a network address implies an unsupported netcard. %n %nThe File Replication Service will restart automatically at a later time. For more information about the automatic restart right click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery. The File Replication Service cannot replicate %1 with the computer %2 because the computer's SID cannot be determined from the distinguished name "%3". %n %nThe File Replication Service will retry later. 8The RPC binding failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service. DThe RPC binding failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service. 0The RPC call failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service. <The RPC call failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service. pThe RPC binding failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be available till the binding succeeds. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service. The RPC binding failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be available till the binding succeeds. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service. dThe RPC call failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be available till the call succeeds. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service. pThe RPC call failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be available till the call succeeds. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service. HThe call to VirtualAlloc failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service. TThe call to VirtualAlloc failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service. HThe call to the Registry failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service. TThe call to the Registry failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. The FileReplicaConn object contains the performance counters of the connections over which files are being replicated by the File Replication Service. pThe File Replication Service cannot replicate %1 because the pathname of the replicated directory is not the fully qualified pathname of an existing, accessible local directory. The File Replication Service cannot replicate %1 because the pathname of the customer designated staging directory: %n %2 %n is not the fully qualified pathname of an existing, accessible local directory. The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's logging pathname %2. The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's working directory %2. The File Replication Service cannot replicate %1 because it overlaps the staging directory %2. The File Replication Service cannot replicate %1 because it overlaps the replicating directory %2. The File Replication Service cannot replicate %1 because it overlaps the staging directory %2 of the replicating directory %3. `The File Replication Service could not prepare the root directory %1 for replication. This is likely due to a problem creating the root directory or a problem removing preexisting files in the root directory. %n %nCheck that the path leading up to the root directory exists and is accessible.  The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside the range of plus or minus %1 minutes. %n %nThe connection to the partner computer is: %n "%2" %nThe detected time difference is: %3 minutes. %n %nNote: If this time difference is close to a multiple of 60 minutes then it is likely that either this computer or its partner computer was set to the incorrect time zone when the computer time was initially set. Check that the time zone and the system time are correctly set on both computers. %n %nIf necessary, the default value used to test for computer time consistency may be changed in the registry on this computer. (Note: This is not recommended.) %n %nTo change this parameter, run regedt32. %n %nClick on Start, Run and type regedt32. %n %nClick on the window entitled HKEY_LOCAL_MACHINE. %nClick down the key path: %n "System\CurrentControlSet\Services\NtFrs\Parameters" %nDouble click on the value name %n "Partner Clock Skew In Minutes" %nand update the value. %n %nIf the value name is not present you may add it with the Add Value function under the Edit Menu item. Type the value name exactly as shown above using the the registry data type REG_DWORD. The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is %1 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further. %n %nThe file name is: "%2" %nThe connection to the partner computer is: %n "%3" %n %nNote: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer. The File Replication Service is unable to open the customer designated staging directory for replica set %1. The path used for the staging directory is, %n "%2" %nThe customer designated root path for this replica set is: %n "%3" %n The service is unable to start replication on this replica set. Among the possible errors to check are: %n -- an invalid staging path, %n -- a missing directory, %n -- a missing disk volume, %n -- a file system on the volume that does not support ACLs, %n -- a sharing conflict on the staging directory with some other application. %n %nCorrect the problem and the service will attempt to restart replication automatically at a later time. The File Replication Service is unable to open (or create) the pre-install directory under the customer designated replica tree directory for replica set %1. The path used for the pre-install directory is, %n "%2" %nThe customer designated root path for this replica set is: %n "%3" %n The service is unable to start replication on this replica set. Among the possible errors to check are: %n -- an invalid root path, %n -- a missing directory, %n -- a missing disk volume, %n -- a file system on the volume that does not support NTFS 5.0 %n -- a sharing conflict on the pre-install directory with some other application. %n %nCorrect the problem and the service will attempt to restart replication automatically at a later time. \The File Replication Service is unable to add this computer to the following replica set: %n "%1" %n %nThis could be caused by a number of problems such as: %n -- an invalid root path, %n -- a missing directory, %n -- a missing disk volume, %n -- a file system on the volume that does not support NTFS 5.0 %n %nThe information below may help to resolve the problem: %nComputer DNS name is "%2" %nReplica set member name is "%3" %nReplica set root path is "%4" %nReplica staging directory path is "%5" %nReplica working directory path is "%6" %nWindows error status code is %7 %nFRS error status code is %8 %n %nOther event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time. The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on his computer until the following recovery steps are performed: %n %n Recovery Steps: %n %n [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window: %n %n net stop ntfrs %n net start ntfrs %n %nIf this fails to clear up the problem then proceed as follows. %n %n [2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled: %n %nIf there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. %n %nIf there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary. %n %nIf there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative. %n %n %n [3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled: %n %n (3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location. %n (3-b) If this server is the only Active Directory Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for %nSites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS. %n (3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. %n (3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published. %n %n %n [4] For other Windows 2000 servers: %n %n (4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location. %n (4-b) net stop ntfrs %n (4-c) rd /s /q %1 %n (4-d) net start ntfrs %n (4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time). %n %nNote: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members. <The File Replication Service has detected what appears to be an attempt to change the root path for the following replica set: %n "%1" %n %nThis is not allowed. To perform this operation you must remove this member from the replica set and add the member back with the new root path. %n %nIt is possible that this is a transient error due to Active Directory replication delays associated with updating FRS configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory replication is required, you must delete and re-add this member to the replica set. %n %nInformation related to this event is shown below: %nComputer DNS name is "%2" %nReplica set member name is "%3" %nThe current Replica set root path is "%4" %nThe desired new Replica set root path is "%5" %nReplica staging directory path is "%6" pThe File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". %nThis was detected for the following replica set: %n "%2" %n %nThis is not allowed and replication will not occur between these two computers until the duplicate connection objects are removed. %n %nIt is possible that this is a transient error due to Active Directory replication delays associated with updating FRS configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory replication is required, you must manually delete the duplicate connection objects by following the steps below: %n %n [1] Start the Active Directory Sites and Services Snapin. %n [2] Click on "%3, %4, %5, %6, %7". %n [3] Look for duplicate connections from "%1" in site "%8". %n [4] Delete all but one of the connections. 0 The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". %nThis was detected for the following replica set: %n "%2" %n %nThis is not allowed and replication will not occur between these two computers until the duplicate connection objects are removed. %n %nIt is possible that this is a transient error due to Active Directory replication delays associated with updating FRS configuration objects. If file replication does not take place after an appropriate waiting time, which could be several hours if cross site Active Directory replication is required, you must manually delete the duplicate connection objects by following the steps below: %n %n [1] Start the Active Directory Users and Computers Snapin. %n [2] Click the view button and advanced features to display the system node. %n [3] Click on "%3, %4, %5". %n [4] Under "%5" you will see one or more DFS related replica set objects. Look for the FRS member object "%6" under the subtree for replica set "%2". %n [5] Under "%6" look for duplicate connections from "%1". %n [6] Delete all but one of the connections. The File Replication Service has detected that the replica root path has changed from "%2" to "%3". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. %nThis was detected for the following replica set: %n "%1" %n %nChanging the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. %n %n [1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set. %n [2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not. @ The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. %n %n Replica set name is : "%1" %n Replica root path is : "%2" %n Replica root volume is : "%3" %n A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. %n %n [1] Volume "%3" has been formatted. %n [2] The NTFS USN journal on volume "%3" has been deleted. %n [3] The NTFS USN journal on volume "%3" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. %n [4] File Replication Service was not running on this computer for a long time. %n [5] File Replication Service could not keep up with the rate of Disk IO activity on "%3". %n %n Following recovery steps will be taken to automatically recover from this error state. %n [1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set. %n [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. QoS: The Packet Scheduler failed to register with the Generic Packet Classifier (msgpc.sys). QoS: The Packet Scheduler was unable to allocate required resources for initialization. QoS: The Packet Scheduler failed to register as a protocol with NDIS. QoS: The Packet Scheduler failed to register as a miniport with NDIS. QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_MAXIMUM_FRAME_SIZE. QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_MAXIMUM_TOTAL_SIZE. QoS [Adapter %2]:%nThe network adapter driver failed the query for OID_GEN_LINK_SPEED. QoS [Adapter %2]:%nThe Packet Scheduler failed to bind to the network adapter's miniport driver. QoS [Adapter %2]:%nThe UpperBindings key is missing from the registry. QoS [Adapter %2]:%nThe Packet Scheduler was unable to register with the NDISWAN Call Manager. QoS [Adapter %2]:%nThe Packet Scheduler could not initialize the virtual miniport with NDIS. QoS [Adapter %2]:%nThe Packet Scheduler could not obtain the network adapter's friendly name from NDIS. QoS [Adapter %2]:%nCould not initialize due to insufficient nonpaged pool memory. QoS [Adapter %2]:%nCould not allocate non-paged pool memory for storing network addresses. dAn extra ExitPoint %2 was found at server %3 \The ExitPoint %2 was missing at server %3 XThe Volume %2 was missing at server %3 `The extra Volume %2 was found at server %3 The extra ExitPoint %2 was deleted successfully from the server %3 |Unable to delete the extra ExitPoint %2 at the server %3 The missing ExitPoint %2 was created at the server %3 successfully Unable to create the missing Exit Point %2 at the server %3 Successfully created the missing volume %2 knowledge at the server %3 |Unable to create the missing Volume %2 info at server %3 lThe extra Volume %2 info was deleted at server %3 tThe extra Volume %2 info was not deleted at server %3 Since the DC %2 was unavailable could not verify volumes knowledge. Detected Knowledge inconsistency with the volume %2 at server %3 The local Prefix %2 was represented as %3 at remote server %4 The remote Prefix %3 was corrected to %2 at remote server %4 The remote Prefix %3 was NOT corrected to %2 at remote server %4 The machine %2 has become unlinked from the domain. Re-join the machine the machine to this domain. Dfs could not create reparse point for directory %1 under directory %2. The return code is in the record data. Share %1 mapped to %2 does not support reparse points. Upgrade Filesystem and retry. Share %1 mapped to %2 directory overlaps an existing root. The DFS Root will not be created. Root %1 has too many errors. No further eventlogs will be logged on this root. DFS could not initialize winsock library. The return code is in the record data. DFS could not initialize security library. The return code is in the record data. DFS could not create DFS support thread. The return code is in the record data. DFS could not initialize IP site cache. The return code is in the record data. DFS could not synchronize all DFS roots. The return code is in the record data. DFS could not create event handle. The return code is in the record data. DFS could not get required computer information. The return code is in the record data. DFS could not get required cluster information. The return code is in the record data. DFS could not get required DC information. The return code is in the record data. DFS could not initialize prefix table. The return code is in the record data. DFS could not initialize DFS namespace.The return code is in the record data. DFS could not Register DFS Namespaces. The return code is in the record data. DFS could not initialize User/kernel communication package. The return code is in the record data. DFS could not contact any DC for Domain DFS operations. This operation will be retried periodically. DFS could not initialize site support table. The return code is in the record data. DFS could not access its private data from the Active Directory. Please manually check network connectivity, security access, and/or consistency of DFS information in the Active Directory. This error occurred on root %1. DFS does not support multiple roots on Standard server SKU. Please cleanup the roots or upgrade. DFS was unable to resynchronize this root target for root: %1. This may lead to inaccessability of portions of the DFS namespace. Please verify the share %1 has all the link directories created for the DFS links. This error may occur if there are directories on this share that may be preventing creation of links. DFS was unable to delete link: %2 for root: %1 during a link move operation. The list of folder targets for the following Distributed File System (DFS) folder is corrupt. DFS folder: %1 LA Distributed File System (DFS) folder with folder targets was created that contains other DFS folders. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder 1: %2 DFS folder 2: %3 $A Distributed File System (DFS) folder with folder targets was created that contains other DFS folders. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder: %2 HA Distributed File System (DFS) folder was created with conflicting descriptions. This can occur if two administrators on different namespace servers create conflicting folder structures at approximately the same time. Namespace: %1 DFS folder path: %2 DFS folder 1: %3 DFS folder 2: %4 The DFS Namespace service could not initialize the trusted domain information on this domain controller, but it will periodically retry the operation. The return code is in the record data. The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data. Bridge: The bridge could not be initialized because the bridge failed to register as a protocol with NDIS. Bridge: The bridge could not be initialized because the bridge's miniport device name is missing from the registry. Bridge: The bridge could not be initialized because the bridge failed to register as a miniport with NDIS. Bridge: The bridge could not be initialized because the bridge failed to create a device object. Bridge: The bridge could not be initialized because the bridge failed to determine a MAC address for itself. |Bridge: The bridge failed to create its virtual miniport. Bridge: The bridge could not initialize its miniport because Ethernet was not offered as a supported medium. Bridge: The bridge could not initialize because it failed to create a system thread. Bridge: The bridge could not initialize because it failed to reference its system thread. Bridge: The bridge could not initialize because it failed to create a packet pool. Bridge: The bridge could not initialize because it failed to create a buffer pool. Bridge: The bridge could not initialize because it failed to allocate memory. Bridge [Adapter %2]:%nThe bridge could not determine the network adapter's link speed. The network adapter will not be used. Bridge [Adapter %2]:%nThe bridge could not determine the network adapter's MAC address. The network adapter will not be used. Bridge [Adapter %2]:%nThe bridge could not modify the network adapter's packet filter. The network adapter will not function correctly. Bridge [Adapter %2]:%nThe bridge could not retrieve the network adapter's description string. The network adapter will not be used. Bridge [Adapter %2]:%nThe bridge failed to bind to the network adapter. The network adapter will not be used. WSK provider has ignored the OwningThread parameter passed to a WSK socket creation request. This happens when the socket needs to be created over a TDI transport provider either because a TDI filter driver is installed or because a client-specified TDI mapping exists that matches the AddressFamily, socketType, and Protocol specified in the socket creation request. |Computer QoS policies failed to refresh. Error code: %2. tUser QoS policies failed to refresh. Error code: %2. QoS failed to open the computer-level root key for QoS policies. Error code: %2. QoS failed to open the user-level root key for QoS policies. Error code: %2. DA computer QoS policy exceeds the maximum allowed name length. The offending policy is listed under the computer-level QoS policy root key, with index %2. 4A user QoS policy exceeds the maximum allowed name length. The offending policy is listed under the user-level QoS policy root key, with index %2. A computer QoS policy has a zero length name. The offending policy is listed under the computer-level QoS policy root key, with index %2. A user QoS policy has a zero length name. The offending policy is listed under the user-level QoS policy root key, with index %2. 8QoS failed to open the registry subkey for a computer QoS policy. The policy is listed under the computer-level QoS policy root key, with index %2. (QoS failed to open the registry subkey for a user QoS policy. The policy is listed under the user-level QoS policy root key, with index %2. QoS failed to read or validate the "%2" field for the computer QoS policy "%3". QoS failed to read or validate the "%2" field for the user QoS policy "%3". QoS failed to read or set inbound TCP throughput level, error code: "%2". QoS failed to read or set the DSCP marking override setting, error code: "%2". 4VS_VERSION_INFO@%@%?StringFileInfo040904B0LCompanyNameMicrosoft CorporationLFileDescriptionNet Event Handlerr)FileVersion6.3.9600.16384 (winblue_rtm.130821-1623): InternalNameNetEvent.Dll.LegalCopyright Microsoft Corporation. All rights reserved.JOriginalFilenameNetEvent.Dll.MUIj%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.16384DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD