Windows 7

  1. The WS-Management service cannot process the request. The system load quota of %1!d! requests per %2!d! seconds has been ...
  2. The WS-Management service cannot process the request. The URI contains a key: (%1). But WS-Management cannot find a value ...
  3. The WS-Management service cannot process the request. The URI contains more keys than maximum number that WS-Management supports ...
  4. The WS-Management service cannot process the request. The URI generated from the CIM path is too long. The maximum supported ...
  5. The WS-Management service cannot process the request. The user does not have permission for the %1 operation on the %2 resource. ...
  6. The WS-Management service cannot process the request. The user load quota of %1!d! requests per %2!d! seconds has been exceeded. ...
  7. The WS-Management service cannot process the request. The WMI service reported that the WMI provider could not perform the ...
  8. The WS-Management service cannot process the request. The WS-Addressing action URI is invalid. Check the documentation for ...
  9. The WS-Management service cannot process the request. The WS-Addressing Address element is missing from the WS-Eventing NotifyTo ...
  10. The WS-Management service cannot process the request. The WS-Eventing EndTo element is missing from the WS-Eventing Delivery ...
  11. The WS-Management service cannot process the request. The WS-Eventing NotifyTo element might be missing from the WS-Eventing ...
  12. The WS-Management service cannot process the request. The XML contains a timeout value that is too small: %1!lu!. The timeout ...
  13. The WS-Management service cannot process the request. The XML contains an invalid boolean value: "%1". Valid boolean values ...
  14. The WS-Management service cannot process the request. The XML contains an invalid integer value "%1". Valid integer values ...
  15. The WS-Management service cannot process the request. The XML contains an invalid port number that is too large: %1!lu! The ...
  16. The WS-Management service cannot process the request. The XML contains an invalid port number: %1!lu! The value must be %2!lu! ...
  17. The WS-Management service cannot process the request. The XML contains an invalid security descriptor "%1";received error ...
  18. The WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1. CIM datetime type ...
  19. The WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1. Ensure that the ...
  20. The WS-Management service cannot process the request. This service is configured to allow a maximum of %1!d! concurrent shell ...
  21. The WS-Management service cannot process the request. This user is allowed a maximum number of %1!d! concurrent operations, ...
  22. The WS-Management service cannot process the request. This user is allowed a maximum number of %1!d! concurrent shells, which ...
  23. The WS-Management service cannot process the request. When setting an array property to null, only one element with that ...
  24. The WS-Management service cannot process the request. WS-Management cannot convert a string to an unsigned number. The request ...
  25. The WS-Management service cannot process the request. WS-Management cannot identify the enumeration context ID in the SOAP ...
  26. The WS-Management service cannot process the request.The computed response packet size (%1!lu!) exceeds the maximum envelope ...
  27. The WS-Management service cannot rename the resource. The selectors for the resource are not correct. The resource may exist ...
  28. The WS-Management service configuration contains ambiguous entries in the URI security table: more than one pattern matches ...
  29. The WS-Management service could not identify the subscription context ID in the SOAP packet that was received. The packet ...
  30. The WS-Management service does not support the character set used in the request. Change the request to use UTF-8 or UTF-16. ...
  31. The WS-Management service does not support the delivery mode for the specified resource. The client should change the subscription ...
  32. The WS-Management service does not support the filter dialect in the request. The filter dialect is the type of filter, such ...
  33. The WS-Management service does not support the options feature for the specified resource. Remove the options from the request ...
  34. The WS-Management service does not support the specified feature. Remove the unsupported feature from the request and retry. ...
  35. The WS-Management service does not support the specified polymorphism mode. Try changing the polymorphism mode specified, ...
  36. The WS-Management service does not support the specified timeout. The value specified is smaller than the minimum allowed ...
  37. The WS-Management service on the remote machine cannot process the shell request. This can happen if the WS-Management service ...
  38. The WS-Management service on the remote machine with which this subscription had been set up has requested that the subscription ...
  39. The WS-Management service received a request which specified a maximum number of elements, but the service does not support ...
  40. The WS-Management service received a SOAP packet that contained a request to do a %1 operation. This operation requires a ...
  41. The WS-Management service received an invalid SOAP packet. The packet contains an invalid or missing WS-Management Delivery ...
  42. The WS-Management service Wmi plugin does not support the specified OptionSet because MustComply for one of the options is ...
  43. The WSCSVC (Windows Security Center) service monitors and reports security health settings on the computer. The health settings ...
  44. The WSDL document contained an extensibility element with name '%1' from namespace '%2' that was required but not recognized. ...
  45. The WSMan client cannot process the request. Proxy is not supported under HTTP transport. Change the transport to HTTPS and ...
  46. The WSMan client cannot process the request. Proxy is not supported when the authentication mechanism with the server is ...
  47. The WSMan client cannot process the request. The authentication mechanism requested by the proxy is not supported by the ...
  48. The WSMan client could not load current configuration settings as the settings are corrupted. The client is operating with ...
  49. The WSMan client received a redirect status from the server, but the server did not give the actual redirect location to ...
  50. The WSMan IIS module failed to read configuration. The error received was %1: %1 %2. User Action Make sure both the schema ...
  51. The WSMan provider host process did not return a proper response. A provider in the host process may have behaved improperly. ...
  52. The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server ...
  53. The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server ...
  54. The WSMan service could not load current configuration settings as the settings are corrupted. The service is started with ...
  55. The WSMan service failed to read configuration of the following plugin: %1. The error received was %2: %2 %3. User Action ...
  56. The wsrmeventlist.xml file cannot be processed. Please reinstall Windows System Resource Manager (WSRM), and then try again. ...
  57. The WSUS Operations Guide gives detailed troubleshooting information to resolve issues with clients not reporting the server, ...
  58. The X property specifies the x offset, in pixels, of the upper left corner of a window if a new window is created. The offsets ...
  59. The XA Transaction Manager attempted to load the XA resource manager DLL. The call to LOADLIBRARY for the XA resource manager ...
  60. The XA Transaction Manager attempted to locate the "GetXaSwitch" function in the XA resource manager DLL. The "GetXaSwitch" ...
  61. The XA Transaction Manager attempted to perform recovery with the XA resource manager. The XA resource manager reported that ...
  62. The XA Transaction Manager called the "GetXaSwitch" function in the XA resource manager DLL. The call to the "GetXaSwitch" ...
  63. The XA Transaction Manager called the "GetXaSwitch" function in the XA resource manager DLL. The call to the "GetXaSwitch" ...
  64. The XA Transaction Manager cannot load the requested XA Dll (%1) since a registry entry is required for this operation. Please ...
  65. The XA Transaction Manager is in an inconsistent state and cannot proceed. XA transactions will not take place. Please contact ...
  66. The XCountChars property, used for processes creating a console window, specifies the screen buffer width in character columns. ...
  67. The XDomainRequest Object allows Web sites to request data across domains from your browser. This policy setting allows you ...
  68. The xml document could not be read because it was larger than expected. The data did not fit within the buffer size of '%1' ...
  69. The XML file (%1) is valid, but failed to parse. This is typically due to the file being in use. It can also be an internal ...
  70. The XML page cannot be displayed Cannot view XML input using %3 style sheet. Please correct the error and then click the ...
  71. The XML script engine does not support script fragments. This error was probably caused by having a script tag with the language ...
  72. The XML script engine does not support script fragments. This error was probably caused by having a script tag with the language ...
  73. The XOffCharacter property specifies the value of the XOFF character for both transmission and reception. XOFF is a software ...
  74. The XOffXMitThreshold property specifies the maximum number of bytes allowed in the input buffer before the XOFF character ...
  75. The XOnCharacter property specifies the value of the XON character for both transmission and reception. XON is a software ...