0x00002711 | Usage: rpcping [-t ] [-s ] [-e |-f [,MajorVer]] [-O ] [-u ] [-a ] [-N ] [-I ] [-C ] [-T ] [-M ] [-S ] [-P ] [-F ] [-H ] [-o ] [-B ] [-b] [-E] [-q] [-c] [-A ] [-U ] [-r ] [-v ] |
Usage: rpcping [-t ] [-s ] [-e |-f [,MajorVer]] [-O ] [-u ] [-a ] [-N ] [-I ] [-C ] [-T ] [-M ] [-S ] [-P ] [-F ] [-H ] [-o ] [-B ] [-b] [-E] [-q] [-c] [-A ] [-U ] [-r ] [-v ] |
0x00002712 | Pings a server using RPC. Options are:-t - protocol sequence to use. Can be one of the standard RPC protocol sequences - ncacn_ip_tcp, ncacn_np, ncacn_http, etc. If not specified, default is ncacn_ip_tcp. -s - the server address. If not specified, the local machine will be pinged. E.g. server, server.com, 157.59.244.141 -e - the endpoint to ping. If none is specified, the endpoint mapper on the target machine will be pinged. This option is mutually exclusive with the interface (-f) option.-o - the binding options for the RPC ping. See the MSDN for more details (RpcStringBindingCompose and RPC over HTTP). -f [,MajorVer] - the interface to ping. This option is mutually exclusive with the endpoint option. The interface is specified as a UUID. If the MajorVer is not specified, version 1 of the interface will be sought. When interface is specified, rpcping will query the endpoint mapper on the target machine to retrieve the endpoint for the specified interface. The endpoint mapper will be queried using the options specified in the command line. -O - Object Uuid if the interface registerd one.-i - number of calls to make. The default is 1. This option is useful for measuring connection latency if multiple iterations are specified. -u - the security package (security provider) RPC will use to make the call. The security package is identified as a number or a name. If a number is used it is the same number as in the RpcBindingSetAuthInfoEx API. The table below gives the names and numbers. Names are not case sensitive: Negotiate - 9 or one of nego, snego or negotiate NTLM - 10 or NTLM SChannel - 14 or SChannel Kerberos - 16 or Kerberos Kernel - 20 or Kernel If you specify this option you must specify authentication level other than none. There is no default for this option. If it is not specified, RPC will not use security for the ping. -a - the authentication level to use. Possible values are connect, call, pkt, integrity and privacy. If this option is specified, the security package id (-u) must also be specified. There is no default for this option. If this option is not specified, RPC will not use security for the ping. |
Pings a server using RPC. Options are:-t - protocol sequence to use. Can be one of the standard RPC protocol sequences - ncacn_ip_tcp, ncacn_np, ncacn_http, etc. If not specified, default is ncacn_ip_tcp. -s - the server address. If not specified, the local machine will be pinged. E.g. server, server.com, 157.59.244.141 -e - the endpoint to ping. If none is specified, the endpoint mapper on the target machine will be pinged. This option is mutually exclusive with the interface (-f) option.-o - the binding options for the RPC ping. See the MSDN for more details (RpcStringBindingCompose and RPC over HTTP). -f [,MajorVer] - the interface to ping. This option is mutually exclusive with the endpoint option. The interface is specified as a UUID. If the MajorVer is not specified, version 1 of the interface will be sought. When interface is specified, rpcping will query the endpoint mapper on the target machine to retrieve the endpoint for the specified interface. The endpoint mapper will be queried using the options specified in the command line. -O - Object Uuid if the interface registerd one.-i - number of calls to make. The default is 1. This option is useful for measuring connection latency if multiple iterations are specified. -u - the security package (security provider) RPC will use to make the call. The security package is identified as a number or a name. If a number is used it is the same number as in the RpcBindingSetAuthInfoEx API. The table below gives the names and numbers. Names are not case sensitive: Negotiate - 9 or one of nego, snego or negotiate NTLM - 10 or NTLM SChannel - 14 or SChannel Kerberos - 16 or Kerberos Kernel - 20 or Kernel If you specify this option you must specify authentication level other than none. There is no default for this option. If it is not specified, RPC will not use security for the ping. -a - the authentication level to use. Possible values are connect, call, pkt, integrity and privacy. If this option is specified, the security package id (-u) must also be specified. There is no default for this option. If this option is not specified, RPC will not use security for the ping. |
0x00002713 | -N - specifies a server principal name. Same semantics as the ServerPrincName argument to RpcBindingSetAuthInfoEx. See the MSDN for more information on RpcBidningSetAuthInfoEx. This field can be used only when authentication level and security package are selected. -I - allows you to specify alternative identity to connect to the server. The identity is in the form user,domain,password where the three fields have the obvious meaning. If the user name, domain or password have special characters that can be interpreted by the shell be sure to enclose the identity in double quotes. You can specify * instead of the password and RPC will prompt you to enter the password without echoing it on the screen. If this field is not specified, the identity of the logged on user will be used. This field can be used only when authentication level and security package are selected. -C - a hex bitmask of flags. It has the same meaning as the Capabilities field in the RPC_SECURITY_QOS structure described in the MSDN. This field can be used only when authentication level and security package are selected. -T - can be static or dynamic. If not specified, dynamic is the default. This field can be used only when authentication level and security package are selected.-M - can be anonymous, identify, impersonate or delegate. Default is impersonate. This field can be used only when authentication level and security package are selected. |
-N - specifies a server principal name. Same semantics as the ServerPrincName argument to RpcBindingSetAuthInfoEx. See the MSDN for more information on RpcBidningSetAuthInfoEx. This field can be used only when authentication level and security package are selected. -I - allows you to specify alternative identity to connect to the server. The identity is in the form user,domain,password where the three fields have the obvious meaning. If the user name, domain or password have special characters that can be interpreted by the shell be sure to enclose the identity in double quotes. You can specify * instead of the password and RPC will prompt you to enter the password without echoing it on the screen. If this field is not specified, the identity of the logged on user will be used. This field can be used only when authentication level and security package are selected. -C - a hex bitmask of flags. It has the same meaning as the Capabilities field in the RPC_SECURITY_QOS structure described in the MSDN. This field can be used only when authentication level and security package are selected. -T - can be static or dynamic. If not specified, dynamic is the default. This field can be used only when authentication level and security package are selected.-M - can be anonymous, identify, impersonate or delegate. Default is impersonate. This field can be used only when authentication level and security package are selected. |
0x00002714 | -S - the expected SID of the server. For more information see the Sid field in the RPC_SECURITY_QOS structure in the MSDN. Using this option requires Windows .NET Server 2003 or higher. This field can be used only when authentication level and security package are selected. -Z - the EffectiveOnly setting to use. For more information see the EffectiveOnly field in the RPC_SECURITY_QOS structure in MSDN. Using this option requires Windows Vista or higher. This field can be used only when authentication level and security package are selected.-D - the security descriptor (in string format) of the server when using mutual authentication. For more information see the ServerSecurityDescriptor field in the RPC_SECURITY_QOS structure in MSDN. Using this option requires Windows 8 or higher. This field can be used only when authentication level and security package are selected.-P - specifies the identity to authenticate with to the RPC/HTTP proxy. Has the same format as for the -I option. Also, you must specify security package (-u), authentication level (-a), and authentication schemes (-H) in order to use this option. -F - the flags to pass for RPC/HTTP front end authentication. The flags may be specified as numbers or names The currently recognized flags are: Use SSL - 1 or ssl or use_ssl Use first auth scheme - 2 or first or use_first See the Flags field in RPC_HTTP_TRANSPORT_CREDENTIALS for more information. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -H - the authentication schemes to use for RPC/HTTP front end authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM Certificate - 65536 or Cert Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -B - the server certificate subject. For more information, see the ServerCertificateSubject field in the RPC_HTTP_TRANSPORT_CREDENTIALS structure in the MSDN. You must use SSL for this option to work. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -b - retrieves the server certificate subject from the certificate sent by the server and prints it to a screen or a log file. Valid only when the Proxy Echo only option (-E) and the use SSL options are specified. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -R - specifies the HTTP proxy. if it's 'none', we will not use HTTP proxy but directly attempt the RPC proxy. the value 'default' means to use the IE settings in your client machine. any other value will be treated as the explicit HTTP proxy. if you don't specify this flag, the default value is assumed, that is, the IE settings are checked. this flag is valid only when the -E (Echo Only) flag is enabled. |
-S - the expected SID of the server. For more information see the Sid field in the RPC_SECURITY_QOS structure in the MSDN. Using this option requires Windows .NET Server 2003 or higher. This field can be used only when authentication level and security package are selected. -Z - the EffectiveOnly setting to use. For more information see the EffectiveOnly field in the RPC_SECURITY_QOS structure in MSDN. Using this option requires Windows Vista or higher. This field can be used only when authentication level and security package are selected.-D - the security descriptor (in string format) of the server when using mutual authentication. For more information see the ServerSecurityDescriptor field in the RPC_SECURITY_QOS structure in MSDN. Using this option requires Windows 8 or higher. This field can be used only when authentication level and security package are selected.-P - specifies the identity to authenticate with to the RPC/HTTP proxy. Has the same format as for the -I option. Also, you must specify security package (-u), authentication level (-a), and authentication schemes (-H) in order to use this option. -F - the flags to pass for RPC/HTTP front end authentication. The flags may be specified as numbers or names The currently recognized flags are: Use SSL - 1 or ssl or use_ssl Use first auth scheme - 2 or first or use_first See the Flags field in RPC_HTTP_TRANSPORT_CREDENTIALS for more information. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -H - the authentication schemes to use for RPC/HTTP front end authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM Certificate - 65536 or Cert Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -B - the server certificate subject. For more information, see the ServerCertificateSubject field in the RPC_HTTP_TRANSPORT_CREDENTIALS structure in the MSDN. You must use SSL for this option to work. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -b - retrieves the server certificate subject from the certificate sent by the server and prints it to a screen or a log file. Valid only when the Proxy Echo only option (-E) and the use SSL options are specified. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. -R - specifies the HTTP proxy. if it's 'none', we will not use HTTP proxy but directly attempt the RPC proxy. the value 'default' means to use the IE settings in your client machine. any other value will be treated as the explicit HTTP proxy. if you don't specify this flag, the default value is assumed, that is, the IE settings are checked. this flag is valid only when the -E (Echo Only) flag is enabled. |
0x00002715 | -E - restricts the ping to the RPC/HTTP proxy only. The ping does not reach the server. Useful when trying to establish whether the RPC/HTTP proxy is reachable. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. To specify an HTTP proxy, use the -R flag. If an HTTP proxy is specified in the -o flag, this option will be ignored. -q - quiet mode. Does not issue any prompts except for passwords. Assumes 'Y' response to all queries. Use this option with care. -c - use smart card certificate. RPCPing will prompt user to choose smart card. -A - specifies the identity to authenticate with to the HTTP proxy. Has the same format as for the -I option. Also, you must specify authentication schemes (-U), security package (-u) and authentication level (-a) in order to use this option. -U - the authentication schemes to use for HTTP proxy authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM You must specify security package (-u) and authentication level (-a) in order to use this option.-r - if multiple iterations are specified, this option will make rpcping display current execution statistics periodically instead after the last call. The report interval is given in seconds. Default is 15. -v - tells rpcping how verbose to make the output. Default value is 1. 2 and 3 provide more output from rpcping. Example: Find out if your Exchange server that you connect throughRPC/HTTP is accessible: rpcping -t ncacn_http -s exchange_server -o RpcProxy=front_end_proxy -P \"username,domain,*\" -H Basic -u NTLM -a connect -F 3When prompted for the password, enter it. exchange_server is the name ofyour exchange server, front_end_proxy is the name of your proxy, usernameand domain are your user name and domain as you would enter them in theOutlook prompt. The other parameters will ask rpcping to ping yourExchange server in exactly the same way as Outlook will connect to it forthe typical profile.-p - Prompt for credentials if authentication fails. |
-E - restricts the ping to the RPC/HTTP proxy only. The ping does not reach the server. Useful when trying to establish whether the RPC/HTTP proxy is reachable. Also, you must specify security package (-u) and authentication level (-a) in order to use this option. To specify an HTTP proxy, use the -R flag. If an HTTP proxy is specified in the -o flag, this option will be ignored. -q - quiet mode. Does not issue any prompts except for passwords. Assumes 'Y' response to all queries. Use this option with care. -c - use smart card certificate. RPCPing will prompt user to choose smart card. -A - specifies the identity to authenticate with to the HTTP proxy. Has the same format as for the -I option. Also, you must specify authentication schemes (-U), security package (-u) and authentication level (-a) in order to use this option. -U - the authentication schemes to use for HTTP proxy authentication. This option is a list of numerical values or names separated by comma. E.g. Basic,NTLM. Recognized values are (names are not case sensitive: Basic - 1 or Basic NTLM - 2 or NTLM You must specify security package (-u) and authentication level (-a) in order to use this option.-r - if multiple iterations are specified, this option will make rpcping display current execution statistics periodically instead after the last call. The report interval is given in seconds. Default is 15. -v - tells rpcping how verbose to make the output. Default value is 1. 2 and 3 provide more output from rpcping. Example: Find out if your Exchange server that you connect throughRPC/HTTP is accessible: rpcping -t ncacn_http -s exchange_server -o RpcProxy=front_end_proxy -P \"username,domain,*\" -H Basic -u NTLM -a connect -F 3When prompted for the password, enter it. exchange_server is the name ofyour exchange server, front_end_proxy is the name of your proxy, usernameand domain are your user name and domain as you would enter them in theOutlook prompt. The other parameters will ask rpcping to ping yourExchange server in exactly the same way as Outlook will connect to it forthe typical profile.-p - Prompt for credentials if authentication fails. |
0x00002725 | Out of memory |
Out of memory |
0x00002726 | Cannot allocate %1!d! bytes |
Cannot allocate %1!d! bytes |
0x00002728 | Invalid switch: %1!s! |
Invalid switch: %1!s! |
0x00002729 | Invalid option %1!c!, missing required parameter |
Invalid option %1!c!, missing required parameter |
0x0000272A | RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006 |
RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006 |
0x0000272B | %1!s! |
%1!s! |
0x0000272D | If you specify auth identity, you must specify authentication level and security package |
If you specify auth identity, you must specify authentication level and security package |
0x0000272E | If you specify identity tracking, you must specify authentication level and security package |
If you specify identity tracking, you must specify authentication level and security package |
0x0000272F | If you specify impersonation type, you must specify authentication level and security package |
If you specify impersonation type, you must specify authentication level and security package |
0x00002730 | If you specify a SID, you must specify authentication level and security package |
If you specify a SID, you must specify authentication level and security package |
0x00002731 | To prompt for credentials, you must specify authentication level and security package |
To prompt for credentials, you must specify authentication level and security package |
0x00002732 | Cannot parse security package id |
Cannot parse security package id |
0x00002733 | Cannot parse authentication level |
Cannot parse authentication level |
0x00002734 | Cannot parse flags string |
Cannot parse flags string |
0x00002735 | Cannot parse auth schemes array |
Cannot parse auth schemes array |
0x00002736 | Cannot parse identity tracking mode |
Cannot parse identity tracking mode |
0x00002737 | Cannot parse impersonation type |
Cannot parse impersonation type |
0x00002774 | Error %1!d! : %2!s! returned in the WinHttpQueryAuthSchemes. possibably anonymous requests or requests on unsecure channel are not allowed |
Error %1!d! : %2!s! returned in the WinHttpQueryAuthSchemes. possibably anonymous requests or requests on unsecure channel are not allowed |
0x00002775 | Error %1!d! : %2!s! returned in WinHttpSetOption |
Error %1!d! : %2!s! returned in WinHttpSetOption |
0x00002776 | Error %1!d! : %2!s! returned in WinhttpSetOption (3) |
Error %1!d! : %2!s! returned in WinhttpSetOption (3) |
0x00002778 | Status %1!d! returned in the RpcCertGeneratePrincipalName |
Status %1!d! returned in the RpcCertGeneratePrincipalName |
0x00002779 | Error %1!d! : %2!s! returned in CredIsMarshaledCredential |
Error %1!d! : %2!s! returned in CredIsMarshaledCredential |
0x0000277A | Error %1!d! : %2!s! returned in CredUnMarshalCredential |
Error %1!d! : %2!s! returned in CredUnMarshalCredential |
0x0000277B | Error %1!d! : %2!s! returned in CertOpenSystemStore |
Error %1!d! : %2!s! returned in CertOpenSystemStore |
0x0000277C | Error %1!d! : %2!s! returned in CertFindCertificateInStore |
Error %1!d! : %2!s! returned in CertFindCertificateInStore |
0x0000277D | Error %1!d! : %2!s! returned in CryptAcquireContext |
Error %1!d! : %2!s! returned in CryptAcquireContext |
0x0000277E | Error %1!d! : %2!s! returned in CryptSetProvParam |
Error %1!d! : %2!s! returned in CryptSetProvParam |
0x0000277F | Error %1!d! : %2!s! returned in WinHttpSetOption (1) |
Error %1!d! : %2!s! returned in WinHttpSetOption (1) |
0x00002780 | Error %1!d! : %2!s! returned in WinHttpSetOption (cert) |
Error %1!d! : %2!s! returned in WinHttpSetOption (cert) |
0x00002781 | Error %1!d! : %2!s! returned in MultiByteToWideChar |
Error %1!d! : %2!s! returned in MultiByteToWideChar |
0x00002782 | Error %1!d! : %2!s! returned in RtlStringCbPrintf |
Error %1!d! : %2!s! returned in RtlStringCbPrintf |
0x00002783 | Error %1!d! : %2!s! returned in WinHttpSetCredentials |
Error %1!d! : %2!s! returned in WinHttpSetCredentials |
0x00002784 | Error %1!d! : %2!s! returned in WinHttpSendRequest |
Error %1!d! : %2!s! returned in WinHttpSendRequest |
0x00002785 | Error %1!d! : %2!s! returned in WinHttpReceivedResponse |
Error %1!d! : %2!s! returned in WinHttpReceivedResponse |
0x00002786 | Error %1!d! : %2!s! returned in WinHttpQueryHeadersFailed |
Error %1!d! : %2!s! returned in WinHttpQueryHeadersFailed |
0x00002787 | Error %1!d! : %2!s! returned in WinHttpSetCredentials for RPC Proxy |
Error %1!d! : %2!s! returned in WinHttpSetCredentials for RPC Proxy |
0x00002788 | Error %1!d! : %2!s! returned in WinHttpSetOption - 4 |
Error %1!d! : %2!s! returned in WinHttpSetOption - 4 |
0x00002789 | Error %1!d! : %2!s! returned in WinHttpSetCredentials for Http Proxy |
Error %1!d! : %2!s! returned in WinHttpSetCredentials for Http Proxy |
0x0000278A | Error %1!d! : %2!s! returned in WinHttpQueryHeaders - 2 |
Error %1!d! : %2!s! returned in WinHttpQueryHeaders - 2 |
0x0000278B | Error %1!d! : %2!s! returned in RtlStringCchCopy |
Error %1!d! : %2!s! returned in RtlStringCchCopy |
0x0000278C | Error %1!d! : %2!s! returned in WinHttpOpen |
Error %1!d! : %2!s! returned in WinHttpOpen |
0x0000278D | Error %1!d! : %2!s! returned in WinHttpConnect |
Error %1!d! : %2!s! returned in WinHttpConnect |
0x0000278E | Error %1!d! : %2!s! returned in WinHttpOpenRequest |
Error %1!d! : %2!s! returned in WinHttpOpenRequest |
0x0000278F | Error %1!d! : %2!s! returned in GetModuleHandle |
Error %1!d! : %2!s! returned in GetModuleHandle |
0x00002790 | Error %1!d! : %2!s! returned in GetProcessAddress |
Error %1!d! : %2!s! returned in GetProcessAddress |
0x00002791 | %1!s! failed - %2!d! (%3!08x!) |
%1!s! failed - %2!d! (%3!08x!) |
0x00002792 | Error %1!d! : %2!s! returned in CertGetCertificateContextProperty |
Error %1!d! : %2!s! returned in CertGetCertificateContextProperty |
0x00002793 | Error %1!d! : %2!s! returned in WinHttpSendRequest - probably server is not configured to accept smart cards |
Error %1!d! : %2!s! returned in WinHttpSendRequest - probably server is not configured to accept smart cards |
0x00002794 | Error retrieving user input |
Error retrieving user input |
0x000027D9 | Use Server Preffered Auth Scheme: %1!d! |
Use Server Preffered Auth Scheme: %1!d! |
0x000027DA | Use Proxy Preffered Auth Scheme: %1!d! |
Use Proxy Preffered Auth Scheme: %1!d! |
0x000027DB | Client failed to authenticate to RPC proxy |
Client failed to authenticate to RPC proxy |
0x000027DC | To use BASIC authentication scheme for RPC Proxy, you must specify the user/domain/password (-P) |
To use BASIC authentication scheme for RPC Proxy, you must specify the user/domain/password (-P) |
0x000027DD | To use BASIC authentication scheme for HTTP Proxy, you must specify the user/domain/password (-A) |
To use BASIC authentication scheme for HTTP Proxy, you must specify the user/domain/password (-A) |
0x000027DE | Setting autologon policy to low |
Setting autologon policy to low |
0x000027DF | To use implicit logon credentials with NTLM, you must use SSL with server certificate subject or disable lanman hash |
To use implicit logon credentials with NTLM, you must use SSL with server certificate subject or disable lanman hash |
0x000027E0 | Setting autologon policy to high |
Setting autologon policy to high |
0x000027E1 | Authentication scheme %1!d! is not supported. Currently only NTLM and BASIC are supported |
Authentication scheme %1!d! is not supported. Currently only NTLM and BASIC are supported |
0x000027E2 | Cannot convert server certificate subject to Unicode |
Cannot convert server certificate subject to Unicode |
0x000027E3 | The server certificate subject from the RPC proxy (%1!s!, %2!s!) does not match the one (%3!s!) specified |
The server certificate subject from the RPC proxy (%1!s!, %2!s!) does not match the one (%3!s!) specified |
0x000027E4 | CredIsMarshaledCredential failed with NULL certCredentialInfo |
CredIsMarshaledCredential failed with NULL certCredentialInfo |
0x000027E5 | CredIsMarshaledCredential failed with wrong CredType: %1!d! |
CredIsMarshaledCredential failed with wrong CredType: %1!d! |
0x000027E6 | CryptAcquireContextW failed with NULL cspProvider |
CryptAcquireContextW failed with NULL cspProvider |
0x000027E7 | Smart card auth has no implicit credentials |
Smart card auth has no implicit credentials |
0x000027E8 | You must specify at least one authentication scheme if you specify the RPC_C_HTTP_FLAG_USE_FIRST_AUTH_SCHEME |
You must specify at least one authentication scheme if you specify the RPC_C_HTTP_FLAG_USE_FIRST_AUTH_SCHEME |
0x000027E9 | WinHttpSetCredentials for target server called |
WinHttpSetCredentials for target server called |
0x000027EA | Sending ping to server |
Sending ping to server |
0x000027EB | Server requires a certificate and client did not specify one. Exiting ... |
Server requires a certificate and client did not specify one. Exiting ... |
0x000027EC | Client certificate is required by the server |
Client certificate is required by the server |
0x000027ED | Smart card specified but not accepted by server (ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED returned). Exiting ... |
Smart card specified but not accepted by server (ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED returned). Exiting ... |
0x000027EE | No smart card specified. Exiting ... |
No smart card specified. Exiting ... |
0x000027EF | Response from server received: %1!d! |
Response from server received: %1!d! |
0x000027F0 | Smart card used and error 401 returned from server - probably server is not configured to accept smart cards |
Smart card used and error 401 returned from server - probably server is not configured to accept smart cards |
0x000027F1 | Client is not authorized to ping RPC proxy |
Client is not authorized to ping RPC proxy |
0x000027F2 | Access denied pinging HTTP proxy |
Access denied pinging HTTP proxy |
0x000027F3 | First WinHttpQueryHeaders should not have succeeded |
First WinHttpQueryHeaders should not have succeeded |
0x000027F4 | You mush specify Rpc Proxy |
You mush specify Rpc Proxy |
0x000027F5 | Error when checking IE settings %1!d! |
Error when checking IE settings %1!d! |
0x000027F6 | Error %1!d! : %2!s! port # is too long |
Error %1!d! : %2!s! port # is too long |
0x000027F7 | The IE settings are ambiguous. We don't know whether we should directly access RPC proxy or use HTTP proxy. You can use -R to clarify it |
The IE settings are ambiguous. We don't know whether we should directly access RPC proxy or use HTTP proxy. You can use -R to clarify it |
0x000027F8 | Either an interface or an endpoint can be given, but not both |
Either an interface or an endpoint can be given, but not both |
0x000027F9 | Cannot find protocol sequence: %1!s!. Exiting... |
Cannot find protocol sequence: %1!s!. Exiting... |
0x000027FA | SChannel requires a certificate to be supplied |
SChannel requires a certificate to be supplied |
0x000027FB | Trying to resolve interface %1!X!-%2!X!-%3!X!-%4!X!%5!X!%6!X!%7!X!%8!X!%9!X!%10!X!%11!X!, Version: %12!d!.0 |
Trying to resolve interface %1!X!-%2!X!-%3!X!-%4!X!%5!X!%6!X!%7!X!%8!X!%9!X!%10!X!%11!X!, Version: %12!d!.0 |
0x000027FC | Wrong access type %1!u! |
Wrong access type %1!u! |
0x000027FD | RPCPinging proxy server %1!s! with Echo Request Packet |
RPCPinging proxy server %1!s! with Echo Request Packet |
0x000027FE | Pinging successfully completed in %1!d! ms |
Pinging successfully completed in %1!d! ms |
0x000027FF | Ping failed |
Ping failed |
0x00002800 | Exception %1!lu! (0x%2!08lX!) |
Exception %1!lu! (0x%2!08lX!) |
0x00002801 | Couldn't get EEInfo: %1!d! |
Couldn't get EEInfo: %1!d! |
0x00002802 | Number of records is: %1!d! |
Number of records is: %1!d! |
0x00002803 | Couldn't finish enumeration: %1!d! |
Couldn't finish enumeration: %1!d! |
0x00002804 | ComputerName is %1!s! |
ComputerName is %1!s! |
0x00002805 | ProcessID is %1!d! |
ProcessID is %1!d! |
0x00002806 | System Time is: %1!d!/%2!d!/%3!d! %4!d!:%5!d!:%6!d!:%7!d! |
System Time is: %1!d!/%2!d!/%3!d! %4!d!:%5!d!:%6!d!:%7!d! |
0x00002807 | Generating component is %1!d! |
Generating component is %1!d! |
0x00002808 | Status is 0x%1!X!, %2!d! |
Status is 0x%1!X!, %2!d! |
0x00002809 | Detection location is %1!d! |
Detection location is %1!d! |
0x0000280A | Flags is %1!d! |
Flags is %1!d! |
0x0000280B | NumberOfParameters is %1!d! |
NumberOfParameters is %1!d! |
0x0000280C | Ansi string: %1!S! |
Ansi string: %1!S! |
0x0000280D | Unicode string: %1!s! |
Unicode string: %1!s! |
0x0000280E | Long val: 0x%1!x! |
Long val: 0x%1!x! |
0x0000280F | Short val: %1!d! |
Short val: %1!d! |
0x00002810 | Pointer val: 0x%1!x! |
Pointer val: 0x%1!x! |
0x00002811 | Truncated |
Truncated |
0x00002812 | Invalid type: %1!d! |
Invalid type: %1!d! |
0x00002813 | If you specify auth identity in the form , a domain must be specified: %1!s! |
If you specify auth identity in the form , a domain must be specified: %1!s! |
0x00002814 | If you specify auth identity in the form , a password must be specified: %1!s!,%2!s! |
If you specify auth identity in the form , a password must be specified: %1!s!,%2!s! |
0x00002815 | Enter password for %1!s!: |
Enter password for %1!s!: |
0x00002816 | Cannot parse bitflags: %1!s! |
Cannot parse bitflags: %1!s! |
0x00002817 | You must specify authentication level, security package and ncacn_http protocol sequence if you want to use RPC/HTTP front end security (%1!s!) |
You must specify authentication level, security package and ncacn_http protocol sequence if you want to use RPC/HTTP front end security (%1!s!) |
0x00002818 | You must specify the binding option if you want to Ping the RPC proxy. (-E) |
You must specify the binding option if you want to Ping the RPC proxy. (-E) |
0x00002819 | Invalid BindingOption (%1!s!). You must specify the RpcProxy |
Invalid BindingOption (%1!s!). You must specify the RpcProxy |
0x0000281A | Cannot retrieve computer name %1!d! : %2!s! |
Cannot retrieve computer name %1!d! : %2!s! |
0x0000281B | Cannot retrieve smart card credentials %1!d! : %2!s! |
Cannot retrieve smart card credentials %1!d! : %2!s! |
0x0000281C | Cannot parse interface UUID: %1!s! |
Cannot parse interface UUID: %1!s! |
0x0000281D | If you specify authentication level other than 1, you must specify a security provider |
If you specify authentication level other than 1, you must specify a security provider |
0x0000281E | If you specify a security package, you must specify authentication level other than none |
If you specify a security package, you must specify authentication level other than none |
0x0000281F | Cannot parse SID: %1!s! |
Cannot parse SID: %1!s! |
0x00002820 | You must specify one or more proxy authentication schemes if you want to authenticate to the HTTP Proxy |
You must specify one or more proxy authentication schemes if you want to authenticate to the HTTP Proxy |
0x00002821 | You must use SSL if you want to verify the server certificate subject |
You must use SSL if you want to verify the server certificate subject |
0x00002822 | You must use SSL if you want to retrieve the server certificate subject |
You must use SSL if you want to retrieve the server certificate subject |
0x00002823 | You can retrieve the server subject certificate only if you do Proxy Echo only |
You can retrieve the server subject certificate only if you do Proxy Echo only |
0x00002824 | If you use a smart card for proxy auth, you cannot specify explicit proxy credentials |
If you use a smart card for proxy auth, you cannot specify explicit proxy credentials |
0x00002825 | If you use certificate for authentication, you must use SSL |
If you use certificate for authentication, you must use SSL |
0x00002826 | If you use a certificate, you must either use SCHANNEL as the auth package or use FE security and specify exactly one auth scheme (cert) |
If you use a certificate, you must either use SCHANNEL as the auth package or use FE security and specify exactly one auth scheme (cert) |
0x00002827 | HTTP Proxy authentication cannot be done with a smart card |
HTTP Proxy authentication cannot be done with a smart card |
0x00002828 | You need to specify the HTTP proxy only when -E is enabled |
You need to specify the HTTP proxy only when -E is enabled |
0x00002829 | Since you have specified the RPC/HTTP proxy echo only option (-E), the endpoint/interface you have specified will be ignored as no calls will reach the RPC/HTTP server |
Since you have specified the RPC/HTTP proxy echo only option (-E), the endpoint/interface you have specified will be ignored as no calls will reach the RPC/HTTP server |
0x0000282A | %1!s! [Y/N]: |
%1!s! [Y/N]: |
0x0000282B | %1!s! : %2!s! |
%1!s! : %2!s! |
0x0000282C | Server Certificate Subject: (%1!s!;%2!s!) |
Server Certificate Subject: (%1!s!;%2!s!) |
0x0000282D | Completed %1!d! calls in %2!d! ms%3!d! T/S or %4!3d!.%5!03d! ms/T |
Completed %1!d! calls in %2!d! ms%3!d! T/S or %4!3d!.%5!03d! ms/T |
0x0000282E | Maximum of seven -n switchs, extra ignored |
Maximum of seven -n switchs, extra ignored |
0x0000282F | You must specify one or more authentication schemes if you want to authenticate to the RPC/HTTP Proxy |
You must specify one or more authentication schemes if you want to authenticate to the RPC/HTTP Proxy |
0x00002830 | |
|
0x00002831 | Time %1!s!: %2!d!.%3!03d! |
Time %1!s!: %2!d!.%3!03d! |
0x00002832 | Couldn't run RPC Network Diagnostics: %1!d! |
Couldn't run RPC Network Diagnostics: %1!d! |
0x00002833 | Error %1!d! : %2!s! returned in CertSetCertificateContextProperty |
Error %1!d! : %2!s! returned in CertSetCertificateContextProperty |
0x00002834 | If you use a smart card for rpc auth, you cannot specify explicit credentials |
If you use a smart card for rpc auth, you cannot specify explicit credentials |
0x00002835 | If you specify the certificate authentication scheme then you must use a smart card |
If you specify the certificate authentication scheme then you must use a smart card |
0x00002836 | Binary val: Length %1!d! %2!X! %3!X! %4!X! %5!X! |
Binary val: Length %1!d! %2!X! %3!X! %4!X! %5!X! |
0x00002837 | RPCPing set Activity ID: {%1!s!} |
RPCPing set Activity ID: {%1!s!} |
0x00002838 | Using basic authentication without SSL can expose your credentials. Do you want to continue? [%1!s!/%2!s!] %0 |
Using basic authentication without SSL can expose your credentials. Do you want to continue? [%1!s!/%2!s!] %0 |
0x00002839 | Y%0 |
Y%0 |
0x0000283A | y%0 |
y%0 |
0x0000283B | N%0 |
N%0 |
0x0000283C | n%0 |
n%0 |
0x0000283D | Error %1!d! : %2!s! returned in ConvertStringSecurityDescriptorToSecurityDescriptor |
Error %1!d! : %2!s! returned in ConvertStringSecurityDescriptorToSecurityDescriptor |
0x0000283E | Cannot parse EffectiveOnly: %1!s! |
Cannot parse EffectiveOnly: %1!s! |
0x0000283F | EffectiveOnly must be either 0 or 1. |
EffectiveOnly must be either 0 or 1. |