Windows Server 2008

  1. The root element of target document '{0}' is not '{1}' (or a substitution of '{1}', with derivations by '{2}' excluded). ...
  2. The root folder on this volume is full. To perform a disk check, Windows requires space in the root folder. Remove some files ...
  3. The root node cannot be set after the SnapIn instance is initialized. Consider adding the root node in the constructor of ...
  4. The root share could not be created because another namespace or share with the same name already exists. To resolve this ...
  5. The root share could not be created because the local path for the share target is a redirected device. To resolve this issue ...
  6. The root share for the namespace could not be created. To resolve this issue use the DFS Management snap-in to create your ...
  7. The root zone was deleted from the server. Root hints must be supplied to allow recursive queries. Would you like to add ...
  8. The round robin with subset policy executes the round robin policy only on paths designated as active. The standby paths ...
  9. The round robin with subset policy executes the round robin policy only on paths designated as active/optimized. The non-active/optimized ...
  10. The Routing and Remote Access service could not start. The most common reason could be because %1 protocol is not installed ...
  11. The Routing and Remote Access Service is in the process of stopping. Until it stops, the Incoming Connections option is not ...
  12. The Routing and Remote Access service is in the process of stopping. Until it stops, the Incoming Connections option is not ...
  13. The Routing and Remote Access Service is not currently running on %1!s!. Please use 'net start remoteaccess' on the machine ...
  14. The Routing and Remote Access Service is not currently running on %1!s!. Use 'net start remoteaccess' on the remote machine ...
  15. The Routing and Remote Access Service is not currently running on the local machine. Please use 'net start remoteaccess' ...
  16. The Routing and Remote Access Service is not currently running on the local machine. Use 'net start remoteaccess' on the ...
  17. The Routing and Remote Access service is not running. You cannot add and configure interfaces unless the service is running. ...
  18. The Routing and Remote Access service may not have been restarted because the following error occurred when trying to query ...
  19. The Routing and Remote Access Service needs to be restarted for this setting to take effect. Use 'net stop remoteaccess' ...
  20. The RPC binding failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be ...
  21. The RPC binding failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be ...
  22. The RPC binding failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. ...
  23. The RPC binding failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. ...
  24. The RPC call failed in the Collect function of the FileReplicaConn Object. The counter data for this object will not be available ...
  25. The RPC call failed in the Collect function of the FileReplicaSet Object. The counter data for this object will not be available ...
  26. The RPC call failed in the Open function of the FileReplicaConn Object. The counter data for this object will not be available. ...
  27. The RPC call failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. ...
  28. The RPC/HTTP Proxy object contains the counters that display information for RPC/HTTP proxy sizing, trouble shooting and ...
  29. The RSM service is delaying its start for %1 seconds to assist with boot time performance . Modify the registry value "DelayStart" ...
  30. The RSOP Security Settings Extension snap-in extends the RSOP snap-in and helps you view resultant security policies for ...
  31. The RSoP snap-in was unable to generate the computer's data due to insufficient permissions. The snap-in will continue to ...
  32. The RSoP snap-in was unable to generate the RSoP data because the target machine is currently running RSoP or processing ...
  33. The RSoP snap-in was unable to generate the user's data due to insufficient permissions. The snap-in will continue to start ...
  34. The RSOP_PolicySetting class is the abstract parent object from which client-side extensions' policy objects are inherited ...
  35. The RSoP_PolicySettingStatus class provides information about a specific error that occured when trying to apply a policy ...
  36. The RSOP_SOM class is an abstraction for a Scope of Management. A scope of management can be a site, domain, organizational ...
  37. The RTSFlowControlType property specifies the request-to-send (RTS) flow control. RTS is used to signal that data is available ...
  38. The rules attached to the trigger %1 with the ID %2 are now valid. All the rules were evaluated successfully, and the actions ...
  39. The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the ...
  40. The run-time environment has detected the absence of a critical resource and has caused the process that hosted it to terminate. ...
  41. The run-time environment was unable to initialize for transactions required to support transactional components. Make sure ...
  42. The RunRepeatedly parameter indicates whether the scheduled job should run repeatedly on the days that the job is scheduled. ...
  43. The RunRepeatedly property indicates whether the scheduled job should run repeatedly on the days that the job is scheduled. ...
  44. The safest way to browse, but also the least functional - Less secure features are disabled - Cookies are disabled (some ...
  45. The SAM database attempted to clear the directory %1 in order to remove files that were once used by the Directory Service. ...
  46. The SAM database attempted to delete the file %1 as it contains account information that is no longer used. The error is ...
  47. The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete ...
  48. The SAM database was unable to lockout the account of %1 due to a resource error, such as a hard disk write failure (the ...
  49. The saved console file was created with a different, incompatible version of the Local Users and Groups snap-in than the ...
  50. The ScanMode property determines whether the display device is interlaced. This property has been deprecated in favor of ...
  51. The scanner does not support the default settings for scan to fax. Click OK to scan with the scanner's default settings, ...
  52. The scanning software could not be found, or your scanner is not connected. Please make sure your scanner and your scanning ...
  53. The Scavenger thread encountered an error while cleaning up the owner-address table. It will try again after the Verify interval ...
  54. The Scavenger thread found active replicas that needed to be verified with the owner WINS server since they were older than ...
  55. The scenario %1 has a configuration error in the WDI registry namespace. The Diagnostic Policy Service will ignore the scenario. ...
  56. The Scenario Event Mapper is configured with an unsupported scenario. The scenario for provider %1 (event ID %2) encountered ...
  57. The Scenario Event Mapper is configured with more than the maximum number of context providers for the scenario with provider ...
  58. The Scenario Event Mapper is configured with more than the maximum number of end events for the scenario with provider %1 ...
  59. The Scenario Event Mapper is configured with more than the maximum number of providers. The provider %1 will be ignored. ...
  60. The Scenario Event Mapper is configured with more than the maximum number of scenarios. The scenario for provider %1 (event ...
  61. The Scenario Event Mapper started a scenario for provider %1 (event ID %2) with %4 context providers. The context logger ...
  62. The Scenario Event Mapper stopped a scenario for provider %1 (event ID %2) with %4 context providers. The context logger ...
  63. The Scenario Event Mapper was unable to start a new scenario for provider %1 (event ID %2) because the maximum number of ...
  64. The schannel security package has failed to load. Operations that require the SSL or TLS cryptographic protocols will not ...
  65. The schedule attribute of the following site link object is configured in a way that the sites it references are never connected. ...
  66. The schedule attribute of the following site link object is not valid. Site link object: %1 As a result, this schedule will ...
  67. The schedule name contains characters that are not valid. The name cannot start with a hyphen (-) and cannot contain spaces ...
  68. The schedule on the following Connection object has been updated. This object represents a replication connection between ...
  69. The schedule type (subaction) was not specified. You must specify one of the following schedule types: full, empty, default, ...
  70. The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. ...
  71. The ScheduledCast namespace %1 using content provider %2 could not be registered as it starts in the past. The namespace ...
  72. The schema document root element is not 'schema', or is missing the 'targetNamespace' attribute, or elementFormDefault is ...
  73. The schema is invalid. You will not be able to import it. More details are in the log window below. Do you want to continue? ...
  74. The schemaIdGuid attribute value for the following schema class duplicates the schemaIdGuid value for an existing class. ...
  75. The schemaIdGuid value for the following attribute duplicates the schemaIdGuid value for an existing attribute. Attribute: ...