text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 This operation is not valid until security negotiation is complete. The translation set cannot contain nulls. Could not connect to {0}. The connection attempt lasted for a time span of {3}. TCP error code {1}: {2}. Certificate-based client authentication is not supported in TransportCredentialOnly security mode. Select the Transport security mode. A base address cannot contain a Uri query string. The channel received an unexpected fault input message while closing. The fault reason given is: '{0}' The configured Trust version does not support sessions. Use WSTrustFeb2005 or above. Cannot create channel for a contract that requires request/reply and a binding that requires manual addressing but only supports duplex communication. The ServiceHost close operation timed out after {0}. This could be because a client failed to close a sessionful channel within the required time. The time allotted to this operation may have been a portion of a longer timeout. The message header with name '{0}' and namespace '{1}' is not present in the set of understood headers. The configured WS-Trust version does not support issued tokens. WS-Trust February 2005 or later is required. Method '{1}' has {0}, but enclosing type '{2}' does not have ServiceContractAttribute. {0} can only be used on methods in ServiceContractAttribute types. KnownType cannot be null in operation {0} The communication object, {0}, cannot be used for communication because it has been Aborted. Configuration files are not supported. Server '{0}' is too busy to process this request. Try again later. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must have the same value for the '{5}' property. In this case, the values are different. To fix it, change the '{5} property of one of the OperationContracts to match the other. Alternatively, changing the name of one of the methods will prevent matching. This OperationContextScope is being disposed out of order. The header '{0}' from the namespace '{1}' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding. Process action '{0}'. Cannot read the token from the '{0}' element with the '{1}' namespace for BinarySecretSecurityToken, with a '{2}' ValueType. If this element is expected to be valid, ensure that security is configured to consume tokens with the name, namespace and value type specified. The message with Action '{0}' cannot be processed at the receiver because this Action is reserved for the connection opening messages only and cannot be sent from client to server. To invoke this operation on the server, call the '{1}' method on the client proxy instead. The value of this argument must be greater than 0. Async End called with an IAsyncResult from a different Begin method. The Name property must be a non-empty string. No clause of type '{0}' was found in the SecurityKeyIdentifier. There was no endpoint listening at {0} that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. The communication object, {0}, is in the {1} state. Communication objects cannot be used for communication unless they are in the Opened state. Attempted to get contract type for {0}, but that type is not a ServiceContract, nor does it inherit a ServiceContract. Too many attributes of type {0} on {1}. There is not a header with name {0} and namespace {1} in the message. Additional XML content is present in the fault detail element. Only a single element is allowed. SynchronizedReadOnlyCollection's CopyTo only works if the underlying list implements ICollection. SSL protocol negotiation failed. Requested '{0}' but was offered '{1}'. Expecting first char - c - to be in set [Char.IsLetter(c) && c == '_', found '{0}'. Error in deserializing body of request message for operation '{0}'. This value cannot be changed after the ServiceHost has opened. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must define the same return type. In this case, the return types are different. To fix it, ensure that method '{0}' and method '{3}' have the same return type. Alternatively, changing the name of one of the methods will prevent matching. The maximum message size quota for incoming messages has been exceeded for the remote channel. See the server logs for more details. The HTTP proxy authentication credential specified an mutual authentication requirement ({0}) that is stricter than the requirement for target server authentication ({1}). {0} is only available in a deserialized RequestSecurityTokenResponse. The one-way operation returned a fault message. The reason for the fault was '{0}'. Open ClientBase. Contract type: '{0}'. The security token authenticator '{0}' cannot validate a token of type '{1}'. The configured SecurityVersion does not support signature confirmation. Use WsSecurity11 or above. Value '{0}' provided for '{1}' from namespace '{2}' is an invalid absolute URI. No Action header was found with namespace '{0}' for the given message. The server didn't accept the connection request. It is possible that the WebSocket protocol version on your client doesn't match the one on the server('{0}'). Failed to create a typed proxy for type '{0}' Unbound prefix used in qualified name '{0}'. Attribute '{0}' is required on element '{1}'. The value '{1}' is not supported in this context for the binding security property '{0}'. The claimType cannot be an empty string. The value of the addressHeaders argument is invalid because the collection contains null values. Null is not a valid value for the AddressHeaderCollection. The value of this argument must be non-negative. The value '{1}' for the '{0}' property is not supported in Windows Store apps. The specified method handle is incorrect for the proxy of type '{0}' The specified nonce is too short. The minimum required nonce length is 4 bytes. A null value cannot be added to the generic collection, because the collection has been parameterized with a value type. The HTTP request to '{0}' has exceeded the allotted timeout of {1}. The time allotted to this operation may have been a portion of a longer timeout. The NetworkCredentials provided for the Kerberos Token does not have a valid UserName. This fault did not provide a reason (MessageFault.Reason was null). An error occurred while loading attribute '{0}' on type '{1}'. Please see InnerException for more details. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must define the same return type. In this case, the return types are different. To fix it, ensure that method '{0}' and method '{3}' have the same return type. Alternatively, changing the name of one of the methods will prevent matching. Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint provided DNS claim '{1}'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity '{1}' as the Identity property of EndpointAddress when creating channel proxy. The transport configured on this binding does not appear to support the CompressionFormat specified ({0}) on the message encoder. To resolve this issue, set the CompressionFormat on the {1} to '{2}' or use a different transport. {0} returned false from OnTryCreateException, but returned a non-null Exception (See InnerException for details). The receiver returned an error indicating that the content type was missing on the request to {0}. See the inner exception for more information. More than one IStreamUpgradeProviderElement was found in the BindingParameters of the BindingContext. This usually is caused by having multiple IStreamUpgradeProviderElements in a CustomBinding. Remove all but one of these elements. The derived key's generation ('{0}') and length ('{1}' bytes) result in a key derivation offset that is greater than the maximum offset ('{2}' bytes) allowed. Calling Post() on '{0}' resulted in multiple callbacks. This indicates a problem in '{0}'. OperationContract method '{0}' in type '{1}' does not properly implement the async pattern, as no corresponding method '{2}' could be found. Either provide a method called '{2}' or set the AsyncPattern property on method '{0}' to false. Close process timed out waiting for service dispatch to complete. The '{0}' from the '{1}' namespace is empty and does not specify a valid identity claim. The key effective and expiration times must be bounded by the token effective and expiration times. The SOAP action specified on the message, '{0}', does not match the action specified on the HttpRequestMessageProperty, '{1}'. ClientCredentialType '{0}' can only be used on the server side, not the client side. Please use one of the following values instead 'None, Basic, Client, Digest, Ntlm, Windows'. The type or member named '{0}' could not be loaded because it has two incompatible attributes: '{1}' and '{2}'. To fix the problem, remove one of the attributes from the type or member. Formatter {0} returned a null reply message for call to operation '{1}'. The derived key's Offset ('{0}' bytes) exceeds the maximum offset ('{1}' bytes) allowed. The message header with name '{0}' and namespace '{1}' is already present in the set of understood headers. The value of this argument must be positive. For request in operation {0} to be a stream the operation must have a single parameter whose type is Stream. Channel type '{1}' was requested, but Binding '{0}' doesn't support it or isn't configured properly to support it. No IPEndpoints were found for host {0}. The StreamUpgradeInitiator specified ({0}) is not supported by this IStreamUpgradeChannelBindingProvider implementation. The most likely cause of this is passing a StreamUpgradeInitiator that was not created by the StreamUpgradeProvider associated with the current IStreamUpgradeChannelBindingProvider implementation. AllowInitializationUI was set to false for this channel, but the channel is configured to use the '{0}' as an interactive initializer. An HTTP Content-Type header is required for SOAP messaging and none was found. Expected XML qualified name, found '{0}'. A reply message was received without a valid RelatesTo header. This may have been caused by a missing RelatesTo header or a RelatesTo header with an invalid WS-Addressing Relationship type. Server faulted with code '{0}'. The operation {0} either has a parameter or a return type that is attributed with MessageContractAttribute. In order to represent the request message using a Message Contract, the operation must have a single parameter attributed with MessageContractAttribute. In order to represent the response message using a Message Contract, the operation's return value must be a type that is attributed with MessageContractAttribute and the operation may not have any out or ref parameters. The valid from time is greater than the valid to time. Operation was aborted while establishing a connection to {0}. Client cannot determine the Service Principal Name based on the identity in the target address '{0}' for the purpose of SspiNegotiation/Kerberos. The target address identity must be a UPN identity (like acmedomain\\alice) or SPN identity (like host/bobs-machine). The remote server returned an unexpected response: ({0}) {1}. Invalid async End method signature for method {0} in ServiceContract type {1}. Your end method must take an IAsyncResult as the last argument. This operation would deadlock because the reply cannot be received until the current Message completes processing. If you want to allow out-of-order message processing, specify ConcurrencyMode of Reentrant or Multiple on {0}. In order to use Streams with the MessageContract programming model, the type {0} must have a single member with MessageBodyMember attribute and the member type must be Stream. The binary encoder session is not valid. There was an error decoding a previous message. Invalid async Begin method signature for method {0} in ServiceContract type {1}. Your begin method must take an AsyncCallback and an object as the last two arguments and return an IAsyncResult. The derived key has not been computed for the security token. This channel cannot send any more messages because IsTerminating operation '{0}' has already been called. Operations marked with IsOneWay=true must not declare output parameters, by-reference parameters or return values. Cannot open ChannelFactory as the inner channel factory was not set during the initialization process. A connection has exceeded the idle timeout of this connection pool ({0}) and been closed. Framing mode {0} is not supported. Method {0} in type {1} has more than one header part of type array of XmlElement. The token provider '{0}' does not support token renewal. Invalid type: '{0}'. It must inherit from base type '{1}', cannot be abstract, and must expose a public default constructor. The argument must be a non-empty string. The algorithm '{0}' is not accepted for operation '{1}' by algorithm suite {2}. XmlArrayAttribute cannot be used in repeating part {1}:{0}. Processing message {0}. The required '{0}' property on the '{1}' security protocol factory is not set or has an invalid value. Cannot resolve the host name of URI \"{0}\" using DNS. Request timed out after {0} while establishing a transport connection to {1}. The time allotted to this operation may have been a portion of a longer timeout. Transport security negotiation failed due to an underlying IO error: {0}. MaxOutboundConnectionsPerEndpoint quota ({0}) has been reached, so connection was closed and not stored in this connection pool. There was an error in serializing body of message {0}: '{1}'. Please see InnerException for more details. Value '{0}' provided for {1} property is an invalid URI. A TCP error ({0}: {1}) occurred while transmitting data. The CloneCore method of {0} type returned an invalid result. Parameter value '{0}' is an invalid URI. In operation '{0}', cannot return null from methods that return Message. The requested service, '{0}' could not be activated. See the server's diagnostic trace logs for more information. A graceful close was attempted on the socket, but the other side ({0}) is still sending data. The '{0}' list is invalid because the property '{1}' of '{2}' is not null. The signing token {0} has no keys. The security token is used in a context that requires it to perform cryptographic operations, but the token contains no cryptographic keys. Either the token type does not support cryptographic operations, or the particular token instance does not contain cryptographic keys. Check your configuration to ensure that cryptographically disabled token types (for example, UserNameSecurityToken) are not specified in a context that requires cryptographic operations (for example, an endorsing supporting token). ContractDescription '{0}' has zero IsInitiating=true operations; a contract must have at least one IsInitiating=true operation. The request operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout. '{0}' from namespace '{1}' is not expected to appear more than once The '{0}' authentication scheme has been specified for the proxy on the HTTP factory. However, the factory only supports specification of exactly one authentication scheme. Valid authentication schemes are Digest, Negotiate, NTLM, Basic, or Anonymous. The dispatch instance for duplex callbacks cannot be activated - you must provide an instance. ... The ClientOperation '{0}' requires Formatter, since SerializeRequest and DeserializeReply are not both false. The channel received an unexpected input message with Action '{0}' while closing. You should only close your channel when you are not expecting any more input messages. The XmlReader used for the body of the message must be positioned on an element. A call to IChannelFactory.CreateChannel made on an object of type {0} failed because Open has not been called on this object. The communication object, {0}, is not part of WCF and is in an unsupported state '{1}'. This indicates an internal error in the implementation of that communication object. Message is closed. Invalid decoder state machine. Execute '{0}.{1}'. A value of type '{0}' cannot be added to the generic collection, because the collection has been parameterized with a different type. The message with To '{0}' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree. Error in deserializing body of reply message for operation '{0}'. {1} The X.509 certificate {0} chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. {1} This fault did not provide a matching translation: {0} This SecurityKeyIdentifier does not have any clause that can create a key. This property sets ManualAddressing on the client. To set ManualAddressing on the server, use ChannelDispatcher's ManualAddressing. MessageHeaderArrayAttribute found on member {0} is not a single dimensional array. The specified size exceeds the remaining buffer space ({0} bytes). The framing via ({0}) is not a valid URI. The Receive operation timed out after '{0}'. For duplex sessionful channels, the receive timeout is also the idle timeout for the channel, so consider setting a suitably large value for the ReceiveTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. The value specified ('{0}') contains more than one subprotocol which is not supported. The OperationFormatter could not deserialize any information from the Message because the Message is empty (IsEmpty = true). Expecting all chars - c - of id to be in set [Char.IsLetter(c), Char.IsNumber(c), '.', '_', '-'], found '{0}'. The operation '{0}' could not be loaded because it specifies \"rpc-style\" in \"literal\" mode, but uses message contract types or the System.ServiceModel.Channels.Message. This combination is disallowed -- specify a different value for style or use parameters other than message contract types or System.ServiceModel.Channels.Message. The collection of type {0} does not support values of type {1}. The body writer does not support writing more than once because it is not buffered. The static CreateChannel method cannot be used with the contract {0} because that contract defines a callback contract. Please try using one of the static CreateChannel overloads on DuplexChannelFactory<TChannel>. In Binding '{0}', TransportBindingElement '{1}' does not appear last in the BindingElementCollection. Please change the order of elements such that the TransportBindingElement is last. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, any additional attributes must be declared on the synchronous OperationContract method. In this case, the asynchronous OperationContract method '{2}' has one or more attributes of type '{5}'. To fix it, remove the '{5}' attribute or attributes from method '{2}'. Alternatively, changing the name of one of the methods will prevent matching. The incoming message with action could not be processed because it is targeted at a request-reply operation, but cannot be replied to as the MessageId property is not set. The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error. Cannot inherit two different operations with the same name, operation '{0}' from contracts '{1}' and '{2}' violate this rule. You can change the name of one of the operations by changing the method name or by using the Name property of OperationContractAttribute. The binding (Name={0}, Namespace={1}) does not contain a TransportBindingElement. StringNullOrEmpty The service does not allow you to log on anonymously. {0} returned false from OnTryCreateFaultMessage, but returned a non-null fault message. In operation '{0}', cannot pass null to methods that take Message as input parameter. The HTTP proxy authentication credential specified an impersonation level restriction ({0}) that is stricter than the restriction for target server authentication ({1}). For TransferMode.Buffered, MaxReceivedMessageSize and MaxBufferSize must be the same value. Cannot find The X.509 certificate using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}' for target '{4}'. The formatter threw an exception while trying to deserialize the message: {0} The SOAP action specified on the message, '{0}', does not match the action specified in the content-type of the HttpRequestMessageProperty, '{1}'. The socket transfer timed out after {0}. You have exceeded the timeout set on your binding. The time allotted to this operation may have been a portion of a longer timeout. This CreateChannel overload cannot be called on this instance of DuplexChannelFactory, as the DuplexChannelFactory was initialized with a Type and no valid InstanceContext was provided. Please call the CreateChannel overload that takes an InstanceContext. Addressing Version '{0}' is not supported. The value of this argument must fall within the range {0} to {1}. The remote certificate is invalid according to the validation procedure. Server returned an invalid SOAP Fault. Please see InnerException for more details. There was an error in serializing one of the headers in message {0}: '{1}'. Please see InnerException for more details. The PrimitiveOperationFormatter was given a parameter or return type which it does not support. Error in deserializing body of reply message for operation '{0}'. The type {1} defines a MessageContract but also derives from a type {0} that does not define a MessageContract. All of the objects in the inheritance hierarchy of {1} must defines a MessageContract. Cannot open ChannelDispatcher because it is does not have a MessageVersion set. The specified offset exceeds the buffer size ({0} bytes). ServiceKnownTypeAttribute in {0} refers to a method {1} that does not exist in type {2} An error occurred while loading attribute '{0}'. Please see InnerException for more details. The Address property on ChannelFactory.Endpoint was null. The ChannelFactory's Endpoint must have a valid Address specified. The security capabilities of binding '{0}' do not match those of the generated runtime object. Most likely this means the binding contains a StreamSecurityBindingElement, but lacks a TransportBindingElement that supports Stream Security (such as TCP or Named Pipes). Either remove the unused StreamSecurityBindingElement or use a transport that supports this element. The synchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a synchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must define the same number and types of parameters. In this case, some of the arguments are different. To fix it, ensure that the OperationContracts define the same number and types of arguments, in the same order. Alternatively, changing the name of one of the methods will prevent matching. Type {0} cannot inherit from any class other than object to be used as body object in RPC style. The {0} binding element requires envelope version '{1}' It doesn't support '{2}'. The 'parameters' argument must be an array that contains a single Message object. A base address cannot contain a Uri user info section. The InstanceContext provided to the ChannelFactory contains a UserObject that does not implement the CallbackContractType '{0}'. This value cannot be changed after the ChannelFactory has opened. The token provider '{0}' was unable to provide a security token. The Identity check failed for the incoming message. The remote endpoint did not provide a domain name system (DNS) claim and therefore did not satisfied DNS identity '{0}'. This may be caused by lack of DNS or CN name in the remote endpoint X.509 certificate's distinguished name. The request message has ReplyTo='{0}' but IContextChannel.LocalAddress is '{1}'. When ManualAddressing is false, these values must be the same, null, or EndpointAddress.AnonymousAddress. Enable ManualAddressing or avoid setting ReplyTo on the message. The given URI must be absolute. Error while reading message framing format at position {0} of stream (state: {1}) An attempt was made to decode a value after the framing stream was ended. A reply message cannot be created because the request message does not have a MessageID. The message containing this stream has been closed. The Session value '{0}' is invalid. Please specify 'CurrentSession','ServiceSession' or a valid non-negative Windows Session Id. The length of the symmetric key specified is too short ({0} bytes). MemoryStream's internal buffer cannot be accessed. In operation {0}, more than one fault is declared with element name {1} in namespace {2} The 'result' argument must be of type Message. In operation {0}, the schema type corresponding to the fault detail type {1} is anonymous. Please set Fault name explicitly to export anonymous types. The {0} X.509 certificate is in an untrusted certificate store. The NTLM authentication scheme was specified, but the target credential does not allow NTLM. Multiple RelatesTo headers with relationship '{0}' found. Only one is allowed per relationship. The IMessageProperty could not be copied. CreateCopy returned null. The DispatchOperation '{0}' requires Formatter, since DeserializeRequest and SerializeReply are not both false. Cannot detect WS-Addressing version. EndpointReference does not start with an Element. The protection level '{0}' was specified, yet SSL transport security only supports EncryptAndSign. ChannelFactory does not support the contract {0} as it defines a callback contract with one or more operations. Please consider using DuplexChannelFactory instead of ChannelFactory. The signing token {0} has no key that supports the algorithm suite {1}. Manual addressing is enabled on this factory, so all messages sent must be pre-addressed. Unexpected internal enum value: {0}. The provided URI scheme '{0}' is invalid; expected '{1}'. Method '{0}' in class '{1}' has bad parameter metadata: a pass-by-reference parameter is marked with the 'in' but not the 'out' parameter mode. Writing audit messages to the Security log is not supported by the current platform. You must write audit messages to the Application log. Channel requirements cannot be met by the ChannelFactory for Binding '{0}' since the contract requires support for one of these channel types '{1}' but the binding doesn't support any of them. Contract requires Session, but Binding '{0}' doesn't support it or isn't configured properly to support it. Element '{0}' with namespace '{1}' not found. Contract requires Request/Reply, but Binding '{0}' doesn't support it or isn't configured properly to support it. Envelope Version '{0}' does not support adding Message Headers. The X.509 certificate {0} is not in the trusted people store. The value of OperationContext.Current is not the OperationContext value installed by this OperationContextScope. XmlSerializer attribute {0} is not valid in {1}. Only XmlElement, XmlArray, XmlArrayItem, XmlAnyAttribute and XmlAnyElement attributes are supported when IsWrapped is true. {0} is only available in a deserialized RequestSecurityToken. Insufficient memory avaliable to complete the operation. Unexpected WebSocket close message received when receiving a message. The underlying channel factory could not be created because no binding information was found in the configuration file for endpoint with name '{0}'. Please check the endpoint configuration section with name '{0}' to ensure that binding information is present and correct. The PSHA1 key length '{0}' is invalid. No DNS entries exist for host {0}. The WebSocket returned by the factory of type '{0}' has the SubProtocol '{1}' that doesn't match the requested SubProtocol value '{2}'. Type {0} implements interface {1} which is not supported for body object in RPC style. ClientCredentials cannot create a local token provider for token requirement {0}. The CallbackContract {0} is invalid because it is not an interface type. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract method '{2}' because they have the same operation name '{3}'. When a synchronous OperationContract method is matched to a task-based asynchronous OperationContract method, the two OperationContracts must have the same value for the '{4}' property. In this case, the values are different. To fix it, change the '{4} property of one of the OperationContracts to match the other. Alternatively, changing the name of one of the methods will prevent matching. Contract requires Duplex, but Binding '{0}' doesn't support it or isn't configured properly to support it. The server didn't accept the connection request. It is possible that the WebSocket subprotocol sent by your client is not supported by the server. Protocol(s) supported by the server are '{0}'. The '{0}' authentication scheme has been specified on the HTTP factory. However, the factory only supports specification of exactly one authentication scheme. Valid authentication schemes are Digest, Negotiate, NTLM, Basic, or Anonymous. This EndpointDispatcher is not currently attached to the provided ChannelDispatcher. An object that is not an exception was thrown. The required UserNameSecurityToken was not provided. The text encoding '{0}' used in the text message format is not supported. The request channel timed out while waiting for a reply after {0}. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. Internal Error: The instance of the MessageContract cannot be null in {0}. The message could not be dispatched to the service at address '{0}'. Refer to the server Event Log for more details The .Net Framing version being used is not supported by '{0}'. See the server logs for more details. The security token manager cannot create a token authenticator for requirement '{0}'. TimeoutStream requires an inner Stream that supports timeouts; its CanTimeout property must be true. Unrecognized message version. Duplex channel to {0} was aborted during the open process. The communication object, {0}, cannot be used for communication because it is in the Faulted state. This CreateChannel overload cannot be called on this instance of DuplexChannelFactory, as the DuplexChannelFactory was not initialized with an InstanceContext. Please call the CreateChannel overload that takes an InstanceContext. Timeout must be greater than or equal to TimeSpan.Zero. To disable timeout, specify TimeSpan.MaxValue. This channel can no longer be used to send messages as the output session was auto-closed due to a server-initiated shutdown. Either disable auto-close by setting the DispatchRuntime.AutomaticInputSessionShutdown to false, or consider modifying the shutdown protocol with the remote server. Request Message is missing a MessageID header. One is required to correlate a reply. The protocol factory cannot create a protocol. WebSocket creation failed. The '{0}' returned a WebSocket that is either null or not opened. The service class of type {0} both defines a ServiceContract and inherits a ServiceContract from type {1}. Contract inheritance can only be used among interface types. If a class is marked with ServiceContractAttribute, it must be the only type in the hierarchy with ServiceContractAttribute. Consider moving the ServiceContractAttribute on type {1} to a separate interface that type {1} implements. Executing user callback. An empty value was found for the required base-64 attribute name '{0}', namespace '{1}'. Only body return values are supported currently for protection, MessagePartDescription was specified. A message was received with a WS-Addressing ReplyTo or FaultTo header targeted at the \"None\" address. These values are not valid for request-reply operations. Please consider using a one-way operation or enabling ManualAddressing if you need to support ReplyTo or FaultTo values of \"None.\" Internal Error: The InnerChannel property is null. The value of MaxPendingAccepts should not be larger than {0}. There was a mismatch between the number of supplied arguments and the number of expected arguments. Specifically, the argument '{0}' has '{1}' elements while the argument '{2}' has '{3}' elements. The operations {0} and {1} have the same action ({2}). Every operation must have a unique action value. The fault does not have detail information. The binding specified requires that the to and via URIs must match because the Addressing Version is set to None. The to URI specified was '{0}'. The via URI specified was '{1}'. This message cannot support the operation because it has been written. Service implementation object invoked with wrong number of input parameters, operation expects {0} parameters but was called with {1} parameters. Cannot handle invocation of {0} on interface {1} because the OperationSelector on ClientRuntime is null. {0} is not available in deserialized RequestSecurityTokenResponse. The creator of this fault did not specify a Reason. An error occurred when creating the WebSocket with the factory of type '{0}'. See the inner exception for details. Sending to via {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout. Cannot read the Identity element. The Identity type is not supported or the Identity element is empty. Header properties cannot be set in MessageHeaderAttribute of {0} as its type is MessageHeader<T>. The contract specified by type '{0}' is ambiguous. The type derives from at least two different types that each define its own service contract. For this type to be used as a contract type, exactly one of its inherited contracts must be more derived than any of the others. Extended protection is not supported on this platform. Please install the appropriate patch or change the ExtendedProtectionPolicy on the Binding or BindingElement to a value with a PolicyEnforcement value of \"Never\" or \"WhenSupported\". Error in deserializing body of request message for operation '{0}'. {1} A connection has exceeded the connection lease timeout of this connection pool ({0}) and been closed. Stream returned by OperationStreamProvider cannot be null. Binding '{0}' lacks a TransportBindingElement. Every binding must have a binding element that derives from TransportBindingElement. This binding element must appear last in the BindingElementCollection. A Channel/Service endpoint's Contract is null. Opening the {0} channel timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout. Opening the channel timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. CreateFactory requires that the Endpoint property be initialized. Either provide a valid ServiceEndpoint in the CreateDescription method or override the CreateFactory method to provide an alternative implementation. A property with the name '{0}' is not present. Framing major version {0} is not supported. More data was expected, but EOF was reached. The configured SecureConversation version does not support sessions. Use WSSecureConversationFeb2005 or above. The Send operation timed out after '{0}'. Increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. For response in operation {0} to be a stream the operation must have a single out parameter or return value whose type is Stream. The listener at Uri '{0}' could not be initialized because it was created for an unrecognized channel type. Receive timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. More than one MessageEncodingBindingElement was found in the BindingParameters of the BindingContext. This usually is caused by having multiple MessageEncodingBindingElements in a CustomBinding. Remove all but one of these elements. RPC Message {1} in operation {0} has an invalid body name {2}. It must be {3} Service implementation object invoked with null input parameters, but operation expects {0} parameters. Close ClientBase. Contract type: '{0}'. Method {0} is not supported on this proxy, this can happen if the method is not marked with OperationContractAttribute or if the interface type is not marked with ServiceContractAttribute. AsyncResult completed twice. Header name cannot be null or empty. The security protocol '{0}' cannot do replay detection. The envelope version of the incoming message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured with the same version as the expected messages. The server certificate with name '{0}' failed identity verification because its thumbprint ('{1}') does not match the one specified in the endpoint identity ('{2}'). As a result, the current HTTPS request has failed. Please update the endpoint identity used on the client or the certificate used by the server. Could not establish trust relationship for the SSL/TLS secure channel with authority '{0}'. The length of this argument must be greater than 0. The item cannot be added. The maximum cache size is ({0} items). Multiple supporting token authenticators with the token parameter type equal to '{0}' cannot be specified. If more than one Supporting Token of the same type is expected in the response, then configure the supporting token collection with just one entry for that SecurityTokenParameters. The SecurityTokenAuthenticator that gets created from the SecurityTokenParameters will be used to authenticate multiple tokens. It is not possible to add SecurityTokenParameters of the same type in the SupportingTokenParameters collection or repeat it across EndpointSupportingTokenParameters and OperationSupportingTokenParameters. This SecurityKeyIdentifierClause does not support key creation. A reply has already been sent from this RequestContext. The HTTP request to '{0}' has exceeded the allotted timeout of {1} while reading the response. The time allotted to this operation may have been a portion of a longer timeout. The token requirement does not contain a property '{0}'. Item does not exist in SynchronizedKeyedCollection. The property '{0}' is not supported when building a ChannelFactory. The property value must be null when calling BuildChannelFactory. {0}: {1} (Fault Detail is equal to {2}). Open timed out after {0} while establishing a transport session to {1}. The time allotted to this operation may have been a portion of a longer timeout. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a task-based asynchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must define the same number and types of parameters. In this case, some of the arguments are different. To fix it, ensure that the OperationContracts define the same number and types of arguments, in the same order. Alternatively, changing the name of one of the methods will prevent matching. GenericCallbackException The version of the header(s) ({0}) differs from the version of the message ({1}). The value specified, '{0}', for the If-Modified-Since header does not parse into a valid date. Check the property value and ensure that it is of the proper format. Timeouts larger than Int32.MaxValue TotalMilliseconds (approximately 24 days) cannot be honored. To disable timeout, specify TimeSpan.MaxValue. The service class of type {0} both defines a ServiceContract and inherits a ServiceContract from type {1}. Contract inheritance can only be used among interface types. If a class is marked with ServiceContractAttribute, then another service class cannot derive from it. The operation '{0}' cannot be the first operation to be called because IsInitiating is false. '{0}' is an invalid XmlNodeType. The remote endpoint of the socket ({0}) did not respond to a close request within the allotted timeout ({1}). It is likely that the remote endpoint is not calling Close after receiving the EOF signal (null) from Receive. The time allotted to this operation may have been a portion of a longer timeout. An exception has been thrown when reading the stream. The .Net Framing mode being used is not supported by '{0}'. See the server logs for more details. The fault reason does not contain any text translations. Callback method {0} is not supported, this can happen if the method is not marked with OperationContractAttribute or if its interface type is not the target of the ServiceContractAttribute's CallbackContract. The CustomBinding on the ServiceEndpoint with contract '{0}' lacks a TransportBindingElement. Every binding must have at least one binding element that derives from TransportBindingElement. In order to use the contract '{0}' with DuplexChannelFactory, the contract must specify a valid callback contract. If your contract does not have a callback contract, consider using ChannelFactory instead of DuplexChannelFactory. Cannot find '{0}' value in dictionary string. Contract requires OneWay, but Binding '{0}' doesn't support it or isn't configured properly to support it. Cannot claim lock within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout. An error ({0}) occurred while parsing the content type of the HTTP request. The content type was: {1}. Header name mismatch in member {1} of type {0}. The header name found in the description is {2}. The element name deduced by the formatter is {3}. This mismatch can happen if the ElementName specified in XmlElementAttribute or XmlArrayAttribute does not match the name specified in the MessageHeaderAttribute or MessageHeaderArrayAttribute or the member name. Element {0} cannot be empty. IAsyncResult not provided or of wrong type. Peer Trust certificate validation is not supported on OSX. See https://go.microsoft.com/fwlink/?linkid=849976 for details. The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '{0}'. You cannot specify an explicit Proxy Address as well as UseDefaultWebProxy=true in your HTTP Transport Binding Element. The asynchronous result object used to end this operation was not the object that was returned when the operation was initiated. Cannot propagate channel parameters because the {0} is in the {1} state. This operation is only supported in the Opening or Opened state when the collection is locked. XmlSerializer attribute {0} is not valid in {1}. Only XmlElement, XmlArray, XmlArrayItem and XmlAnyElement attributes are supported in MessageContract when IsWrapped is false. The channel received an unexpected fault input message with Action = '{0}' while closing. You should only close your channel when you are not expecting any more input messages. Async End called on wrong channel. Contract does not allow Session, but Binding '{0}' does not support Datagram or is not configured properly to support it. {0} returned true from OnTryCreateFaultMessage, but did not return a fault message. The security timestamp is stale because its expiration time ('{0}') is in the past. Current time is '{1}' and allowed clock skew is '{2}'. Contract requires TwoWay (either request-reply or duplex), but Binding '{0}' doesn't support it or isn't configured properly to support it. {0} returned true from OnTryCreateException, but did not return an Exception. Body object cannot be null in message {0} A body element was not found inside the message envelope. Close '{0}'. The content type {0} of the response message does not match the content type of the binding ({1}). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first {2} bytes of the response were: '{3}'. MaxBufferSize must not exceed MaxReceivedMessageSize. Couldn't find required attribute of type {0} on {1}. This collection does not support setting extensions by index. Please consider using the InsertItem or RemoveItem methods. Content Type {0} was not supported by service {1}. The client and service bindings may be mismatched. This message cannot support the operation because it has been read. The ChannelDispatcher at '{0}' with contract(s) '{1}' is unable to open its IChannelListener. The ChannelDispatcher at '{0}' is unable to open its IChannelListener as there are no endpoints for the ChannelDispatcher. The open operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout. The value could not be added to the collection, as the collection already contains an item of the same type: '{0}'. This collection only supports one instance of each type. The underlying channel factory could not be created because no Binding was passed to the ChannelFactory. Please supply a valid Binding instance via the ChannelFactory constructor. X509CertificateValidationMode.Custom requires a CustomCertificateValidator. Specify the CustomCertificateValidator property. DispatchOperation requires Invoker. Header name mismatch in operation {0} from contract {1}:{2}. The header name found in the description is {3}. The element name deduced by the formatter is {4}. This mismatch can happen if the ElementName specified in XmlElementAttribute or XmlArrayAttribute does not match the name specified in the MessageHeaderAttribute or MessageHeaderArrayAttribute or the member name. The socket was aborted because an asynchronous receive from the socket did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout. An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: There was an error while trying to deserialize parameter {0}:{1}. Please see InnerException for more details. Part {1}:{0} is repeating and is not supported in Soap Encoding. This factory buffers messages, so the message sizes must be in the range of an integer value. The security timestamp is stale because its creation time ('{0}') is too far back in the past. Current time is '{1}', maximum timestamp lifetime is '{2}' and allowed clock skew is '{3}'. The socket connection was aborted because an asynchronous send to the socket did not complete within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout. The security timestamp is invalid because its creation time ('{0}') is in the future. Current time is '{1}' and allowed clock skew is '{2}'. The scheme parameter must not be empty. The operation '{0}' could not be invoked because the property '{1}' on the OperationContract is set to '{2}'. To invoke this operation on the server, call the '{3}' method on the client proxy instead. Cannot add outgoing headers to message as MessageVersion in OperationContext.Current '{0}' does not match with the header version of message being processed '{1}'. Cannot process contentType. RPC Message {1} in operation {0} must have a single MessageBodyMember. The contract '{0}' is not self-consistent -- it has one or more IsTerminating or non-IsInitiating operations, but it does not have the SessionMode property set to SessionMode.Required. The IsInitiating and IsTerminating attributes can only be used in the context of a session. HTTP request streaming cannot be used in conjunction with HTTP authentication. Either disable request streaming or specify anonymous HTTP authentication. The security timestamp is invalid because its creation time ('{0}') is greater than or equal to its expiration time ('{1}'). Unrecognized identity type Name='{0}', Namespace='{1}'. The operation contract '{0}' is not self-consistent. When the '{1}' is set to '{2}', both '{3}' and '{4}' properties must be true, and the operation must not have any input parameters. The token requirement '{0}' does not specify the target address. This is required by the token manager for creating the corresponding security token provider. The HTTP service located at {0} is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later. This collection does not support setting items by index. The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs. Cannot modify channel parameters because the {0} is in the {1} state. This operation is only supported in the Created state. TimeSpan must be greater than TimeSpan.Zero. HttpChannelFactory cannot create the channel with shape '{0}' when the {1} of {2} was set as '{3}'. Unrecognized contentType ({0}). Expected: {1}. The message could not be dispatched because the service at the endpoint address '{0}' is unavailable for the protocol of the address. An error occurred while receiving the HTTP response to {0}. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The {0} object has been disposed. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a task-based asynchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, the two OperationContracts must have the same value for the '{5}' property. In this case, the values are different. To fix it, change the '{5} property of one of the OperationContracts to match the other. Alternatively, changing the name of one of the methods will prevent matching. The '{0}' header cannot be added because it does not support the specified message version '{1}'. Unrecognized identity property type: '{0}'. There is a problem with the XML that was received from the network. See inner exception for more details. Operation '{0}' could not be loaded as it uses an unsupported combination of Use and Style settings: Document with Encoded. To fix the problem, change the Use setting to Literal or change the Style setting to Rpc. Construct ChannelFactory. Contract type: '{0}'. This fault did not provide a reason (MessageFault.Reason.Translations.Count was 0). The value '{0}' cannot be parsed as the type '{1}'. The XML element {0} does not have a child of type {1}. Specified size is too large for this implementation. Message part {0} in namespace {1} appears more than once in Message. --- End of inner ExceptionDetail stack trace --- Incoming binary negotiation has invalid ValueType {0}. The number of bytes available is inconsistent with the HTTP Content-Length header. There may have been a network error or the client may be sending invalid requests. An error occurred while loading attribute '{0}' on method '{1}' in type '{2}'. Please see InnerException for more details. Required xml:lang attribute value is missing. The value specified for the AuthenticationScheme property on the HttpTransportBindingElement ('{0}') is not allowed when building a ChannelFactory. If you used a standard binding, ensure the ClientCredentialType is not set to HttpClientCredentialType.InheritedFromHost, a value which is invalid on a client. If you set the value to '{0}' directly on the HttpTransportBindingElement, please set it to Digest, Negotiate, NTLM, Basic, or Anonymous. The input handler list cannot be empty. XML child node {0} of type {1} is unexpected for element {2}. The InstanceContext has no provider for creating Service implementation objects. Unable to obtain XmlDictionaryReaderQuotas from the Binding. If you have specified a custom EncodingBindingElement, verify that the EncodingBindingElement can handle XmlDictionaryReaderQuotas in its GetProperty<T>() method. The HTTP request is unauthorized with client authentication scheme '{0}'. The authentication header received from the server was '{1}'. {0} must contain either a single ServiceKnownTypeAttribute that refers to a method or a set of ServiceKnownTypeAttributes, each specifying a valid type The requested upgrade is not supported by '{0}'. This could be due to mismatched bindings (for example security enabled on the client and not on the server). {0} is not available in deserialized RequestSecurityToken. The message containing this stream has been closed. Note that request streams cannot be accessed after the service operation returns. None of the binding elements in binding '{0}' define a message version. At least one binding element must define a message version and return it from the GetProperty<MessageVersion> method. The subprotocol '{0}' is invalid because it contains the invalid character '{1}'. ContractDescription '{0}' has zero operations; a contract must have at least one operation. Empty string is not a valid subprotocol value. Please use \"null\" to specify no value. '{0}' from namespace '{1}' is not expected. Expecting element '{2}' from namespace '{3}' When using the rpc-encoded style, message contract types or the System.ServiceModel.Channels.Message type cannot be used if the operation has no parameters or has a void return value. Add a blank message contract type as a parameter or return type to operation '{0}'. A Channel/Service endpoint's Binding is null. Cannot write to the stream because the end of the stream marker was already written. The X.509 certificate ({0}) usage time is invalid. The usage time '{1}' does not fall between NotBefore time '{2}' and NotAfter time '{3}'. The size necessary to buffer the XML content exceeded the buffer quota. Because base ServiceContract '{0}' has a CallbackContract '{1}', derived ServiceContract '{2}' must also specify either '{1}' or a derived type as its CallbackContract. Cannot add EndpointDispatcher to more than one ChannelDispatcher. The {0} declared on method '{1}' in type '{2}' is invalid. {0}s are only valid on methods that are declared in a type that has ServiceContractAttribute. Either add ServiceContractAttribute to type '{2}' or remove {0} from method '{1}'. A reply message was received for operation '{0}' with action '{1}'. However, your client code requires action '{2}'. CallbackBehaviorAttribute can only be run as a behavior on an endpoint with a duplex contract. Contract '{0}' is not duplex, as it contains no callback operations. There was an error deserializing the security token XML. Please see the inner exception for more details. The operation '{0}' could not be loaded because it has a parameter or return type of type System.ServiceModel.Channels.Message or a type that has MessageContractAttribute and other parameters of different types. When using System.ServiceModel.Channels.Message or types with MessageContractAttribute, the method must not use any other types of parameters. ActivityBoundary A Channel/Service endpoint's Contract's name is null or empty. The body reader is in ReadState '{0}' and cannot be consumed. A Channel/Service endpoint's Contract's namespace is null. The incoming message contains a SOAP header representing the WS-Addressing '{0}', yet the HTTP transport is configured with AddressingVersion.None. As a result, the message is being dropped. If this is not desired, then update your HTTP binding to support a different AddressingVersion. This property sets EnableFaults on the client. To set EnableFaults on the server, use ChannelDispatcher's EnableFaults. The following remote identity failed verification: '{0}'. Could not connect to {0}. TCP error code {1}: {2}. The token provider '{0}' does not support token cancellation. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract method '{2}' because they have the same operation name '{3}'. When a synchronous OperationContract method is matched to a task-based asynchronous OperationContract method, the two OperationContracts must define the same return type. In this case, the return types are different. To fix it, ensure that method '{0}' and method '{2}' have the same return type. Alternatively, changing the name of one of the methods will prevent matching. The one-way operation returned a fault message with Action='{0}'. There is no namespace binding for prefix '{0}' in scope. Wrapper element name cannot be empty. IAsyncResult's State must be the state argument passed to your Begin call. Binding name cannot be null or empty. Multiple headers with name '{0}' and namespace '{1}' found. You have tried to create a channel to a service that does not support .Net Framing. The QName is invalid. This collection already contains an address with scheme {0}. There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting 'system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled' to true or specifying 'system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters'. The identity check failed for the outgoing message. The expected identity is '{0}' for the '{1}' target endpoint. The binary encoder session information is not properly formed. OperationDescription '{0}' is invalid because its Messages property contains an invalid number of MessageDescription instances. Each OperationDescription must have one or two messages. ... Error reading body: {0}: {1} ... Unrecognized charSet '{0}' in contentType. The request channel timed out attempting to send after {0}. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. The message version of the outgoing message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured with the same version as the message. An internal error has occurred. Invalid MessageState. Only an absolute Uri can be used as a base address. Failed to copy the HTTP header '{0}' with value '{1}' to '{2}'. The task-based asynchronous OperationContract method '{0}' in type '{1}' was matched with the asynchronous OperationContract methods '{2}' and '{3}' because they have the same operation name '{4}'. When a task-based asynchronous OperationContract method is matched to a pair of asynchronous OperationContract methods, any additional attributes must be declared on the task-based asynchronous OperationContract method. In this case, the asynchronous OperationContract method '{2}' has one or more attributes of type '{5}'. To fix it, remove the '{5}' attribute or attributes from method '{2}'. Alternatively, changing the name of one of the methods will prevent matching. The array passed does not have enough space to hold all the properties contained by this collection. The 'parameters' argument must be either null or an empty array. OperationContract method '{0}' in type '{1}' does not properly implement the async pattern, as more than one corresponding method '{2}' was found. When using the async pattern, exactly one end method must be provided. Either remove or rename one or more of the '{2}' methods such that there is just one, or set the AsyncPattern property on method '{0}' to false. The username is not provided. Specify username in ClientCredentials. The maximum message size quota for incoming messages ({0}) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. Clone() was not implemented properly by '{0}'. The cloned object was '{1}'. All parameter names used in operations that make up a service contract must not be null. Invalid IContextChannel passed to OperationContext. Must be either a server dispatching channel or a client proxy channel. Binding '{0}' doesn't support creating any channel types. This often indicates that the BindingElements in a CustomBinding have been stacked incorrectly or in the wrong order. A Transport is required at the bottom of the stack. The recommended order for BindingElements is: TransactionFlow, ReliableSession, Security, CompositeDuplex, OneWay, StreamSecurity, MessageEncoding, Transport. The body writer returned from OnCreateBufferedCopy was not buffered. WaitForMessage timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. The body of the message cannot be read because it is empty. The element '{0}' in namespace '{1}' is not valid. This either means that element '{0}' is a duplicate element, or that it is not a legal extension because extension elements cannot be in the addressing namespace. The ClientCredentials cannot be added to the binding parameters because the binding parameters already contains a SecurityCredentialsManager '{0}'. If you are configuring custom credentials for the channel, please first remove any existing ClientCredentials from the behaviors collection before adding the custom credential. Method '{0}' has OperationContractAttribute, but enclosing type '{1}' does not have ServiceContractAttribute. OperationContractAttribute can only be used on methods in ServiceContractAttribute types or on their CallbackContract types. The framing fault size ({0}) exceeds the quota. Outgoing reply message for operation '{0}' specified Action='{1}', but contract for that operation specifies ReplyAction='{2}'. The Action specified in the Message must match the ReplyAction in the contract, or the operation contract must specify ReplyAction='*'. Close timed out after {0}. Increase the timeout value passed to the call to Close or increase the CloseTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. Found multiple X.509 certificates using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}'. Provide a more specific find value. In operation {0}, more than one fault is declared with detail type {1} The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract method '{2}' because they have the same operation name '{3}'. When a synchronous OperationContract method is matched to a task-based asynchronous OperationContract method, the two OperationContracts must define the same number and types of parameters. In this case, some of the arguments are different. To fix it, ensure that the OperationContracts define the same number and types of arguments, in the same order. Alternatively, changing the name of one of the methods will prevent matching. Expected record type '{0}', found '{1}'. Cannot have two operations in the same contract with the same name, methods {0} and {1} in type {2} violate this rule. You can change the name of one of the operations by changing the method name or by using the Name property of OperationContractAttribute. The token provider of type '{0}' did not return a token of type '{1}'. Check the credential configuration. The return type of method {1} in type {2} must be IEnumerable<Type> to be used by ServiceKnownTypeAttribute in {0} One way operation {0} cannot not specify a reply action. Message {0} must not have headers to be used in RPC encoded style. There was an error creating the security key identifier clause from the security token XML. Please see the inner exception for more details. The type argument passed to the generic ChannelFactory class must be an interface type. The localId cannot be empty. Specify a valid 'localId'. Insufficient winsock resources available to complete socket connection initiation. An operation marked as IsTerminating has already been invoked on this channel, causing the channel's connection to terminate. No more operations may be invoked on this channel. Please re-create the channel to continue communication. A ServiceContract has more the one operation with an Action of \"*\". A ServiceContract can have at most one operation an Action = \"*\". Cannot add two items with the same key to SynchronizedKeyedCollection. Buffer size must be at least {0} bytes. This request operation sent to {0} did not receive a reply within the configured timeout ({1}). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. This request operation did not receive a reply within the configured timeout ({0}). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client. You cannot Send messages on a channel after CloseOutputSession has been called. The extensions cannot contain an Identity if one is supplied as a constructor argument. Multiple headers with name '{0}' and namespace '{1}' and role '{2}' found. Unrecognized envelope version: {0}. The server at {0} rejected the session-establishment request. Header namespace mismatch in member {1} of type {0}. The header namespace found in the description is {2}. The element namespace deduced by the formatter is {3}. This mismatch can happen if the Namespace specified in XmlElementAttribute or XmlArrayAttribute does not match the namespace specified in the MessageHeaderAttribute or MessageHeaderArrayAttribute or the contract namespace. The 'parameters' argument must be an array of one element. The binding (Name={0}, Namespace={1}) cannot be used to create a ChannelFactory or a ChannelListener because it appears to be missing a TransportBindingElement. Every binding must have at least one binding element that derives from TransportBindingElement. The method '{1}' in type '{0}' is marked IsOneWay=true and declares one or more FaultContractAttributes. One-way methods cannot declare FaultContractAttributes. To fix it, change IsOneWay to false or remove the FaultContractAttributes. Connecting to via {0} timed out after {1}. Connection attempts were made to {2} of {3} available addresses ({4}). Check the RemoteAddress of your channel and verify that the DNS records for this endpoint correspond to valid IP Addresses. The time allotted to this operation may have been a portion of a longer timeout. Object is read-only. Some of the binding elements in this binding were not used when building the ChannelFactory / ChannelListener. This may be have been caused by the binding elements being misordered. The recommended order for binding elements is: TransactionFlow, ReliableSession, Security, CompositeDuplex, OneWay, StreamSecurity, MessageEncoding, Transport. Note that the TransportBindingElement must be last. The following binding elements were not built: {0}. The communication object, {0}, cannot be modified while it is in the {1} state. The identity check failed for the incoming message. The expected identity is '{0}' for the '{1}' target endpoint. The operation '{0}' could not be completed because the sessionful channel timed out waiting to receive a message. To increase the timeout, either set the receiveTimeout property on the binding in your configuration file, or set the ReceiveTimeout property on the Binding directly. The specified channel type {0} is not supported by this channel manager. The authentication modes using Kerberos do not support the impersonation level '{0}'. Specify identification or impersonation. Envelope Version '{0}' is not supported. You have tried to create a channel to a service that does not support .Net Framing. It is possible that you are encountering an HTTP endpoint. The synchronous OperationContract method '{0}' in type '{1}' was matched with the task-based asynchronous OperationContract method '{2}' because they have the same operation name '{3}'. When a synchronous OperationContract method is matched to a task-based asynchronous OperationContract method, any additional attributes must be declared on the synchronous OperationContract method. In this case, the task-based asynchronous OperationContract method '{2}' has one or more attributes of type '{4}'. To fix it, remove the '{4}' attribute or attributes from method '{2}'. Alternatively, changing the name of one of the methods will prevent matching. An error occurred while loading attribute '{0}' on parameter {1} of method '{2}' in type '{3}'. Please see InnerException for more details. The callback contract of contract {0} either does not exist or does not define any operations. If this is not a duplex contract, consider using ChannelFactory instead of DuplexChannelFactory. There was an error while trying to deserialize parameter {0}:{1}. The InnerException message was '{2}'. Please see InnerException for more details. The framing content type size ({0}) exceeds the quota. The server rejected the upgrade request. Cannot find the X.509 certificate using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}'. OperationFormatter encountered an invalid Message body. Expected to find node type 'Element' with name '{0}' and namespace '{1}'. Found node type '{2}' with name '{3}' and namespace '{4}' At least one fault reason must be specified. Found multiple X.509 certificates using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}' for target '{4}'. Provide a more specific find value. The current channel does not support closing the output session as this channel does not implement ISessionChannel<IDuplexSession>. MessageBuffer is closed. The space needed for encoding ({0} bytes) exceeds the message frame offset. Cannot make a call on this channel because a call to Open() is in progress. The ReplayWindow and ClockSkew cannot be the maximum possible value when replay detection is enabled. The HTTP request was forbidden with client authentication scheme '{0}'. An internal error has occurred. The XML buffer is not in the correct state to perform the operation. The client certificate is not provided. Specify a client certificate in ClientCredentials. The message cannot be deserialized into MessageContract type {0} since it does not have a default (parameterless) constructor. Header namespace mismatch in operation {0} from contract {1}:{2}. The header namespace found in the description is {3}. The element namespace deduced by the formatter is {4}. This mismatch can happen if the Namespace specified in XmlElementAttribute or XmlArrayAttribute does not match the namespace specified in the MessageHeaderAttribute or MessageHeaderArrayAttribute or the contract namespace. The maximum message size quota for outgoing messages ({0}) has been exceeded. The requestContext has been aborted. The value '{1}' is not supported in this context for the binding property '{0}'. The username cannot be empty. The value '{0}' is not valid for the Location property. The Location property must be a valid absolute or relative URI. Creation time must be before expiration time. A base address cannot contain a Uri fragment. XmlSerializer attribute {0} is not valid in {1}. Only SoapElement attribute is supported. This CreateChannel overload cannot be called on this instance of DuplexChannelFactory, as the InstanceContext provided to the DuplexChannelFactory does not contain a valid UserObject. ChannelDispatcher requirements cannot be met by the IChannelListener for Binding '{0}' since the contract requires support for one of these channel types '{1}' but the binding only supports these channel types '{2}'. The Identity check failed for the outgoing message. The remote endpoint did not provide a domain name system (DNS) claim and therefore did not satisfied DNS identity '{0}'. This may be caused by lack of DNS or CN name in the remote endpoint X.509 certificate's distinguished name. An error occurred while transmitting data. This operation cannot be done after processing is started. Outgoing request message for operation '{0}' specified Action='{1}', but contract for that operation specifies Action='{2}'. The Action specified in the Message must match the Action in the contract, or the operation contract must specify Action='*'. The '{0}' operation timed out after '{1}'. The time allotted to this operation may have been a portion of a longer timeout. Via '{0}' is too long to be processed by the remote host. See the server logs for more details. There was an error in deserializing one of the headers in message {0}. Please see InnerException for more details. OperationDescription's Name must be a non-empty string. Method '{0}' in class '{1}' has bad parameter metadata: a pass-by-value parameter is marked with the 'out' parameter mode. A DispatchOperation (or ClientOperation) can only be added to its parent DispatchRuntime (or ClientRuntime). Seek is not supported on this stream. The one-way operation returned a non-null message with Action='{0}'. The service implementation object was not initialized or is not available. The TransportBindingElement of type '{0}' in this CustomBinding returned a null or empty string for the Scheme. TransportBindingElement's Scheme must be a non-empty string. Could not find XmlSerializer for type {0}. The framing via size ({0}) exceeds the quota. The IEndpointBehavior '{0}' cannot be used on the server side; this behavior can only be applied to clients. ... stream ... The callback passed to operation '{0}' was called more than once. This indicates an internal error in the implementation of that operation. The communication object, {0}, has overridden the virtual function {1} but it does not call version defined in the base class. Unexpected end of file. There was an error while trying to serialize parameter {0}:{1}. The InnerException message was '{2}'. Please see InnerException for more details. The socket connection has been disposed. The service type provided could not be loaded as a service because it does not have a default (parameter-less) constructor. To fix the problem, add a default constructor to the type, or pass an instance of the type to the host. In a contract inheritance hierarchy, the ServiceContract's CallbackContract must be a subtype of the CallbackContracts of all of the CallbackContracts of the ServiceContracts inherited by the original ServiceContract, Types {0} and {1} violate this rule. The value of argument '{0}' ({1}) is invalid for Enum type '{2}'. The token requirement has an unexpected type '{1}' for property '{0}'. The expected property type is '{2}'. The request message has FaultTo='{0}' but IContextChannel.LocalAddress is '{1}'. When ManualAddressing is false, these values must be the same, null, or EndpointAddress.AnonymousAddress. Enable ManualAddressing or avoid setting FaultTo on the message. A property with the name '{0}' already exists. Addressing Version '{0}' does not support adding WS-Addressing headers. The client was unable to process the callback request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from CallbackBehaviorAttribute or from the <clientDebug> configuration behavior) on the client in order to send the exception information back to the server, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the client trace logs. This operation is not supported because the collection is read-only. Content type '{0}' is too long to be processed by the remote host. See the server logs for more details. The StreamUpgradeProvider {0} does not support the specified ChannelBindingKind ({1}). Instance of MessagePartDescription Name='{0}' Namespace='{1}' cannot be used in this context: required 'Type' property was not set. The remote server did not satisfy the mutual authentication requirement. The value cannot be accessed because it has not yet been fully decoded. The ConfigurationName property must be a non-empty string. The binary encoder session information exceeded the maximum size quota ({0}). To increase this quota, use the MaxSessionSize property on the BinaryMessageEncodingBindingElement. When using the IAsyncResult design pattern, the End method cannot be decorated with OperationContractAttribute. Only the corresponding Begin method can be decorated with OperationContractAttribute; that attribute will apply to the Begin-End pair of methods. Method '{0}' in type '{1}' violates this. The socket connection was aborted by your local machine. This could be caused by a channel Abort(), or a transmission error from another thread using this socket. The channel is configured to use interactive initializer '{0}', but the channel was Opened without calling DisplayInitializationUI. Call DisplayInitializationUI before calling Open or other methods on this channel. The '{0}' list created by the Func '{1}' is invalid because it contains one or more null items. ContractDescription's Name must be a non-empty string. The security token manager cannot create a token provider for requirement '{0}'. The message with Action '{0}' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None). The token provider '{0}' was unable to renew the security token. The ClaimType '{0}' is not recognized. Expected ClaimType '{1}'. This message cannot support the operation because it has been copied. Identity check failed for incoming message. The expected DNS identity of the remote endpoint was '{0}' but the remote endpoint provided DNS claim '{1}'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity '{1}' as the Identity property of EndpointAddress when creating channel proxy.