Windows Server 2008

  1. The WinRM service encountered a catastrophic security failure. The service can no longer run under its security context. ...
  2. The WinRM service executed an operation and the provider returned inconclusive information regarding success or failure of ...
  3. The WinRM service had a failure (%1) reading configuration during ip address change notification. Service will continue running ...
  4. The WinRM service had a failure applying the current configuration and is stopping. User Action Check for previous event ...
  5. The WinRM service had a failure during migration. User Action Create the configuration again using the WinRM command line ...
  6. The WinRM service had a failure reading the current configuration and is stopping. User Action Use the following command ...
  7. The WinRM service has been configured to accept basic authentication for unsecure HTTP connections. This is not a secure ...
  8. The WinRM service has received an unsecure HTTP connection from %1. This is not a secure configuration. User Action Set AllowUnencrypted ...
  9. The WinRM service is listening for WS-Management requests. User Action Use the following command to see the specific IPs ...
  10. The WinRM service is not listening for %1 requests because there was a failure binding to the URL (%2) in HTTP.SYS. Another ...
  11. The WinRM service is not listening for HTTP requests because there was a failure binding to the URL (%1) in HTTP.SYS. No ...
  12. The WinRM service is not listening for HTTPS requests because there was a failure binding to the URL (%1) in HTTP.SYS. No ...
  13. The WinRM service is not listening for policy changes because there was a failure registering for changes to the contents ...
  14. The WinRM service is not listening for requests since it failed to listen on at least one address and port. Remote management ...
  15. The WinRM service is not listening for WS-Management requests. User Action If you did not intentionally stop the service, ...
  16. The WinRM service is stopping because there was a failure registering for changes to the configuration. User Action Restart ...
  17. The WinRM service is stopping because there was a failure registering for changes to the IP addresses. User Action Restart ...
  18. The WinRM Shell client cannot process the request. One of the argument value passed to the WSManRunShellCommand function ...
  19. The WinRM Shell client cannot process the request. One of the environment variable name passed to the WSManCreateShell function ...
  20. The WinRM Shell client cannot process the request. One of the parameters required for the WinrsCloseShell function is null ...
  21. The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null ...
  22. The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is ...
  23. The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is ...
  24. The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null ...
  25. The WinRM Shell client cannot process the request. One of the parameters required for the WSMansReceiveShellOutput function ...
  26. The WinRM Shell client cannot process the request. One of the stream id name passed to the WSManCreateShell function is null ...
  27. The WinRM Shell client cannot process the request. The command handle passed to the WSMan Shell function is not valid. The ...
  28. The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The ...
  29. The WinRM Shell client cannot process the request. The stream id index from within WSMAN_STREAM_ELEMENT passed to the WSManSendShellInput ...
  30. The WinRS client cannot process the request. An invalid flag was specified for this request. Remove or change the invalid ...
  31. The WinRS client cannot process the request. One of the parameters required for the WinrsGet function is null or zero. Change ...
  32. The WinRS client cannot process the request. One of the parameters required for the WinrsPull function is null or zero. Change ...
  33. The WinRS client cannot process the request. One of the parameters required for the WinrsPush function is null or zero. Change ...
  34. The WinRS client cannot process the request. One of the parameters required is null or zero. Change the request to include ...
  35. The WinRS client cannot process the request. The parameter required for the WinrsCloseReceiveHandle function is null or zero. ...
  36. The WinRS client cannot process the request. The parameter required for the WinrsCloseSendHandle function is null or zero. ...
  37. The WinRS client cannot process the request. The parameter required for the WinrsFreeCreateShellResult function is null or ...
  38. The WinRS client cannot process the request. The parameter required for the WinrsFreePullResult function is null or zero. ...
  39. The WinRS client cannot process the request. The parameter required for the WinrsFreeRunCommandResult function is null or ...
  40. The WinRS client cannot process the request. The server cannot set Code Page. You may want to use the CHCP command to change ...
  41. The WINS configuration key could not be created or opened. Check to see if the permissions on the key are set properly, system ...
  42. The WINS database is inconsistent. The number of owners found in the name-address mapping table are different from the number ...
  43. The WINS database of name-to-address mappings is empty. It could mean that a previous invocation of WINS created the database ...
  44. The WINS database of owner-to-address mappings is empty. It could mean that a previous invocation of WINS created the table ...
  45. The WINS Pull configuration key could not be created or opened. Check to see if the permissions on the key are set properly, ...
  46. The WINS Push configuration key could not be created or opened. Check to see if the permissions on the key are set properly, ...
  47. The WINS Replication Pull Handler could not connect to a WINS server. All retries failed. WINS will try again after a set ...
  48. The WINS replication request is being ignored since WINS suspects that the Wins\Partners key information has changed (because ...
  49. The WINS replicator Pull thread encountered an error while processing a request. Check other log entries to determine what ...
  50. The WINS Scavenger thread could not scavenge a record. This record will be ignored. The Scavenger will continue on to the ...
  51. The WINS server %s denied the replication request because the current WINS server is not listed among its replication partners. ...
  52. The WINS server can use multicast to automatically configure itself for replication. Use this option only on small networks. ...
  53. The WINS server cannot make or accept this connection since the connections limit has been reached. This situation is temporary ...
  54. The WINS server completed the burst handling of incoming requests because the queue length became a quarter of what it was ...
  55. The WINS server received a pull request from the non-configured WINS server with the address, %1. The WINS server rejected ...
  56. The WINS server received an update notification from the non-configured WINS server at the address, %1. The WINS server rejected ...
  57. The WINS server started the burst handling of incoming requests. WINS does this to handle a sudden increase of incoming requests. ...
  58. The WINS server you specified cannot be located. The WINS server might be down, there might be network problems, or the WINS ...
  59. The WINSEnableLMHostsLookup parameter specifies the lookup files containing mappings of IP addresses to host names. If available, ...
  60. The WINSEnableLMHostsLookup parameter specifies whether local lookup files are used. Lookup files will contain mappings of ...
  61. The WINSEnableLMHostsLookup property indicates whether local lookup files are used. Lookup files will contain a map of IP ...
  62. The WINSHostLookupFile property contains a path to a WINS lookup file on the local system. This file will contain a map of ...
  63. The WINSScopeID parameter specifies the Scope ID value that will be appended to the end of the computer's NetBIOS name. Systems ...
  64. The WINSScopeID property provides a way to isolate a group of computer systems that communicate with each other only. The ...
  65. The WINS\Parameters key could not be created or opened. Check to see if the permissions on the key are set properly, system ...
  66. The WINS\Parameters\ConsistencyCheck subkey could not be created or opened. This key should be there if you want WINS to ...
  67. The wireless capability setting on this computer does not match the requirements of "%ws" The selected radio type (802.11a/b/g) ...
  68. The wireless connection on this computer appears to be working correctly The Internet connection on the wireless router or ...
  69. The wireless connectivity problems on this computer might be caused by an incorrect network security key or low signal strength ...
  70. The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change ...
  71. The wireless network adapter on this computer cannot connect to a wireless network This might because there are no wireless ...
  72. The wireless network adapter settings on this computer don't match the requirements of "%ws" The connection mode for ( "ad ...
  73. The wireless network adapter settings on this computer don't match the requirements of "%ws" The selected data rate (802.11a/b/g) ...
  74. The wireless network policy storage could not be opened due to insufficient access rights. You must be an administrator. ...
  75. The wireless network settings on this computer don't match the requirements of "%ws" The wireless setting for the connection ...