Hacked By AnonymousFox

Current Path : C:/Windows/SysWOW64/en-US/
Upload File :
Current File : C:/Windows/SysWOW64/en-US/WsmRes.dll.mui

MZ@	!L!This program cannot be run in DOS mode.

$<ߵRRRЫRЫPRRichRPEL!


$@ 8.rdata@@.rsrc @@/e
T88/e$8.rdata8x.rdata$zzzdbg p.rsrc$01p!.rsrc$02 =
W[Ͻ|qJȎv{J/e`0Hh		 	0	@	Ph! "%(lMUI1!̊
y/\ޘ~MUIen-USWSMan Quota StatisticsWSMan Quota StatisticsKDisplays quota usage and violation information for WS-Management processes.Total Requests/SecondTotal Requests/SecondWDisplays the number of approved and rejected requests per second from authorized users.User Quota Violations/SecondUser Quota Violations/Second-Displays the number of user quota violations.System Quota Violations/SecondSystem Quota Violations/Second=Displays the number of requests subject to system throttling.
Active Shells
Active Shells;Displays the current number of active shells for all users.Active OperationsActive Operations?Displays the current number of active operations for all users.Active UsersActive Users8Displays the current number of active, authorized users.
Process ID
Process ID%Displays the current process ID (PID)PA0u'y'D~''''8'' ''P*[88\00\Q3@53@\PP@mppm33p-.!4%&6(17TW=Z[AC@DG@HH@MO0PV Z0Z0\$\\4Nhbmnot${||,}Ѐ؅03|܈23ĉ|The WinRM service is not listening for requests since it failed to listen on at least one address and port. %n%n Remote management using WinRM will fail. %n%n User Action %n Configure listeners by enabling GPO policy for Auto Configuration of listeners or manually create a listener using WinRM command line tool.

The WinRM service is not listening for %1 requests because there was a failure binding to the URL (%2) in HTTP.SYS. %n%n Another process is registered to listen on the WinRM service URL prefix. %n%n User Action %n Correct this problem by stopping the other process, changing its URL prefix, or by changing the configuration for the WS-Management listening address.

The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n Another process is registered to listen on the WinRM client URL prefix. %n%n User Action %n Correct this problem by stopping the other process, changing its URL prefix, or by changing the configuration for the WS-Management listening address.

The WinRM service is not listening for HTTPS requests because there was a failure binding to the URL (%1) in HTTP.SYS.  %n%n No remote requests will be serviced on that URL. %n%n User Action %n Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys is %2: %%%2

`The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n User Action %n Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys was %2: %%%2

HThe WinRM service cannot validate the client certificate because the revocation status of the certificate or one of the certificates in the certificate chain is either offline or stale. %n%n User Action %n Please ensure that the Certificate Revocation List is accessible and up-to-date.

User authentication using Basic authentication scheme failed. %n%n Additional Data %n Unexpected error received from LogonUser %1: %%%1.

tThe client certificate exceeded the maximum size allowed by the WinRM service.%n%n User Action %n Please use a different client certificate or a different authentication mechanism.

Request processing failed because the WinRM service cannot load data or event source: DLL="%1" %n%n User Action %n Please check if "%1" exists. %n%n Additional Data %n Loading %1 failed with error="%2" (%%%2).

The SSL configuration for IP %1 and port %2 is shared with another service, such as Internet Information Services (IIS).

The WinRM service is unable to start because of a failure during initialization. %n%n Additional Data %n The error code is %1.

The WinRM service has received an unsecure HTTP connection from %1. %n%n This is not a secure configuration. %n%n User Action %n Set AllowUnencrypted to False in WinRM configuration to ensure packets are encrypted on the wire.

The WinRM service has been configured to accept basic authentication for unsecure HTTP connections. %n%n This is not a secure configuration. %n%n User Action %n Set AllowUnencrypted to False in WinRM configuration to ensure packets are encrypted on the wire.

The WinRM service is not listening for HTTP requests because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n No remote requests will be serviced on that URL. %n%n User Action %n Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys is %2: %%%2

`The WS-Management client is not listening for pushed events because there was a failure binding to the URL (%1) in HTTP.SYS. %n%n User Action %n Please use "netsh http" to check if ACL for URL (%1) is set to Network Service. %n%n Additional Data %n The error code received from HTTP.sys was %2: %%%2

|IP Filter %1 specified in the GPO policy for Auto Configuration of listeners is invalid and it will be ignored. Due to this issue, the WinRM service cannot use the autoconfigured listener. %n%n "*" is used to indicate that the service should listen on all available IPs on the machine. When "*" is used, other ranges cannot be specified in the filter. %n%n User Action %n Remove other IP ranges if "*" needs to be included in the IP Filter.

0The IP Range %1 is invalid and it will be ignored.  %n%n Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using "," as delimiter. %n Example IPv4 ranges:  2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22 %nExample IPv6 ranges:  3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562 %n%n User Action %n Correct the IP filter %1 using the syntax described above.

hThe WinRM service is not listening for policy changes because there was a failure registering for changes to the contents of the WS-Management policy key. %n%n No group policy change will be serviced. %n%n User Action %n Stop and restart the WinRM service. %n%n Additional Data %n The error code was %1.

The WinRM service encountered a catastrophic security failure. The service can no longer run under its security context. %n%n User Action %n Stop and restart the WinRM service. %n%n Additional Data %n The error code is %1.

The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the IP address does not exist on the destination computer. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct IP address.

 The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the IP address %3 does not exist on the destination computer. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct IP address.

 The WinRM service cannot migrate the listener with IP address %1 and Port %2 because the MAC address %3 does not exist on the destination computer. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct MAC address.

$The WinRM service cannot migrate the listener with Address %1 and Transport %2 because the MAC address %3 does not exist on the destination machine. This listener was ignored during migration. %n%n User Action %n Create the listener again with the correct MAC address.

\The WinRM service cannot migrate the listener with IP address %1, Port %2 and Transport %3. A listener that has Address=%4 and Transport=%5 configuration already exists.

LThe WinRM service cannot migrate the listener with Address %1 and Transport %2. A listener that has the same Address and Transport configuration already exists.

The WinRM service had a failure during migration. %n%n User Action %n Create the configuration again using the WinRM command line tool. %n%n Additional Data %n The error code is: %1 %%%1

The WinRM service had a failure reading the current configuration and is stopping. %n%n User Action %n Use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} %n%n Then add any custom configuration settings and restart the service. %n%n Additional Data %n The error code is: %1 %%%1

XThe WinRM service had a failure applying the current configuration and is stopping. %n%n User Action %n Check for previous event log messages and restart the service.

The WinRM service had a failure reading the current configuration and is stopping. %n%n User Action %n Use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} %n%n Then add any custom configuration settings and restart the service. %n%n Additional Data %n The error code is: %1 %%%1

hThe host name pattern "%1" is invalid and it will be ignored. Host name patterns must not be empty and they can contain at most one wildcard ("*"). "*" pattern can be used to indicate all hosts; if this pattern is used, no other pattern can show up in the list. Special string "<local>" can be used to indicate all host names that do not have a '.'%n%n User Action %n Correct the host name pattern using the syntax described above.

The WinRM service is listening for WS-Management requests. %n%n User Action %n Use the following command to see the specific IPs on which WinRM is listening: %n%n winrm enumerate winrm/config/listener

The WinRM service is not listening for WS-Management requests. %n%n User Action %n If you did not intentionally stop the service, use the following command to see the WinRM configuration: %n%n winrm enumerate winrm/config/listener

The WinRM service could not use the following listener to receive WS-Management requests.  The listener is enabled but the listener does not have an IP address configured. %n%n User Action %n Check the underlying network configuration to determine if this listener has at least one valid IP. If the IP is valid, ensure that WinRM configuration does not exclude that IP address by using the following command: %n%n winrm get winrm/config/service %n%n Additional Data %n Listener transport: %1 %n Listener address: %2

The WinRM service had a failure (%1) reading configuration during ip address change notification. %n%n Service will continue running with old configuration.%n%n User Action %n If immediae changes are required manually restart the service

The WinRM service successfully processed an address change notification.

pThe WSMan IIS module failed to read configuration. The error received was %1: %%%1 %n %2.%n%n User Action %n Make sure both the schema and validation files are present and valid.

The WinRM service failed to create the following SPNs: %1; %2. %n%n Additional Data %n The error received was %3: %%%3.%n%n User Action %n The SPNs can be created by an administrator using setspn.exe utility.

The WSMan service failed to read configuration of the following plugin: %n %1. %n%nThe error received was %2: %%%2 %n %3.%n%n User Action %n Make sure this plugin configuration is valid.

The WinRM service failed to initialize CredSSP. %n%n Additional Data %n The error received was %1.%n%n User Action %n Configure CertificateThumbprint setting under the WinRM configuration for the service. Use the thumbprint of a valid certificate and make sure that Network Service has access to the private key of the certificate.

The WinRM service received an error while trying to unloading a data or event source: DLL="%1" %n%n User Action %n Please check if there is an updated version of this file available: "%1". %n%n Additional Data %n Shutting down %1 failed with error="%2" (%%%2).

The WinRM service is listening on the default %1 port %2 and on %1 (Compatibility) port %3 for WS-Management requests. %1 port %3 is no longer the default port for the WinRM service.%n%n If you want to disable the listener on the (Compatibility) port %3, run the following command:%n%n Winrm set winrm/config/service @{%4="False"}

pThe WinRM service has terminated %1 unauthenticated connections over the past %2 minutes to maintain healthy system state. This will likely happen if the service is overloaded or if the service is under an authentication based attack. %n%n Action: %nEnable and observe Windows Remote Management Analytic log and look for warning events with Id 1843. These include additional information about the clients that got abruptly terminated.

 Soap Trace

Client

Server

Security

(QuotaViolation

,Activity Transfer

Error

Classic

Start

Stop

The WS-Management service cannot process the request because the URI contains a '?' but no key was present.

4The WS-Management service cannot process the request. The URI contains a key: (%1). But WS-Management

cannot find a value because no '=' was found.

The WS-Management service cannot process the request because the URI contains a value in parentheses followed by '%1!c!'.

The URI should either end or a new key should start following a '+'.

PThe WS-Management service cannot process the request. 

The resource URI is longer (%1!d! characters) than the maximum length that is supported (%2!d! characters).

\The WS-Management service cannot process the request. 

The filter dialect URI is longer (%1!d! characters) than the maximum length that is supported (%2!d! characters).

The WS-Management service cannot process the request. 

The SOAP packet contained a WS-Addressing Action element that was longer (%1!d! characters) that the maximum length  that is supported (%2!d! characters).

 The WS-Management service cannot process the request.

The URI contains more keys than maximum number that WS-Management supports (%1!d!).

The WS-Management service cannot process the request. The URI contains a duplicate key (%1).

The WS-Management service cannot process the request. The URI lacks a closing or an opening parenthesis.

The WS-Management service does not support concurrent pull operations for enumerations.

The WS-Management service cannot process the request. The resource URI (%1) was not found in the WS-Management

catalog. The catalog contains the metadata that describes resources, or logical endpoints.

<Not used. To be removed.

The WS-Management service cannot process the request. The resource URI does not support the %1 operation.

The WS-Management service cannot process the request. The operation id %1 is larger than expected.

hProvSysException, ErrorCode=%1!d!, Message=%2.

tThe function: "%1" failed unexpectedly. Error=%2!d!.

The function "%1" failed unexpectedly. Error=%2!d!, GetLastError=%3!d!.

tThe function "%1" failed unexpectedly. Hresult=%2!X!.

Could not access the WS-Management catalog from %1. The catalog contains the metadata that describes

resources, or logical endpoints.

The function: "%1" failed unexpectedly. GetLastError=%2!d!.

Unexpected result from internal function: "%1".%n

GetLastError: %2!d!.%n

File: %3:%4!d! %n

A call to the function "%1" supplied an invalid parameter.

A call to the function "%1" supplied an invalid parameter. The invalid parameter = %2.

xThe WS-Management service does not support the request.

The WS-Management cannot locate the data source with the specified id (%1).

The WS-Management service cannot process the request. The number of outstanding requests exceeds the

maximum number allowed.

TThe WS-Management service cannot process the request. The SOAP packet contains a WS-Management

ResourceURI element that is either invalid, duplicated, or too long.

PThe WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing

MessageID element that was either invalid, duplicated, or too long.

DThe WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing

To element that was either invalid, duplicated, or too long.

HThe WS-Management service cannot process the request. The SOAP packet contains a WS-Addressing Action

element that is either invalid, duplicated, or too long.

The WS-Management service cannot process the request. The SOAP packet does not contain a valid

WS-Addressing ReplyTo element. The element is duplicated or is not the WS-Addressing anonymous URI.

http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous.

The WS-Management service cannot process the request. The SOAP packet does not contain a valid WS-Addressing

FaultTo element. The element is duplicated or is not the WS-Addressing anonymous URI.

http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous.

The WS-Management service cannot process the request. The SOAP packet did not contain a valid WS-Management

Locale element. The element is duplicated or does not match the system locale.

The WS-Management service cannot process the request. The SOAP packet does not contain a valid

enumeration context ID element. The incoming Pull or Release packet should contain a body entry containing

an WS-Enumeration EnumerationContext.

The WS-Management service cannot process the request. WS-Management cannot identify the enumeration context ID

in the SOAP packet. The packet may have been invalid, or the operation may have timed out.

xThe WS-Management service could not identify the subscription context ID in the SOAP packet that was received.

The packet may have been invalid, or the operation may have timed out.

The WS-Management service received a SOAP packet that contained a request to do a %1 operation.

This operation requires a single element in the body.Number of elements found in the soap body was %2!d!.

XThe WS-Management service cannot process the request. The SOAP packet contains the request to do a %1 operation.

This operation requires a single element in the body.

The WS-Management service cannot process the request. The SOAP packet does not have all the fields that are required.

\The WS-Management service cannot process the request. The input XML contains an unrecognized XML element: "%1".

Ensure that the spelling of the element name is correct.

The WS-Management service cannot process the configuration request. XML element %1 must contain sub-elements

and none are present.

HThe WS-Management service cannot process the request. The XML contains an invalid boolean

value: "%1". Valid boolean values are "true", "false", "1", or "0".

The WS-Management service cannot process the request. The XML contains an invalid integer value "%1".

Valid integer values consist of the characters '0' through '9' and are no more than 10 digits in length.

The WS-Management service cannot process the request. The XML contains an invalid security

descriptor "%1";received error (%2!d!) from ConvertStringSecurityDescriptorToSecurityDescriptor.

\The WS-Management service cannot process the configuration request. The XML contains an invalid

security descriptor: "%1". The security descriptor is missing an owner.

XThe WS-Management service cannot process the configuration request. The XML contains an invalid

security descriptor: "%1". The security descriptor is missing a group.

The WS-Management service cannot process the configuration request. The XML contains an invalid

security descriptor: "%1". The security descriptor is missing a discretionary access control list (DACL).

The WS-Management service cannot process the configuration request. The XML contains an invalid

security descriptor: "%1". WS-Management does not support the access control entry (ACE) type: %2!d!.

Invalid security descriptor "%1"; access right

must be a combination of

GR (generic read = WSManGet, WSManEnumerate, WSManSubscribe),

GW (generic write = WSManPut, WSManCreate, WSManDelete), or

GX (generic execute = WSManInvoke)

GA (generic all)

8The WS-Management service cannot process the configuration request.

The request has a blank setting. %1 cannot be "" (blank or empty string) or NULL.

\The WS-Management service cannot process the configuration request. WS-Management configuration received

an invalid URL. The URL prefix cannot start or end with a '/'.

@The WS-Management service cannot process the configuration request. The XML contains a URL with an invalid

character. The URL prefix cannot contain %1!c!.

lThe WS-Management service cannot process the configuration request. The XML contains an invalid integer

setting: %1 that is too small: %2!lu!. The value must be %3!lu! or more.

lThe WS-Management service cannot process the configuration request. The XML contains an invalid integer setting: %1

that is too large: %2!lu!. The value must be %3!lu! or less.

The WS-Management service cannot process the request. The XML contains an invalid port number: %1!lu! The

value must be %2!lu! or more.

@The WS-Management service cannot process the request. The XML contains an invalid port number that is

too large: %1!lu! The value must be %2!lu! or less.

The WS-Management service cannot process the configuration request. The XML contains an invalid setting type: %1!d!.

The WS-Management service cannot process the configuration request. The XML contains an invalid setting: %1!d!.

LThe WS-Management service cannot process the configuration request. The XML contains an invalid setting %1. The

value is longer than the maximum length of %2!d!

The WS-Management service cannot process the configuration request because it cannot enable the %1 privilege.

This privilege is required to set security on registry keys. The error code is %2!d!.

The WS-Management service cannot process the configuration request because it cannot open a registry key.

The error code is %1!d!.

The WS-Management service cannot process the configuration request. The XML contains an unknown URI: %1.

The WS-Management service cannot process the configuration request. The XML contains a repeated element: %1.

PThe WS-Management service cannot process the configuration request. The XML contains a complex

element: %1. WS-Management configuration requires a simple element.

PThe WS-Management service cannot process the configuration request. The XML contains a simple element: %1.

WS-Management configuration requires a complex element.

The WS-Management service cannot process the configuration request. The WS-Addressing Action URI (%1) and

resource URI (%2) do not match. The %3 action can only be used on the %4 resource.

,The WS-Management service cannot process the configuration request. This action requires input XML with an element name of %1 and no parameters.

<Not used. To be removed.

The WS-Management service cannot process the request. The user does not have permission for the %1 operation

on the %2 resource.

The WS-Management service cannot process the request. The XML contains an invalid timeout field in the SOAP header: %1.

The WS-Management service cannot process the request. The URI does not contain keys, but the class is not a singleton.

LThe WS-Management service cannot process the request. The XML contains a timeout value that

is too small: %1!lu!. The timeout value must be larger than %2!lu!.

The WS-Management service cannot process the request. The SOAP header  %1 contains the mustUnderstand attribute, 

but  it is not a known header by this  WS-Management implementation. This could be caused by the use of a version 

of the protocol which is not supported, or may be an incompatibility between the client and server implementations.

The WS-Management service cannot process the request. The SOAP batch parameter %1 is invalid.

The WS-Management service cannot process the request. The SOAP packet did not contain a valid Timeout

element, was duplicated or the duration was not a valid xs:Duration. For example, the timeout PT30S is 30 seconds.

 <not used>

The WS-Management service cannot process the request. The data source failed to return the result.

0The WS-Management service cannot process the request. The data source failed to return the result URI from an

operation to create a new instance.

WS-Management could not connect to the specified destination: (%1:%2!d!).

@The operation was aborted.

WS-Management cannot process the request. The operation failed because of an HTTP error.

The HTTP error (%1!lu!) is: %2.

The server certificate on the destination computer (%1:%2!d!) has the following errors: %3 %4 %5 %6 %7 %8 %9 %10

WS-Management cannot process the request. The destination computer (%1:%2!d!) returned an 'access denied' error.

WS-Management cannot process the request. The HTTP response from the destination

computer was not in the same format as the request. A Unicode request packet may have been sent and an

ANSI packet received.

4The client specified username and password in the request to the destination computer. But the destination

computer requested a client certificate.

TWS-Management cannot process the request. The response received from the destination computer

includes element %1. But this element does not match what is expected.

WS-Management cannot process the request. The element %1 is missing from the response

sent by the destination computer.

|WS-Management encountered an invalid internal parameter.

4The WS-Management service cannot process the configuration request because the certificate

thumbprint in the request is not a valid hex string: %1.

The WS-Management service does not support concurrent event delivery operations.

|The WS-Management service encountered an internal error.

The WS-Management service cannot process the request. The response from the destination computer is invalid.

The WS-Management service cannot process the request because it cannot find the requested System.

The WS-Management service cannot process the request because the URI contains incorrect keys that WS-Management

cannot process.

The WS-Management service cannot process the request because port %1 is invalid.

The WS-Management service cannot process the request because IP address %1 is invalid.

pThe WS-Management service cannot process the configuration request because the transport is not supported

by the service: %1. The value should be one of the accepted values: %2.

PThe WS-Management service cannot process the configuration request because the configuration

for a static listening address requires an empty MAC address setting.

0The WS-Management service cannot process the request because the SOAP packet contained an invalid

or duplicate WS-Management SelectorSet element.

`The data source encountered the error: %1.

\The WS-Management service cannot process the configuration request. After a listener is configured,

you cannot change the value of the IP address or of the port number.

The WS-Management service received an invalid SOAP packet. The packet contains an invalid or missing WS-Management Delivery mode.

(The WS-Management service cannot process the configuration request. The configuration of a dynamic ip

address requires a MAC address setting.

PThe WS-Management service cannot process the configuration request. The SSL configuration for IP %1 and

port %2 is owned by another service and cannot be shared. 

The WS-Management service cannot process the request. The value for the selector %1 is invalid.

The WS-Management service cannot process the request because the maximum envelope size header was invalid or duplicated.

@The WS-Management service cannot process the request because the maximum envelope size requested

is (%1!lu!) too small. The size must be %2!lu! or larger.

DThe WS-Management service cannot process the request because the maximum envelope size requested

is (%1!lu!) too large. The size must be %2!lu! or smaller.

,The WS-Management service cannot process the request because the timeout value is too large: %1!lu! The

timeout value must be less than %2!lu!.

DThe WS-Management service cannot process the request. The computed response packet size (%1!lu!)

exceeds the maximum envelope size that is allowed (%2!lu!).

An arithmetic operation failed in function "%1". The error code is %2!d!.

The WS-Management service cannot process the request. The MAC address for the network

adapter does not have the dynamic IP address.

0The WS-Management service cannot process the enumeration request. The server is already executing

the maximum number of enumerations. Retry later.

The WS-Management service cannot process the request because the Endpoint Reference does

not contain a WS-Addressing Address element.

PWS-Management service cannot process the request because the WS-Addressing Address in the

Endpoint Reference (EPR) contains one or more unexpected child elements.

$The WS-Management service cannot process the request because the WS-Addressing EndPointReference (EPR)

contained an unexpected XML element.

$The WS-Management service cannot process the request because the WS-Addressing EndPointReference (EPR)

contained an unexpected XML element.

The WS-Management service cannot process the request because the WS-Addressing EndPointReference

contains a repeated child element: %1.

Not used.

The WS-Management service cannot process the request because the service does not support the action: %1.

The WS-Management service cannot process the request because the filter or dialect has syntax errors,

contains both a WS-Enumeration and WS-Management version of the filter, other semantic problems, or is

too complex.

(The data source cannot add another item to a WS-Management message envelope because a single

element in the batch exceeded the envelope size.

The WS-Management service cannot process the request. The SOAP packet that WS-Management received

did not contain a valid %1 element.

The WS-Management service cannot process the request because the XML in the SOAP packet is invalid.

<The WS-Management service cannot process the request. The URI generated from the CIM path is too long.

The maximum supported length is %1!d! characters.

The WS-Management service cannot process the request. The key %2 in an instance of class %3 has an unexpected CIM type.

The WS-Management service cannot process the request because the request contains an embedded object or

array of embedded objects. WS-Management does not support retrieving or updating instances containing

embedded objects or arrays of embedded objects.

The WS-Management service cannot process the request because a WMI instance contains an invalid char16 value: %1.

The WS-Management service cannot process the request because the XML contains an unknown CIM type for the property: %1.

The WS-Management service cannot process the request because the XML contains an invalid datetime value (%1) in

a WMI instance.

The WS-Management service cannot process the request. The request contains an XML element (%1) that does not

represent a string property. Only string properties can be empty. To specify a null value, add the xsi:nil

attribute to the element.

dThe WS-Management service cannot process the request. When setting an array property to null, only

one element with that name can be present in the input XML. Property: %1.

TThe WS-Management service cannot process the request because it contains several XML elements with

the same name for a property that is not an array. Property: %1.

hThe WS-Management service cannot process the request because it contains an invalid type for a

property qualifier on an instance or on the class. Property: %2 Qualifier: %1.

The WS-Management service cannot process the request because it contains an invalid empty string

for representing a number.

The WS-Management service cannot process the request because it contains an invalid character.

WS-Management cannot convert the string to a number. String: %1. Ensure that the string represents the correct datatype.

The WS-Management service cannot process the request. WS-Management cannot convert a string to an unsigned

number. The request contains an unexpected minus sign. String: %1. Ensure that the string represents the correct datatype.

The WS-Management service cannot process the request because the service cannot convert string %1 to a

number with %2!d! bits. The string does not represent a number in the allowed range. Ensure that the string

represents the correct datatype.

tThe WS-Management service cannot process the request because the request contains an invalid boolean

value (%1) for element %2. The value must contain "true", "false", "1", or "0".

DThe WS-Management service cannot process the request. An element of the array named %1 contains

the xsi:nil attribute. The array cannot have a NULL element.

PThe WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1.

Ensure that the string represents the correct datatype.

TThe WS-Management service cannot process the request. The XML contains an invalid xs:duration string: %1.

CIM datetime type does not accept more than 99999999 days.

xThe WS-Management service cannot process the request. The request contains an invalid datetime.

The string %1 does not represent any of these types: xs:dateTime, xs:date, or xs:time.

\The WS-Management service cannot process the request because it contains an invalid value for a

system property: %1. The value is not a string or it is an empty string.

The WS-Management service cannot process the request because the XML simple content is invalid: %1.

hThe WS-Management service cannot process the request because a class has an invalid Singleton qualifier.

The class is %1. The type is not boolean or the value is not 'TRUE'.

The WS-Management service cannot process the request. The element for a

datetime value must have exactly one child and no mixed content.

The WS-Management service cannot process the request. An element in a datetime property has an incorrect name: %1.

hThe WS-Management service cannot process the request because it cannot convert the string (%1) to a double value.

Ensure that the type that the string represents is correct.

The WS-Management service cannot process the request because it cannot convert the string (%1) to a floating

point value. The value is too large. Ensure that the type that the string represents is correct.

The element for a endpoint reference value must have one and only one child.

The WS-Management service cannot process the request. The action URI (%1) is invalid. Method %2 does not exist in class %3.

The WS-Management service cannot process the request. The elements for an array property (%1) must be in consecutive order.

0The WS-Management service cannot process the configuration request. The SSL configuration

for IP %1 and port %2 is shared with another service. Client certificates for Mutual configuration

must map to a user account. The other service does not have this http configuration.

The WS-Management service failed to set the user certificate for user authentication.

The WS-Management service cannot guarantee that all data is returned in the requested locale as some data sources

may not be able to comply. Resend the remote request with locale as a hint (the SOAP header should have

mustUnderstand="false").

$The WS-Management service cannot perform the configuration operation. A listener with Address=%1 and Transport=%2

configuration already exists. You have to delete the existing listener first in order to be able to create it with the same Address

and Transport values.

 The WS-Management service cannot process the request because the Endpoint Reference does

not contain a WS-Management ResourceURI element.

The xsi:type attribute is missing from element (%1). This attribute is required for embedded objects.

The WS-Management FragmentTransfer element has no text content.

The WS-Management FragmentTransfer element contains one or more child elements.

The SOAP packet that was received did not contain a valid WS-Management FragmentTransfer element, or was duplicated.

The response received from the destination machine includes unexpected element %1.

pThere is no filter specified for the given dialect.

The specified class does not exist in the given namespace.

dNo instance found with given property values.

The WS-Management service cannot process the request.

The WQL query is invalid.

Invalid policy setting %1;

The specified value %2!lu! is below the minimum required value of %3!lu!.

Invalid policy setting %1;

value must be no larger than %3!lu!, but given %2!lu!

|Invalid policy setting %1; the policy has the wrong type.

@Invalid policy setting %1;

DInvalid listener address %1. 

An exception was thrown (%1!d!) while parsing the following fragment path : %2.

Syntax error at position %1!d! for the following fragment path : %2.

Lexical error at position %1!d! for the following fragment path : %2.

Parsing error (%1!d!) at position %2!d! for the following fragment path : %3.

An absolute fragment path must start with the class name present in the resource URI.

(Node %1 is invalid : the previous node must correspond to a WMI object and this node must a property of that object

or the previous node must correspond to a datetime property and this node must have one of these values

(Datetime, Date, Time, Interval or CIM_DateTime).

Cannot apply text() function to array, object, datetime or reference properties.

The fragment path selected an unknown attribute. Only 'type' and 'nil' can be used.

The position of the element must be a non-zero positive integer. Value %1!lu! was given.

Node %1 does not correspond to an array property; position context cannot be used for it.

An attribute was selected by the fragment path, but updating attributes is not supported.

The input XML is not valid for this fragment-level Put operation : it must contain a single element

(the WS-Management XmlFragment element), which must have a simple content or be empty; empty content

is allowed only for string properties.

Node %1 selects a key property, but keys cannot be updated.

hThe input XML is not valid for this fragment-level Put operation : it must contain a single element

(the WS-Management XmlFragment element), which must have a single child with name matching the property to be updated;

 the child can have empty content only if the operation updates a string property.

The fragment path cannot select a property more than %1!d! levels deep.

The WS-Management service cannot process the request. The request contains more options than maximum supported(%1!d!).

`The WS-Management service cannot process the request because the SOAP packet that was received contained a invalid WS-Management OptionSet

element, or it was duplicated.

The WS-Management service Wmi plugin does not support the specified OptionSet because MustComply for one of the options is set.

`The resource URI does not support options.

The WS-Management service does not support the specified compression scheme (%1).

XThe config setting %1 cannot be changed because is controlled by policies.

The policy would need to be set to "Not Configured" in order to change the config setting.

There exists no property corresponding to index %1!d! in the specified array.

|WS-Management does not allow changes to a listener created automatically by the group policy.

The policy "Allow Auto Configuration of listeners on WinRm service" would need to be set to "Not Configured" in order to create

a new listener for same Address and Transport or to modify an already existing listener.

It is not allowed to change the value of the address or of the transport for a configured listener.

DThe WS-Management service cannot process the request because appending port number to service principal name cannot be executed.

Appending port number to the service principal name of the remote server requires a version of WinHTTP.dll that implements

WINHTTP_OPTION_SPN option flag.

8The requested operation cannot be performed. No default authorization schemes are available

when using HTTPS. Username and password must be specified.

The fragment path must not contain tokens longer than 1023 characters.

hUnit test plugin for Windows Remote Management

`WMIv1 plugin for Windows Remote Management

\SEL plugin for Windows Remote Management

\Test plugin for Windows Remote Management

TTest plugin for Windows Command Shell

tEvent collector plugin for Windows Remote Management

tBuilt-in catalog plugin for Windows Remote Management

pWinRM failed to load the plugin DLL for %1. Loading the DLL failed for the

path %2 with error code %3!d!. The plugin may be unavailable or the DLL may

not be properly installed.

WinRM cannot process the request because the request is missing the

element titled '%1'.

WinRM cannot process the request because a selector set contains text.

Selector sets must contain only '%1' elements.

WinRM cannot process the request because a selector set contains an

unrecognized element. Selector sets must contain only '%1' elements.

WinRM cannot process the request because a '%1' element is missing a '%2'

attribute.

WinRM cannot process the request because a selector contains multiple child

elements.

WinRM cannot process the request because a selector contains both text and a

child element. Remove the text.

WinRM cannot process the request because an option set contains text. Option

sets must contain only '%1' elements.

WinRM cannot process the request because an option set contains an

unrecognized element. Option sets must contain only '%1' elements.

WinRM cannot process the request because an option contains multiple child

elements or complex content.

WinRM cannot process the request because a key is either "" (blank or empty string) or NULL.

WinRM cannot process the request because an option contains a name attribute which is either "" (blank or empty string) or NULL.

WinRM cannot process the request because a WMI option value is NULL.

$WinRM cannot process the request because a non-array WMI option occurred more

than once. WMI array options must use the prefix 'wmiarray:'.

WinRM cannot process the request because a WMI option was defined both as an

array option and as a non-array option. WMI options must occur exactly once

with the prefix 'wmi:' or at least once with the prefix 'wmiarray:'.

The xsi:type attribute (%1) does not identify an existing class.

The XML namespace URI (%1) is invalid. Check the documentation for constructing the namespace URI for a CIM class.

%nThe SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable.

L%nThe SSL certificate is invalid.

P%nThe SSL certificate was revoked.

%nThe SSL certificate is signed by an unknown certificate authority.

%nThe SSL certificate contains a common name (CN) that does not match the hostname.

L%nThe SSL certificate is expired.

%nThe SSL certificate is not appropriate for server authentication.

p%nEncountered an internal error in the SSL library.

The WS-Management service cannot process the request. The resource URI (%1) was not found in the WS-Management catalog.

For getting Windows Remote Management configuration, use the following resource URI: %2.

8Cannot update an instance of class %1 using a representation of an instance for class %2; please provide a representation of an instance for class %1.

tBuilt-in catalog plugin for Windows Remote Management

lBuilt-in catalog plugin for Windows Command Shell

The WS-Management service cannot process the request because an embedded object

or reference element contains mixed content.

The WS-Management service cannot process the request because a date-time

element or simple property contains child elements.

\The WS-Management service cannot process the request because an element ("%1") is missing from the input XML. Non-array properties cannot be missing from the input XML.

WinRM cannot process the request because the XML parser unexpectedly reached

the end of input.

<Not used. To be removed.

<Not used. To be removed.

<Not used. To be removed.

<Not used. To be removed.

<Not used. To be removed.

WinRM cannot process the request because the input XML uses an undefined XML

namespace.

<Not used. To be removed.

<Not used. To be removed.

<Not used. To be removed.

The WinRM migrated configuration from R2 is corrupted. The listener configuration is not valid.

The WinRM configuration is corrupted. Use the following command to restore defaults:

%n%n

winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{}

%n%n

Then add any custom configuration settings.

The WS-Management service cannot process the request. The SOAP packet does not contain a valid

subscription ID element. The incoming Unsubscribe request should contain a header entry with the reference

property element obtained from the Subscribe response.

WinRM cannot process the configuration request.

The hostname pattern is invalid: "%1"

Hostname patterns must contain one or more patterns.

A pattern can contain at most one wildcard ("*").

The special pattern "<local>" can be used to indicate all hostnames that do not have a '.'.

To trust all hosts use "*" as the only pattern.

The WinRM client cannot process the request. The WinRM client received an 'access denied' error from the server

and it tried to send again the message, but the configuration changed and the new settings did not allow the message to be re-sent.

Try the request again with an authentication mechanism that is allowed by the updated configuration.

The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration.

Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server. 

To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain.

To use Basic, specify the computer name as the remote destination, specify Basic authentication and provide user name and password.

Possible authentication mechanisms reported by server: %1 %2 %3 %4 %5

The WinRM client cannot process the request. The destination computer (%1:%2!d!) returned an 'access denied' error.

Specify one of the authentication mechanisms supported by the server. If Kerberos mechanism is used,

verify that the client computer and the destination computer are joined to a domain.

Possible authentication mechanisms reported by server: %3 %4 %5 %6 %7

The WinRM client cannot process the request. The WinRM client tried to use %1 authentication mechanism, but the destination computer (%2:%3!d!) returned an 'access denied' error.

Change the configuration to allow %1 authentication mechanism to be used or specify one of the authentication mechanisms supported by the server.

To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain.

To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password.

Possible authentication mechanisms reported by server: %4 %5 %6 %7 %8

The WS-Management service cannot process the request.

The WS-Eventing NotifyTo element might be missing from the WS-Eventing Delivery section or it might be invalid.

It might be longer than the maximum length allowed.

 The WS-Management service cannot process the request.

The WS-Addressing Address element is missing from the WS-Eventing NotifyTo section.

The WS-Management service cannot process the request. The SOAP packet contains an WS-Addressing Address element in the WS-Eventing NotifyTo section

that is either invalid, duplicated, or too long.

pThe WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing expiration element 

that is either invalid, duplicated, not supported, or too long.

hThe WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing locale element that is either invalid, 

duplicated, not supported, or too long.

The WS-Management service cannot process the request. The SOAP packet contains an WS-Management heartbeat element that is invalid.

The WS-Management service cannot process the request. This request is valid only when the -remote option is specified. 

The WinRM client cannot process the request. API was called with no session.

<Not used. To be removed.

<Not used. To be removed.

The WS-Management service cannot process the configuration request. The XML contains a

value longer than the maximum length of %1!d!

WinRM cannot process the request. The requested locale '%1' contains an invalid

language code.

WinRM cannot process the request. The requested locale '%1' contains an invalid

country code.

,The WS-Management service cannot process the request. The batch is smaller (%1!d! bytes) than the

minimum size that is supported (%2!d! bytes).

8The WS-Management service cannot process the request. 

The WS-Eventing EndTo element is missing from the WS-Eventing Delivery section, or is invalid.

WinRM cannot process the configuration request. The service resource URI (%1) only supports the following actions: %2 and %3.

WinRM cannot process the configuration request. This action requires input XML with an element name of %1.

WinRM cannot process the configuration request. This action requires input XML with an element name of %1.

Create a WinRM listener on %1://%2 to accept WS-Man requests to any IP on this machine.

Created a WinRM listener on %1://%2 to accept WS-Man requests to any IP on this machine.

dCould not create a WinRM listener on %1://%2.

TEnable the WinRM listener on %1://%2.

XEnabled the WinRM listener on %1://%2.

hCould not enable the WinRM listener on %1://%2.

tThis resource requires the following selectors: %1 %2

TThis resource requires no selectors.

<Start the WinRM service.

lSet the WinRM service type to delayed auto start.

\Set the WinRM service type to auto start.

8WinRM service started.

TCould not start the WinRM service: %1

\WinRM service type changed successfully.

`Could not change the WinRM service type: %1

The WinRM service cannot process the request. A configuration setting or group policy setting denies access to the resource URI (%1).

HThe action URI (%1) is invalid.

The following authentication mechanisms were specified in the request: %1 %2 %3 %4 %5 %6

<Not used. To be removed.

The WS-Management service cannot process the request. The URI contains a invalid character (%1). 

WinRM cannot process the request. The following error with errorcode 0x%1!x! occurred while using %2 authentication: %3 %n

Possible causes are:%n

 -The user name or password specified are invalid.%n

 -Kerberos is used when no authentication method and no user name are specified.%n

 -Kerberos accepts domain user names, but not local user names.%n

 -The Service Principal Name (SPN) for the remote computer name and port does not exist.%n

 -The client and remote computers are in different domains and there is no trust between the two domains.%n

After checking for the above issues, try the following:%n

 -Check the Event Viewer for events related to authentication.%n

 -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.%n

Note that computers in the TrustedHosts list might not be authenticated.%n 

 -For more information about WinRM configuration, run the following command: winrm help config.

lUnable to check the status of the WinRM service.

`Unable to check the status of the firewall.

TEnable the WinRM firewall exception.

 <not used>

\Unable to enable the firewall for WinRM.

Warning: The WinRM firewall exception could not be enabled for all active profiles.

LWinRM firewall exception enabled.

The WinRM client received an HTTP status code of %1!d! from the remote WS-Management service.

The subscribe packet had a Locale element with missing lang attribute. The lang attribute is required for the Locale element. 

$WinRM cannot process the configuration request. This action requires input XML containing an element name of %1 with value "http" or "https".

|The Windows Remote Shell cannot process the request. The server is already executing

the maximum number of concurrent shells an user can remotely open on the same system. Retry later.

lThe Windows Remote Shell cannot process the request. The server exceeded the maximum number of users 

concurrently performing remote operations on the same system. Retry later.

The Windows Remote Shell cannot process the request. The server attempted to apply the quota limits for the Remote Shell object, however the system determined that the limits were invalid. 

Please correct the configuration settings, the settings can be viewed using the following command "winrm get winrm/config/winrs".

The Windows Remote Shell received a request to perform an operation on a command identifier that does not exist. Either the command has completed execution or the client specified an invalid command identifier.

The Windows Remote Shell cannot process the request because it requires the following selector: %1. Retry with the correct selector. 

HThe request for the Windows Remote Shell with ShellId %1 failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.

$Only one rsp:Send can be outstanding per instance of the shell or command. Resend the rsp:Send request after a rsp:SendResponse is received. 

8Only one rsp:Receive can be outstanding per instance of the shell or command. Resend the rsp:Receive request after a rsp:ReceiveResponse is received. 

0Only one rsp:Signal can be outstanding per instance of the shell or command. Resend the rsp:Signal request after a rsp:SignalResponse is received. 

The WS-Management service cannot process the request with a wsman:Locale different from that used in the initiating wxf:Create request.

Resend the remote request without locale or with the same locale initially used by wxf:Create.

The Windows Remote Shell cannot process the request. It is not permitted for other users then the initial creator to make use of a 

running shell instance, even if they have permissions to create shells themselves with the same or even greater privileges.

The administrator can enumerate all running shell instances, also get and delete a running shell instance.

The Windows Remote Shell cannot process the request. The resource URI is not valid or the service cannot find the resource identified by the resource URI and selectors.

The wsman:ResourceURI value should be %1 or be defined in the CustomRemoteShell table. 

Check the documentation or use the following command for information on how to populate CustomRemoteShell table: "winrm help customremoteshell".

The selectors are relative to the resource URI.

Retry the request with the correct resource URI or selectors.

The Windows Remote Shell cannot process the request. The command id returned from the shell plugin is empty.

The Windows Remote Shell cannot process the request. The WS-Addressing action URI is invalid. The valid actions are Command, Receive, Send and Signal.

Check the Windows Remote Shell documentation for information on how to construct an action URI.

The Windows Remote Shell cannot process the request. The SequenceId element is empty or invalid. 

The Windows Remote Shell cannot process the request. The computed response packet size exceeds the maximum envelope size that is allowed.

@The WS-Management service cannot process the fragment filter because the specified XPath filter is not supported.

Try simplifying the path and try again.

DThe Windows Remote Shell cannot process the request. The SOAP packet contains an element %1 that is invalid.

Retry the request with the correct XML element.

LThe WinRM client cannot process the request. The following setting is read-only and cannot be modified: %1.

Remove this setting from the command and try again.

|Subscription Manager plugin for Windows Remote Management

4The WS-Management service cannot process the request.

The SOAP packet contains a MachineID element that was either invalid, duplicated, or too long.

The WS-Management service configuration contains ambiguous entries in the URI security table: more than one pattern matches the following resource URI: %1.

Authorization process cannot continue. Fix the entries in the URI security table and try the request again.

<Windows Remote Management

DFull Control(All Operations)

DRead(Get,Enumerate,Subscribe)

<Write(Put,Delete,Create)

(Execute(Invoke)

$Only one Command can be outstanding per instance of the shell. You must terminate the command using Signal as the last message in all cases, whether the command is terminated early or run to completion. 

Resend the Command request after a SignalResponse is received. 

The filter contains a property (%1) that does not exist in the class.

lThe filter contains a property (%1) that is of an unsupported type.

Filtering is not supported on properties with the following types: datetime, 

reference, object, and array.

The resource URI (%1) does not support unfiltered enumeration.  One of the following filter dialects is required: %2.

It is not allowed to change the value of the Issuer,Subject or the URI for a configured certmapping entry.

|This resource requires the following selectors: %1 %2 %3

lThis resource requires the following selector: %1

DThe following selector is not a key property of the resource accessed : %1. 

Use selectors that are key properties for the resource that you want to access.

WinRM cannot process the request because the input XML contains an invalid XML header.

WinRM cannot process the request because the input XML contains a mismatched

element. The ending name does not match the starting name.

WinRM cannot process the request because the input XML contains an invalid

attribute or element name.

WinRM cannot process the request because the input XML contains an invalid

attribute.

WinRM cannot process the request because the input XML contains a syntax error.

WinRM cannot process the request because the input XML contains too many nested

levels of elements.

WinRM cannot process the request because an XML element has content or child elements but is 

marked as NULL with the xsi:nil attribute.

WinRM cannot process the request because a boolean attribute contains an

invalid boolean value.

The WinRM client cannot process the request. The batch items must be at least: %1!d!

The WinRM client cannot process the request. The max characters must be at least: %1!d!

The resource URI (%1) supports unfiltered enumeration and the following filter dialects: %2.

Invalid session option %1;

The specified value %2!lu! is below the minimum required value of %3!lu!.

Invalid session option %1;

the value is too large: %2!lu!. The value must be %3!lu! or less.

Invalid session option %1;

the type of the option is not valid.

lThis resource requires the following selector: %1

The configuration XML is not valid. The configuration XML contains an 

unexpected XML element: "%1" while element: "%2%" is expected at this point. 

Ensure that the elements are in correct sequence and that the spelling of the element name is correct.

The configuration XML is not valid. The configuration XML contains an invalid XML element: "%1". 

Ensure that the elements are in correct sequence and that the spelling of the element name is correct.

The configuration XML is not valid. The namespace for XML element: "%1" is not correct.

The configuration XML is not valid. Too many instances of XML element: "%1" found.

The configuration XML is not valid. The XML element: "%1" is expected but not found.

The configuration XML is not valid. Text for XML element: "%1" is not expected.

The configuration XML is not valid. Either attribute: "%1" is not expected for element: "%2" or its namespace is invalid.

The configuration XML is not valid. Attribute: "%1" is repeated for element: "%2".

The configuration XML is not valid. Attribute: "%1" is required for element: "%2".

The configuration XML is not valid. The configuration value length for attribute %1 exceeded the maximum limit of 10240 characters.

The configuration XML is not valid. Attribute value: "%1" is not a valid integer.

Valid integer values consist of the characters '0' through '9' and are no more than 10 digits in length.

The configuration XML is not valid. Attribute value: "%1" is not a valid boolean.

Valid boolean values are "true" and "false".

The configuration XML is not valid. Attribute value: "%1" is not a valid capability type.

Valid capability types are "Identify", "Get", "Put", "Create", "Delete", "Invoke", "Enumerate",  "Subscribe" and "Shell".

TThe configuration XML is not valid. Attribute value: "%1" is not a valid plugin name.

Plugin name cannot be empty and cannot exceeded 255 characters. Plugin name should not have any preceding space or tab characters.

The plugin name should not contain backslash and double quote characters.

The configuration XML is not valid. SDK Version: "%1" is currently not supported.

0The configuration XML is not valid. Attribute value: "%1" is not a valid xml rendering type.

Valid xml rendering types are "text" and "XmlReader".

The configuration XML is not valid. Resource Uri: "%1" is registered more than once in the

plugin configuration.

,The configuration XML is not valid. Resource Uri: "%1" is not valid. Plugin resource Uris cannot

have WSMan configuration root uri as a prefix.

The configuration XML is not valid. Resource Uri: "%1" cannot be exposed by more than one plugin.

The configuration XML is not valid. Capability: "%1" is defined multiple times for 

resource uri: "%2".

The configuration XML is not valid. Fragments are not supported for capability: "%1".

The configuration XML is not valid. Filters are not supported for capability: "%1".

The configuration XML is not valid. Resource uri: %1 cannot simultaneously support shell 

capability with other capabilities.

The configuration XML is not valid. Value of attribute "name" does not match the given selector.

The configuration XML is not valid. Attribute value: "%1" is not a valid file path. 

Valid file path should be absolute, reside in the system32 directory and should point to an existing file.

HThe WS-Management service cannot process the request. Configuration for plugin: "%1" is corrupted.

This plugin needs to be reconfigured or deleted. Use the following command to delete a plugin configuration

%n%n

winrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz

%n%n

Or use the following command to restore default plugin configuration. 

Note that all external plugins will be unregistered during this restore operation.

%n%n

winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{}

The WS-Management service cannot process the request. The selector for plugin configuration cannot exceed 255 characters.

The WS-Management service cannot perform the configuration operation. A plugin configuration with plugin name=%1 already exists.

You have to delete the existing plugin configuration first in order to be able to create it with the same plugin name.

An error occurred while reading the IIS configuration. %n

File:  %1 %n

Line:  %2 %n

Issue: %3 

@The WSMan client cannot process the request. The authentication mechanism requested by the proxy is not supported by the client.

The only proxy authentication mechanisms supported are Negotiate, Basic or Digest.

Possible authentication mechanisms reported by proxy: %1 %2 %3 %4 %5

The WSMan client received a redirect status from the server, but the server did not give

the actual redirect location to use.

Configure CertificateThumbprint setting for the service, to be used for CredSSP authentication.

|Configured CertificateThumbprint setting for the service.

Could not configure CertificateThumbprint setting for the service.

The WS-Management service cannot process the request.

This user is allowed a maximum number of %1!d! concurrent shells, which has been exceeded.

Close existing shells or raise the quota for this user.

The WS-Management service cannot process the request.

This user is allowed a maximum number of %1!d! concurrent operations, which has been exceeded.

Close existing operations for this user, or raise the quota for this user.

LThe WS-Management service cannot process the request.

The user load quota of %1!d! requests per %2!d! seconds has been exceeded.

Send future requests at a slower rate or raise the quota for this user.

The next request from this user will not be approved for at least %3!d! milliseconds.

DThe WS-Management service cannot process the request.

The system load quota of %1!d! requests per %2!d! seconds has been exceeded.

Send future requests at a slower rate or raise the system quota.

The next request from this user will not be approved for at least %3!d! milliseconds.

DThe WSMan service could not launch a host process to process the given request. 

Make sure the WSMan provider host server and proxy are properly registered.

The WSMan provider host process did not return a proper response. 

A provider in the host process may have behaved improperly.

The configuration XML is not valid. Initialization xml attribute values for "Name" and "Value" cannot be empty.

Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.

Configured LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.

Could not configure LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.

The authorization plugin returned the following error: %1.

The WS-Management service cannot process the request.

This service is configured to allow a maximum of %1!d! concurrent shell users, which has been exceeded.

Retry your request after sometime or raise the quota for concurrent shell users.

(The WS-Management service cannot process the request. The SOAP packet did not contain a valid WS-Management ActivityId element. 

The element is duplicated or is not in the correct format. The ActivityId should be a 128 bit value in the UUID format specified as a string.

The WS-Management service cannot guarantee that the ActivityId will be used as the tracing is turned OFF by default. 

Resend the remote request with ActivityId as a hint (the SOAP header should have mustUnderstand="false").

DThe WS-Management service cannot process the request.

The configuration setting "%1" is deprecated and cannot be changed. Remove this setting and try again.

tThe configuration XML is not valid. Attribute value: "%1" is not a valid architecture type.

Valid architecture types are "32" on a 32-bit system; "32" and "64" on a 64-bit system.

dThe WSMan client cannot process the request. Proxy is not supported under HTTP transport. 

Change the transport to HTTPS and specify valid proxy information and try again.

The WSMan client cannot process the request. Proxy is not supported when the authentication mechanism with the server is Kerberos or CredSSP. 

Change the authentication mechanism to Negotiate or Digest or Basic and try again.

xThe configuration XML is not valid.

Resource Uri: "%1" is not valid.

The Resource URI does not conform to RFC 3986.

Change the Resource URI in the configuration XML and try again.

4The WS-Management service cannot process the request. The SOAP packet did not contain a valid remote shell CompressionType element. 

The element is duplicated, is not marked as must understand or is not in the correct format.

The only supported compression type is "xpress".

The configuration XML is not valid. Resource Uri: "%1" is reserved for the WSMan shell manager.

PThe configuration XML is not valid.

The provider "%1" supports the %2 method but it could not be loaded.

Verify that the provider exports the %2 method properly.

|Windows Remote Management - Compatibility Mode (HTTP-In)

,Configure "Network access: Sharing and security model for local accounts" policy to allow local users to authenticate as themselves over network.

0Configured "Network access: Sharing and security model for local accounts" policy to allow local users to authenticate as themselves over network.

@Could not configure "Network access: Sharing and security model for local accounts" policy to allow local users to authenticate as themselves over network.

The WS-Management service cannot process the request because the SOAP packet does not contain a valid SessionID element. Verify that the SessionID element is not a duplicate or GUID and retry the operation.

The WinRM service cannot process the request because the WinRS shell instance is already processing a connect operation.

The configuration XML is not valid. 

The value for the attribute "%1" must be between %2 and %3.

The configuration XML is not valid. 

The attribute "%1" can be specified only if the attribute "%2" is also specified.

The configuration XML is not valid. 

The attribute "%1" can be non-zero only if the attribute "%2" is set to true.

The configuration XML is not valid. 

The attribute "%1" can be specified only if the attribute "%2" is set to true, the attribute "%3" is specified, and the attribute "%4" is at least %5.

The configuration XML is not valid. 

The attribute "%1" must be specified to change the attribute "%2".

The configuration XML is not valid. 

The plugin "%1" is a default plugin and its attributes cannot be modified.

An error %1!d! was encountered while subscribing to a Group Policy change notification.

The configuration XML is not valid. A plugin cannot simultaneously support the shell capability with other capabilities.

The configuration XML is not valid. The quota %1 is not valid for this plugin.

 The configuration XML is not valid. The attribute value "%1" must be changed to a valid Server Buffering Mode value of either "%2"or "%3".

The WS-Management service cannot process the request. This user has exceeded the maximum number of %1!d! concurrent shells for plugin "%2".

Close the existing shells or raise the plugin quota for this user.

The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent users allowed for plugin "%2".

Retry the request later or raise the quota for concurrent users.

The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent shells allowed for plugin "%2".

Retry the request later or raise the Maximum Shells per Plugin quota.

The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent operations allowed for plugin "%2".

Retry the request later or raise the Maximum Shells per Plugin quota.

The WS-Management service cannot process the request. This service has exceeded its maximum of %1!d! concurrent operations per user allowed for plugin "%2".

Retry the request later or raise the Maximum Operations per User quota.

The WS-Management service cannot process the command. This service has exceeded its maximum of %1!d! concurrent commands per shell allowed for plugin "%2".

Retry the request later or raise the Maximum Commands per Shell quota.

The WS-Management service cannot process the command.

The service does not have minimum required resources to start a new operation for the plugin "%1".

Try the request later or lower the minimum requirement for the plugin.

The WS-Management service cannot process the request.

The WS-Management service cannot accept subscriptions to an indication class, when either the filter or the dialect is specified.

Retry with filter removed.

The verification of the runAs user credentials failed with the error %1!d!.

The WS-Management service cannot process the request.

The CIM namespace %1 is invalid.

The WS-Management service cannot process the request.

The class %1 does not exist in the %2 namespace.

`Configure service to allow remote requests.

Configure service to allow authenticating requests using Kerberos protocol.

Configure service to allow authenticating requests using Negotiate protocol.

Could not configure one or more configuration settings for the service.

dConfigured required settings for the service.

Modify the GP setting "Allow remote server management through WinRM" to either "Not Configured" or "Enabled".

Modify the GP setting "Disallow Kerberos authentication" to either "Not Configured" or "Disabled".

Modify the GP setting "Disallow Negotiate authentication" to either "Not Configured" or "Disabled".

Modify the GP setting "Allow remote server management through WinRM" to either "Not Configured" or "Disabled".

The WinRM client cannot process the request because the XML contains an unsupported type (%1).

The WS-Management service cannot process the request because no CIM namespace was specified.

Choose a valid CIM namespace and try again.

8Enabled remote access.

HUnable to enable remote access.

8Disabled remote access.

LUnable to disable remote access.

The WinRM client cannot process the request. "AllowRemoteAccess" setting is read-only and cannot be modified.

Use the following commands instead to change the remote access behavior:

%n%n

winrm invoke EnableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service

%n%n

winrm invoke DisableRemoting http://schemas.microsoft.com/wbem/wsman/1/config/service

0The WS-Management service cannot process the configuration request. The service resource URI %1 only supports the following actions: %2, %3 and %4.

$The WS-Management service cannot process the configuration request. The configuration resource URI %1 only supports the following action: %2.

WinRM cannot process the request. The following error occurred while using %1 authentication: Cannot find the computer %2. Verify that the computer exists on the network and that the name provided is spelled correctly.

The WS-Management service cannot process the request. There was no matching certificate mapping found for the requested resource URI.

The WS-Management service cannot process the request. Retry requests are not supported.

The WS-Management service cannot process the request. Operations involving multiple messages from the client are not supported.

0The WS-Management service cannot process the request. The configuration XML is not valid. The value for Quota %1 cannot be less than value for %2.

WinRM cannot process the request. The following error with error code 0x%1!x! occurred while using Negotiate authentication: %2 %n

This can occur if the provided credentials are not valid on the target server, or if the server identity could not be verified. 

If you trust the server identity, add the server name to the TrustedHosts list, and then retry the request.

Use winrm.cmd to view or edit the TrustedHosts list. Note that computers in the TrustedHosts list might not be authenticated.

For more information about how to edit the TrustedHosts list, run the following command: winrm help config.

Unable to enable remote access because of the following reason: %1.

The WS-Management service cannot process the request. The requested IdleTimeout of %1!d! is outside the allowed range. Specify an IdleTimeout value between %2!d! and %3!d!, and retry the operation.

,WinRM cannot process the request. The following error occurred while using Kerberos authentication: The computer %1 is unknown to Kerberos. Verify that the computer exists on the network, that the name provided is spelled correctly, and that the Kerberos configuration for accessing the computer is correct. The most common Kerberos configuration issue is that an SPN with the format HTTP/%1 is not configured for the target. If Kerberos is not required, specify the Negotiate authentication mechanism and resubmit the operation.

tThe WinRM client cannot process the request.

Property "%1" with MI type %2 does not match the expected type from the schema: %3.

Specify the correct type and retry the operation.

The metadata failed to be retrieved from the server, due to the following error: %1

The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x%1!x!

pThe WS-Management service cannot process the request. The SOAP packet contains an WS-Eventing Encoding element that is either not valid, 

duplicated, not supported, or too long.

TThe WS-Management service cannot process the request.

The object contains an unrecognized property: "%1".

Verify that the spelling of the property name is correct.

DThe WinRM client cannot process the request.

The object contains an unrecognized property: "%1".

Verify that the spelling of the property name is correct.

TThe WS-Management service cannot process the request.

The object contains an unrecognized argument: "%1".

Verify that the spelling of the argument name is correct.

DThe WinRM client cannot process the request.

The object contains an unrecognized argument: "%1".

Verify that the spelling of the argument name is correct.

0The WS-Management service cannot process the request.

The method name "%1" is not valid.

Verify that the spelling of the method name is correct.

The WinRM client cannot process the request.

The method name "%1" is not valid.

Verify that the spelling of the method name is correct.

%1 The network connection to %2 has been interrupted. Attempting to reconnect for up to %3!d! minutes...

T%1 Attempting to reconnect to %2 ...

p%1 The network connection to %2 has been restored.

\%1 The reconnection attempt to %2 failed.

%1 The reconnection attempt to %2 failed while trying to retrieve the CIM schema needed for the operation.

The WS-Management service cannot process the request. You must be an administrator in order to access the WinRS shell instance.

The WS-Management service cannot process the request. The WinRS shell instance is not accessible over a remote connection.

Unable to look up SID of group: "%1". 

Ensure that the group is valid.

Username specified looks like a Manged Service Account. Passwords to such accounts are managed and should not be specified.

The verification of the Managed Service Account failed with error %1!d!. Ensure that the account is valid.

Error

Warning

 Information

4WSMan API Initialize

8WSMan API Deinitialize

<WSMan Session initialize

@WSMan Session deinitialize

(WSMan API call

DAuto-detecting proxy settings

0User authentication

0User authorization

,Request handling

,Response handling

<Winrm service start/stop

0Winrm configuration

(Winrm Operation

<WinRM MI Protocol Handler

,WinRM MI Session

0WinRM MI Operation

4Winrm Verbose Message

The WS-Management service cannot process the request. The service cannot find the resource identified by the resource URI and selectors.

\The WS-Management service cannot process the request. The WS-Addressing action URI is invalid. Check the documentation for information on how to construct an action URI.

The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect format.

Check the documentation or use the following command for information on how to construct a resource URI: "winrm help uris". 

`An error was encountered inside the plugin.

The WS-Management service cannot complete the request. The WSManEnumerator object is full and no more items can be added.

The WS-Management configuration is corrupted. Use the following command to restore defaults:

%n%n

winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config @{}

%n%n

Then add any custom configuration settings.

The WS-Management service cannot process a pull request because a pull operation is already in progress.

The WS-Management enumeration session is finished or cancelled and cannot be used. Start a new enumeration.

The event subscription is already closed and cannot be used. Start a new subscription.

The event subscription session is closing and cannot be used. Start a new subscription.

|The application or script that has an event subscription did not request a pull operation within the heartbeat interval.

The subscription session was closed. Start a new subscription.

The event source did not return events within the heartbeat interval.

The subscription session was closed. Start a new subscription.

The WS-Management service does not support the specified timeout.

The value specified is smaller than the minimum allowed value for this setting.

Change the timeout value and try the request again.

The WS-Management service does not support the SOAP version specified in the request.

The WS-Management service does not support the encoding specified in the request.

The WS-Management service cannot process the request. The request contains one or more invalid SOAP headers.

@The WS-Management service cannot process a SOAP header in the request that is marked as mustUnderstand by the client. 

This could be caused by the use of a version of the protocol which is not supported, or may be an incompatibility 

between the client and server implementations.

The WS-Management service cannot process the request. The request does not have all the expected SOAP headers.

`The client cannot connect to the destination specified in the request.

Verify that the service on the destination is running and is accepting requests.

Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.

If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".

The WS-Management service does not support the action specified in the request.

 The WS-Management service cannot process the request because the resource is offline. Retry the request

later when the resource is online.

The WS-Management service cannot identify the format of the object passed to a Put or Create method.

The input XML may not be appropriate for the resource or uses the wrong schema for the resource.

Change the input XML in the request.

The expiration time passed to the WS-Management Enumerate method is not valid. The time value may be zero

or refer to a time in the past. Change the expiration time and try the request again.



The data source does not support expiration time. Remove the expiration time from the request and try the request again.

The data source does not support filtering. Remove the filter from the request and try the request again.

lThe filter dialect (the type associated with the filter) was not supported for this resource.

Change the filter dialect or remove it from the request and try the request again.

,The data source could not process the filter. The filter might be missing or it might be invalid.

Change the filter and try the request again. 

xThe WS-Enumeration context in the enumeration is not valid. Enumeration may have been completed or canceled.

You cannot use this enumeration context anymore. Start a new enumeration.

\The pull operation did not get any data in the MaxTime duration. But the enumeration is still valid.

The client can attempt to do another pull request to retrieve data.

The WS-Management service cannot renew the enumeration. Start a new enumeration.

hThe WS-Management service does not support the delivery mode for the specified resource. The client should change the

subscription to use one of the supported delivery modes.

xThe expiration time of the subscription is invalid. The time is either not supported, zero or a time that happened in the past.

Change the expiration time and try the request again.

The expiration time specified for subscription was invalid. Specify the expiration time as a duration.

The event source does not support filtering. Remove the filter from the request and try the request again.

The event source cannot process the specified filter.

Change the filter or remove it from the request and try the request again.

lThe event source cannot process the subscription.

The WS-Management service cannot renew the event subscription. Create a new subscription.

8The WS-Management service cannot complete the WS-Eventing request because the request had some unknown or invalid content and could

not be processed.

The WS-Management service cannot process the response because it is larger than the maximum size allowed.

The WS-Management service cannot process the request because the request packet does not have a valid SOAP body.

The resumption context specified in the subscription is invalid. It may have expired, or be in the wrong format.

The WS-Management service cannot complete the operation within the time specified in OperationTimeout. 

The event source does not support subscriptions that can be resumed.

The WS-Management service does not support the type of resumption requested by the subscription.

The request contains character encoding that is unsupported. WS-Management only supports requests that are

encoded in UTF-8 or UTF-16. Change the character encoding in the request and try the request again.

pThe URI is longer than the maximum length allowed.

The WS-Management service cannot process the request because the subscription ID is invalid.

The WS-Management service cannot process the batch request. The request must specify either MaxItems, MaxCharacters,

or MaxTime.

The receiver of the event did not acknowledge the event delivery.

Submit the subscription again without the acknowledgement option.

(The WS-Management service cannot process the request because the WS-Addressing Action URI in the request is not

compatible with the resource.

The WS-Management service cannot complete the WS-Addressing Action URI in the request because the resource

was already in use.

The WS-Management service cannot create the resource because it already exists.

The WS-Management service cannot complete the request because the receiver does not accept the delivery of events.

The receiver requests that the subscription be cancelled. Event receivers return this message to force the

cancellation of a subscription.

The WS-Management service cannot process the request because the encoding of the request exceeds an internal

encoding limit. Reconfigure the client to send messages which fit the encoding limits of the service.

|The WS-Management service cannot authenticate the sender.

The WS-Management service does not support the format of the WS-Addressing Endpoint Reference.

XThe bookmark in the subscription is invalid. The bookmark may be expired or corrupted. Issue a new subscription

without any bookmarks or locate the correct bookmark.

DThe WS-Management service cannot process the request because one or more options are not valid. The option names or

values may not be valid or they are used in incorrect combinations. Retrieve the catalog entry for the resource and

determine how to correct the invalid option values.

The WS-Management service cannot process the request because a parameter for the operation is not valid.

The WS-Management service cannot process the request. The resource URI is missing or it has an incorrect format.

Check the documentation or use the following command for information on how to construct a resource URI: "winrm help uris".

The WS-Management service requires a valid System URI to process the request.

The WS-Management service cannot process the request because the selectors for the resource are not valid.

The requested metadata is not available at the current address. Retry the request with a new address.

The WS-Management service is busy servicing other requests. Retry later.

The WS-Management service cannot rename the resource. The selectors for the resource are not correct. The

resource may exist already, the address may be incorrect, or the resource URI may be invalid. Change the

request and retry.

The SOAP XML in the message does not match the corresponding XML schema definition. Change the XML and retry.

The WS-Management service does not support the specified feature. Remove the unsupported feature from the request and retry.

The WS-Management service cannot process the request because the XML is invalid.

The WS-Management service cannot process the request because the URI contains an unexpected selector.

The event source is attempting to deliver an event when a delivery is in progress already.

pThe WS-Management service cannot locate the system.

The maximum envelope size in the request is too large.

Change the maximum envelope size and try the request again. 

The response that the WS-Management service computed exceeds the maximum envelope size in the request.

The response that the WS-Management service computed exceed the internal limit for envelope size.

The WS-Management service cannot process the request because the URI contains too many selectors.

The WS-Management service cannot process the request because it contains too many options.

The WS-Management service does not support the character set used in the request. Change the request to use UTF-8 or UTF-16.

The operation succeeded and cannot be reversed but the result is too large to send.

The WS-Management service does not support white space in the request XML.

(The WS-Management service does not support the filter dialect in the request. The filter dialect is the type of filter, such

as XPath or WQL.

The WS-Management service cannot process the request because it contains a bookmark that is expired.

pThe WS-Management provider does not support the specified option set because mustComply for one of the options is set to true.

Change mustComply for one of the options to false.

The WS-Management service cannot process the request because one or more of the options has an invalid name.

The WS-Management service cannot process the request because one or more of the options has an invalid value.

The WS-Management service cannot process the request. A parameter that is required for the operation is not the

correct type.

The WS-Management service cannot process the request. A parameter name is invalid.

The WS-Management service cannot process the request because the XML content has invalid values.

The WS-Management service cannot process the request because the XML content has missing values.

The WS-Management service cannot identify the format of the object passed to a Put or Create method.

The XML namespace for the input XML is invalid. Change the XML namespace for the input XML in the request.

The WS-Management service cannot process the request because an XML fragment in the URI is invalid.

The WS-Management service cannot process the request because the request did not contain all required selectors.

The WS-Management service cannot process the request because the request contained invalid selectors for the resource.

The WS-Management service cannot process the request because a value for a selector is of the wrong type.

The WS-Management service cannot process the request because a value for the selector is invalid.

The WS-Management service cannot process the request because the selectors for the resource are ambiguous.

The WS-Management service cannot process the request because the request contains duplicate selectors.

The WS-Management service cannot process the request because the request contains invalid selectors for the target resource.

The WS-Management service cannot process the request because the request contains an invalid URI for the target resource.

The WS-Management service cannot process the request because the request contains an invalid target system.

The WS-Management service cannot process a Create request because the target already exists.

The WS-Management service does not support the mode of authorization.

`The client does not support acknowledgment.

The data source does not support timeouts for the operation.

xThe WS-Management service does not support the locale.

The WS-Management service does not support the expiration time.

tThe WS-Management service does not retry deliveries.

dThe event source does not support heartbeats.

dThe event source does not support bookmarks.

The WS-Management service does not support the configuration for MaxItems.

The WS-Management service does not support the configuration for MaxTime.

The WS-Management service does not support the value in the configuration for MaxEnvelopeSize.

|The event source does not support the MaxEnvelopePolicy.

The WS-Management service does not support unfiltered enumeration.  

The WS-Management service does not support insecure addresses.

The WS-Management service does not support format mismatch.

The WS-Management service does not support the format of the security token.

The service returned a response that indicates that the method is unsupported.

The WS-Management service does not support the specified media type.

The WS-Management service does not support the addressing mode.

The WS-Management service does not support fragment transfer.

The client sent a request before the enumeration was initialized.

The WS-Management service failed to locate the component that can process the request.

A syntax error occurred in the query string for the resource URI.

The MAC that is configured is not in the list of enabled DHCP adapters on the computer.

The MAC address that is configured does not have any unicast addresses.

The WS-Management service cannot find the dynamic IP address on the adapter with the configured MAC address.

The WS-Management service cannot process the request because the envelope size in the request is too small.

,The WS-Management service cannot process the request. The EndPointReference contains more nested EndPointReferences

than WS-Management supports.

|The WS-Management service cannot initialize the request.

The WS-Management service cannot process the request because the timeout header in the request is invalid.

The WS-Management service cannot find the certificate that was requested.

The WS-Management service cannot process the request. The data source failed to return results for the request.

The enumeration is invalid because previous Pull request failed.

The WS-Management service cannot change a mutual configuration.

The WS-Management service does not support the specified enumeration mode.

The WS-Management service cannot guarantee that all data is returned in the requested locale as some

data sources may not be able to comply. Resend the remote request with locale as a hint (the SOAP

header should have mustUnderstand="false")

pThe WSMan group policy configuration is corrupted.

The listener address specified is invalid. The address can be specified in one of the following formats: *, IP:<ip_address>, MAC:<mac_address>.

Change the listener address and try the request again.

TCannot change GPO controlled setting.

The client is attempting to concurrently receive events from a single subscription session.This is not supported.

The source is sending event batches faster than the subscriber can consume.

This can happen if acknowledgments are not specified for the subscription and

new events are arriving from the source before the client has consumed them.

The source is sending events in a connection that did not match the security restrictions imposed by the client.

<The WS-Management client cannot process the request. The event source identity does not match the identity of the machine that the client subscribed to.

The client could not start a valid listener to receive subscription events based on the specified input settings.

The fragment path dialect is not supported for this resource.

Cannot execute the Fragment-Level operation. The fragment path cannot be missing if the fragment dialect is specified.

Cannot execute the Fragment-Level operation because of invalid value for the fragment dialect.

LCannot execute the Fragment-Level operation because the fragment path is invalid. Check the syntax of the fragment path string.

Also check the spelling and the case of the property names in the fragment path string: they have to match the spelling and the case of the resource properties.

XThe specified batch parameter is incompatible with the specified event delivery mode. This can happen if batchSettings for a specific mode are

passed for a different mode. For example, batchSettings like "MaxItems" and

"MaxLatency" are not compatible with single event push mode or pull mode.

The connectivity test from the push subscription source to the client failed. This can happen if the client machine initiating the push subscription

is unreachable from the server machine where the event source is located. Possible reasons include firewall or some other network boundary.

Modify subscription to use Pull based subscription.

LThe subscribe packet had an EndTo element address that does not match the NotifyTo element address or it was invalid. For subscription the EndTo element

need not be present in the subscription request. If it exists then it's address should match the address specified in NotifyTo element.

The event source sent an event packet whose header could not be processed by the client. This can happen if it was malformed

or if the header had a mustUnderstand attribute that could not be understood by the client.

DAn operation is being attempted on a session that is being closed.This can happen if the session that is being used is also being closed

by another thread.

The listener on which the subscription session was established is no longer valid. This can happen if the WSMAN service listener configuration has been changed

and a subscription was already active and using one of the configurations that was deleted.

TThe system failed to load the plugin.

The WS-Management service on the remote machine with which this subscription had been set up has requested that the subscription be closed.

This can happen if the WS-Management service on the remote machine was being shutdown.

To correct this problem restart the WS-Management service on the remote machine and re-create the subscription.

8The event source was unable to deliver events to the client.This can happen due to network issues preventing the source from connecting

to the client.

PAn unknown security error occurred.

tThe event source cancelled the subscription session.

TrustedHosts list contains an invalid hostname or hostname pattern.

The subscribe packet does not have NotifyTo element in the delivery section. 

The subscribe packet does not have Address element in the NotifyTo section. 

The subscribe packet contains invalid Address in the NotifyTo section. 

The subscribe packet contains invalid Locale value in the delivery section.

xThe subscribe packet contains invalid heartbeat value.

The WS-Management service cannot process the request. This request is valid only when the -remote option is specified. 

The WS-Management service does not support the options feature for the specified resource. Remove the options from the request and retry.

The subscribe packet contains batch size value which is smaller than supported value.

The WS-Management service cannot process the subscribe request. The delivery mode is either invalid or missing.

The WS-Management service cannot process the request. The provider method was not found.

The WinRM client could not create a push subscription because there are no listeners configured that match the specified hostname and transport, or because there is no enabled firewall exception on the port used by the selected listener.

Change the hostname and transport, create an appropriate firewall exception, or run winrm quickconfig.

The WinRM client could not process the request because credentials were specified along with the 'no authentication' flag.  

No user name, password or client certificate should be specified with the 'no authentication' option.

@The WinRM client cannot process the request. An invalid flag was specified for this request.

Remove or change the invalid flag and try the request again.

XThe WinRM client cannot process the request. The request must specify only one authentication mechanism.

If the No Authentication flag is set, no authentication mechanism should be specified.

Change the request to specify only one authentication mechanism or 'no authentication' and try again.

The WinRM client cannot process the request. The SPN Server Port can only be used when the authentication mechanism is Negotiate or Kerberos.

Remove the SPN Server Port or change the authentication mechanism and try the request again.

The WinRM client cannot process the request. The request must not include credentials when using a smart card or default certificate.

Remove the credentials or change the authentication mechanism and try the request again.

The WinRM client cannot process the request. Requests must include user name and password when Basic or Digest authentication mechanism is used.

Add the user name and password or change the authentication mechanism and try the request again.

The WinRM client cannot process the request. Requests must not include user name and password when a certificate is used for authentication.

Remove the user name and password or change the authentication mechanism and try the request again.

The WinRM client cannot process the request. Requests must include credentials if they specify the following flag: WSManFlagCredUsernamePassword.

Add the credentials or remove the WSManFlagCredUsernamePassword flag and try the request again.

The WinRM client cannot process the request. Requests with credentials must include the following flag: WSManFlagCredUsernamePassword.

Add the flag or remove the credentials and try the request again.

The WinRM client cannot process the request. Requests must include the certificate thumbprint when a certificate is used for authentication.

Change the request to include the certificate thumbprint and try again.

The WinRM client cannot process the request. Requests must include the type of certificate to use for authentication.

Change the request to include the type of the certificate and try again.

The WinRM client cannot process the request. Requests must include the location (machine or user certificate store) of the certificate used for authentication.

Change the request to include the location of the certificate and try again.

0The WinRM client cannot process the request. The certificate structure was incomplete.

Change the certificate structure and try the request again.

4The WinRM client cannot process the request. Credentials must not be provided for local requests.

Remove the credentials and try the request again.

PThe WinRM client cannot process the request. Connection options must not be provided for local requests.

Remove the connection options and try the request again.

The WinRM client cannot process the request. One of the parameters required for the WSManCreateSession function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManEnumerate function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManSubscribe function is null or zero.

Change the request to include the missing parameter and try again.

tThe WinRM client cannot process the request. The parameter that should contain the result of the request is null.

Change the request to include the missing parameter and try again.

`The WinRM client cannot process the request. The request is missing the session or enumeration handle.

Change the request to include the missing parameter and try again.

LThe WinRM client cannot process the request. The resource URI must not be "" (blank or empty string) or NULL.

Change the resource URI and try the request again.

The WinRM client cannot process the request. The resource locator was invalid.

Change the resource locator and try the request again.

@The WinRM client cannot process the request. The input XML must not be "" (blank or empty string) or NULL.

Change the input XML and try the request again.

The WinRM client cannot process the request. The maximum number of elements to be retrieved in a batch is too small.

Change the value for the maximum number of elements in a batch and try the request again.

The WinRM client cannot process the request. The maximum number of characters to be retrieved in a batch is too small.

Change the value for the maximum number of characters in a batch and try the request again.

DThe WinRM client cannot process the request. The action URI must not be "" (blank or empty string) or NULL.

Change the action URI and try the request again.

4The WinRM client cannot process the request. The heartbeat interval must be greater than 0.

Change the heartbeat interval and try the request again.

`The WinRM client cannot process the request. The request must contain one and only one delivery mode.

Change the request to contain only one delivery mode and try again.

The WinRM client cannot process the request. The request contained multiple settings for the policy regarding the maximum envelope size.

Change the request to contain only one setting for the policy and try again.

The WinRM client cannot process the request. The request contained an expiration time, but did not specify if it was absolute or relative.

Change the request to specify the type of the expiration time (absolute or relative) and try again.

The WinRM client cannot process the request. The request specified the type of the expiration time (absolute or relative) but it did not contain an expiration time.

Change the request to include the expiration time and try again.

XThe WinRM client cannot process the request. The pull subscription request contained flags related to a push subscription.

Change the flags and try the request again.

The WinRM client cannot process the request because the push subscription request contained an unsupported delivery transport. HTTP and HTTPS are the only currently supported transports.

Change the delivery transport and try the request again.

HThe WinRM client cannot process the request. The delivery address for push subscriptions was too long.

Change the delivery address and try the request again.

The WinRM client cannot process the request. The request contained the compression option but contained an unrecognized value.

Change the value for the compression option and try the request again.

The WinRM client cannot process the request. One of the parameters required for the WSManDeliverEndSubscriptionNotification function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManDeliverEvents function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManGetBookmark function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManDecodeObject function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManEncodeObject(Ex) function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorAddObject function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorNextObject function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManConstructError function is null or zero.

Change the request to include the missing parameter and try again.

4The WinRM service cannot process the request. Push subscriptions are not supported for local session. Change subscription type to Pull and try again.

tThe WinRM client cannot process the request. The unencrypted flag only applies to the HTTP transport.

Remove the unencrypted flag or change the transport and try again the request.

The WinRM client cannot process the request. Certificate parameters are not valid when the HTTP transport is also specified.

Remove the certificate parameters or change the transport and try again the request.

8The WinRM client cannot process the request. The connection string should be of the form [<transport>://]<host>[:<port>][/<suffix>] where transport is one of "http" or "https".

Transport, port and suffix are optional. The host may be a hostname or an IP address.

For IPv6 addresses, enclose the address in brackets - e.g. "http://[1::2]:80/wsman".

Change the connection string and try the request again.

The WinRM client cannot process the request. The connection string contains an unsupported transport.

Valid transports are "http" or "https".

Change the connection string and try the request again.

The WinRM client cannot process the request because the port specified in the connection string is not valid.

Verify the port and retry the request.

Valid values are between 1 and 65535.

Change the value for port and try the request again.

The WinRM client cannot process the request. The port specified in the configuration is invalid.

Valid values are between 1 and 65535.

Change the value for port and try the request again.

The WinRM service cannot process the request. WSMAN_FLAG_SEND_HEARTBEAT flag requires the event enumerator to be empty.

Change the flag or change the event enumerator and try the request again.

hThe WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration.

Change the client configuration and try the request again.

lThe WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration.

Change the client configuration and try the request again.

lThe WinRM client cannot process the request. Digest authentication is currently disabled in the client configuration.

Change the client configuration and try the request again.

The WinRM client cannot process the request. Negotiate authentication is currently disabled in the client configuration.

Change the client configuration and try the request again.

If this is a request for the local configuration, use one of the enabled authentication mechanisms still enabled.

To use Kerberos, specify the local computer name as the remote destination. 

To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password.

pThe WinRM client cannot process the request. Kerberos authentication is currently disabled in the client configuration.

Change the client configuration and try the request again.

xThe WinRM client cannot process the request. Certificate authentication is currently disabled in the client configuration.

Change the client configuration and try the request again.

The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain,

then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting.

Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.

You can get more information about that by running the following command: winrm help config.

The WinRM client cannot process the request. 

Default credentials with Negotiate over HTTP can be used only if the target machine is part of the TrustedHosts list or the Allow implicit credentials for Negotiate option is specified.

DThe WinRM client cannot process the request. The CertificateThumbprint property must be empty when the SSL configuration will be shared with another service.

The WinRM client cannot process the request. The CertificateThumbprint property must not be "" (blank or empty string) or NULL.

The WinRM client cannot process the request. The WinRM client tried to create an SSL configuration for a pair of IP address and port according to the request,

but the SSL configuration for that pair is owned by another service and cannot be shared. 

Use a different IP address and port combination and try the request again.

The WinRM client cannot process the request. The certificate CN and the hostname that were provided do not match.

 <not used>

LThe WinRM client cannot process the request. When HTTP is the transport, the Certificate thumbprint must be blank.

HTTP does not use the Certificate thumbprint.

@The WinRM client cannot process the request. The IP Filter is invalid.

Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using , as delimiter.

* is used to indicate that the service should listen on all available IPs on the machine.

When * is used, other ranges in the filter are ignored. If filter is blank, the service doesn't listen on any address.

For example, if service should be restricted to listen on only IPv4 addresses, IPv6 filter should be left empty.

%nExample IPv4 filters:

2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22



%n Example IPv6 filters:

3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562

The WinRM client cannot process the request. The input XML modifies selectors or keys for the instance.

You cannot create a new instance or change the identity of an instance by changing the keys.

Change the input XML and try the request again.

The WinRM client cannot process the request. The Enhanced Key Usage (EKU) field of the certificate is not set to "Server Authentication".

Retry the request with a certificate that has the correct EKU.

The WinRM client cannot process the request. The response from the destination computer does not include any results.

The WinRM client cannot process the request. The response to a create request did not contain a valid end point reference.

The ResourceCreated element was not found or did not contain valid content.

 The WinRM client cannot process the request. The response from the destination computer does not contain a valid SOAP enumeration context.

The WinRM client cannot process the request. The response from the destination computer contains a WS-Management FragmentTransfer header but the content of the body is not wrapped by the WS-Management XmlFragment wrapper.

The WinRM client cannot process the request. The response from the destination computer contains one or more invalid SOAP headers.

$The WinRM client cannot process the request. It cannot find any SOAP Headers or Body elements in the response from the destination computer.

The WinRM client cannot process the request. The destination computer returned an empty response to the request.

The WinRM client cannot process the request. The destination computer returned an invalid SOAP fault.

dThe WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.

The WinRM client cannot process the request. The HTTP response from the destination computer was not in the same format as the request. A Unicode request packet may have been sent and an ANSI packet received.

The WinRM client cannot process the request. The encrypted message body has an invalid format and cannot be decrypted. Ensure that the service is encrypting the message body according to the specifications.

The WinRM client cannot process the request. The resource URI is not valid: it does not contain keys, but the class selected is not a singleton.

To access an instance which is not a singleton, keys must be provided.

Use the following command to get more information in how to construct a resource URI: "winrm help uris".

,The WinRM client cannot process the request. The resource URI for an enumeration operation with WQL filter must not contain keys and the class name must be '*' (star).

Use the following command to get more information in how to construct a resource URI: "winrm help uris".

The WS-Management identification operation is only available on remote sessions.

Subscribe operation with Push delivery mode is only available on remote sessions.

The subscription manager address is invalid. The response was not received from the address to which the subscription request was sent.

Only subscriptions with Pull delivery mode are supported by the plugin.

WinRM cannot process the request because the WMI object contains too many levels of nested embedded objects.

The WS-Management service cannot process the request. 

It does not support retrieving a WMI object that contains a property of type CIM_REFERENCE and the value of that property contains a remote machine name.

(The WS-Management service cannot process the request. The WMI service reported that the WMI provider could not perform the requested operation.

The WS-Management service cannot process the request. A value retrieved from the WMI service or the WMI provider is invalid.

The WS-Management service cannot process the request. The WMI service returned an 'access denied' error.

The WS-Management service cannot process the request. The WMI provider returned an 'access denied' error.

<The WS-Management service cannot process the request. An 'access denied' error was received when connecting to the WMI service on the computer specified.

The WS-Management service cannot process the request because the filter XML is invalid.

The WS-Management service cannot process the request. The resource URI for an Enumerate operation must not contain keys.

Cannot execute the Fragment-Level operation because the fragment path contains either "" (blank or empty string) or NULL.

Change the value of the fragment path and try the request again.

4The WinRM client cannot process the request. The response received from the destination machine contains invalid characters and cannot be processed.

The WinRM client cannot process the request.

Kerberos authentication cannot be used when the destination is an IP address.

Specify a DNS or NetBIOS destination or specify Basic or Negotiate authentication.

The WinRM client cannot process the request. Kerberos authentication cannot be used with implicit credentials if the client computer is not joined to a domain.

Use explicit credentials or specify a different authentication mechanism than Kerberos.

The WinRM client cannot process the request. The batch settings parameter is invalid.

The WinRM client cannot process the request. If you do not specify an authentication mechanism or you specify Kerberos, then you cannot use "localhost" or "127.0.0.1" or "[::1]" for the remote host name.

You can explicitly specify a different authentication mechanism than Kerberos or specify the remote host as a DNS name or NetBIOS name.

The WinRM client received an unknown HTTP status code from the remote WS-Management service.

The WinRM client received a HTTP redirect status code from the remote WS-Management service. WinRM does not support redirects.

<The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota.

The connection to the specified remote host was refused.

Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL.

The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available.

This is usually returned by a HTTP server that does not support the WS-Management protocol.

The subscribe packet had a Locale element with missing lang attribute. The lang attribute is required for the Locale element. 

Cannot create a WinRM listener on HTTPS because this machine does not have an appropriate certificate. To be used for SSL, a certificate must have a CN matching the hostname, be appropriate for Server Authentication, and not be expired, revoked, or self-signed.

Firewall does not allow exceptions; WinRM cannot be setup for remote access.

The Windows Remote Management (WinRM) service cannot be configured for remote access because Group Policy does not allow local firewall changes. Check the Group Policy settings to allow local firewall exceptions and add WinRM to the firewall exceptions.

The WinRM client cannot process the request because the selector name is not valid. Change the selector name and retry the request.

The WS-Management service does not support the encoding type specified.

The WS-Management service cannot process the request because the selector values do not match a known resource, or the resource is offline. 

Retry the request later when the resource is online, or try a different selector.

The WS-Management service cannot process the request because the a header in the request is invalid.

The expiration time specified for enumeration was invalid. Specify the expiration time as a duration.

The WS-Management service received a request which specified a maximum number of elements, but the service does not support this feature.

Retry the request without this element specified.

The WS-Management service cannot process the request. The WMI provider returned an 'invalid parameter' error.

lThe WinRM client cannot process the request. The request must contain one and only one enumeration mode.

Change the request to contain only one enumeration mode and try again.

@The WinRS client cannot process the request. An invalid flag was specified for this request.

Remove or change the invalid flag and try the request again.

LThe WinRS client cannot process the request. One of the parameters required is null or zero.

Change the request to include the missing parameter and try again.

The data source could not process the filter. The filter might be missing, invalid or too complex to process.

If a service only supports a subset of a filter dialect (such as XPath level 1), it may return this fault for valid

filter expressions outside of the supported subset.

Change the filter and try the request again. 

The WinRM client cannot process the request. One of the parameters required for the WSManEnumeratorAddEvent function is null or zero. Change the request to include the missing parameter and try again.

lThe WinRM client cannot process the request. The object parameter for the WSManEnumeratorAddObject function is null or zero, but the enumeration mode is Object or ObjectAndEPR.

`The WinRM client cannot process the request. The EPR parameter for the WSManEnumeratorAddObject function is null or zero, but the enumeration mode is EPR or ObjectAndEPR.

WinRM cannot complete the operation.

Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer.

By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet.

<Not used. To be removed.

The WinRS client cannot process the Receive request because the shell plugin returned an empty response to the request.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WinrsCloseShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. The parameter required for the WinrsFreeCreateShellResult function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. The parameter required for the WinrsFreeRunCommandResult function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSMansReceiveShellOutput function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. The parameter required for the WinrsFreePullResult function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. One of the parameters required for the WinrsPull function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. The parameter required for the WinrsCloseReceiveHandle function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. One of the parameters required for the WinrsPush function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. The parameter required for the WinrsCloseSendHandle function is null or zero.

Change the request to include the missing parameter and try again.

The WinRS client cannot process the request. One of the parameters required for the WinrsGet function is null or zero.

Change the request to include the missing parameter and try again.

The WS-Management service does not support the specified polymorphism mode. Try changing the polymorphism mode specified, and try again.

@The WS-Management service cannot process the request because the specified URI is not supported on the service side. Retry the request with local session.

8The WS-Management service cannot process the request. A DMTF resource URI was used to access a non-DMTF class. Try again using a non-DMTF resource URI.

The WS-Management service cannot process the request. The DMTF class in the repository uses a different major version number from the requested class. This class can be accessed using a non-DMTF resource URI.

hThe WS-Management service cannot process the request. The resource URI and __cimnamespace selector attempted to use different namespaces. Try removing the __cimnamespace selector or using a DMTF resource URI. If a non-DMTF resource URI is used with a __cimnamespace selector, the namespaces must match.

The WS-Management client cannot process the request. To use the WSManSubscribe API the user has to be running under Network Service account. No other account is supported currently for push subscriptions.

The WS-Management client cannot process the request. The event source machine is not joined to a domain.

To set up a push subscription session to an event source the source has to be connected to a domain.

To fix this problem either join the event source machine to a domain or use PULL as the delivery mode for the subscription.

The WS-Management client cannot process the request. The subscriber machine is not joined to a domain.

To set up a push subscription session to an event source, the subscriber machine has to be connected to a domain.

To fix this problem either join the subscriber machine to a domain or use PULL as the delivery mode for the subscription.

4The WinRM client cannot process the request because it is trying to update a read-only setting.

Remove this setting from the command and try again.

The WinRS client cannot process the request. The server cannot set Code Page.

You may want to use the CHCP command to change the client Code Page to 437 and receive the results in English.

<Not used. To be removed.

<Not used. To be removed.

HThe WS-Management client received too many results from the server.

The server implementation should never return more items than are specified by the client.

DThe WinRM client cannot process the request. A certificate thumbprint was specified together with a user name or password. 

Only one credentials type can be specified. Remove the credentials type that does not correspond to the intended authentication mechanism and retry the request.

tThe WinRM client cannot process the request. The flag that specifies the authentication mechanism to use is incorrect.

Remove or change the invalid flag and try the request again.

The WinRM client cannot process the request. When an authentication mechanism is not specified, only user name and password credentials are allowed.

If you want to use a different type of credentials then you need to specify the authentication mechanism.

Specify the authentication mechanism or the correct credentials and try the request again.

The WinRM client cannot process the request. For authentication mechanisms that require the credentials of an user account, both user name and password must be specified.

Specify the missing user name or password and try the request again.

 The WinRM client cannot process the request. If you are using a machine certificate, it must contain a DNS name in the Subject Alternative Name extension or in the Subject Name field, and no UPN name.

If you are using a user certificate, the Subject Alternative Name extension must contain a UPN name and must not contain a DNS name.

Change the certificate structure and try the request again.

The WinRM Shell client cannot process the request. One of the environment variable name passed to the WSManCreateShell function is null or zero.

Change the request to include the missing parameter and try again.

<An operation is being attempted on a shell that is being closed. This can happen if the shell that is being used is also being closed by another thread.

The WinRM Shell client cannot process the request. One of the stream id name passed to the WSManCreateShell function is null or zero.

Change the request to include the missing parameter and try again.

$The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid.

The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again.

4The WinRM Shell client cannot process the request. The command handle passed to the WSMan Shell function is not valid.

The command handle is valid only when WSManRunShellCommand function completes successfully. Change the request including a valid shell handle and try again.

The WinRM Shell client cannot process the request. One of the argument value passed to the WSManRunShellCommand function is null or zero.

Change the request to include the missing parameter and try again.

PAn operation is being attempted on a command that is being closed. This can happen if the command handle that is being used is also being freed

by another thread.

The WinRM Shell client cannot process the request. The stream id index from within WSMAN_STREAM_ELEMENT passed to the WSManSendShellInput function is invalid.

The stream id index should be an index from within inputStreamSet array passed to the WSManCreateShell function.

Change the request with a valid index and try again.

<Not used. To be removed.

The WS-Management operations to update the certificate mapping store of the WINRM service config can only be done remotely.

8The WINRM certificate mapping configuration store has reached an internal limit and cannot create any more entries. Remove some entries and try again.

The WINRM certificate mapping configuration operation cannot be completed because the user credentials could not be verified. 

Please check the username and password used for mapping this certificate and verify that it is a non-domain account and try again.



The WinRM client cannot process the request. The Enhanced Key Usage (EKU) field of the certificate is not set to "Client Authentication".

Retry the request with a certificate that has the correct EKU.

The WinRM client cannot process the request. A certificate thumbprint was specified, but the following flag is missing: WSManFlagUseClientCertificate.

Add the flag and try the request again.

The WinRM client cannot process the request. The following flags cannot be specified together: WSManFlagUseClientCertificate and WSManFlagCredUsernamePassword.

Remove one of the flags and try the request again.

The WinRM client cannot process the request because the CustomRemoteShell URI specified is invalid.

CustomRemoteShell URI should start with WinRM shell resource URI prefix: "http://schemas.microsoft.com/wbem/wsman/1/windows/shell".

The URI should not contain invalid characters including '*', '?', white spaces and tabs.

The CustomRemoteShell URI cannot be longer than 1023 characters.

The WinRM client cannot process the request because the CustomRemoteShell URI specified is invalid.

Windows command shell URI ("http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd") cannot be a CustomRemoteShell URI.

The WinRM client cannot process the request because the process path specified for the CustomRemoteShell table entry is invalid.

The process path should be absolute and should point to an existing executable.

<Not used. To be removed.

The WinRM client cannot process the request because the provided security descriptor is invalid.

The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo is too complex or uses a structure not understood by the service.

The WinRM service supports a single layer of policy assertions underneath a wsp:ExactlyOne element.

The WinRM service cannot process the request because the WS-Policy contained in the DeliverTo does not contain any options that the service can comply with.

The WinRM service supports the following profiles: Negotiate or Kerberos over HTTP, Negotiate or Kerberos over HTTPS, and mutual certificate authentication over HTTPS using issuer thumbprints.

The WinRM service cannot process the request because the wsman:ConnectionRetry element in the DeliverTo is invalid.

WinRM cannot make the configuration change. 

The URI supplied for the certificate mapping operation is not valid. 

It must contain at least one character.

It must not contain internal whitespace.

It must not contain '?' character.

A prefix may be specified by using "*" as the last character.

The URI cannot be longer than 1023 characters.

WinRM cannot make the configuration change.

The Subject used for the certificate mapping operation is not valid. 

It must contain at least one character. 

It must contain at most one "*" character which should be the first character.

(This may be the only character in which case it matches all subjects). 

The Subject cannot be longer than 1023 characters.

WinRM cannot make the configuration change because the Issuer used for the certificate mapping operation is not valid. 

The certificate identified by the issuer thumbprint must be present in the machine "Trusted Root Certification Authorities" or "Intermediate Certification Authorities" store. 

The certificate must have key usage that allows it to sign other certificates.

The WinRM client cannot process the request because the type field in the WSMAN_ALLOWED_PUBLISHERS argument is invalid.

Collector-initiated subscriptions must use WSMAN_SINGLE_PUBLISHER and Source-initiated subscriptions must use WSMAN_MULTIPLE_PUBLISHERS.

The WinRM client cannot process the request because the delivery retry parameters are invalid.

If delivery retry is requested, the deliveryRetryInterval and deliveryRetryAttempts fields must both be nonzero.

lThe WinRM client cannot process the request.

The required WSMAN_ALLOWED_PUBLISHERS settings is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request because client certificate subject filters were specified without any issuers.

When using client certificate authentication, specify at least one issuer thumbprint.

The WinRM client cannot process the request because the subscription contains no domain or non-domain sources.

Subscriptions using WSMAN_MULTIPLE_PUBLISHERS must specify either a security descriptor or an issuer list or both.

The WinRM service cannot process the request because the subscription manager returned invalid enumeration results.

The m:Subscription XML object or m:Version element is missing or invalid.

WinRM firewall exception will not work since one of the network connection types on this machine is set to Public.

Change the network connection type to either Domain or Private and try again.

`WinRM cannot make the configuration change.

The Password used for updating the certificate mapping configuration is not valid. 

It cannot be longer than 255 characters.

WinRM cannot make the configuration change.

The Password used for updating the certificate mapping configuration is not valid. 

A user account used for configuring a certificate mapping cannot have a blank password.

WinRM cannot make the configuration change.

The credential used for updating or creating the certificate mapping configuration is not valid. 

The credential consists of both Password and UserName being supplied together in a pair.

The WinRM service executed an operation and the provider returned inconclusive information regarding success or failure of the operation.

The status was marked as failed, but no error code was given.

<The WS-Management service on the remote machine cannot process the shell request.

This can happen if the WS-Management service on the remote machine was being shutdown.

To correct this problem restart the WS-Management service on the remote machine and re-send the shell request.

The WinRM service cannot process the request. 

The URI parameter is the key to CustomRemoteShell table and cannot be modified.

<The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure.

<The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure.

\The WinRM service cannot make the configuration change.

The selector keys of Subject, URI or Issuer cannot be changed by overriding the selector key value in the body. 

The WinRM client cannot process the request because it received an HTML error packet.

The WinRM client cannot process the request. One of the parameters required for the WSManInitialize function is null or zero.

Change the request to include the missing parameter and try again.

XThe WinRM client cannot process the request. An invalid flag was specified for the WSManInitialize API call.

Remove or change the invalid flag and try the call again.

\The WinRM client cannot process the request. An invalid flag was specified for the WSManDeinitialize API call.

Remove or change the invalid flag and try the call again.

The WinRM client cannot process the request. One of the parameters required for the WSManSetSessionOption function is null or zero.

Change the request to include the missing parameter and try again.

`The WinRM client cannot process the request. One of the parameters required for the WSManSetSessionOption function is invalid.

Change the invalid parameter and try again.

DThe WinRM client cannot process the request. One of the parameters required to get a session option is invalid.

Change the invalid parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManCreateShell function is null or zero.

Change the request to include the missing parameter and try again.

\The WinRM client cannot process the request. An invalid flag was specified for the WSManCreateShell API call.

Remove or change the invalid flag and try the call again.

XThe WinRM client cannot process the request. An invalid flag was specified for the WSManCloseShell API call.

Remove or change the invalid flag and try the call again.

\The WinRM client cannot process the request. An invalid flag was specified for the WSManCloseCommand API call.

Remove or change the invalid flag and try the call again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManCloseCommand function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManRunShellCommand function is null or zero.

Change the request to include the missing parameter and try again.

dThe WinRM client cannot process the request. An invalid flag was specified for the WSManRunShellCommand API call.

Remove or change the invalid flag and try the call again.

@The WinRM client cannot process the request. You must wait for the WSManRunShellCommand API call to complete before calling WSManCloseShellOperationEx API.

The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element.

The CommandResponse element was not found or did not contain valid content.

8The WinRM client cannot process the request. The OptionSet element is invalid.

Change the request to include a valid OptionSet element and try again.

The WinRM client cannot process the request. The response to a Command request did not contain a valid CommandResponse element.

The CommandId element was not found or did not contain valid content.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManSignalShell function is null or zero.

Change the request to include the missing parameter and try again.

\The WinRM client cannot process the request. An invalid flag was specified for the WSManSignalShell API call.

Remove or change the invalid flag and try the call again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManSendShellInput function is null or zero.

Change the request to include the missing parameter and try again.

`The WinRM client cannot process the request. An invalid flag was specified for the WSManSendShellInput API call.

Remove or change the invalid flag and try the call again.

 The WinRM client cannot process the request. An invalid parameter was specified for the WSManSendShellInput API call. 

streamData parameter should be specified in binary format using WSMAN_DATA_TYPE_BINARY type. 

Change the invalid parameter and try the call again.

The WinRM Shell client cannot process the request. The stream name passed to the WSManSendShellInput function is not valid.

The input stream name should be specified as part of the input streams during shell creation using WSManCreateShell function. 

Change the request including a valid input stream name and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManReceiveShellOutput function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. The stream or list of streams passed to the WSManReceiveShellOutput function is not valid.

The desired stream names should be specified as part of the output streams during shell creation using WSManCreateShell function. 

Change the request including valid desired streams and try again.

hThe WinRM client cannot process the request. An invalid flag was specified for the WSManReceiveShellOutput API call.

Remove or change the invalid flag and try the call again.

The WinRM client cannot process the request. The response to a Receive request did not contain a valid ReceiveResponse element.

The ReceiveResponse element was not found or did not contain valid content.

dThe WSMan plugin configuration is corrupted.

The file path specified is either not absolute, not in the system32 directory, or not valid.

PThe file specified does not exist.

tThe WSMan extension failed to read IIS configuration.

The WinRM client cannot process the request. The locale option is invalid.

Change the locale and try again.

The WinRM client cannot process the request. The UI language option is invalid.

Change the UI language and try again.

The WinRM client cannot process the request. One of the parameters required for the WSManGetErrorMessage function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. The language code parameter is invalid. The language code parameter should be either NULL or a valid RFC 3066 language code.

Change the language code and try the request again.

dThe WinRM client cannot process the request. An invalid flag was specified for the WSManGetErrorMessage API call.

Remove or change the invalid flag and try the call again.

dThe WinRM service cannot process the request because the request needs to be sent to a different machine.

Use the redirect information to send the request to a new machine.

The WinRM client cannot process the request. The flag that specifies the proxy authentication mechanism to use is incorrect. 

Remove or change the invalid flag and try the request again.

The WinRM client cannot process the request. The credentials for proxy authentication are not specified correctly. Both user name and password credentials must be valid.

Specify the correct credentials and try the request again.

The WinRM client cannot process the request. The proxy access type is incorrect. Use one of the proxy access type flags; the flags cannot be combined.

Change the invalid proxy access type and try the request again.

The WinRM client cannot process the request. The direct connection to the server option cannot be used with non empty proxy authentication data. 

Change the invalid proxy access type or use empty proxy authentication data and try the request again.

The WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsDword function is null or zero.

Change the request to include the missing parameter and try again.

pThe WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsDword function is invalid.

Change the invalid parameter and try again.

pThe WinRM client cannot process the request. One of the parameters required for the WSManGetSessionOptionAsString function is invalid.

Change the invalid parameter and try again.

The WinRM client cannot process the request. Requests must include user name and password when CredSSP authentication mechanism is used.

Add the user name and password or change the authentication mechanism and try the request again.

The WinRM client cannot process the request.

CredSSP authentication is currently disabled in the client configuration.

Change the client configuration and try the request again.

CredSSP authentication must also be enabled in the server configuration.

Also, Group Policy must be edited to allow credential delegation to the target computer.

Use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Delegating Fresh Credentials. 

Verify that it is enabled and configured with an SPN appropriate for the target computer.

For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com

hThe WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer.

Use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Delegating Fresh Credentials. 

Verify that it is enabled and configured with an SPN appropriate for the target computer.

For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com.


The WinRM client cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer because the computer is not trusted.

The identity of the target computer can be verified if you configure the WSMAN service to use a valid certificate using the following command: winrm set winrm/config/service @{CertificateThumbprint="<thumbprint>"} 

Or you can check the Event Viewer for an event that specifies that the following SPN could not be created: WSMAN/<computerFQDN>. If you find this event, you can manually create the SPN using setspn.exe . 

If the SPN exists, but CredSSP cannot use Kerberos to validate the identity of the target computer and you still want to allow the delegation of the user credentials to the target computer, use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Fresh Credentials with NTLM-only Server Authentication. 

Verify that it is enabled and configured with an SPN appropriate for the target computer.

For example, for a target computer name "myserver.domain.com", the SPN can be one of the following: WSMAN/myserver.domain.com or WSMAN/*.domain.com.

Try the request again after these changes. 

|The WS-Management service cannot process the request.

The maximum number of concurrent shells for this user has been exceeded.

Close existing shells or raise the quota for this user.

The WS-Management service cannot process the request.

The maximum number of concurrent operations for this user has been exceeded.

Close existing operations for this user, or raise the quota for this user.

hThe WS-Management service cannot process the request.

The load quota for this user has been exceeded.

Send future requests at a slower rate or raise the quota for this user.

\The WS-Management service cannot process the request.

The load quota for the system has been exceeded.

Send future requests at a slower rate or raise the system quota.

The WS-Management service cannot complete the authorization under the given token.

A previous authorization attempt for the same user resulted in a different token.

The user record will be revoked and the next request will reauthorize.

An application tried to retrieve the HTTP Redirect location from the session when no redirect error (ERROR_WSMAN_REDIRECT_REQUESTED) was returned.

The application needs to be updated so as to only retrieve the location after this error is returned.

The WS-Management service cannot process the request.

The maximum number of users executing shell operations has been exceeded.

Retry after some time or raise the quota for concurrent shell users.

The WS-Management service cannot process the request.

The service is configured to not accept any remote shell requests.

The WS-Management service cannot complete the Pull operation for the enumeration because the wsman:MaxEnvelopeSize, wsen:MaxCharacters or wsen:MaxElements parameters differ from those specified to the enumeration.

The application needs to specify the same parameters for Pull as were specified for the enumeration.

8The WinRM service cannot process the request because it is trying to update a deprecated setting.

Remove this setting from the command and try again.

<The WS-Management service cannot process the configuration settings.

A Security element contains a URI that does not match its parent Resource element.

The WinRM client cannot process the request. Allow implicit credentials for Negotiate authentication option is only valid for HTTPS transport.

Remove the allow implicit credentials for Negotiate authentication option and try the request again.

The WinRM client cannot process the request. Setting proxy information is not valid when the HTTP transport is specified.

Remove the proxy information or change the transport and try the request again.

The WinRM client cannot process the request. Setting proxy information is not valid when the authentication mechanism with the remote machine is Kerberos.

Remove the proxy information or change the authentication mechanism and try the request again.

The WinRM client cannot process the request. Setting proxy information is not valid when the authentication mechanism with the remote machine is CredSSP.

Remove the proxy information or change the authentication mechanism and try the request again.

The WinRM client cannot process the request. The request must specify only one authentication mechanism for proxy.

Change the request to specify only one authentication mechanism and try again.

`The WinRM client received a redirect error from the server when it is not appropriate.  

The only time a redirect error can be reported correctly is during the authorization of a user.

This would result in a properly formatted redirect response from the server that includes the redirect endpoint.

The WinRM service received a redirect error from an authorization plug-in where the redirect location was too long.

The WinRM service received a HTTP redirect message redirecting the client but the location URL is invalid.

The WinRM service cannot process the request. The Channel Binding Token Hardening Level (CbtHardeningLevel) value is invalid.

The valid values are "None", "Relaxed" and "Strict". Change the CbtHardeningLevel value and try again.

The WinRM client cannot process the request because the server name cannot be resolved.

dThe SSL connection cannot be established.

Verify that the service on the remote host is properly configured to listen for HTTPS requests.

Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM.

If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https".

The WinRM client cannot process the request.

Default authentication may be used with an IP address under the following conditions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided.

Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.

For more information on how to set TrustedHosts run the following command: winrm help config.

The WinRM client cannot process the request.

Custom Remote Shell has been deprecated and cannot be used.

The WinRM client cannot process the request.

The feature in use has been deprecated and cannot be used.

The WinRM client used a parameter to specify the use of SSL while specifying http in the connection string.

The WinRM service cannot process the request because the security for this resource URI cannot be changed.

The WinRM service cannot process the request. The enumeration request expects a selector based filter to specify the shell identifier.

The WinRM service cannot process the request. The enumeration of end point resources for shell commands is not supported.

The WinRM Shell client cannot process the request because the shell name has exceeded 255 characters in length.

The WinRM runAs configuration operation cannot be completed because the user credentials could not be verified.

Verify that the username and password used for configuration are valid and retry the operation.

The WinRM service cannot process the request because the WinRS shell instance is currently disconnected.

The WinRM service cannot process the request. This WinRS shell instance does not support disconnect and reconnect operations

because it was created by an older WinRS client or its provider does not support the disconnect operation.

The WinRM service cannot process the request because the WinRS shell instance is connected to a different client.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManDisconnectShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShell function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManConnectShellCommand function is null or zero.

Change the request to include the missing parameter and try again.

The WinRM client cannot process the request. The body response is not a valid connect request response.

The WinRM Shell client cannot process the request. The command is currently terminating or was terminated.

The WinRM service cannot process the request. The WinRS shell instance is currently connected to a different client.

The WinRM client encountered an error while communicating with the WinRM service during the disconnect operation.

The shell has been disconnected and the streams were possibly suspended abruptly.

(The WinRM client cannot process the request. A disconnect operation cannot be performed on a WinRS shell instance that is already disconnected.

$The WinRM client cannot process the request. A reconnect operation cannot be performed on a WinRS shell instance that is currently connected.

An error was encountered while subscribing to the Group Policy change notification.

The WinRM Shell client cannot process the request. One of the parameters required for the WSManReconnectShellCommand function is null or zero.

Change the request to include the missing parameter and try again.

4The WinRM client cannot process the request. A reconnect operation cannot be performed on a WinRS shell command instance that is currently connected.

@The WinRM service cannot process the request because the command ID specified by the client is not a valid GUID. Modify the request and retry the request.

,The WinRM service cannot process the request because the shell ID specified by the client is not a valid GUID. Provide a valid ID and try again.

The WinRM service cannot process the request. A command already exists with the command ID specified by the client.

The WinRM service cannot process the request. A resource already exists with the shell ID specified by the client.

(The WinRM client cannot process the request. A disconnect operation cannot be performed on a WinRS shell command instance that is disconnected.

The WS-Management service cannot process the request. The resource URI for the Subscribe operation must not contain keys.

hThe WinRM client cannot process the request. 

A flag that is not valid was specified for the WSManDisconnectShell method.

Remove or change the flag and retry the operation.

The WinRM client cannot process the request

because the command handle is not associated with the provided shell handle.

<The WS-Management service did not receive a response for an extended semantics operation within the timeframe specified in the OperationTimeout setting.

The WS-Management service is configured to not allow remote requests. 

The WS-Management service cannot process the request because the stream is currently disconnected.

`The creation of a new Shell failed. Verify that the RunAsPassword value is correctly configured and that the Group Policy setting "Disallow WinRM from storing RunAs credentials" is Disabled or Not Configured.

To enable WinRM to store RunAs credentials, change this Group Policy setting to Disabled.

The supplied plugin configuration XML is not valid.

To enable WinRM to store RunAs credentials, change the "Disallow WinRM from storing RunAs credentials" Group Policy setting to Disabled.

The WinRM client cannot process the request because the XML instance does not match the class schema provided by the server.

The WinRM client cannot process the request because the XML contains an unsupported type. Verify the XML and retry the operation.

The WS-Management service cannot process the request.

The service is configured to reject remote connection requests for this plugin.

The WS-Management service cannot process the request. This user has exceeded the maximum number of concurrent shells allowed for this plugin.

Close at least one open shell or raise the plugin quota for this user.

The WS-Management service cannot process the request. The maximum number of users executing remote operations has been exceeded for this plugin.

Retry the request later or raise the quota for concurrent users.

The WS-Management service cannot process the request. The maximum number of concurrent shells allowed for this plugin has been exceeded.

Retry the request later or raise the Maximum Shells per Plugin quota.

The WS-Management service cannot process the request. The maximum number of concurrent operations allowed for this plugin has been exceeded.

Retry the request later or raise the Maximum Operations per Plugin quota.

The WS-Management service cannot process the request. This user has exceeded the maximum number of allowed concurrent operations.

Retry the request later or raise the Maximum Operations per User quota.

The WS-Management service cannot process the request. The maximum number of concurrent commands per shell has been exceeded.

Retry the request later or raise the Maximum Commands per Shell quota.

The WS-Management service cannot process the request.

There are not enough resources available to process this operation.

Retry the operation later or close one or more of the currently running operations.

The WinRM client cannot process the request because the MI Deserializer cannot be created.

The WinRM client cannot process the request because the metadata could not be deserialized.

The WinRM client cannot process the request because the metadata failed to be retrieved from the server.

The WinRM client cannot process the request because a WinRM session could not be created.

XThe WinRM client cannot process the request because the target object has a key property set to NULL.

Incomplete objects cannot be used as the target of an operation.

$The WinRM client cannot process the request as the server identity could not be verified. If the identity of the server is trusted, add it to the TrustedHosts list and retry the request.

Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated.

For more information on how to set TrustedHosts, run the following command: winrm help config

The WinRM client cannot process the request because the octet string array type is not supported.

The WS-Management service cannot process the request. The requested IdleTimeout is outside the allowed range.

The WinRM client cannot process the request because insufficient metadata is available.

The application does not allow all properties to be returned as strings, but the server does not support correctly typing the properties.

Change the request to allow all properties to be returned as strings and retry the request.

|The WinRM client cannot process the request because the MI_OperationOptions contained both a Resource URI and a Resource URI Prefix. Specify only one of these two options and try again.

,The WinRM client cannot process the request because keysOnly and WSMAN_ENUMERATIONMODE_OBJECTONLY were specified at the same time.

These two settings are incompatible.

Remove the WSMAN_ENUMERATIONMODE_OBJECTONLY option, or set keysOnly to MI_FALSE, and retry the request.

LThe WinRM client cannot process the request because the class name is not valid.

Supply a valid class name or set the Resource URI option and retry the request.

The subscribe packet contains an Encoding value that is not valid in the delivery section.

0The WinRM client cannot process the request.

The destination computer name must be a hostname or an IP address, and must not be a URL.

To use an IPv6 address, enclose the address in brackets, like the following: "[::1]".

The transport, port number, and URL prefix may be controlled by setting the appropriate destination options.

Change the destination computer name string and retry the operation.

The server does not support WS-Management Identify operations. Skip the TestConnection part of the request and try again.

The WS-Management service cannot process the operation. The operation is being attempted on a client session that is unusable. 

This may be related to a recent restart of the WS-Management service. Please create a new client session and retry the operation if re-executing the operation does not have undesired behavior.

The WS-Management service cannot process the operation. An attempt to create a virtual account failed. Ensure that WinRM service is running as Local System and that it has TCB privilege enabled.

The WS-Management service cannot process the operation. Virtual account feature is only available in Windows 7, Server 2008 R2 and above.

The WS-Management service cannot process the operation. An attempt to logon using the configured RunAs Managed Service Account failed.

The WS-Management service cannot process the operation. An attempt to query mapped credential failed. This will happen if the security context associated with WinRM service has changed since the credential was originally mapped.

`Microsoft-Windows-Windows Remote Management

PMicrosoft-Windows-WinRM/Operational

LMicrosoft-Windows-WinRM/Analytic

8Initializing WSMan API

lInitialization of WSMan API failed, error code %1

<Deinitializing WSMan API

pDeinitialization of WSMan API failed, error code %1

tCreating WSMan Session. The connection string is: %1

tWSMan Create Session operation failed, error code %1

4Closing WSMan Session

`Closing WSMan Session failed, error code %1

Setting WSMan Session Option (%1) - %2 with value (%3) completed successfully.

Creating WSMan shell with the ResourceUri: %1 and ShellId: %2

`WSMan shell creation failed, error code %1

\Running WSMan command with CommandId: %1

`Running WSMan command failed, error code %1

4Closing WSMan command

0Closing WSMan shell

Access Denied error: the %1 API caller does not match the creator of the application object

lInitialization of WSMan API completed successfuly

pDeinitialization of WSMan API completed successfuly

tWSMan Create Session operation completed successfuly

Setting WSMan Session Option (%1) - %2 failed, error code %3.

`Closing WSMan Session completed successfuly

\Closing WSMan shell failed, error code %1

`Closing WSMan command failed, error code %1

lClosing WSMan %1 operation failed, error code %2

The WinRM protocol handler has began loading for application %1.

hThe WinRM protocol handler completed unloading.

The WinRM protocol handler unloaded prematurely due to the following error: %2.

The WinRM protocol handler started to create a session at the following destination: %1.

hThe WinRM protocol handler closed the session.

The WinRM protocol session closed prematurely due to the following error: %2.

The WinRM protocol session began an operation of type %1 to the server. The operation accesses class %3 under the %2 namespace.

The WinRM protocol session successfully completed the operation.

The WinRM protocol operation failed due to the following error: %2.

0The maximum number of users (%1) executing shell operations has been exceeded.%nRetry after sometime or raise the quota for concurrent shell users.

0The %1 user is allowed a maximum number of %2 concurrent shells, which has been exceeded.%nClose existing shells or raise the quota for this user.

\The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. Error code %1

The WSMan host process was unexpectedly terminated. Error code %1

RunAs was disabled by Group Policy; WSMan service has erased all RunAs credentials.

pCreating WSMan shell on server with ResourceUri: %1

Received redirect status code from Network layer; status: 302 (HTTP_STATUS_REDIRECT); location: %1

\WSMan operation %1 completed successfully

Re-sending the request as a result of ERROR_WINHTTP_CANNOT_CONNECT, using next proxy

Re-sending the request as a result of ERROR_WINHTTP_NAME_NOT_RESOLVED, using next proxy

Network layer returned ERROR_WINHTTP_NAME_NOT_RESOLVED - The server name cannot be resolved. Aborting the operation

The client got a timeout from the network layer (ERROR_WINHTTP_TIMEOUT)

The client got a login failure from the network layer (ERROR_WINHTTP_LOGIN_FAILURE)

\WSMan operation %1 failed, error code %2

hWSMan operation %1 started with resourceUri %2

%1

Authenticating the user failed. The credentials didn't work.

LThe authentication mechanism (%1) requested by the client is not supported by the server.%nPossible authentication mechanisms reported by server: %2 %3 %4 %5 %6

The destination computer (%1) returned an 'access denied' error. Verify your credentials are correct.

The authentication mechanism requested by the proxy is not supported by the client. The only proxy authentication mechanism supported are Negotiate, Basic or Digest. %nPossible authentication mechanisms reported by proxy: %1 %2 %3 %4 %5

Authenticating the user with the proxy failed. The credentials didn't work.

<The server certificate on the destination computer (%1:%2) has the following errors: %3 %4 %5 %6 %7 %8 %9 %10. Fix the server certificate and try again.

pThe authorization of the user failed with error %1

Request for user %1 (%2) will be executed using WinRM virtual account %3 (%4)

DThe Winrm service is starting

XThe Winrm service started successfully

The WinRM service is unable to start because of a failure during initialization. The error code is %1

DThe Winrm service is stopping

`The Winrm service was stopped successfully

The WSMan service could not load current configuration settings as the settings are corrupted. The service is started with default settings instead. %n%n User Action %n Use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} 

HThe WSMan client could not load current configuration settings as the settings are corrupted. The client is operating with default settings instead. %n%n User Action %n Start the WinRM service and use the following command to restore defaults: %n%n winrm invoke Restore winrm/config @{} 

The WSMan service failed to restart the plugins marked for AutoRestart. The error code received was %1.

The WSMan service failed to restart the %1 plugin on service startup. The error code received was %2.

The WSMan service successfully restarted the following plugin on service startup: %1.

$The WSMan shell instance %1 will no longer support disconnect reconnect functionality because a non-supported request was sent by the client.

%1

The WinRM %1 failed to register for group policy change notifications. The error code is %2.

<Deletion of registry key %1 resulted in access denied. If this registry entry is not marked specifically as read only, this seems like a potential issue.

,Activity Transfer

`Plug-in reporting context for operation %1

hPlug-in reporting data object for operation %1

xPlug-in reporting data object and EPR for operation %1

Plug-in reporting data object and bookmark for operation %1

dPlug-in reporting data for operation Receive

`Plug-in reporting operation complete for %1

Plug-in getting operational information for parameter %1 and operation %2

Plug-in reporting the authorization for user %1 completed with error code %2

Plug-in reporting the authorization operation completed with error %1 for operation %2 and ResourceUri %3

lUpdating the quota for the user %1 with error code %2%n maxAllowedConcurrentShells=%3%n maxAllowedConcurrentOperations=%4%n timeslotSize=%5%n maxAllowedOperationsPerTimeslot=%6

The plugin called WSManPluginGetConfiguration with the parameter %1 and obtained a return value of %2.

The plugin called WSManPluginReportCompletion with the parameter %1 and obtained a return value of %2.

The plugin %1 is being shut down because it was idle for longer than the configured HostIdleTimeoutSecs quota.

dSignaling WSMan command failed, error code %1

8Signaling WSMan command

DSending input to the command

@Sending input to the shell

dSending input operation failed, error code %1

pCalling into WSMan to receive output from the shell

dWSMan receive operation failed, error code %1

tCalling into WSMan to receive output from the command

Getting message for error code %1 completed successfully. The languageCode parameter was: %2

XGetting WSMan Session Option (%1) - %2.

4Signaling WSMan shell

TSignaling WSMan shell, error code %1

8Closing WSMan operation

lClosing WSMan %1 operation completed successfully

LDisconnecting shell with Id : %1

\Disconnecting shell failed, error code %1

LReconnecting shell  with Id : %1

\Reconnecting shell failed, error code %1

HConnecting shell  with Id : %1

XConnecting shell failed, error code %1

\Reconnecting shell command  with Id : %1

lReconnecting shell command failed, error code %1

XConnecting shell command  with Id : %1

hConnecting shell command failed, error code %1

DAuto-detecting proxy settings

|Proxy AutoDetect done.%nProxy list: %1 %nBypass list: %2 

|Setting proxy info %n Proxy list: %1 %n Bypass list: %2 

SOAP [client sending index %1 of %2 total chunks (%3 bytes)] %4

SOAP [listener receiving index %1 of %2 total chunks (%3 bytes)] %4

\The %1 user is allowed a maximum number of %2 concurrent operations, which has been exceeded.%nClose existing operations for this user, or raise the quota for this user.

The user load quota of %1 requests per %2 seconds has been exceeded.%nSend future requests at a slower rate or raise the quota for the %3 user.%nThe next request from this user will not be approved for at least %4 milliseconds.

The system load quota of %1 requests per %2 seconds has been exceeded.%nSend future requests at a slower rate or raise the system quota.%nThe next request from the user %3 will not be approved for at least %4 milliseconds.

|The WinRM %1 has encountered network connectivity issues.

The WinRM Client is attempting to re-establish a network connection.

The WinRM Service has detected a new network connection from the client.

The WinRM %1 has successfully re-established a network connection.

The WinRM %1 failed to re-establish a network connection and is reporting a failure.

hThe WSMan host process was started for user %1.

pThe WSMan host process was terminated for user %1.

Sending the request for operation %1 to destination machine and port %2:%3

`Processing client request for operation %1

Entering the plugin for operation %1 with a ResourceURI of <%2>

PLeaving the plugin for operation %1

The WinRM service failed to enumerate DASH/SMASH specifications with MI error: %1.

hSending response error packet for ActionURI: %1

SOAP [client receiving index %1 of %2 total chunks (%3 bytes)] %4

SOAP [listener sending index %1 of %2 total chunks (%3 bytes)] %4

DEnumeration is shutting down

DSubscription is shutting down

Received the response from Network layer; status: 200 (HTTP_STATUS_OK)

An extended semantics callback timed out for the %1 operation.

tReceived the response from Network layer; status: %1

Sending HTTP error back to the client due to a transport failure.%nThe HTTP status code is %1%nThe error code is %2

`Sending timeout response for operation: %1

LSending response for operation %1

tReceived the response from Network layer; status: %1

WSMan operation %1 got suspended because of WSMan Shell disconnection.

WSMan operation %1 resuming because of WSMan Shell reconnection.

Network layer AutoLogon policy was set to Low as a result of a HTTP 401 response from Network layer

hNetwork layer AutoLogon policy was set to High

\The chosen authentication mechanism is %1

Sending HTTP 401 response to the client and disconnect the connection after sending the response

User %1 authenticated successfully using %2 authentication

The authentication using client certificate with subject %1 done successfully

`Authenticating the user using %1 mechanism

4Authorizing the user

pThe authorization of the user was done successfully

An error was encountered while processing an operation.%nError Code: %1%nError String:%2

An error was encountered while processing an operation.%nError Code: %1

Extra information.  Refer to the XML parameters for more details.

An unauthenticated connection from client %1 is terminated.

d[Filename:- %1; Line:- %2; Function:- %3;] %4

[Filename:- %1; Line:- %2; Function:- %3; ErrorCode:- %4] %5

xThe WinRM service loaded the following plugin: %1 (%2)

|The WinRM service unloaded the following plugin: %1 (%2)

The WinRM service is stopping because there was a failure registering for changes to the IP addresses. %n%n User Action %n Restart the WinRM service. %n%n Additional Data %n The error code was %1.

The WinRM service is stopping because there was a failure registering for changes to the configuration. %n%n User Action %n Restart the WinRM service. %n%n Additional Data %n The error code was %1.

4VS_VERSION_INFO
cE
cE?StringFileInfo040904B0LCompanyNameMicrosoft CorporationNFileDescriptionWSMan Resource DLLh$FileVersion10.0.17763.1 (WinBuild.160101.0800)6InternalNameWsmRes.dll.LegalCopyright Microsoft Corporation. All rights reserved.FOriginalFilenameWsmRes.dll.muij%ProductNameMicrosoft Windows Operating System>
ProductVersion10.0.17763.1DVarFileInfo$Translation	PADDINGX

Hacked By AnonymousFox1.0, Coded By AnonymousFox