UNPLATED EN-US 200 24 [Embedded Binary Data] Saasplat.xr.xml Assets\LockScreenLogo.scale-200.png Assets\SplashScreen.scale-200.png Assets\Square150x150Logo.scale-200.png Assets\Square44x44Logo.targetsize-24_altform-unplated.png Assets\Square44x44Logo.scale-200.png Assets\StoreLogo.png Assets\Wide310x150Logo.scale-200.png Properties\Default.rd.xml ReactNative\ReactNative.xr.xml [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] ReactNative\Tracing\LoggingActivityBuilderExtensions.tt WinMetadata\Windows.winmd WinRTXamlToolkit\WinRTXamlToolkit.xr.xml [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] [Embedded Binary Data] WinRTXamlToolkit\Properties\WinRTXamlToolkit.rd.xml [Embedded Binary Data] Cannot call an abstract base member: '{0}' Operator '{0}' is ambiguous on operands of type '{1}' and '{2}' The call is ambiguous between the following methods or properties: '{0}' and '{1}' Ambiguity between '{0}' and '{1}' Ambiguous user defined conversions '{0}' and '{1}' when converting from '{2}' to '{3}' Operator '{0}' is ambiguous on an operand of type '{1}' The left-hand side of an assignment must be a variable, property or indexer A readonly field cannot be assigned to (except in a constructor or a variable initializer) Members of readonly field '{0}' cannot be modified (except in a constructor or a variable initializer) Cannot assign to '{0}' because it is read-only Cannot assign to '{0}' because it is a '{1}' Property or indexer '{0}' cannot be assigned to -- it is read only A static readonly field cannot be assigned to (except in a static constructor or a variable initializer) Fields of static readonly field '{0}' cannot be assigned to (except in a static constructor or a variable initializer) '{0}' is inaccessible due to its protection level No overload for method '{0}' takes '{1}' arguments Argument '{0}' should not be passed with the '{1}' keyword Argument '{0}' must be passed with the '{1}' keyword Argument '{0}': cannot convert from '{1}' to '{2}' The best overloaded method match for '{0}' has some invalid arguments The best overloaded Add method '{0}' for the collection initializer has some invalid arguments Using the generic {1} '{0}' requires '{2}' type arguments Operator '{0}' cannot be applied to operands of type '{1}' and '{2}' In order to be applicable as a short circuit operator a user-defined logical operator ('{0}') must have the same return type as the type of its 2 parameters The right hand side of a fixed statement assignment may not be a cast expression '{0}' does not contain a constructor that takes '{1}' arguments Delegate '{0}' does not take '{1}' arguments Delegate '{0}' has some invalid arguments The delegate '{0}' does not have a valid constructor '{0}' does not contain a definition for '{1}' and the best extension method overload '{2}' has some invalid arguments Wrong number of indices inside []; expected '{0}' Cannot apply indexing with [] to an expression of type '{0}' Instance argument: cannot convert from '{0}' to '{1}' The best overload for '{0}' does not have a parameter named '{1}' The delegate '{0}' does not have a parameter named '{1}' Cannot access protected member '{0}' via a qualifier of type '{1}'; the qualifier must be of type '{2}' (or derived from it) '{1} {0}' has the wrong return type The type '{0}' may not be used as a type argument Operator '{0}' cannot be applied to operand of type '{1}' Type parameter '{0}' inherits conflicting constraints '{1}' and '{2}' Cannot perform member assignment on a null reference Binary operators cannot be invoked with one argument Binary operators must be invoked with two arguments Overload resolution failed Cannot dynamically invoke method '{0}' because it has a Conditional attribute Explicit conversion takes exactly one argument Implicit conversion takes exactly one argument Cannot invoke a non-delegate type The event '{0}' can only appear on the left hand side of + The name '{0}' is bound to a method and cannot be used like a property Cannot bind call with no calling object '{0}' is not supported by the language Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor method '{1}' Property, indexer, or event '{0}' is not supported by the language; try directly calling accessor methods '{1}' or '{2}' Cannot implicitly convert type 'void' to 'object' Unary operators must be invoked with one argument '{0}' is a type not supported by the language Do not directly call your base class Finalize method. It is called automatically from your destructor. Destructors and object.Finalize cannot be called directly. Consider calling IDisposable.Dispose if available. '{0}': cannot explicitly call operator or accessor The type arguments for method '{0}' cannot be inferred from the usage. Try specifying the type arguments explicitly. The operation overflows at compile time in checked mode Circular constraint dependency involving '{0}' and '{1}' Constant value '{0}' cannot be converted to a '{1}' Constant value '{0}' cannot be converted to a '{1}' (use 'unchecked' syntax to override) Cannot convert to static type '{0}' Type parameter '{1}' has the 'struct' constraint so '{1}' cannot be used as a constraint for '{0}' Cannot bind delegate to '{0}' because it is a member of 'System.Nullable<T>' Named argument '{0}' cannot be specified multiple times A field initializer cannot reference the non-static field, method, or property '{0}' You cannot use the fixed statement to take the address of an already fixed expression '{0}': static types cannot be used as type arguments The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. The nullable type '{3}' does not satisfy the constraint of '{1}'. Nullable types can not satisfy any interface constraints. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no implicit reference conversion from '{3}' to '{1}'. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion or type parameter conversion from '{3}' to '{1}'. The type '{3}' cannot be used as type parameter '{2}' in the generic type or method '{0}'. There is no boxing conversion from '{3}' to '{1}'. The non-generic {1} '{0}' cannot be used with type arguments The property or indexer '{0}' cannot be used in this context because the get accessor is inaccessible The property or indexer '{0}' cannot be used in this context because the set accessor is inaccessible The operand of an increment or decrement operator must be a variable, property or indexer The best overloaded method match '{0}' for the collection initializer element cannot be used. Collection initializer 'Add' methods cannot have ref or out parameters. Division by constant zero An unexpected exception occurred while binding a dynamic operation Literal of type double cannot be implicitly converted to type '{1}'; use an '{0}' suffix to create a literal of this type Cannot take the address of, get the size of, or declare a pointer to a managed type ('{0}') No overload for '{0}' matches delegate '{1}' Cannot convert method group '{0}' to non-delegate type '{1}'. Did you intend to invoke the method? Missing compiler required member '{0}.{1}' The type ('{0}') must contain declarations of operator true and operator false Named argument specifications must appear after all fixed arguments have been specified Named argument '{0}' specifies a parameter for which a positional argument has already been given '{2}' must be a non-abstract type with a public parameterless constructor in order to use it as parameter '{1}' in the generic type or method '{0}' The type '{0}' has no constructors defined Cannot convert type '{0}' to '{1}' Cannot implicitly convert type '{0}' to '{1}' Cannot implicitly convert type '{0}' to '{1}'. An explicit conversion exists (are you missing a cast?) Non-invocable member '{0}' cannot be used like a method. '{0}' does not contain a definition for '{1}' '{0}' does not contain a definition for '{1}' and no extension method '{1}' accepting a first argument of type '{0}' could be found (are you missing a using directive or an assembly reference?) Cannot perform runtime binding on a null reference Member '{0}' cannot be accessed with an instance reference; qualify it with a type name instead An object reference is required for the non-static field, method, or property '{0}' Cannot create delegate from method '{0}' because it is a partial method without an implementing declaration Predefined type '{0}' is declared incorrectly Predefined type '{0}' is not defined or imported The property or indexer '{0}' cannot be used in this context because it lacks the get accessor The type '{2}' must be a reference type in order to use it as parameter '{1}' in the generic type or method '{0}' A ref or out argument must be an assignable variable A property or indexer may not be passed as an out or ref parameter A readonly field cannot be passed ref or out (except in a constructor) Members of readonly field '{0}' cannot be passed ref or out (except in a constructor) Cannot pass '{0}' as a ref or out argument because it is read-only Cannot pass '{0}' as a ref or out argument because it is a '{1}' A static readonly field cannot be passed ref or out (except in a static constructor) Fields of static readonly field '{0}' cannot be passed ref or out (except in a static constructor) Cannot modify the return value of '{0}' because it is not a variable '{0}' does not have a predefined size, therefore sizeof can only be used in an unsafe context (consider using System.Runtime.InteropServices.Marshal.SizeOf) Anonymous methods, lambda expressions, and query expressions inside structs cannot access instance members of 'this'. Consider copying 'this' to a local variable outside the anonymous method, lambda expression or query expression and using the local instead. The {1} '{0}' cannot be used with type arguments Cannot convert null to type parameter '{0}' because it could be a non-nullable value type. Consider using 'default({0})' instead. '{0}' cannot implement both '{1}' and '{2}' because they may unify for some type parameter substitutions Dynamic calls cannot be used in conjunction with pointers The type '{2}' must be a non-nullable value type in order to use it as parameter '{1}' in the generic type or method '{0}' Cannot convert null to '{0}' because it is a non-nullable value type Extension methods '{0}' defined on value type '{1}' cannot be used to create delegates Cannot access a non-static member of outer type '{0}' via nested type '{1}' Conversion from type '{0}' to type '{1}' is ambiguous. Argument matching parameter '{0}' cannot convert from '{1}' to '{2}'. Argument matching parameter '{0}' cannot convert from '{1}' to '{2}' because the conversion is ambiguous. ByRef parameter '{0}' cannot convert from '{1}' to '{2}' when assigning back to the matching argument because the conversion is ambiguous. ByRef parameter '{0}' cannot convert from '{1}' to '{2}' when assigning back to the matching argument. Argument matching parameter '{0}' narrows from '{1}' to '{2}'. ByRef parameter '{0}' narrows from '{1}' to '{2}' when assigning back to the matching argument. Argument '{0}' cannot be converted to a numeric value. Collection index must be in the range 1 to the size of the collection. Argument '{0}' must be greater than or equal to -1. Argument '{0}' must be greater than or equal to 1. Argument '{0}' must be greater or equal to zero. Argument '{0}' must be greater than zero. Loop control variable of type '{1}' does not implement the 'System.IComparable' interface. Argument '{0}' must be less than or equal to the length of argument '{1}'. Argument '{0}' cannot be converted to type 'Date'. Named arguments are not valid as array subscripts. Argument '{0}' is Nothing. Argument '{0}' is not valid for the array. Arguments are not valid. Argument '{0}' is not a valid value. Argument '{0}' cannot be converted to type '{1}'. Length of argument '{0}' must be greater than zero. Argument '{0}' must be greater than 0 or equal to -1. Type of argument '{0}' is '{1}', which is not numeric. Argument '{0}' must be within the range 0 to 99. Argument '{0}' must be within the range of -32768 to 65535. Argument '{0}' cannot be a multi-dimensional array. 'ReDim' cannot change the number of dimensions. 'ReDim' can only change the rightmost dimension. Operator '{0}' is not defined for {1} and {2}. 'Before' and 'After' arguments cannot be combined. Add failed. Duplicate key value supplied. Expression '{0}' is not a procedure, but occurs as the target of a procedure call. Substitution of type arguments failed. Cannot convert start value of type '{0}' and step value of type '{1}' to a common numeric type. Cannot convert start value of type '{0}', limit value of type '{1}', and step value of type '{2}' to a common numeric type. Cannot convert argument '{0}' of type '{1}' to type '{2}'. Type '{0}' must define an operator '{1}', with parameters of type '{0}', to be used in a 'For' statement. Return and parameter types of '{0}' must be of type '{1}' to be used in a 'For' statement. Parameter types of '{0}' must be of type '{1}' to be used in a 'For' statement. Object variable or With block variable not set. For loop not initialized. Invocation of '{0}' on type '{1}' returned Nothing. Internal error in the Microsoft Visual Basic runtime. Conversion from string \"{0}\" to type '{1}' is not valid. Conversion from type '{0}' to type '{1}' is not valid. Managed classes derived from a COM class cannot be called late bound. Method invocation failed because '{0}' cannot be called with these arguments:{1} Error number must be within the range 0 to 65535. Method '{0}' cannot be the target of an assignment. Public member '{0}' on type '{1}' not found. No default member found for type '{0}'. Field '{0}' of type '{1}' is 'ReadOnly'. Parameter '{0}' of '{1}' already has a matching argument. Named argument '{0}' cannot match a ParamArray parameter. Named argument '{0}' matches no parameter of '{1}'. Overload resolution failed because no accessible '{0}' accepts this number of arguments. Overload resolution failed because no Public '{0}' can be called with these arguments:{1} Property '{0}' is WriteOnly. Overload resolution failed because no Public '{0}' is most specific for these arguments:{1} Overload resolution failed because no Public '{0}' can be called without a narrowing conversion:{1} Property '{0}' is ReadOnly. Not most specific. Overload resolution failed because no accessible '{0}' accepts this number of type arguments. type '{0}' string \"{0}\" Overload resolution failed because no '{0}' is Public. Reference to non-shared member '{0}' requires an object reference. Argument not specified for parameter '{0}'. Omitted argument cannot match a ParamArray parameter. Call to set property '{0}' requires at least one argument. Late-bound assignment to a field of value type '{0}' is not valid when '{1}' is the result of a late-bound expression. 'SyncLock' operand cannot be of type '{0}' because '{0}' is not a reference type. Type argument inference fails for argument matching parameter '{0}'. Operator '{0}' is not defined for type '{1}'. Type parameter '{0}' cannot be determined. The buffer is not associated with this pool and may not be returned to it. CompleteAdding may not be used concurrently with additions to the collection. The underlying collection didn't accept the item. At least one of the specified collections is marked as complete with regards to additions. All collections are marked as complete with regards to additions. The collection argument is empty and has been marked as complete with regards to additions. The collection has been marked as complete with regards to additions. The array argument is of the incorrect type. The array argument is multidimensional. The index argument must be greater than or equal zero. The number of elements in the collection is greater than the available space from index to the end of the destination array. The boundedCapacity argument must be positive. The collection argument contains more items than are allowed by the boundedCapacity. The collection has been disposed. The underlying collection was modified from outside of the BlockingCollection<T>. The specified timeout must represent a value between -1 and {0}, inclusive. The collections argument contains at least one disposed element. The collections length is greater than the supported range for 32 bit machine. The collections argument contains at least one null element. The collections argument is a zero-length array. The operation was canceled. The array argument is null. The index argument must be greater than or equal zero. The collection argument is null. The SyncRoot property may not be used for the synchronization of concurrent collections. The array is multidimensional, or the type parameter for the set cannot be cast automatically to the type of the destination array. The index is equal to or greater than the length of the array, or the number of elements in the dictionary is greater than the available space from index to the end of the destination array. The capacity argument must be greater than or equal to zero. The concurrencyLevel argument must be positive. The index argument is less than zero. TKey is a reference type and item.Key is null. The key already existed in the dictionary. The source argument contains duplicate keys. The key was of an incorrect type for this dictionary. The value was of an incorrect type for this dictionary. The count argument must be greater than or equal to zero. The sum of the startIndex and count arguments must be less than or equal to the collection's Count. The startIndex argument must be greater than or equal to zero. Can not call GetEnumerator on partitions after the source enumerable is disposed MoveNext must be called at least once before calling Current. Dynamic partitions are not supported by this partitioner. Object is not a array with the same initialization state as the array to compare it to. Object is not a array with the same number of elements as the array to compare it to. Cannot find the old value Capacity was less than the current Count of elements. MoveToImmutable can only be performed when Count equals Capacity. Collection was modified; enumeration operation may not execute. An element with the same key but a different value already exists. Key: {0} This operation does not apply to an empty instance. This operation cannot be performed on a default instance of ImmutableArray<T>. Consider initializing the array, or checking the ImmutableArray<T>.IsDefault property. Array cannot be null. Collection cannot be null. Dictionary cannot be null. Key cannot be null. Insertion index was out of range. Must be non-negative and less than or equal to size. Larger than collection size. Count must be positive and count must refer to a location within the string/array/collection. Load factor needs to be between 0.1 and 1.0. Index was out of range. Must be non-negative and less than the size of the collection. '{0}' must be non-negative. Non-negative number required. Queue grow factor must be between {0} and {1}. capacity was less than the current size. Item has already been added. Key in dictionary: '{0}' Key being added: '{1}' At least one object must implement IComparable. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Destination array is not long enough to copy all the items in the collection. Check array index and length. Hashtable's capacity overflowed and went negative. Check load factor, capacity and the current size of the table. Only single dimensional arrays are supported for the requested action. Cannot remove the specified item because it was not found in the specified Collection. Queue empty. Stack empty. Enumeration already finished. Collection was modified; enumeration operation may not execute. Enumeration has not started. Call MoveNext. Enumeration has either not started or has already finished. Hashtable insert failed. Load factor too high. The most common cause is multiple threads writing to the Hashtable simultaneously. This range in the underlying list is invalid. A possible cause is that elements were removed. Collection was of a fixed size. Mutating a key collection derived from a dictionary is not allowed. The specified operation is not supported on Ranges. Collection is read-only. This operation is not supported on SortedList nested types because they require modifying the original SortedList. Index is less than zero. An item with the same key has already been added. Key: {0} Argument {0} should be larger than {1}. Insufficient space in the target location to copy the information. Multi dimension array is not supported on this operation. The lower bound of target array must be zero. Bit vector is full. Collection is read-only. Collection was modified after the enumerator was instantiated. Enumerator is positioned before the first element or after the last element of the collection. The OrderedDictionary is read-only and cannot be modified. Larger than collection size. Count must be positive and count must refer to a location within the string/array/collection. Index was out of range. Must be non-negative and less than the size of the collection. Index must be within the bounds of the List. Non-negative number required. Non-negative number required. capacity was less than the current size. An item with the same key has already been added. The input array length must not exceed Int32.MaxValue / {0}. Otherwise BitArray.Length would exceed Int32.MaxValue. At least one object must implement IComparable. Type of argument is not compatible with the generic comparer. Target array type is not compatible with the type of items in the collection. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Array lengths must be the same. Destination array is not long enough to copy all the items in the collection. Check array index and length. Only supported array types for CopyTo on BitArrays are Boolean[], Int32[] and Byte[]. HashSet capacity is too big. Hashtable's capacity overflowed and went negative. Check load factor, capacity and the current size of the table. Insufficient space in the target location to copy the information. Multi dimension array is not supported on this operation. The lower bound of target array must be zero. Only single dimensional arrays are supported for the requested action. The value '{0}' is not of type '{1}' and cannot be used in this generic collection. The LinkedList node does not belong to current LinkedList. Index {0} is out of range. Queue empty. Stack empty. Enumeration already finished. Collection was modified; enumeration operation may not execute. Enumeration has not started. Call MoveNext. Enumeration has either not started or has already finished. Target array type is not compatible with the type of items in the collection. The LinkedList is empty. The LinkedList node already belongs to a LinkedList. Mutating a key collection derived from a dictionary is not allowed. This operation is not supported on SortedList nested types because they require modifying the original SortedList. Mutating a value collection derived from a dictionary is not allowed. The argument '{0}' cannot be null, empty or contain only white space. The associated metadata type for type '{0}' contains the following unknown properties or fields: {1}. Please make sure that the names of these members match the names of the properties on the main type. The type '{0}' must be public. The type '{0}' does not contain a public method named '{1}'. The type '{0}' does not contain a public property named '{1}'. Value cannot be null or empty. The property {0}.{1} could not be found. '{0}' and '{1}' do not match. Could not find a property named {0}. The {0} field is not a valid credit card number. The CustomValidationAttribute method '{0}' in type '{1}' must return System.ComponentModel.DataAnnotations.ValidationResult. Use System.ComponentModel.DataAnnotations.ValidationResult.Success to represent success. The CustomValidationAttribute method '{0}' does not exist in type '{1}' or is not public and static. The CustomValidationAttribute.Method was not specified. The CustomValidationAttribute method '{0}' in type '{1}' must match the expected signature: public static ValidationResult {0}(object value, ValidationContext context). The value can be strongly typed. The ValidationContext parameter is optional. Could not convert the value of type '{0}' to '{1}' as expected by method {2}.{3}. The custom validation type '{0}' must be public. {0} is not valid. The CustomValidationAttribute.ValidatorType was not specified. The custom DataType string cannot be null or empty. The {0} property has not been set. Use the {1} method to get the value. The {0} field is not a valid e-mail address. The type provided for EnumDataTypeAttribute cannot be null. The type '{0}' needs to represent an enumeration type. The {0} field only accepts files with the following extensions: {1} Cannot retrieve property '{0}' because localization failed. Type '{1}' is not public or does not contain a public static string property with the name '{2}'. MaxLengthAttribute must have a Length value that is greater than zero. Use MaxLength() without parameters to indicate that the string or array can have the maximum allowable length. The field {0} must be a string or array type with a maximum length of '{1}'. MetadataClassType cannot be null. MinLengthAttribute must have a Length value that is zero or greater. The field {0} must be a string or array type with a minimum length of '{1}'. The {0} field is not a valid phone number. The type {0} must implement {1}. The maximum value '{0}' must be greater than or equal to the minimum value '{1}'. The minimum and maximum values must be set. The OperandType must be set when strings are used for minimum and maximum values. The field {0} must be between {1} and {2}. The field {0} must match the regular expression '{1}'. The pattern must be set to a valid regular expression. The {0} field is required. The maximum length must be a nonnegative integer. The field {0} must be a string with a maximum length of {1}. The field {0} must be a string with a minimum length of {2} and a maximum length of {1}. The key parameter at position {0} with value '{1}' is not a string. Every key control parameter must be a string. The key parameter at position {0} is null. Every key control parameter must be a string. The key parameter at position {0} with value '{1}' occurs more than once. The number of control parameters must be even. The {0} field is not a valid fully-qualified http, https, or ftp URL. Either ErrorMessageString or ErrorMessageResourceName must be set, but not both. IsValid(object value) has not been implemented by this class. The preferred entry point is GetValidationResult() and classes should override IsValid(object value, ValidationContext context). Both ErrorMessageResourceType and ErrorMessageResourceName need to be set on this attribute. The property '{0}' on resource type '{1}' is not a string type. The resource type '{0}' does not have an accessible static property named '{1}'. The field {0} is invalid. A service of type '{0}' already exists in the container. The ValidationContext for the type '{0}', member name '{1}' must provide the MethodInfo. The instance provided must match the ObjectInstance on the ValidationContext supplied. The value for property '{0}' must be of type '{1}'. A non-null SendOrPostCallback must be supplied. This operation has already had OperationCompleted called on it and further calls are illegal. Operation has been cancelled. This BackgroundWorker is currently busy and cannot run multiple tasks concurrently. This BackgroundWorker states that it doesn't report progress. Modify WorkerReportsProgress to state that it does report progress. This BackgroundWorker states that it doesn't support cancellation. Modify WorkerSupportsCancellation to state that it does support cancellation. Buffer cannot be null. The frequency must be between {0} and {1}. The value must be greater than or equal to zero and less than the console's buffer size in that dimension. The console buffer size must not be less than the current size and position of the console window, nor greater than or equal to short.MaxValue. Console key values must be between 0 and 255 inclusive. The console title is too long. The value must be less than the console's current maximum window size of {0} in that dimension. Note that this value depends on screen resolution and the console font. The window position must be set such that the current window size fits within the console's buffer, and the numbers must not be negative. The new console window size would force the console buffer size to be too large. The cursor size is invalid. It must be a percentage between 1 and 100. Specified file length was too large for the file system. Non-negative number required. Positive number required. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. The ConsoleColor enum value was not defined on that enum. Please use a defined color from the enum. Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader. Cannot see if a key has been pressed when either application does not have a console or when console input has been redirected from a file. Try Console.In.Peek. Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read. Stack empty The printf operation failed. Cannot create '{0}' because a file or directory with the same name already exists. The file '{0}' already exists. Unable to find the specified file. Could not find file '{0}'. There is no console. Could not find a part of the path. Could not find a part of the path '{0}'. The specified file name or path is too long, or a component of the specified path is too long. The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. The terminfo database is invalid. Stream does not support reading. Stream does not support seeking. Stream does not support writing. Cannot access a closed file. The home directory of the current user could not be determined. Access to the path is denied. Access to the path '{0}' is denied. Unknown error '{0}'. Format of the initialization string does not conform to specification starting at index {0}. Expecting non-empty string for '{0}' parameter. Internal .Net Framework Data Provider error {0}. Invalid destination buffer (size of {0}) offset: {1} Invalid keyword, contain one or more of 'no characters', 'control characters', 'leading or trailing whitespace' or 'leading semicolons'. Invalid source buffer (size of {0}) offset: {1} The value contains embedded nulls. Keyword not supported: '{0}'. Cannot convert object of type '{0}' to object of type '{1}'. Buffer offset '{1}' plus the bytes available '{0}' is greater than the length of the passed in buffer. Data length '{0}' is less than 0. Specified file length was too large for the file system. ---- DEBUG ASSERTION FAILED ---- ---- Assert Long Message ---- ---- Assert Short Message ---- Assertion Failed: Cancel=Debug, OK=Continue Assertion Failed The file '{0}' already exists. Unable to find the specified file. Could not find file '{0}'. Could not find a part of the path. Could not find a part of the path '{0}'. The specified file name or path is too long, or a component of the specified path is too long. The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. RTL_False Access to the path is denied. Access to the path '{0}' is denied. More than one key matching '{0}' was found in the ExpandoObject. Argument count must be greater than number of named arguments. Argument type cannot be void The result type '{0}' of the binder '{1}' is not compatible with the result type '{2}' expected by the call site. Bind cannot return null. Collection was modified; enumeration operation may not execute. Collection is read-only. The result type '{0}' of the dynamic binding produced by binder '{1}' is not compatible with the result type '{2}' expected by the call site. The result of the dynamic binding produced by the object with type '{0}' for the binder '{1}' needs at least one restriction. The result type '{0}' of the dynamic binding produced by the object with type '{1}' for the binder '{2}' is not compatible with the result type '{3}' expected by the call site. Enumeration has either not started or has already finished. Expression must be readable Expression of type '{0}' cannot be used for constructor parameter of type '{1}' Expression of type '{0}' cannot be used for parameter of type '{1}' of method '{2}' Expression of type '{0}' cannot be used for parameter of type '{1}' First argument of delegate must be CallSite Incorrect number of arguments for constructor Incorrect number of arguments supplied for lambda invocation Incorrect number of arguments supplied for call to method '{0}' Invalid argument value An IDynamicMetaObjectProvider {0} created an invalid DynamicMetaObject instance. The value null is not of type '{0}' and cannot be used in this collection. The value '{0}' is not of type '{1}' and cannot be used in this collection. The specified key '{0}' does not exist in the ExpandoObject. Method precondition violated Non-empty collection required No or Invalid rule produced {0} must be greater than or equal to {1} An element with the same key '{0}' already exists in the ExpandoObject. Type {0} contains generic parameters Type {0} is a generic type definition Type must be derived from System.Delegate Type parameter is {0}. Expected a delegate. Index was out of range. Must be non-negative and less than the size of the collection. Index and count must refer to a location within the buffer. Non-negative number required. IDN labels must be between 1 and 63 characters long. Invalid IDN encoded string. Decoded string is not a valid IDN name. Invalid Unicode code point found at index {0}. String contains invalid Unicode code points. Value of flags is invalid. Invalid normalization form. Insufficient memory to continue the execution of the program. Unknown error '{0}'. The argument must be non-negative. Enum value was out of legal range. Positive number required. Illegal characters in path. String cannot be empty. Reading from the compression stream is not supported. Writing to the compression stream is not supported. Central Directory corrupt. Central Directory is invalid. The magic number in GZip header is not correct. Make sure you are passing in a GZip stream. Cannot create entries on an archive opened in read mode. Cannot use create mode on a non-writable stream. Entries cannot be created while previously created entries are still open. Entries in create mode may only be written to once, and only one entry may be held open at a time. The DateTimeOffset specified cannot be converted into a Zip file timestamp. Cannot modify deleted entry. Delete can only be used when the archive is in Update mode. Cannot delete an entry currently open for writing. Cannot access entries in Create mode. The specified entry name encoding is not supported. Entry names cannot require more than 2^16 bits. Entries larger than 4GB are not supported in Update mode. End of Central Directory record could not be found. Compressed Size cannot be held in an Int64. Local Header Offset cannot be held in an Int64. Number of Entries cannot be held in an Int64. Offset to Central Directory cannot be held in an Int64. Offset to Zip64 End Of Central Directory record cannot be held in an Int64. Start Disk Number cannot be held in an Int64. Uncompressed Size cannot be held in an Int64. An entry in the ZipArchive has a path that contains invalid characters. Cannot modify entry in Create mode after entry has been opened for writing. Found invalid data while decoding. A stream from ZipArchiveEntry has been disposed. Offset plus count is larger than the length of target array. Only one asynchronous reader or writer is allowed time at one time. Block length does not match with its complement. The CRC in GZip footer does not match the CRC calculated from the decompressed data. Failed to construct a huffman tree using the length array. The stream might be corrupted. The stream size in GZip footer does not match the real stream size. Length properties are unavailable once an entry has been opened for writing. A local file header is corrupt. This operation is not supported. Stream does not support reading. Stream does not support writing. Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory. Can not access a closed Stream. The offset and length parameters are not valid for the array that was given. This stream from ZipArchiveEntry does not support reading. Cannot use read mode on a non-readable stream. Cannot modify read-only archive. This stream from ZipArchiveEntry does not support seeking. SetLength requires a stream that supports seeking and writing. Split or spanned archives are not supported. Zip file corrupt: unexpected end of stream reached. Unknown block type. Stream might be corrupted. The compression mode specified in GZip header is unknown. Decoder is in some unknown state. This might be caused by corrupted data. The archive entry was compressed using an unsupported compression method. Update mode requires a stream with read, write, and seek capabilities. Entries cannot be opened multiple times in Update mode. This stream from ZipArchiveEntry does not support writing. Zip 64 End of Central Directory Record not where indicated. The underlying compression routine could not be loaded correctly. The stream state of the underlying compression routine is inconsistent. The underlying compression routine received incorrect initialization parameters. The underlying compression routine could not reserve sufficient memory. The underlying compression routine returned an unexpected error code. The version of the underlying compression routine does not match expected version. Zip entry name ends in directory separator character but contains data. Extracting Zip entry would have resulted in a file outside the specified destination directory. Buffer cannot be null. File name cannot be null. Path cannot be null. Enum value was out of legal range. Specified file length was too large for the file system. Specified handle value was out of range for the file system. Non-negative number required. Positive number required. Empty file name is not legal. Empty path name is not legal. The stream's length cannot be changed. Append access can be requested only in write-only mode. Combining FileMode: {0} with FileAccess: {1} is invalid. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Illegal characters in path. Invalid seek origin. The directory specified, '{0}', is not a subdirectory of '{1}'. Path cannot be the empty string or all whitespace. The given path's format is not supported. FileStream will not open Win32 devices such as disk partitions and tape drives. Avoid use of '\\\\.\\' in the path. The target file '{0}' is a directory, not a file. Handle does not support asynchronous operations. The parameters to the FileStream constructor may need to be changed to indicate that the handle was opened synchronously (that is, it was not opened for overlapped I/O). Handle does not support synchronous operations. The parameters to the FileStream constructor may need to be changed to indicate that the handle was opened asynchronously (that is, it was opened explicitly for overlapped I/O). Invalid File or Directory attributes value. Invalid handle. Search pattern cannot contain '..' to move up directories and can be contained only internally in file/directory names, as in 'a..b'. Second path fragment must not be a drive or UNC name. Path must not be a drive. Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader. Cannot create '{0}' because a file or directory with the same name already exists. BindHandle for ThreadPool failed on this handle. The specified directory '{0}' cannot be created. Unable to read beyond the end of the stream. The file '{0}' already exists. Unable to find the specified file. Could not find file '{0}'. The OS handle's position is not what FileStream expected. Do not use a handle simultaneously in one FileStream and in Win32 code or another FileStream. This may cause data loss. The file is too long. This operation is currently limited to supporting files less than 2 gigabytes in size. IO operation will not work. Most likely the file will become too long or the handle was not opened to support synchronous IO operations. Could not find a part of the path. Could not find a part of the path '{0}'. The specified file name or path is too long, or a component of the specified path is too long. Unable seek backward to overwrite data that previously existed in a file opened in Append mode. Unable to truncate data that previously existed in a file opened in Append mode. The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. Source and destination path must be different. Source and destination path must have identical roots. Move will not work across volumes. Synchronous operations should not be performed on the UI thread. Consider wrapping this method in Task.Run. [Unknown] FileStream was asked to open a device that was not a file. For support for devices like 'com1:' or 'lpt1:', call CreateFile, then use the FileStream constructors that take an OS handle as an IntPtr. Stream does not support reading. Stream does not support seeking. Stream does not support writing. Cannot access a closed file. Access to the path is denied. Access to the path '{0}' is denied. Unknown error '{0}'. Path cannot be null. Non-negative number required. Absolute path information is required. Empty path name is not legal. The given path's format is not supported. Could not find the drive '{0}'. The drive might not be ready or might not be mapped. Unable to find the specified file. Could not find file '{0}'. Cannot create '{0}' because a file or directory with the same name already exists. The file '{0}' already exists. <Path discovery permission to the specified directory was denied.> The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. Unable to create directory. Unable to delete, directory not empty or does not exist. Unable to delete file. An error occurred while accessing IsolatedStorage. Invalid mode, see System.IO.FileMode. Initialization failed. The new quota must be larger than the old quota. Operation not permitted. Operation not permitted on IsolatedStorageFileStream. Path must be a valid file name. Invalid origin, see System.IO.SeekOrigin. Store must be open for this operation. Could not find a part of the path. Could not find a part of the path '{0}'. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. Access to the path is denied. Access to the path '{0}' is denied. Unknown error '{0}'. Buffer cannot be null. Stream cannot be null. The number of bytes requested does not fit into BinaryReader's internal buffer. Non-negative number required. Positive number required. Capacity must be positive. capacity was less than the current size. Stream length must be non-negative and less than 2^31 - 1 - origin. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Invalid seek origin. Stream was not readable. Stream was not writable. Decimal byte array constructor requires an array of length four containing valid decimal bytes. Attempted to access a path that is not on the disk. Attempted to read past the end of the stream. Unicode surrogate characters must be written out as pairs together in the same call, not individually. Consider passing in a character array instead. Too many bytes in what should have been a 7 bit encoded Int32. Found invalid data while decoding. The stream is currently in use by a previous operation on the stream. WinRT Interop has already been initialized and cannot be initialized again. Timeouts are not supported on this stream. Unable to read beyond the end of the stream. BinaryReader encountered an invalid string length of {0} characters. An attempt was made to move the position before the beginning of the stream. Stream was too long. Memory stream is not expandable. Stream does not support reading. Stream does not support writing. Cannot access a closed file. Cannot read from a closed TextReader. Cannot access a closed Stream. Cannot write to a closed TextWriter. Buffer cannot be null. Enum value was out of legal range. The length cannot be greater than the capacity. Non negative number is required. Positive number required. The position may not be greater or equal to the capacity of the accessor. Stream length must be non-negative and less than 2^31 - 1 - origin. The UnmanagedMemoryStream capacity would wrap around the high end of the address space. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Offset and length were greater than the size of the SafeBuffer. Invalid seek origin. There are not enough bytes remaining in the accessor to read at this position. There are not enough bytes remaining in the accessor to write at this position. Offset and capacity were greater than the size of the view. The UnmanagedMemoryAccessor capacity and offset would wrap around the high end of the address space. Read an invalid decimal value from the buffer. Not enough space available in the buffer. Unmanaged memory stream position was beyond the capacity of the stream. The method cannot be called twice on the same instance. Unable to expand length of this stream beyond its capacity. An attempt was made to move the position before the beginning of the stream. Stream was too long. Accessor does not support reading. This operation is not supported for an UnmanagedMemoryStream created from a SafeBuffer. Stream does not support reading. Stream does not support writing. Accessor does not support writing. Cannot access a closed Stream. Cannot access a closed accessor. Accessor indexes cannot be passed ByRef. Accessor method should not have VarArgs. All case bodies and the default body must have the same type. All test values must have the same type. Cannot jump to ambiguous label '{0}'. Argument type cannot be System.Void. The member '{0}' is not declared on type '{1}' being created Argument must be array Argument for array index must be of type Int32 Argument must be boolean Argument must be either a FieldInfo or PropertyInfo Argument must be either a FieldInfo, PropertyInfo or MethodInfo Argument must be an instance member Argument must be of an integer type Argument must be single dimensional array type Argument must not have a value type. Argument type '{0}' does not match the corresponding member type '{1}' Argument types do not match arrayType must be an array type The binary operator {0} is not defined for the types '{1}' and '{2}'. Body of catch must have the same type as body of try. Both accessors must be static. Bounds count cannot be less than 1 Cannot auto initialize elements of value type through property '{0}', use assignment instead Cannot auto initialize members of value type through property '{0}', use assignment instead Cannot close over byref parameter '{0}' referenced in lambda '{1}' CompileToMethod cannot compile constant '{0}' because it is a non-trivial value, such as a live object. Instead, create an expression tree that can construct this value. Dynamic expressions are not supported by CompileToMethod. Instead, create an expression tree that uses System.Runtime.CompilerServices.CallSite. Coalesce used with type that cannot be null No coercion operator is defined between types '{0}' and '{1}'. Collection was modified; enumeration operation may not execute. Control cannot enter an expression--only statements can be jumped into. Control cannot enter a try block. Control cannot leave a filter test. Control cannot leave a finally block. Conversion is not supported for arithmetic types without operator overloading. Count must be non-negative. Default body must be supplied if case bodies are not System.Void. Found duplicate parameter '{0}'. Each ParameterExpression in the list must be a unique object. Parameter '{0}' of element initializer method '{1}' must not be a pass by reference parameter Element initializer method must be named 'Add' Element initializer method must be an instance method Element initializer method must have at least 1 parameter Enumeration has either not started or has already finished. The user-defined equality method '{0}' must return a boolean value. Expression must be readable Expression must be writeable The expression '{0}' is not supported for nullable type '{1}' The expression '{0}' is not supported for type '{1}' An expression of type '{0}' cannot be used to initialize an array of type '{1}' Expression of type '{0}' cannot be used for assignment to type '{1}' Expression of type '{0}' cannot be used for constructor parameter of type '{1}' Expression of type '{0}' cannot be used for label of type '{1}' Expression of type '{0}' cannot be used for parameter of type '{1}' of method '{2}' Expression of type '{0}' cannot be used for parameter of type '{1}' Expression of type '{0}' cannot be used for return type '{1}' Expression of type '{0}' cannot be invoked Extension node must override the property {0}. Extension should have been reduced. Fault blocks are not supported fault cannot be used with catch or finally clauses Field '{0}.{1}' is not defined for type '{2}' Field '{0}' is not defined for type '{1}' Filter blocks are not supported No generic method '{0}' on type '{1}' is compatible with the supplied type arguments and arguments. No type arguments should be provided if the method is non-generic. Dynamic operations can only be performed in homogenous AppDomain. Cannot create instance of {0} because it contains generic parameters Incorrect number of arguments for the given members Incorrect number of arguments for constructor Incorrect number of indexes Incorrect number of arguments supplied for lambda invocation Incorrect number of parameters supplied for lambda declaration Incorrect number of members for constructor Incorrect number of arguments supplied for call to method '{0}' An incorrect number of type args were specified for the declaration of an Action type. An incorrect number of type args were specified for the declaration of a Func type. The type used in TypeAs Expression must be of reference or nullable type, {0} is neither Indexing parameters of getter and setter must match. Method '{0}' declared on type '{1}' cannot be called with instance of type '{2}' Instance field '{0}' is not defined for type '{1}' Instance property '{0}' is not defined for type '{1}' Instance property '{0}' that takes no argument is not defined for type '{1}' Instance property '{0}{1}' is not defined for type '{2}' Invalid argument value Invalid assembly name or file extension. Cannot cast from type '{0}' to type '{1} Invalid lvalue for assignment: {0}. Invalid member type: {0}. The value null is not of type '{0}' and cannot be used in this collection. The value '{0}' is not of type '{1}' and cannot be used in this collection. Invalid operation: '{0}' Invalid output directory. Can only unbox from an object or interface type to a value type. Label type must be System.Void if an expression is not supplied Cannot redefine label '{0}' in an inner block. Cannot jump to undefined label '{0}'. Type must be System.Void for this label argument Lambda type parameter must be derived from System.Delegate List initializers must contain at least one initializer The user-defined operator method '{1}' for operator '{0}' must have associated boolean True and False operators. Member '{0}' not field or property MethodBuilder does not have a valid TypeBuilder Method {0} contains generic parameters No method '{0}' exists on type '{1}'. Method {0} is a generic method definition The method '{0}.{1}' is not a property accessor No method '{0}' on type '{1}' is compatible with the supplied arguments. More than one method '{0}' on type '{1}' is compatible with the supplied arguments. must be reducible node node cannot reduce to itself or null Rewriting child expression from type '{0}' to type '{1}' is not allowed, because it would change the meaning of the operation. If this is intentional, override '{2}' and change it to allow this rewrite. When called from '{0}', rewriting a node of type '{1}' must return a non-null value of the same type. Alternatively, override '{2}' and change it to not visit children of this type. Rewritten expression calls operator method '{0}', but the original node had no operator method. If this is is intentional, override '{1}' and change it to allow this rewrite. Non-empty collection required Cannot jump to non-local label '{0}' with a value. Only jumps to labels defined in outer blocks can pass values. Non-reducible expression extensions are not supported '{0}' is not a member of type '{1}' Static field requires null instance, non-static field requires non-null instance. Static method requires null instance, non-static method requires non-null instance. Static property requires null instance, non-static property requires non-null instance. The operands for operator '{0}' do not match the parameters of method '{1}'. The operator '{0}' is not implemented for type '{1}' {0} must be greater than or equal to {1} The return type of overload method for operator '{0}' does not match the parameter type of conversion method '{1}'. ParameterExpression of type '{0}' cannot be used for delegate parameter of type '{1}' DebugInfoGenerator created by CreatePdbGenerator can only be used with LambdaExpression.CompileToMethod. Property cannot have a managed pointer type. The property '{0}' has no 'get' or 'set' accessors The property '{0}' has no 'get' accessor The property '{0}' has no 'set' accessor Property '{0}' is not defined for type '{1}' Property type must match the value type of setter Property cannot have a void type. More than one property '{0}' on type '{1}' is compatible with the supplied arguments. Queue empty. Quoted expression must be a lambda cannot assign from the reduced node type to the original node type reducible nodes must override Expression.Reduce() Reference equality is not defined for the types '{0}' and '{1}'. Rethrow statement is valid only inside a Catch block. Setter must have parameters. Setter should have void type. Start and End must be well ordered Switch value of type '{0}' cannot be used for the comparison method parameter of type '{1}' Test value of type '{0}' cannot be used for the comparison method parameter of type '{1}' try must have at least one catch, finally, or fault clause Try expression is not allowed inside a filter body. TryExpression is not supported as an argument to method '{0}' because it has an argument with by-ref type. Construct the tree so the TryExpression is not nested inside of this expression. TryExpression is not supported as a child expression when accessing a member on type '{0}' because it is a value type. Construct the tree so the TryExpression is not nested inside of this expression. Type {0} contains generic parameters Type doesn't have constructor with a given signature Type {0} is a generic type definition Type '{0}' does not have a default constructor type must not be ByRef Type '{0}' is not IEnumerable The unary operator {0} is not defined for the type '{1}'. variable '{0}' of type '{1}' referenced from scope '{2}', but it is not defined Unexpected coalesce operator. Unexpected VarArgs call to method '{0}' Unhandled binary: {0} Unhandled binding Unhandled Binding Type: {0} Unhandled convert: {0} Unhandled Expression Type: {0} Unhandled unary: {0} Unknown binding type unknown lift type: '{0}'. The expression type '{0}' is not supported User-defined operator method '{0}' must be static. User-defined operator method '{0}' must not be void. The user-defined operator method '{1}' for operator '{0}' must have identical parameter and return types. The user-defined operator method '{1}' for operator '{0}' must return the same type as its parameter or a derived type. Variable '{0}' uses unsupported type '{1}'. Reference types are not supported for variables. Enumeration yielded no results Sequence contains more than one element Sequence contains more than one matching element Sequence contains no elements Sequence contains no matching element The second data source of a binary operator must be of type System.Linq.ParallelQuery<T> rather than System.Collections.Generic.IEnumerable<T>. To fix this problem, use the AsParallel() extension method to convert the right data source to System.Linq.ParallelQuery<T>. The CancellationTokenSource associated with this CancellationToken has been disposed. The mergeOptions argument contains an invalid value. The executionMode argument contains an invalid value. The returned array's length must equal the number of partitions requested. Elements returned must not be null. The return value must not be null. The WithDegreeOfParallelism operator may be used at most once in a query. The WithExecutionMode operator may be used at most once in a query. The WithMergeOptions operator may be used at most once in a query. The WithTaskScheduler operator may be used at most once in a query. The WithCancellation operator may by used at most once in a query. AsOrdered may only be called on the result of AsParallel, ParallelEnumerable.Range, or ParallelEnumerable.Repeat. Non-generic AsOrdered may only be called on the result of the non-generic AsParallel. AsOrdered may not be used with a partitioner that is not orderable. Partitioner returned a null partition. Partitioner returned null instead of a list of partitions. Partitioner returned a wrong number of partitions. Enumeration has not started. MoveNext must be called to initiate enumeration. The query enumerator has been disposed. The query enumerator previously threw an exception. The query has been canceled via the token supplied to WithCancellation. {0} is not IEnumerable<> Argument {0} is not valid Cannot enumerate a query created from a null IEnumerable<> There is no method '{0}' on type '{1}' There is no method '{0}' on type '{1}' that matches the specified arguments Enumeration yielded no results Enumeration has either not started or has already finished. Sequence contains more than one element Sequence contains more than one matching element Sequence contains no elements Sequence contains no matching element Specified file length was too large for the file system. Request for {0} completed successfully. Returning response {1}: {2} Content set to '<null>'. Value for header '{0}' has invalid format. Value: '{1}'. An invalid character was found in header name. The file '{0}' already exists. Unable to find the specified file. Could not find file '{0}'. Could not find a part of the path. Could not find a part of the path '{0}'. The specified file name or path is too long, or a component of the specified path is too long. The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. The specified string is not in the form required for an e-mail address. An invalid character was found in the mail header: '{0}'. The mail header is malformed. The '{0}'='{1}' part of the cookie is invalid. The value cannot be null or empty. The buffer was not long enough. Both 'Content-Length' and 'Transfer-Encoding: chunked' headers can not be specified at the same time. 'Transfer-Encoding: chunked' header can not be used when content object is not specified. The base address must be an absolute URI. An error occurred while sending the request. Only 'http' and 'https' schemes are allowed. An invalid request URI was provided. The request URI must either be an absolute URI or BaseAddress must be set. The request message was already sent. Cannot send the same request message multiple times. Request for {0} was canceled. An error occurred while sending {0}. {1} Cannot write more bytes to the buffer than the configured maximum buffer size: {0}. Buffering more than {0} bytes is not supported. The field cannot be longer than {0} characters. The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. The stream does not support concurrent read operations. The async operation did not return a System.Threading.Tasks.Task object. The stream does not support writing. The stream was already consumed. It cannot be read again. Error while copying content to a stream. The number of elements is greater than the available space from arrayIndex to the end of the destination array. A request message must be provided. It cannot be null. Handler did not return a response message. The inner handler has not been assigned. The specified value is not a valid quoted string. The specified value is not a valid 'From' header string. The header name format is invalid. The specified value is not a valid 'Host' header string. Invalid range. At least one of the two parameters must not be null. The format of value '{0}' is invalid. Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects. The given header was not found. New-line characters in header values must be followed by a white-space character. Cannot add value because header '{0}' does not support multiple values. The format of the HTTP method is invalid. When using CookieUsePolicy.UseSpecifiedCookieContainer, the CookieContainer property must not be null. CookieContainer property must not be null. The {0} property must be set to '{1}' to use this property. When using WindowsProxyUsePolicy.UseCustomProxy, the Proxy property must not be null. When using a non-null Proxy, the WindowsProxyUsePolicy property must be set to WindowsProxyUsePolicy.UseCustomProxy. The read operation failed, see inner exception. Unable to read data from the transport connection. The connection was closed before all data could be read. Expected {0} bytes, read {1} bytes. The write operation failed, see inner exception. Type '{0}.CopyToAsync()' did not return a System.Threading.Tasks.Task object. The 'q' value is invalid: '{0}'. Value for header '{0}' contains invalid new-line characters. Value: '{1}'. Value '{0}' is not a valid email address. Error: {1} Response status code does not indicate success: {0} ({1}). The stream does not support concurrent I/O read or write operations. This instance has already started one or more requests. Properties can only be modified before sending the first request. Value '{0}' is not a valid Base64 string. Error: {1} The reason phrase must not contain new-line characters. The HTTP response headers length exceeded the set limit of {0} bytes. The handler was disposed of while active operations were in progress. The libcurl library in use ({0}) does not support HTTPS. The libcurl library in use ({0}) and its SSL backend ("{1}") do not support custom handling of certificates. A libcurl built with OpenSSL is required. The libcurl library in use ({0}) does not support different credentials for different authentication schemes. The server returned an invalid or unrecognized response. The username for a credential object cannot be null or empty. The specified value must be greater than {0}. The value '{0}' is not supported for property '{1}'. The requested security protocol is not supported. Access to the path is denied. Access to the path '{0}' is denied. This operation cannot be performed on a completed asynchronous result object. IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. The IAsyncResult object was not returned from the corresponding asynchronous method on this class. {0} can only be called once for each asynchronous operation. Exception in {0}::{1} - {2}. The size of {0} is too long. It cannot be longer than {1} characters. An invalid physical address was specified. The collection is read-only. This operation cannot be performed on a completed asynchronous result object. An error was encountered while parsing network information from the operating system. The information requested in unavailable on the current platform. The IAsyncResult object was not returned from the corresponding asynchronous method on this class. {0} can only be called once for each asynchronous operation. Exception in {0}::{1} - {2}. This method is not implemented by this class. No loopback interface was found on the local machine. An error was encountered while querying information from the operating system. This property is not implemented by this class. Argument must be between {0} and {1}. Cannot get the effective time of the SSPI context. Cannot get the expiry time of the SSPI context. The specified content disposition is invalid. The specified content type is invalid. An invalid IP address was specified. The AsyncResult is not valid. An invalid character was found in header name. An invalid character was found in header value. Invalid hex digit '{0}'. Collection was modified after the enumerator was instantiated. Enumerator is positioned before the first element or after the last element of the collection. Either the IAsyncResult object did not come from the corresponding async method on this type, or EndRead was called multiple times with the same IAsyncResult. Either the IAsyncResult object did not come from the corresponding async method on this type, or EndWrite was called multiple times with the same IAsyncResult. The specified port is invalid. The port must be greater than 0. The SSPI context is not valid. A null session key was obtained from SSPI. Invalid SSPI BinaryNegotiationElement. The specified string is not in the form required for an e-mail address. An invalid character was found in the Base-64 stream. The collection is read-only. The date is in an invalid format. The specified singleton field already exists in the collection and cannot be added. An invalid character was found in the mail header: '{0}'. The mail header is malformed. The header name does not match this property. The index value is outside the bounds of the array. The ContentID cannot contain a '<' or '>' character. The Item property can only be used with singleton fields. The underlying list has been changed and the enumeration is out of date. The stream should have been consumed before resetting. The target array is too small to contain all the headers. The SMTP host was not found. GetContentStream() can only be called once. Premature end of stream. Server does not support secure connections. The server response was: {0} The specified string is not in the form required for a subject. This operation cannot be performed while in content. The specified media type is invalid. One of the streams has already been used and can't be reset to the origin. The MIME transfer encoding '{0}' is not supported. Buffer and BufferList properties cannot both be non-null. The target array is too small. The supplied authentication module is not registered. There is no registered module for this authentication scheme. Authentication failed on the remote side (the stream might still be available for additional authentication attempts). The server has rejected the client credentials. Either the target name is incorrect or the server has rejected the client credentials. Once authentication is attempted as the client or server, additional authentication attempts must use the same client or server role. A security requirement was not fulfilled during authentication. Required: {0}, negotiated: {1}. A remote side security requirement was not fulfilled during authentication. Try increasing the ProtectionLevel and/or ImpersonationLevel. Protocol error: cannot proceed with SSPI handshake because an empty blob was received. Authentication failed because the remote party has closed the transport stream. Authentication failed, see inner exception. Re-authentication failed because the remote party continued to encrypt more than {0} bytes before answering re-authentication. Protocol error: A received message contains a valid signature but it was not encrypted as required by the effective Protection Level. An extended protection policy must specify either a custom channel binding or a custom service name collection. This operation is only allowed using a successfully authenticated context. This authenticated context does not support data encryption. The TokenImpersonationLevel.Anonymous level is not supported for authentication. This operation is not allowed on a security context that has already been authenticated. A call to SSPI failed, see inner exception. The supported values are Identification, Impersonation or Delegation. The value of the date string in the header is invalid. Cannot set null or blank methods on request. An invalid IP address prefix was specified. An invalid physical address was specified. The Buffer space specified by the Count property is insufficient for the AcceptAsync method. For this RequestCache object, {0} access is denied. The request failed because no cache entry (CacheKey : {0}) was found and the effective CachePolicy is {1}. The request (Method : {0}) cannot be served from the cache and will fail because of the effective CachePolicy: {1}. The transport stream instance passed in the RangeStream constructor is not seekable and therefore is not supported. The cache protocol refused the server response. To allow automatic request retrying, set request.AllowAutoRedirect to true. No cache protocol is available for this request. The cached response is not supported for a request with a content body. The cached response is not supported for a request with the specified request method. The cache protocol returned a cached response but the cache entry is invalid because it has a null stream. (Cache Key : {0}). Cache retrieve failed: {0}. Shadow stream must be writable. A partial content stream does not support this operation or some method argument is out of range. The validation method {0}() returned a failure for this request. The validation method {0}() returned the unexpected status: {1}. The specified value cannot be false. Failed to load the proxy script runtime environment from the Microsoft.JScript assembly. Unable to create another web proxy script environment at this time. Can't determine OS installation type: Can't read key '{0}'. Exception message: {1} This operation cannot be performed while the AppDomain is shutting down. The Content-Length value must be greater than or equal to zero. The collection is read-only. This operation cannot be performed on a completed asynchronous result object. Error creating the modules specified in the 'system.net/authenticationModules' configuration section. Insufficient permissions for setting the configuration element '{0}'. Insufficient permissions for setting the configuration property '{0}'. Error creating the Web Proxy specified in the 'system.net/defaultProxy' configuration section. The specified proxy module type is not public. Error creating the Web Request caching policy specified in the 'system.net/requestCaching' configuration section. Insufficient permissions for setting the configuration section '{0}'. Error creating the modules specified in the 'system.net/webRequestModules' configuration section. Keep-Alive and Close may not be set using this property. The underlying connection was closed: {0}. An error occurred when adding a cookie to the container. When performing a write operation with AllowWriteStreamBuffering set to false, you must either set ContentLength to a non-negative number or set SendChunked to true. The '{0}'='{1}' part of the cookie is invalid. '{0}' has to be greater than '{1}' and less than '{2}'. Cookie already exists. Cookie format error. Invalid contents for cookie : '{0}'. An error occurred when parsing the Cookie header for Uri '{0}'. The value size of the cookie is '{0}'. This exceeds the configured maximum size, which is '{1}'. The parameter '{0}' cannot be an empty string. This property cannot be set to an empty string. The Registry value '{0}' was either empty or not a string type. You must write ContentLength bytes to the request stream before calling [Begin]GetResponse. Bytes to be written to the stream exceed the Content-Length bytes size specified. The shell expression '{0}' could not be parsed because it is formatted incorrectly. The payload size is limited to {0}, attempted set it to {1}. Received incomplete authentication message. Remote party has probably closed the connection. Cannot determine the frame size or a corrupted frame was received. Received an invalid authentication frame. The message size is limited to {0} bytes, attempted to read {1} bytes. The From parameter cannot be less than To. This type of FTP request does not return a response stream. Need account for storing files Local error in processing Page type unknown File name not allowed File unavailable (e.g., file not found, no access) File unavailable (e.g., file busy) Insufficient storage space in system Syntax error in parameters or arguments Bad sequence of commands Can't open data connection Command not implemented Syntax error, command unrecognized Connection closed; transfer aborted Exceeded storage allocation (for current directory or data set) Not logged in Service not available, closing control connection The data connection was made from an address that is different than the address to which the FTP connection was made. FTP Method names cannot be null or empty. The RenameTo filename cannot be null or empty. The server returned the filename ({0}) which is not valid. The status response ({0}) is not expected in response to '{1}' command. The requested URI is invalid for this FTP command. Default credentials are not supported on an FTP request. The requested FTP command is not supported when using HTTP proxy. Offsets are not supported when sending an FTP request over an HTTP proxy. SSL cannot be enabled when using a proxy. The response string '{0}' has invalid format. The server failed the passive mode request with status response ({0}). This method is not supported. The '{0}' header must be modified using the appropriate property or method. This collection holds response headers and cannot contain the specified request header. This collection holds request headers and cannot contain the specified response header. Header values cannot be longer than {0} characters. Ambiguous Redirect Bad Gateway Bad Request Conflict Forbidden Found Redirect Gateway Timeout Gone Http Version Not Supported Internal Server Error Length Required Method Not Allowed Moved Redirect Moved Permanently Redirect Multiple Choices Redirect No Content Non Authoritative Information Not Acceptable Not Found Not Implemented Not Modified Partial Content Payment Required Proxy Authentication Required Redirect Redirect Keep Verb Redirect Method Request Timeout Reset Content See Other Server Unavailable Temporary Redirect Unauthorized Use Proxy Redirect The '{0}' attribute cannot appear when '{1}' is present. The '{0}' attribute can only appear when '{1}' is present. An asynchronous call is already in progress. It must be completed or canceled before you can call this method. The AddressFamily {0} is not valid for the {1} end point, use {2} instead. None of the discovered or specified addresses match the socket address family. The supplied EndPoint of AddressFamily {0} is not valid for this Socket, use {1} instead. The buffer length must not exceed 65500 bytes. The supplied {0} is an invalid size for the {1} end point. The socket handle is not valid. The status code must be exactly three digits. The server returned a status code outside the valid range of 100-599. This protocol version is not supported. Invalid cast from {0} to {1}. The specified value is not valid in the '{0}' enumeration. The specified value is not a valid Host header string. IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. Value of offset cannot be negative or greater than the length of the buffer. Cannot block a call on this socket while an earlier asynchronous call is in progress. The parameter: {0} is not valid. Use the object returned from corresponding Begin async call. The socket has already been bound to an io completion port. The connection was closed The decryption operation failed, see inner exception. The encryption operation failed, see inner exception. Received an unexpected EOF or 0 bytes from the transport stream. Found a wrong header field {0} read : {1}, expected : {2}. Internal Error: A socket handle could not be bound to a completion port. The IAsyncResult object was not returned from the corresponding asynchronous method on this class. {0} can only be called once for each asynchronous operation. The {0} method cannot be called when another {1} operation is pending. The stream has to be read/write. Cannot close stream until all bytes are written. NetworkStream does not support a 0 millisecond timeout, use a value greater than zero for the timeout instead. The byte count must not exceed {0} bytes for this stream type. The read operation failed, see inner exception. Unable to read data from the transport connection: {0}. Timeout can be only be set to 'System.Threading.Timeout.Infinite' or a value >= 0. Timeout can be only be set to 'System.Threading.Timeout.Infinite' or a value > 0. Unable to create a transport connection. The write operation failed, see inner exception. Unable to write data to the transport connection: {0}. IPv4 is not installed. IPv6 is not installed. The proxy JScript file threw an exception while being initialized: {0}. Failed to listen on prefix '{0}' because it conflicts with an existing registration on the machine. Cannot re-call {0} while a previous call is still in progress. Custom channel bindings are not supported. HTTP.SYS doesn't support extended protection. Please install the latest HTTP.SYS update. Can't close Url group. Status code: {0}. Can't detach Url group from request queue. Status code: {0}. Only Uri prefixes with a valid hostname are supported. Querying the {0} Channel Binding is not supported. Please call the {0} method before calling this method. The in-progress method {0} must be completed first. No service names could be determined from the registered prefixes. Either add prefixes from which default service names can be derived or specify an ExtendedProtectionPolicy object which contains an explicit list of service names. This method cannot be called twice. Only Uri prefixes starting with 'http://' or 'https://' are supported. Only Uri prefixes ending in '/' are allowed. Attempting to restart the session using the user-provided certificate: {0}. The challenge string is not valid for this authentication module: {0} Buffered {0} bytes. A 206 Response has been received and either ETag or Last-Modified header value does not match cache entry. The starting position for 206 Response is not adjusted to the end of cache entry. A 304 response resulted from a HEAD request has different Last-Modified header. 304 response was received on an unconditional request. 304 response was received on an unconditional request, but expected response code is 200 or 206. Accept this response base on the retry count : {0}. After Response Cache Validation. Cache Age : {0}, Cache MaxAge : {1}. [Age1] Now - LastSynchronized : [Age1] Now - LastSynchronized : {0}, Last Synchronized: {1}. [Age1] NowTime-Date Header : {0}, Date Header: {1}. [Age1] Now - LastSynchronized + AgeHeader : {0}, Last Synchronized: {1}. [Age1] Now - LastSynchronized + AgeHeader : {0}, Last Synchronized: {1}, Age Header: {2}. [Age2] AgeHeader : {0}. Request carries Authorization Header and no s-maxage, proxy-revalidate or public directive found. The cached entry has Authorization Header and cache is not fresh. The cached entry has Authorization Header and no Cache-Control directive present that would allow to use that entry. Cache Cache-Control : {0}. Invalid CacheControl header : {0}. Cache LastModified={0}, ContentLength= {1}. A Conditional Range request cannot be constructed. A Conditional Request cannot be constructed. {0} Cannot Remove (throw): Key : {1}, Error : {2}. Cannot update cache if Response status == 304 and a cache entry was not found. Cannot update cache with HEAD response if the cache entry does not exist. {0}: {1} Closing effective cache stream, type : {2}, cache entry key : {3}. Creation of a combined response has been requested from the cache protocol. {0}, Key : {1}, Committed entry as partial, not cached bytes count : {2}. {0}, Key : {1}, Commit operation failed -> {2}. A Conditional Range request on Http <= 1.0 is not implemented. Request Condition : If-Modified-Since:{0}. Request Condition : If-None-Match:{0}. Request Condition : If-Range:{0}. Invalid format of Response Content-Range:{0}. Cached CacheControl : must-revalidate and Cache is not fresh. Cached CacheControl : no-cache. Cached CacheControl : no-cache, Removing some headers. Could be a Partial Cached Response, Size : {0}, Response Content Length : {1}. Create operation failed -> {0}. Response Date header value is older than that of the cache entry. {0}, Key : {1}, Delete operation failed -> {2}. Disable MaxStale (set to 0). Do not update Cached Headers. ...Dumping... ...Dumping Cache Context... ...Dumping Metadata... Enable MaxStale (sec) ={0}. {0}, Cache Entry not found, freshness result : Undefined. Cached Entry Size : {0} is too big, cannot do a range request. {0}, Error deleting a Filename : {1}. {0}, Exception : {1}. {0}: an exception (ignored) on {1} : {2}. An existing cache entry has to be discarded. An existing cache entry should be discarded. Existing cache entry should but cannot be removed due to unexpected response Status : ({0}) {1}. Expected length (0=none)= {0}. Expires (0=none)= {0}. Failing request with the WebExceptionStatus : {0}. {0} -> Filename : {1}, Status : {2}. Response freshness is not within the specified policy limits. FTP request method={0}. This FTP request is configured to use a proxy through HTTP protocol. Cache revalidation and partially cached responses are not supported. FTP Response Status={0}, {1}. Caching is not supported for non-binary FTP request mode. A response resulted from a HEAD request has different Content-Length header. A response resulted from a HEAD request has different Content-MD5 header. A response resulted from a HEAD request has different ETag header. Cannot parse HTTP headers in entry metadata, offending string: {0}. HttpWebResponse is null. Entry Status Line : HTTP/{0} {1} {2}. Cannot Parse Cache HTTP Status Line: {0}. The cached version is invalid, assuming HTTP 1.0. {0}, Key : {1}. {0}, Key : {1}, Remove operation failed -> Status : {2}. {0}, Key : {1}, -> Status : {2}. LastModified (0=none)= {0}. HTTP 1.0 Response Last-Modified header value is older than that of the cache entry. The cache entry last synchronized time : {0}. {0}, Lookup operation failed -> {1}. [MaxAge] Absolute time expiration check (sensitive to clock skew), cache Expires: {0}. [MaxAge] Cache MaxAge : {0}. [MaxAge] Cache s_MaxAge : {0}. [MaxAge] Cache Expires - Date : {0}, Expires: {1}. MaxStale (sec) : {0}. {0}, MaxStale : {1}, Update Status : {2}. Cannot parse all strings in system metadata as \"name:value\", offending string: {0}. Multiple/complex ranges are not implemented. Response can be cached although it will always require revalidation. Need to remove an invalid cache entry with status code == 304(NotModified). This was Not a GET, HEAD or POST request. {0}, Cache is not updated based on the current cache protocol status : {1}. Cache is not updated based on the FTP response status. Expected : {0}, actual : {1}. Cache is not updated based on Policy : {0}. Cache is not updated because there is no response associated with the request. [Now Time (UTC)] : {0}. {0} has requested a cache response but the entry does not exist (Stream.Null). {0}, Nothing was written to the stream, do not commit that cache entry. No request headers are found in cached metadata to test based on the cached response Vary header. This Cache Entry does not carry HTTP response headers. [MaxAge] Cannot compute Cache MaxAge, use 10% since LastModified: {0}, LastModified: {1}. [MaxAge] Cannot compute Cache MaxAge, using default RequestCacheValidator.UnspecifiedMaxAge: {0}. Cache is not updated based on the request Method : {0}. {0} has requested a cache response but the cached stream is null. Response is null so this Request should fail. {0} exception: {1}. Ranges other than bytes are not implemented. A Cache Entry is partial and the user request has non zero ContentOffset : {0}. A restart from cache is not supported for partial cache entries. Serving Partial Response (206) from cache, Content-Range:{0}. A partial response is not combined with existing cache entry, Cache Stream Size : {0}, response Range Start : {1}. Client Policy CacheSyncDate (UTC) : {0}, Cache LastSynchronizedUtc : {1}. Client Policy MaxAge : {0}. Client Policy MaxStale : {0}. Client Policy MinFresh : {0}. POST Response without Cache-Control or Expires headers. Request Range (not in Cache yet) : Range:{0}. Invalid format of Request Range:{0}. Serving Request Range from cache, Range:{0}. Cannot serve from Cache, Range:{0}. Range Request (user specified), Range: {0}. Caching protocol has refused the server response. To allow automatic request retrying set request.AllowAutoRedirect=true. Existing cache entry is removed since a restarted response was changed on the server, cache LastModified date : {0}, new LastModified date : {1}. Existing cache entry is removed based on the request Method : {0}. Existing cache entry is removed based on Policy : {0}. Existing entry is removed because it was found invalid. Replacing cache entry metadata with 'HTTP/1.1 200 OK' status line to satisfy HTTP cache protocol logic. {0} has requested a combined response but the cached stream is null. User Request contains a conditional header. Request Method : {0}. Response LastModified={0}, ContentLength= {1}. Response is valid based on Policy : {0}. Response=304 or Request was HEAD, updating cache entry. Response explicitly allows caching : Cache-Control: {0}. Response Cache-Control : no-store. Response Cache-Control : private, and Cache is public. Response Cache-Control : private+Headers, removing those headers. Response Cache-Control : public. Response with no CacheControl and Status Code : {0}. HttpWebResponse date is older than of the cached one. Response Status : {0}. Response status == 304 but the cache entry does not exist. Accept this response as valid based on the retry count : {0}. {0}, result : {1}. {0} has returned a range cache stream, Offset : {1}, Length : {2}. {0}, No cache entry revalidation is needed. Response revalidation is always required but neither Last-Modified nor ETag header is set on the response. Saving Request Headers, Vary: {0}. Server did not satisfy the range: {0}. Set Expires ={0}. Set LastModified ={0}. Set LastSynchronized ={0}. Set new Metadata. A Response Status Code is not 304 or 206. {0}, stream : {1}. Suppressing cache headers update on 304, new headers don't add anything. Suppressing cache update since the entry was synchronized within the last minute. A 5XX Response and Cache-Only like policy, serving from cache. A 5XX Response that can be replaced by existing cache entry. The cache protocol method {0} has returned unexpected status: {1}. Update Cached Headers. {0}, Key : {1}, Update operation failed -> {2}. Cache update is not supported for restarted FTP responses. Restart offset : {0}. Updating headers on 304 response. Updating cache entry last synchronized time : {0}. Request Uri has a Query, and cached response is from HTTP 1.0 server. Request Uri has a Query, and no explicit expiration time is provided. {0}, UseCount : {1}, File : {2}. Resubmitting this request because cache cannot validate the response. This validator should not be called for policy : {0}. Valid as fresh or because of Cache Policy : {0}. Valid based on Status Code: {0}. Cache entry Vary header contains '*'. Cache entry Vary header is empty. All required Request headers match based on cached Vary response header. Vary header: Request and cache header fields count does not match, header name : {0}. Vary header: A Cache header field mismatch the request one, header name : {0}, cache field : {1}, request field : {2}. Certificate is of type X509Certificate2 and contains the private key. {0}#{1} - Closed as idle. Cannot find the certificate in either the LocalMachine store or the CurrentUser store. The hash algorithm is not supported by Digest authentication: {0}. The Quality of Protection value is not supported by Digest authentication: {0}. A nonce parameter required for Digest authentication was not found or was preceded by an invalid parameter. Exception in {0}::{1} - {2}. Exception in callback: {0}. Trying to find a matching certificate in the certificate store. Found the certificate in the {0} store. Got a certificate from the client delegate. Can't convert bytes '{0}' into UTF-16 characters: {1} Can't convert percent encoded value '{0}'. Can't convert Uri path '{0}' using encoding '{1}'. Can't convert string '{0}' into UTF-8 bytes: {1} Can't create Uri from string '{0}://{1}{2}{3}'. Channel binding check enabled. Failed to create a valid Identity for an incoming request. Sending 500 response, AuthenticationSchemeSelectorDelegate threw an exception: {0}. Exception thrown while reading Registry key '{0}': {1} Can't open Registry key '{0}'. No channel binding check because extended protection is disabled. No channel binding check for requests without a secure channel. No channel binding check because the underlying platform does not support extended protection. No channel binding check for the trusted proxy scenario. No service name check because the channel binding was already checked. No service name check because extended protection is disabled. No explicit service name check because Kerberos authentication already validates the service name. No service name check because the authentication was from a client on the local machine. No service name check because the underlying platform does not support extended protection. No service name check because the client did not provide a service name and the server was configured for PolicyEnforcement.WhenSupported. Client provided service name '{0}'. Adding default service name '{0}' from prefix '{1}'. Service name check failed. Service name check failed because the client did not provide a service name and the server was configured for PolicyEnforcement.Always. Dumping acceptable service names: No acceptable service names were configured! No default service name added for prefix '{0}'. No default service name removed for prefix '{0}'. Service name check succeeded. Removing default service name '{0}' from prefix '{1}'. Received a request with an unmatched or no authentication scheme. AuthenticationSchemes:{0}, Authorization:{1}. Received a request with an unsupported authentication scheme, Authorization:{0} SupportedSchemes:{1}. Locating the private key for the certificate: {0}. Method={0}. Client delegate did not provide a certificate; and there are not other user-provided certificates. Need to attempt a session restart. Client delegate did not provide a certificate; but there are other user-provided certificates. We have user-provided certificates. The server has not specified any issuers, so try all the certificates. Left with {0} client certificates to choose from. Opening Certificate store {0} failed, exception: {1}. {0} failed with error {1}. {0} returned {1}. WebProxy failed to autodetect a Uri for a proxy script. WebProxy failed to parse the auto-detected location of a proxy script:\"{0}\" into a Uri. {0} was called with an invalid parameter. {0} was called with a null '{1}' parameter. RAS is not supported. Can't create RasHelper instance. RAS supported: {0} WebProxy caught an exception while downloading/compiling the proxy script: {0}. WebProxy caught an exception while executing the ScriptReturn script: {0}. ScriptEngine was notified of a potential change in the system's proxy settings and will update WebProxy settings. ScriptEngine was notified of a change in the IP configuration and will update WebProxy settings. Can't open WinHttp session. Error code: {0}. Can't retrieve proxy settings for Uri '{0}'. Error code: {1}. Can't specify proxy discovery timeout. Error code: {0}. Received headers\r\n{{\r\n{0}}}. Received response [{0}] Received status line: Version={0}, StatusCode={1}, StatusDescription={2}. Releasing FTP connection#{0}. Remote certificate: {0}. Remote certificate has errors: Remote certificate has no errors. Certificate name mismatch. The remote server did not provide a certificate. Remote certificate was verified as invalid by the user. Remote certificate was verified as valid by the user. A resolved ServicePoint host could be wrongly considered as a remote server. Resubmitting request. An unexpected exception while retrieving the local address list: {0}. Selected certificate: {0}. Sending command [{0}] Sending headers\r\n{{\r\n{0}}}. We have user-provided certificates. The server has specified {0} issuer(s). Looking for certificates that match any of the issuers. Error code {0} was received from server response. ShellServices.ShellExpression.Parse() was called with a badly formatted 'pattern':{0}. Accepted connection from {0} to {1}. Created connection from {0} to {1}. Connecting to a DnsEndPoint. Not logging data from file: {0}. Enumerating security packages: {0}(In-Buffer length={1}, Out-Buffer length={2}, returned code={3}). {0}(In-Buffers count={1}, Out-Buffer length={2}, returned code={3}). Security package '{0}' was not found. {0}(Protocol={1}, Cipher={2} {3} bit strength, Hash={4} {5} bit strength, Key Exchange={6} {7} bit strength). Unexpected exception in {0}. unknown Using the cached credential handle. The maximum number of service points was exceeded. Too many addresses to sort. The maximum number of addresses allowed are {0}. This method is not implemented by this class. This method is not supported by this class. Multiple buffers cannot be used with this method. The {0} parameter must represent a valid Uri (see inner exception). You must provide a request body if you set ContentLength>0 or SendChunked==true. Do this by calling [Begin]GetRequestStream before [Begin]GetResponse. The requirement for mutual authentication was not met by the remote server. TransferEncoding requires the SendChunked property to be set to true. There were not enough free threads in the ThreadPool to complete the operation. This request requires buffering data to succeed. 100-Continue may not be set using this property. Chunked encoding must be set via the SendChunked property. Chunked encoding upload is not supported on the HTTP/1.0 protocol. Content-Length or Chunked Encoding cannot be set for an operation that does not write data. Default credentials cannot be supplied for the {0} authentication scheme. A non-CLS Compliant Exception (i.e. an object that does not derive from System.Exception) was thrown. The URI scheme for the supplied IWebProxy has the illegal value '{0}'. Only 'http' is supported. This stream does not support seek operations. The operation is not allowed on non-connected sockets. The operation is not allowed on non-stream oriented sockets. The supplied string is not a valid HTTP token. Specified value does not contain 'IPermission' as its tag. Cannot send a content-body with this verb-type. Specified value does not contain a 'class' attribute. The stream does not support concurrent IO read or write operations. The value class attribute is not valid. Sum of offset and count cannot be greater than the length of the buffer. Current OS installation type is '{0}'. Argument must be a string instead of {0}. Can't queue counter initialization logic on a thread pool thread. System.Net performance counters will not be available. System.Net performance counter initialization started. System.Net performance counters initialization completed with errors. See System.Net trace file for more information. System.Net performance counters initialization completed successful. Performance counter category '{0}' doesn't exist. No System.Net performance counter values available. The value for '{0}' must be specified. The permission '{0}={1}' cannot be added. Add a separate Attribute statement. Cannot subset Regex. Only support if both patterns are identical. The argument value '{0}' is invalid for creating a SocketPermission object. The parameter value '{0}={1}' is invalid. The '{0}' element contains one or more invalid values. There are no permissions to check. Cannot cast target permission type. An exception occurred during a Ping request. This property is not implemented by this class. This property is not supported by this class. The '{0}' protocol is not supported by this class. '{0}' Client can only accept InterNetwork or InterNetworkV6 addresses. Multicast family is not the same as the family of the '{0}' Client. The ServicePointManager does not support proxies with the {0} scheme. The specified value is not a valid day of the week. The system proxy settings contain an invalid proxy server setting: '{0}'. The specified value is not a valid GMT time. The From or To parameter cannot be less than 0. A different range specifier has already been added to this request. The stream does not support writing. WebPermission demand failed for redirect URI. Cannot re-call BeginGetRequestStream/BeginGetResponse while a previous call is still in progress. This operation cannot be performed after the request has been submitted. The request was aborted: {0}. An error occurred on an automatic resubmission of the request. Cannot handle redirect from HTTP/HTTPS protocols to other dissimilar ones. Failed to revert the thread token after authenticating a Web Request. This operation cannot be performed after the response has been submitted. The requested security package is not supported. The requested security protocol is not supported. The '{0}' select mode is not supported by this class. The remote server returned an error: {0}. This property is not supported for protocols that do not use URI. Failed to impersonate a thread doing authentication of a Web Request. An asynchronous socket operation is already in progress using this SocketAsyncEventArgs instance. The operation is not allowed on a non-blocking Socket. Once the socket has been disconnected, you can only accept again asynchronously. BeginAccept must be called on a thread that won't exit until the operation has been completed. Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won't exit until the operation has been completed. All lists are either null or empty. The parameter {0} must not be of type DnsEndPoint. The number of specified IP addresses has to be greater than 0. The specified value is not a valid '{0}'. The specified value is not valid. The specified value for the socket information is invalid. This operation is only valid for IPv6 Sockets. You must call the Bind method before performing this operation. You must call the Listen method before performing this operation. The socket must not be bound or connected. You may not perform this operation after calling the Listen method. {0}: The socket must not be bound or connected. BeginConnect cannot be called while another asynchronous operation is in progress on the same Socket. The operation is not allowed on objects of type {0}. Use only objects of type {1}. The {0} list contains too many items; a maximum of {1} is allowed. Use the Blocking property to change the status of the Socket. The parameter {0} must contain one or more elements. Async context creation failed. The remote certificate is invalid according to the validation procedure. The security context has expired. The stream is corrupted due to an invalid SSL version number in the SSL protocol header. The decryption operation failed, see inner exception. The encryption operation failed, see inner exception. The handshake failed due to an unexpected packet format. The handshake failed, see inner exception. The handshake failed. The remote side has dropped the stream. {0} cannot be called when another {1} operation is pending. {0} can only be called once for each asynchronous operation. The server mode SSL must use a certificate with the associated private key. The Security Service Providers don't support extended protection. Please install the latest Security Service Providers update. Not listening. You must call the Start() method before calling this method. The TcpListener must not be listening before performing this operation. The operation has timed out. The SSL version is not supported. The size of {0} is too long. It cannot be longer than {1} characters. Too many automatic redirections were attempted. The specified value must be greater than 0. Cannot send packets to an arbitrary host while connected. Unknown Windows installation type '{0}'. The URI prefix is not recognized. A URI scheme name '{0}' already has a registered custom parser. Invalid URI: The Authority/Host could not be parsed. Invalid URI: The Authority/Host cannot end with a backslash character ('\\'). Invalid URI: The format of the URI could not be determined. Invalid URI: The hostname could not be parsed. Invalid URI: Invalid port specified. Invalid URI: The URI scheme is not valid. Invalid URI: There is an invalid sequence in the string. An invalid Unicode character by IDN standards was specified in the host. Invalid URI: The username:password construct is badly formed. A relative URI cannot be created because the 'uriString' parameter represents an absolute URI. Invalid URI: The URI is empty. The generic authority '{0}' is not a valid dns name. The value '{0}' passed for the UriKind parameter is invalid. Invalid URI: A Dos path must be rooted, for example, 'c:\\'. The URI parser instance passed into 'uriParser' parameter is already registered with the scheme name '{0}'. This operation is not supported for a relative URI. UriComponents.SerializationInfoString must not be combined with other UriComponents. A derived type '{0}' has reported an invalid value for the Uri port '{1}'. Invalid URI: The Uri scheme is too long. Invalid URI: The Uri string is too long. A derived type '{0}' is responsible for parsing this Uri instance. The base implementation must not be used. The specified value cannot be negative. An exception occurred during a WebClient request. The Content-Type header cannot be changed from its default value for this request. The specified value is not a valid base address. The Content-Type header cannot be set to a multipart type for this request. WebClient does not support concurrent I/O operations. Specified value has invalid Control characters. Specified value has invalid CRLF characters. Specified value has invalid HTTP Header characters. Specified value has invalid non-ASCII characters. Specified value does not have a ':' separator. CR must be followed by LF Invalid header name Response chunk format is invalid 'Content-Length' header value is invalid Header name is invalid Unexpected server response received The {0} operation was called on an incoming WebSocket request without required '{1}' header. The {0} operation was called on an incoming request that did not specify a '{1}: {2}' header or the {2} header not contain '{3}'. {2} specified by the client was '{4}'. The WebSocket client request requested '{0}' protocol(s), but server is only accepting '{1}' protocol(s). The {0} operation was called on an incoming request with WebSocket version '{1}', expected '{2}'. There is already one outstanding '{0}' call for this WebSocket instance. ReceiveAsync and SendAsync can be called simultaneously, but at most one outstanding operation for each of them is allowed at the same time. The WebSocket has already been started. The byte array must have a length of at least '{0}' bytes. The value of the '{0}' parameter ({1}) must be less than or equal to {2}. The argument must be a value greater than {0}. The message type '{0}' is not allowed for the '{1}' operation. Valid message types are: '{2}, {3}'. To close the WebSocket, use the '{4}' operation instead. The WebSocket client did not request any protocols, but server attempted to accept '{0}' protocol(s). The WebSocket client sent a blank '{0}' header; this is not allowed by the WebSocket protocol specification. The client should omit the header if the client is not negotiating any sub-protocols. The server returned status code '{0}' when status code '101' was expected. The remote party closed the WebSocket connection without completing the close handshake. An internal WebSocket error occurred. Please see the innerException, if present, for more details. The WebSocket request or response contained unsupported header(s). The buffer type '{0}' is invalid. Valid buffer types are: '{1}', '{2}', '{3}', '{4}', '{5}'. The WebSocket protocol '{0}' is invalid because it contains the invalid character '{1}'. The close status code '{0}' is reserved for system use only and cannot be specified when calling this method. The close status description '{0}' is too long. The UTF8-representation of the status description must not be longer than {1} bytes. Empty string is not a valid subprotocol value. Please use \"null\" to specify no value. The received message type '{2}' is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. The received message type is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. The WebSocket schemes must be registered with the HttpWebRequest class. The '{0}' header value '{1}' is invalid. The WebSocket is in an invalid state ('{0}') for this operation. Valid states are: '{1}' The '{0}' instance cannot be used for communication because it has been transitioned into the '{1}' state. The WebSocket instance cannot be used for communication because it has been transitioned into an invalid state. An error occurred when sending the WebSocket HTTP upgrade response during the {0} operation. The HRESULT returned is '{1}' Duplicate protocols are not allowed: '{0}'. A WebSocket operation was called on a request or response that is not a WebSocket. The WebSocket is not connected. The close status description '{0}' is invalid. When using close status code '{1}' the description must be null. The WebSocket is in an invalid state for this operation. The '{0}' method has already been called before on this instance. Use '{1}' instead to keep being able to receive data but close the output channel. Only Uris starting with 'ws://' or 'wss://' are supported. The WebSocket protocol is not supported on this platform. The WebSocket request or response operation was called with unsupported protocol(s). Unsupported WebSocket version. An exception caused the WebSocket to enter the Aborted state. Please see the InnerException, if present, for more details. The request cache-only policy does not allow a network request and the response is not found in cache Unable to connect to the remote server The connection was closed unexpectedly A connection that was expected to be kept alive was closed by the server The message length limit was exceeded The remote name could not be resolved A pipeline failure occurred The proxy name could not be resolved An unexpected error occurred on a receive The request was canceled The request could not be satisfied using a cache-only policy The IWebProxy object associated with the request did not allow the request to proceed Could not create SSL/TLS secure channel An unexpected error occurred on a send The server committed a protocol violation Status success The operation has timed out Could not establish trust relationship for the SSL/TLS secure channel The stream does not support reading. This property cannot be set after writing has started. Only HTTP/1.0 and HTTP/1.1 version requests are currently supported. Stream does not support reading. Stream does not support writing. Cannot access a closed Stream. Reading is not supported on this stream. The ServiceNameCollection must contain at least one service name. To construct a policy with PolicyEnforcement.Never, the single-parameter constructor must be used. A service name must not be null or empty. X509Certificate is not supported. Use X509Certificate2 instead. Seeking is not supported on this stream. Unable to send to all recipients. Already connected. Authentication failed. Authentication failed due to lack of credentials. The server returned an invalid response in the authentication handshake. Bad sequence of commands. Client does not have permission to submit mail to this server. Command not implemented. Command parameter not implemented. Syntax error, command unrecognized. Data stream is still open. This is a multi-part MIME message. @@SOAP Application Message The server returned an invalid response to the EHLO command. Exceeded storage allocation. A from address must be specified. Cannot get IIS pickup directory. Help message. Insufficient system storage. The address has an invalid host name: {0}. This operation cannot be performed while a message is being sent. Smtp server returned an invalid response. Error in processing. Mailbox unavailable. Mailbox name not allowed. Mailbox unavailable. The SMTP server requires a secure connection or the client was not authenticated. Only absolute directories are allowed for pickup directory. The client or server is only configured for E-mail addresses with ASCII local-parts: {0}. Not connected. Completed. Previous operation is still in progress. Client does not have permission to Send As this sender. SSL must not be enabled for pickup-directory delivery methods. Unable to send to a recipient. A recipient must be specified. Failure sending mail. Service closing transmission channel. Service not available, closing transmission channel. Service ready. Start mail input; end with <CRLF>.<CRLF>. Syntax error in parameters or arguments. System status, or system help reply. Transaction failed. User not local; please try a different path. User not local; will forward to specified path. AuthenticationType and ServicePrincipalName cannot be specified as null for server's SSPI Negotiation module. '{0}' is not a supported handle type. {0} failed with error {1}. The SMTP host was not specified. Writing is not supported on this stream. Cannot set null or blank methods on request. The parameter '{0}' cannot be an empty string. This collection holds response headers and cannot contain the specified request header. Header values cannot be longer than {0} characters. The IAsyncResult object was not returned from the corresponding asynchronous method on this class. {0} can only be called once for each asynchronous operation. Timeout can be only be set to 'System.Threading.Timeout.Infinite' or a value >= 0. This method is not implemented by this class. Cannot send a content-body with this verb-type. This property is not implemented by this class. Cannot re-call BeginGetRequestStream/BeginGetResponse while a previous call is still in progress. The request was aborted: The request was canceled. This operation cannot be performed after the request has been submitted. The remote server returned an error: ({0}) {1}. The URI prefix is not recognized. This property cannot be set after writing has started. This operation is not supported. Argument must be between {0} and {1}. Accepted connection from {0} to {1}. Connecting to a DnsEndPoint. Not logging data from file: {0}. Buffer and BufferList properties cannot both be non-null. The Buffer space specified by the Count property is insufficient for the AcceptAsync method. This operation cannot be performed on a completed asynchronous result object. The AddressFamily {0} is not valid for the {1} end point, use {2} instead. None of the discovered or specified addresses match the socket address family. The supplied EndPoint of AddressFamily {0} is not valid for this Socket, use {1} instead. The supplied {0} is an invalid size for the {1} end point. The socket handle is not valid. This protocol version is not supported. Cannot block a call on this socket while an earlier asynchronous call is in progress. The connection was closed The IAsyncResult object was not returned from the corresponding asynchronous method on this class. {0} can only be called once for each asynchronous operation. Unable to read data from the transport connection: {0}. Timeout can be only be set to 'System.Threading.Timeout.Infinite' or a value > 0. Unable to write data to the transport connection: {0}. Exception in {0}::{1} - {2}. Created connection from {0} to {1}. Multiple buffers cannot be used with this method. This stream does not support seek operations. The operation is not allowed on non-connected sockets. The operation is not allowed on non-stream oriented sockets. '{0}' Client can only accept InterNetwork or InterNetworkV6 addresses. Multicast family is not the same as the family of the '{0}' Client. The stream does not support writing. An asynchronous socket operation is already in progress using this SocketAsyncEventArgs instance. This platform does not support receiving data with Socket.AcceptAsync. Instead, make a separate call to Socket.ReceiveAsync. The operation is not allowed on a non-blocking Socket. This platform does not support connecting sockets to DNS endpoints via the instance Connect and ConnectAsync methods, due to the potential for a host name to map to multiple IP addresses and sockets becoming invalid for use after a failed connect attempt. Use the static ConnectAsync method, or provide to the instance methods the specific IPAddress desired. Sockets on this platform are invalid for use after a failed connection attempt. Once the socket has been disconnected, you can only accept again asynchronously. BeginAccept must be called on a thread that won't exit until the operation has been completed. Once the socket has been disconnected, you can only reconnect again asynchronously, and only to a different EndPoint. BeginConnect must be called on a thread that won't exit until the operation has been completed. This platform does not support packet information for dual-mode sockets. If packet information is not required, use Socket.Receive. If packet information is required set Socket.DualMode to false. All lists are either null or empty. The parameter {0} must not be of type DnsEndPoint. The number of specified IP addresses has to be greater than 0. The specified value is not a valid '{0}'. The specified value is not valid. You must call the Bind method before performing this operation. You must call the Listen method before performing this operation. The socket must not be bound or connected. You may not perform this operation after calling the Listen method. {0}: The socket must not be bound or connected. The operation is not allowed on objects of type {0}. Use only objects of type {1}. The {0} list contains too many items; a maximum of {1} is allowed. Use the Blocking property to change the status of the Socket. The parameter {0} must contain one or more elements. Not listening. You must call the Start() method before calling this method. The TcpListener must not be listening before performing this operation. Cannot send packets to an arbitrary host while connected. The specified value cannot be negative. The stream does not support reading. This collection holds response headers and cannot contain the specified request header. This collection holds request headers and cannot contain the specified response header. Specified value has invalid Control characters. Specified value has invalid CRLF characters. Specified value has invalid HTTP Header characters. Specified value has invalid non-ASCII characters. Exception in {0}::{1} - {2}. This operation is not supported for a relative URI. The {0} operation was called on an incoming WebSocket request without required '{1}' header. The {0} operation was called on an incoming request that did not specify a '{1}: {2}' header or the {2} header not contain '{3}'. {2} specified by the client was '{4}'. The WebSocket client request requested '{0}' protocol(s), but server is only accepting '{1}' protocol(s). The {0} operation was called on an incoming request with WebSocket version '{1}', expected '{2}'. There is already one outstanding '{0}' call for this WebSocket instance. ReceiveAsync and SendAsync can be called simultaneously, but at most one outstanding operation for each of them is allowed at the same time. The WebSocket has already been started. The byte array must have a length of at least '{0}' bytes. The value of the '{0}' parameter ({1}) must be less than or equal to {2}. The argument must be a value greater than {0}. The message type '{0}' is not allowed for the '{1}' operation. Valid message types are: '{2}, {3}'. To close the WebSocket, use the '{4}' operation instead. The WebSocket client did not request any protocols, but server attempted to accept '{0}' protocol(s). The WebSocket client sent a blank '{0}' header; this is not allowed by the WebSocket protocol specification. The client should omit the header if the client is not negotiating any sub-protocols. The server returned status code '{0}' when status code '101' was expected. The remote party closed the WebSocket connection without completing the close handshake. An internal WebSocket error occurred. Please see the innerException, if present, for more details. The WebSocket request or response contained unsupported header(s). The buffer type '{0}' is invalid. Valid buffer types are: '{1}', '{2}', '{3}', '{4}', '{5}'. The WebSocket protocol '{0}' is invalid because it contains the invalid character '{1}'. The close status code '{0}' is reserved for system use only and cannot be specified when calling this method. The close status description '{0}' is too long. The UTF8-representation of the status description must not be longer than {1} bytes. Empty string is not a valid subprotocol value. Please use \"null\" to specify no value. The received message type '{2}' is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. The received message type is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. The WebSocket schemes must be registered with the HttpWebRequest class. The '{0}' header value '{1}' is invalid. The WebSocket is in an invalid state ('{0}') for this operation. Valid states are: '{1}' The '{0}' instance cannot be used for communication because it has been transitioned into the '{1}' state. The WebSocket instance cannot be used for communication because it has been transitioned into an invalid state. An error occurred when sending the WebSocket HTTP upgrade response during the {0} operation. The HRESULT returned is '{1}' Duplicate protocols are not allowed: '{0}'. A WebSocket operation was called on a request or response that is not a WebSocket. The WebSocket is not connected. The close status description '{0}' is invalid. When using close status code '{1}' the description must be null. The WebSocket is in an invalid state for this operation. The '{0}' method has already been called before on this instance. Use '{1}' instead to keep being able to receive data but close the output channel. Only Uris starting with 'ws://' or 'wss://' are supported. The WebSocket protocol is not supported on this platform. The WebSocket request or response operation was called with unsupported protocol(s). Unsupported WebSocket version. An exception caused the WebSocket to enter the Aborted state. Please see the InnerException, if present, for more details. Unable to connect to the remote server The remote party closed the WebSocket connection without completing the close handshake. An internal WebSocket error occurred. Please see the innerException, if present, for more details. The WebSocket request or response contained unsupported header(s). The received message type is invalid after calling {0}. {0} should only be used if no more data is expected from the remote endpoint. Use '{1}' instead to keep being able to receive data but close the output channel. The WebSocket is in an invalid state ('{0}') for this operation. Valid states are: '{1}' The WebSocket instance cannot be used for communication because it has been transitioned into an invalid state. A WebSocket operation was called on a request or response that is not a WebSocket. The WebSocket request or response operation was called with unsupported protocol(s). Unsupported WebSocket version. An exception caused the WebSocket to enter the Aborted state. Please see the InnerException, if present, for more details. Index was out of bounds: Number of elements in source vector is greater than the destination array Only one-dimensional arrays are supported The method was called with a null array argument. length must be less than Specified type is not supported Vector<T>.Count cannot be called via reflection when intrinsics are enabled. The specified threshold for creating dictionary is out of range. Non-negative number required. An item with the same key has already been added. Target array type is not compatible with the type of items in the collection. The specified item does not exist in this KeyedCollection. Destination array is not long enough to copy all the items in the collection. Check array index and length. The lower bound of target array must be zero. Only single dimensional arrays are supported for the requested action. Index cannot be negative. Constructor only supports either a Reset, Add, or Remove action. Collection is read-only. Cannot change ObservableCollection during a CollectionChanged event. Reset action must be initialized with index -1. Reset action must be initialized with no changed items. Constructor supports only the '{0}' action. Array length '{0}' provided by the get-only collection of type '{1}' is less than the number of array elements found in the input stream. Consider increasing the length of the array. Array length '{0}' provided by Size attribute is not equal to the number of array elements '{1}' from namespace '{2}' found. An internal error has occurred. '{0}[]' is not supported when generating code for serialization. Assembly '{0}' is not found. Type '{0}' cannot inherit from a type that is not marked with DataContractAttribute or SerializableAttribute. Consider marking the base type '{1}' with DataContractAttribute or SerializableAttribute, or removing them from the derived type. XML '{2}' '{3}:{4}' does not contain expected attribute '{0}:{1}'. The deserializer has no knowledge of which type to deserialize. Check that the type being serialized has the same contract as the type being deserialized. Serialization Callback '{1}' in type '{0}' must return void. Serialization Callback '{1}' in type '{0}' must have a single parameter of type '{2}'. Virtual Method '{0}' of type '{1}' cannot be marked with '{2}' attribute. Cannot deserialize since root element references unrecognized object with id '{0}'. Cannot load member type '{0}'. Object graph for type '{0}' contains cycles and cannot be serialized if references are not tracked. Consider using the DataContractAttribute with the IsReference property set to true. An internal error has occurred. Data can only be stored into ArgBuilder or LocalBuilder. Got: {0}. An internal error has occurred. Char is not a valid schema primitive and should be treated as int in DataContract. The deserializer cannot load the type to deserialize because type '{1}' could not be found in assembly '{0}'. Check that the type being serialized has the same contract as the type being deserialized and the same assembly is used. '{0}' is a collection type and cannot be serialized when assigned to an interface type that does not implement IEnumerable ('{1}'.) Collection type '{0}' does not have a valid Add method. Collection type '{0}' does not have a valid GetEnumerator method. Collection type '{0}' must have a non-null item type. {0} is a built-in type and cannot be a collection. {0} has DataContractAttribute attribute. {0} does not have a valid Add method with parameter of type '{1}'. {0} does not have a default constructor. {0} has multiple definitions of interface '{1}'. {0} does not implement IEnumerable interface. An internal error has occurred. DataContract cache overflow. ContractNamespaceAttribute attribute maps CLR namespace '{2}' to multiple data contract namespaces '{0}' and '{1}'. You can map a CLR namespace to only one data contract namespace. DataContract namespace '{0}' is not a valid URI. DataContract namespace '{0}' cannot be specified since it is reserved. Member '{0}.{1}' has DataMemberAttribute attribute. Use EnumMemberAttribute attribute instead. Element '{2}:{3}' contains data of the '{0}:{1}' data contract. The deserializer has no knowledge of any type that maps to this contract. Add the type corresponding to '{1}' to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to DataContractSerializer. Type '{0}' with data contract name '{1}:{2}' is not expected. Add any types not known statically to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding them to the list of known types passed to DataContractSerializer. Element '{2}:{3}' contains data from a type that maps to the name '{0}:{1}'. The deserializer has no knowledge of any type that maps to this name. Consider changing the implementation of the ResolveName method on your DataContractResolver to return a non-null value for name '{1}' and namespace '{0}'. Deserialized object with reference id '{0}' not found in stream. Type '{0}' cannot be added to list of known types since another type '{1}' with the same data contract name '{2}:{3}' is already present. Type '{2}' contains two members '{0}' 'and '{1}' with the same name '{3}'. Multiple members with the same name in one type are not supported. Consider changing one of the member names using EnumMemberAttribute attribute. The collection data contract type '{0}' specifies the same value '{1}' for both the KeyName and the ValueName properties. This is not allowed. Consider changing either the KeyName or the ValueName property. Invalid Callback. Method '{3}' in type '{2}' has both '{0}' and '{1}'. Invalid attribute. Both '{0}' and '{1}' in type '{2}' have '{3}'. Type '{2}' contains two members '{0}' 'and '{1}' with the same data member name '{3}'. Multiple members with the same name in one type are not supported. Consider changing one of the member names using DataMemberAttribute attribute. {0}. Encountered '{1}' with name '{2}', namespace '{3}'. Enum type '{0}' cannot have the IsReference setting of '{1}'. Either change the setting to '{2}', or remove it completely. DataContractJsonSerializer does not support data members of type '{0}'. Consider using int, System.Object, or a concrete enum definition instead. There was an error deserializing the object {0}. {1} Error in line {0} position {1}. There was an error checking start element of object {0}. {1} There was an error serializing the object {0}. {1} of type {0} There was an error writing end element of object {0}. {1} There was an error writing start element of object {0}. {1} Maximum number of items that can be serialized or deserialized in an object graph is '{0}'. Expecting element '{1}' from namespace '{0}'. Expecting state '{0}' when ReadObject is called. Expecting End'{0}'. Expecting state '{0}'. Object graph of type '{0}' with Id '{2}' contains a reference to itself. The object has been replaced with a new object of type '{1}' either because it implements IObjectReference or because it is surrogated. The serializer does not support fixing up the nested reference to the new object and cannot deserialize this object. Consider changing the object to remove the nested self-reference. A user callback threw an exception. Check the exception stack and inner exception to determine the callback that failed. The data contract name '{0}' for type '{1}' has a curly brace '{{' that is not matched with a closing curly brace. Curly braces have special meaning in data contract names - they are used to customize the naming of data contracts for generic types. In the data contract name for type '{1}', there are curly braces with '{0}' inside, which is an invalid value. Curly braces have special meaning in data contract names - they are used to customize the naming of data contracts for generic types. Based on the number of generic parameters this type has, the contents of the curly braces must either be a number between 0 and '{2}' to insert the name of the generic parameter at that index or the '#' symbol to insert a digest of the generic parameter namespaces. Collection interface type '{0}' is being used as a get-only property and does not have an Add method. Consider adding a setter to the property or using a collection data contract that does have an Add method - for example IList or ICollection<T>. The IsReference setting for type '{0}' is '{1}', but the same setting for its parent class '{2}' is '{3}'. Derived types must have the same value for IsReference as the base type. Change the setting on type '{0}' to '{3}', or on type '{2}' to '{1}', or do not set IsReference explicitly. Property '{1}' in type '{0}' cannot be serialized because serialization of indexed properties is not supported. Encountered invalid character '{0}'. Type '{0}' cannot have CollectionDataContractAttribute attribute ItemName set to null or empty string. Type '{0}' cannot have CollectionDataContractAttribute attribute KeyName set to null or empty string. The collection data contract type '{0}' specifies '{1}' for the KeyName property. This is not allowed since the type is not IDictionary. Remove the setting for the KeyName property. Type '{0}' cannot have CollectionDataContractAttribute attribute Name set to null or empty string. Type '{0}' cannot have CollectionDataContractAttribute attribute Namespace set to null. Type '{0}' cannot have CollectionDataContractAttribute attribute ValueName set to null or empty string. The collection data contract type '{0}' specifies '{1}' for the ValueName property. This is not allowed since the type is not IDictionary. Remove the setting for the ValueName property. Type '{0}' with CollectionDataContractAttribute attribute is an invalid collection type since it Type '{0}' is an invalid collection type since it Type '{0}' cannot have DataContractAttribute attribute Name set to null or empty string. Type '{0}' cannot have DataContractAttribute attribute Namespace set to null. Member '{0}' in type '{1}' cannot have DataMemberAttribute attribute Name set to null or empty string. '{0}' is an invalid data node when deserializing extension data. '{0}' in type '{1}' cannot have EnumMemberAttribute attribute Value set to null or empty string. Invalid enum value '{0}' cannot be deserialized into type '{1}'. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute. Enum value '{0}' is invalid for type '{1}' and cannot be serialized. Ensure that the necessary enum values are present and are marked with EnumMemberAttribute attribute if the type has DataContractAttribute attribute. Type '{0}' cannot have MethodName on XmlSchemaProviderAttribute attribute set to null or empty string. CLR namespace '{0}' cannot have ContractNamespace set to null. The empty string is not a valid local name. Member '{0}.{1}' cannot be serialized since it is neither a field nor a property, and therefore cannot be marked with the DataMemberAttribute attribute. Remove the DataMemberAttribute attribute from the '{1}' member. Method '{0}.{1}()' returns a non-null value. The return value must be null since IsAny Type '{0}' is not a valid serializable type. Method '{0}.{1}()' returns '{2}'. The return type must be compatible with '{3}'. Invalid Size '{0}'. Must be non-negative integer. An internal error has occurred. ExtensionDataReader is in an invalid state. XML data contract Name for type '{0}' cannot be set to null or empty string. The XML encountered when deserializing extension data is invalid. Invalid Id '{0}'. Must not be null or empty. Invalid Ref '{0}'. Must not be null or empty. A null value cannot be serialized at the top level for IXmlSerializable root type '{0}' since its IsAny setting is 'true'. This type must write all its contents including the root element. Verify that the IXmlSerializable implementation is correct. An object of type '{0}' cannot be serialized at the top level for IXmlSerializable root type '{1}' since its IsAny setting is 'true'. This type must write all its contents including the root element. Verify that the IXmlSerializable implementation is correct. Type '{0}' cannot specify an XmlRootAttribute attribute because its IsAny setting is 'true'. This type must write all its contents including the root element. Verify that the IXmlSerializable implementation is correct. An internal error has occurred. '{0}' is not assignable from '{1}' - error generating code for serialization. '{0}.{1}' has the IsRequired setting of '{2}. However, '{0}' has the IsReference setting of '{2}', because either it is set explicitly, or it is derived from a base class. Set IsRequired on '{0}.{1}' to false, or disable IsReference on '{0}'. Type '{0}' cannot be IXmlSerializable and have CollectionDataContractAttribute attribute. Type '{0}' cannot be IXmlSerializable and have DataContractAttribute attribute. This method cannot be called from IXmlSerializable implementations. IXmlSerializable.WriteXml method of type '{0}' did not close all open tags. Verify that the IXmlSerializable implementation is correct. IXmlSerializable Type '{0}' must have default constructor. IXmlSerializable.WriteXml method of type '{0}' attempted to close too many tags. Verify that the IXmlSerializable implementation is correct. Cannot write attribute with local name '{0}' multiple times. WriteStartElement must be called at least once before WriteStartAttribute may be called. Cannot write a CLR value that maps to number, array, object, true, false or null in JSON after a string value has been written. Attempted to write text after writing attribute type='{0}'. Text may be written only after the attributes type='number', type='boolean', or type='string'. A circular reference has been detected when serializing an object of type {0} to JSON. Circular references are not supported in the JSON format. DateTime values that are greater than DateTime.MaxValue or smaller than DateTime.MinValue when converted to UTC cannot be serialized to JSON. The data contract type '{0}' cannot be deserialized because the data member '{1}' was found more than once in the input. The data contract type '{0}' is not serializable with DataContractJsonSerializer because the data member '{1}' is duplicated in its type hierarchy. Encoding not supported in JSON. UTF-8, Unicode, and BigEndianUnicode are the only supported encodings. Encountered unexpected character '{0}'. No corresponding start element is open. The expected encoding '{0}' does not match the actual encoding '{1}'. Invalid byte encoding. Attempted to write an attribute '{0}'='{1}' after writing the attribute with local name '{2}'. The attribute with local name '{2}' is only valid with an attribute '{0}'='{3}'. DateTime content '{0}' does not start with '{1}' and end with '{2}' as required for JSON. Characters with hexadecimal values 0xFFFE and 0xFFFF are not valid. Encountered unexpected element local name '{0}' for item in collection. '{1}' is the only valid local name for elements in a collection. The empty string is not a valid local name in JSON. Cannot write content while an attribute is being written. Encountered invalid root element name '{0}'. '{1}' is the only allowed root element name. WriteStartElement can be called at only the start of a document or immediately after calling WriteEndElement. '{0}' cannot be called while WriteState is '{1}'. This XmlDictionaryWriter implementation does not support the '{0}' method. This XmlDictionaryWriter implementation does not support the writing of multiple root elements. You must write an attribute '{0}'='{1}' after writing the attribute with local name '{2}'. To write attribute values with this XmlDictionaryWriter implementation, you must write either string or char[] values. Encountered unexpected namespace '{0}'. The namespace must be empty. Nested arrays are not supported. WriteStartElement cannot be called immediately after WriteStartElement without writing the 'type'='array' or 'type='object' attribute. There is no open attribute. The specified offset exceeds the buffer size ({0} bytes). The data contract type '{0}' cannot be deserialized because the required data member '{1}' was not found. Unexpected character '{0}'. '{1}' can write only white space characters. Cannot call {0} while an attribute is being written. Encountered unexpected prefix '{0}'. The prefix must be null or empty. The data contract type '{0}' cannot be deserialized because the required data members '{1}' were not found. Attempted to write an attribute with local name '{0}' after writing the attribute '{1}'='{2}'. An attribute with local name '{0}' may be written only after writing the attribute '{1}'='{3}'. The specified size exceeds the remaining buffer space ('{0}' bytes). DataContractJsonSerializer does not support objects of type '{0}'. Encountered unexpected attribute local name '{0}'. 'type' and '__type' are the only allowed local names for attributes. 'type' can be used to influence how data is written; its valid values are 'object', 'string', 'number', 'null', 'boolean', and 'array'. '__type' can be used to provide type hint information to the writer. The attribute 'type' must have one of the following strings as its values: 'string', 'number', 'array', 'object', 'null', or 'boolean'. Encountered unexpected value '{0}' Unexpected end of file. The type '{0}' cannot be serialized to JSON because its IsReference setting is '{1}'. The JSON format does not support references because there is no standardized format for representing references. To enable serialization, disable the IsReference setting on the type or an appropriate parent class of the type. To write JSON arrays, use XML writer methods to write the attribute type='array' followed by methods like WriteStartElement (with the local name 'item'), WriteAttributeString, and WriteEndElement to write the JSON array items. The writer is closed. XML declaration can only be written at the beginning of the document. Processing instructions (other than the XML declaration) are not supported. The dictionary of type '{0}' cannot be deserialized as a simple dictionary because its key type '{1}' does not have a public static Parse method. Method name specified by KnownTypeAttribute attribute on type '{0}' cannot be the empty string. Method specified by KnownTypeAttribute attribute on type '{0}' returned null. KnownTypeAttribute attribute on type '{0}' contains no data. Type '{0}': If a KnownTypeAttribute attribute specifies a method it must be the only KnownTypeAttribute attribute on that type. KnownTypeAttribute attribute on type '{0}' specifies a method named '{1}' to provide known types. The return type of this method is invalid because it is not assignable to IEnumerable<Type>. Ensure that the method exists and has a valid signature. KnownTypeAttribute attribute on type '{1}' specifies a method named '{0}' to provide known types. Static method '{0}()' was not found on this type. Ensure that the method exists and is marked as static. Method specified by KnownTypeAttribute attribute on type '{0}' does not expose valid types. The maximum array length ({0}) has been exceeded while reading XML data for array of type '{1}'. Type '{0}' does not have a static method '{1}' that takes a parameter of type 'System.Xml.Schema.XmlSchemaSet' as specified by the XmlSchemaProviderAttribute attribute. Invalid XML encountered. The same Id value '{0}' is defined more than once. Multiple objects cannot be deserialized using the same Id. An internal error has occurred. No conversion is possible to '{0}' - error generating code for serialization. No get method for property '{1}' in type '{0}'. The Type '{0}' must have a parameterless constructor. {0}.{1}' is not marked with OptionalFieldAttribute, thus indicating that it must be serialized. However, '{0}' derives from a class marked with DataContractAttribute and an IsReference setting of '{2}'. It is not possible to have required data members on IsReference classes. Either decorate '{0}.{1}' with OptionalFieldAttribute, or disable the IsReference setting on the appropriate parent class. No set method for property '{1}' in type '{0}'. One of the known types provided to the serializer via '{0}' argument was invalid because it was null. All known types specified must be non-null values. The get-only collection of type '{0}' returned a null value. The input stream contains collection items which cannot be added if the instance is null. Consider initializing the collection either in the constructor of the object or in the getter. Invalid escape code encountered in a JSON string. '{0}' is not a valid JSON primitive. This error can also occur when extraneous data is present after the JSON data. JSON array ended with a trailing comma. Invalid member name encountered in a JSON object. An internal error has occurred. JSON string not properly quoted. Unexpected character encountered in JSON. Expected '{1}', got '{0}'. Unterminated JSON string encountered. JSON strings must start with a single or double quote character and end with the same character. An internal error has occurred. JSON dictionary type {0} not supported. An internal error has occurred. Object table overflow. This could be caused by serializing or deserializing extremely large object graphs. The specified offset exceeds the buffer size ({0} bytes). Property 'Order' in DataMemberAttribute attribute cannot be a negative number. Invalid number of parameters to call method '{0}'. Expected '{1}' parameters, but '{2}' were provided. The collection data contract type '{0}' cannot be deserialized because the method '{1}' is not public. Making the method public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The collection data contract type '{0}' cannot be deserialized because it does not have a public parameterless constructor. Adding a public parameterless constructor will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The collection data contract type '{0}' cannot be deserialized because it does not have a public parameterless constructor. Adding a public parameterless constructor will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be serialized because the member '{1}' is not public. Making the member public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be deserialized because the member '{1}' is not public. Making the member public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be serialized because the member '{1}' is not public. Making the member public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be deserialized because the member '{1}' is not public. Making the member public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be deserialized because the OnDeserialized method '{1}' is not public. Making the method public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be deserialized because the OnDeserializing method '{1}' is not public. Making the method public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be serialized because the OnSerialized method '{1}' is not public. Making the method public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be serialized because the OnSerializing method '{1}' is not public. Making the method public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be serialized because the property '{1}' does not have a public getter. Adding a public getter will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' cannot be deserialized because the property '{1}' does not have a public setter. Adding a public setter will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The data contract type '{0}' is not serializable because it is not public. Making the type public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The IXmlSerializable type '{0}' is not serializable in partial trust because it is not public. Adding a public parameterless constructor will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The IXmlSerializable type '{0}' cannot be deserialized because it does not have a public parameterless constructor. Adding a public parameterless constructor will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. The type '{0}' cannot be deserialized because it does not have a public parameterless constructor. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications. Cannot copy XmlDictionaryReaderQuotas. Target is readonly. The '{0}' quota is readonly. Quota must be a positive value. Type '{0}' is a recursive collection data contract which is not supported. Consider modifying the definition of collection '{0}' to remove references to itself. Member {0} in type {1} cannot be serialized. This exception is usually caused by trying to use a null value where a null value is not allowed. The '{0}' member is set to its default value (usually null or zero). The member's EmitDefault setting is 'false', indicating that the member should not be serialized. However, the member's IsRequired setting is 'true', indicating that it must be serialized. This conflict cannot be resolved. Consider setting '{0}' to a non-default value. Alternatively, you can change the EmitDefaultValue property on the DataMemberAttribute attribute to true, or changing the IsRequired property to false. An object of type '{0}' which derives from DataContractResolver returned false from its TryResolveType method when attempting to resolve the name for an object of type '{1}', indicating that the resolution failed. Change the TryResolveType implementation to return true. An object of type '{0}' which derives from DataContractResolver returned a null typeName or typeNamespace but not both from its TryResolveType method when attempting to resolve the name for an object of type '{1}'. Change the TryResolveType implementation to return non-null values, or to return null values for both typeName and typeNamespace in order to serialize as the declared type. Type '{0}' cannot be serialized, serialization code for the type is missing. Consult the SDK documentation for adding it as a root serialization type. The specified size exceeds the remaining buffer space ({0} bytes). Multi-dimensional arrays are not supported. Using surrogates with get-only collection properties is not supported. Consider removing the surrogate associated with '{0}'. Type '{0}' has more than one CollectionDataContractAttribute attribute. Type '{0}' has more than one DataContractAttribute attribute. Member '{0}.{1}' has more than one DataMemberAttribute attribute. Member '{0}.{1}' has more than one EnumMemberAttribute attribute. Member '{0}.{1}' has more than one IgnoreDataMemberAttribute attribute. Type '{0}' cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members you want serialized with the DataMemberAttribute attribute. Alternatively, you can ensure that the type is public and has a parameterless constructor - all public members of the type will then be serialized, and no attributes will be required. An internal error has occurred. Unexpected contract type '{0}' for type '{1}' encountered. '{0}' '{1}' from namespace '{2}' is not expected. Expecting element '{3}'. Unexpected end of file. Unrecognized constant type '{0}'. Unknown data contract: '{0}'. Type '{0}' is not a valid XML type. The value of this argument must fall within the range {0} to {1}. The value of this argument must be non-negative. ValueType '{0}' cannot be null. Data contract '{0}' from namespace '{1}' is a value type and cannot have base contract '{2}' from namespace '{3}'. ValueType '{0}' cannot have id. Value type '{0}' cannot have the IsReference setting of '{1}'. Either change the setting to '{2}', or remove it completely. ValueType '{0}' cannot have ref to another object. Array too small. Array too small. Length of available data must be at least {0}. Array too small. Must be able to hold at least {0}. An asynchronous operation is already in progress. Unrecognized Byte Order Mark. Base64 encoded data expected. Found {0}. CData elements not valid at top level of an XML document. ']]>' not valid in text node content. The value '{0}' cannot be represented with the type '{1}'. An XML declaration with an encoding is required for all non-UTF8 documents. An XML declaration is required for all non-UTF8 documents. Version not found in XML declaration. No characters can appear before the XML declaration. XmlDictionaryString IDs must be in the range from {0} to {1}. XmlDictionaryString ID {0} not defined in the XmlBinaryReaderSession. XmlDictionaryString ID {0} not defined in the static dictionary. Duplicate attribute found. Both '{0}' and '{1}' are from the namespace '{2}'. Only Element nodes have attributes. The empty namespace requires a null or empty prefix. The encoding in the declaration '{0}' does not match the encoding of the document '{1}'. XML encoding not supported. End element '{0}' from namespace '{1}' expected. Found {2}. No corresponding start element is open. The expected encoding '{0}' does not match the actual encoding '{1}'. Element {0} from namespace {1} cannot have child contents to be deserialized as an object. Please use XElement to deserialize this pattern of XML. cdata '{0}' comment '{0}' element '{0}' from namespace '{1}' end element '{0}' from namespace '{1}' end of file node {0} text '{0}' Non-empty start element expected. Found {0}. Non-empty start element '{0}' from namespace '{1}' expected. Found {2}. Non-empty start element '{0}' expected. Found {1}. ID already defined. Text cannot be written outside the root element. Base64 sequence length ({0}) not valid. Must be a multiple of 4. The characters '{0}' at offset {1} are not a valid Base64 sequence. BinHex sequence length ({0}) not valid. Must be a multiple of 2. The characters '{0}' at offset {1} are not a valid BinHex sequence. Invalid byte encoding. Character reference not valid. XML comments cannot contain '--' or end with '-'. The value '{0}' cannot be parsed as the type '{1}'. The value cannot be parsed as the type '{0}'. XML declaration can only be written at the beginning of the document. Cannot call '{0}' while Depth is '{1}'. XML encoding must be 'UTF-8'. Characters with hexadecimal values 0xFFFE and 0xFFFF are not valid. The input source is not correctly formatted. High surrogate char '0x{0}' not valid. High surrogate chars range from 0xD800 to 0xDBFF. ID must be > Low surrogate char '0x{0}' not valid. Low surrogate chars range from 0xDC00 to 0xDFFF. The reader cannot be advanced. A prefix cannot be defined while WriteState is '{0}'. Expected XML qualified name. Found '{0}'. The data at the root level is invalid. 'standalone' value in declaration must be 'yes' or 'no'. Surrogate char '0x{0}' not valid. Surrogate chars range from 0x10000 to 0x10FFFF. UniqueId cannot be zero length. '{0}' contains invalid UTF8 bytes. XML version must be '1.0'. '{0}' cannot be called while WriteState is '{1}'. The byte 0x{0} is not valid at this location. '{0}' is not a valid xml:space value. Valid values are 'default' and 'preserve'. The specified key already exists in the dictionary. Line {0}, position {1}. Malformed XML declaration. The maximum array length quota ({0}) has been exceeded while reading XML data. This quota may be increased by changing the MaxArrayLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader. The 'maximum bytes per Read operation' quota ({0}) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader. The maximum read depth ({0}) has been exceeded because XML data being read has more levels of nesting than is allowed by the quota. This quota may be increased by changing the MaxDepth property on the XmlDictionaryReaderQuotas object used when creating the XML reader. The maximum nametable character count quota ({0}) has been exceeded while reading XML data. The nametable is a data structure used to store strings encountered during XML processing - long XML documents with non-repeating element names, attribute names and attribute values may trigger this quota. This quota may be increased by changing the MaxNameTableCharCount property on the XmlDictionaryReaderQuotas object used when creating the XML reader. The maximum string content length quota ({0}) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader. This XmlWriter implementation does not support the '{0}' method. The surrogate pair is invalid. Missing a low surrogate character. There are multiple root elements. The namespace '{0}' is not defined. Nested arrays are not supported. The document does not have a root element. '{0}' is an XML type and cannot be serialized when assigned to an interface type that does not implement IXmlSerializable ('{1}'.) Only one root element is permitted per document. Only a single typed value may be written inside an attribute or content. Only white space characters can be written with this method. The prefix '{0}' is bound to the namespace '{1}' and cannot be changed to '{2}'. Processing instructions (other than the XML declaration) and DTDs are not supported. Prefixes beginning with 'xml' (regardless of casing) are reserved for use by XML. Whitespace must appear between attributes. The namespace '{1}' can only be bound to the prefix '{0}'. The prefix '{0}' can only be bound to the namespace '{1}'. Start element expected. Found {0}. Start element '{0}' from namespace '{1}' expected. Found {2}. Start element '{0}' expected. Found {1}. Start element '{0}' does not match end element '{1}'. The token '{0}' was expected but found '{1}'. The prefix '{0}' is not defined. No matching start tag for end element. Unexpected end of file. Following elements are not closed: {0}. The XmlWriter is closed. WriteState '{0}' not valid. Caller must write start element before serializing in contentOnly mode. A binding instance has already been associated to listen URI '{0}'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config. The operation to establish the WebSocket connection timed out. To increase this time limit, use the OpenTimeout property on the service endpoint's binding. Could not perform an AccessCheck (error=0x{0:X}). Access is denied. A Channel/Service Endpoint is null. A Channel/Service endpoint's Binding is null. A Channel/Service endpoint's Contract is null. A Channel/Service endpoint's Contract's name is null or empty. A Channel/Service endpoint's Contract's namespace is null. The remote endpoint requested an address for acknowledgements that is not the same as the address for application messages. The channel could not be opened because this is not supported. Ensure the endpoint address used to create the channel is identical to the one the remote endpoint was set up with. The address for acknowledgements must be the same as the address for application messages. Verify that your endpoint is configured to use the same URI for these two addresses. The set of actions cannot be empty. ActivityBoundary Executing user callback. Close '{0}'. Close ChannelFactory. Contract type: '{0}'. Close ClientBase. Contract type: '{0}'. Close ServiceHost '{0}'. Construct ChannelFactory. Contract type: '{0}'. Construct ServiceHost '{0}'. Execute Async: Begin: '{0}.{1}'; End: '{2}.{3}'. Execute '{0}.{1}'. Listen at '{0}'. Open '{0}'. Open ChannelFactory. Contract type: '{0}'. Open ClientBase. Contract type: '{0}'. Open ServiceHost '{0}'. Process action '{0}'. Processing message {0}. Reading data from connection on '{0}'. Receiving data at via '{0}'. Receive bytes on connection '{0}'. Close Security Session. Renew Secure Session. Set up Secure Session. Shared listener connection: '{0}'. Socket connection: '{0}'. 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. Addressing Version '{0}' does not support adding WS-Addressing headers. Addressing Version '{0}' is not supported. The required address keyword was not specified. MTAWorkerThread exception Multiple link-local only interfaces detected. Please specifiy the interface you require by using the ListenIpAddress attribute in the PeerTransportBindingElement The service does not allow you to log on anonymously. The configured application was not found. (The Application ID was {0}.) The argument must be a non-empty string. value must be >= {0} and <= {1}. System error. The {0}:{1} assertion is not supported. AsymmetricSecurityBindingElement cannot build a channel or listener factory. The InitiatorTokenParameters property is required but not set. Binding element configuration: {0} AsymmetricSecurityBindingElement cannot build a channel or listener factory. The RecipientTokenParameters property is required but not set. Binding element configuration: {0} An AsyncCallback threw an exception. Async End called on wrong channel. Async End called with an IAsyncResult from a different Begin method. The request message must be protected. This is required by an operation of the contract ('{0}','{1}'). The protection must be provided by the binding ('{2}','{3}'). The response message must be protected. This is required by an operation of the contract ('{0}', '{1}'). The protection must be provided by the binding ('{2}', '{3}'). At least one fault reason must be specified. Only one primary signature is allowed in a security header. At most one reference list is supported with default policy check. At most one signature is supported with default policy check. The Atom10 specification requires '{0}' to have one of these values: \"text\", \"html\", \"xhtml\", however this value is '{1}' in the document being deserialized. Attempted to get contract type for {0}, but that type is not a ServiceContract, nor does it inherit a ServiceContract. The initial request context was already specified. Can not create two for same message. The authenticate method in the ServiceAuthenticationManager returned null. If you do not want to return any authorization policies in the collection then return an empty ReadOnlyCollection instead. The caller was not authenticated by the service. The authentication schemes cannot be inherited from the host for binding '{0}'. No AuthenticationScheme was specified on the ServiceHost or in the virtual application in IIS. This may be resolved by enabling at least one authentication scheme for this virtual application in IIS, through the ServiceHost.Authentication.AuthenticationSchemes property or in the configuration at the <serviceAuthenticationManager> element. The authentication schemes configured on the host ('{0}') do not allow those configured on the binding '{1}' ('{2}'). Please ensure that the SecurityMode is set to Transport or TransportCredentialOnly. Additionally, this may be resolved by changing the authentication schemes for this application through the IIS management tool, through the ServiceHost.Authentication.AuthenticationSchemes property, in the application configuration file at the <serviceAuthenticationManager> element, by updating the ClientCredentialType property on the binding, or by adjusting the AuthenticationScheme property on the HttpTransportBindingElement. The RequestSecurityTokenResponseCollection does not contain an authenticator. Authentication failed. The CloseTarget specified '{0}' does not identify the security token that signed the message. The security context token is expired or is not valid. The message was not processed. The message could not be processed. This is most likely because the action '{0}' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding. Invalid data buffer. The Dispatch ID '{0}' could not be found or is invalid. Invalid format for encrypted body. The EncryptedData or EncryptedKey is in an invalid state for this operation. The client token at least needs to have the SecurityImpersonationLevel of at least Impersonation for Out of process Webhost activations. Bad Interface Registration Incorrect Interface version in registry The issued token is of unexpected type '{0}'. Expected token type '{1}'. Invalid key encryption algorithm {0}. Badly terminated value {0}. The number of parameters in the request did not match the number supported by the method. Ensure that the correct number of parameters are specified. There is no endorsing session token that matches the specified RenewTarget '{0}'. Security negotiation failure because an incorrect Context attribute specified in RequestSecurityToken/RequestSecurityTokenResponse from the other party. A base address cannot contain a Uri fragment. A base address cannot contain a Uri query string. A base address cannot contain a Uri user info section. 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'. Only an absolute Uri can be used as a base address. BasicHttpContextBinding {0}:{1} requires that AllowCookies property is set to true. Supporting SecurityToken cannot be written without encryption. A basic token is not expected in the security header in this context. Bearer Key Type is not supported with WSFederationHttpBinding. Please use WS2007FederationHttpBinding. A Proof Token was found in the response that was returned by the Security Token Service for a Bearer Key Type token request. Note that Proof Tokens should not be generated when a Bearer Key Type request is made. Service behavior {0} requires that the binding associated with endpoint {1} listening on {2} supports the context protocol, because the contract associated with this endpoint may require a session. Currently configured binding for this endpoint does not support the context protocol. Please modify the binding to add support for the context protocol or modify the SessionMode on the contract to NotAllowed. The binary encoder session is not valid. There was an error decoding a previous message. The binary encoder session information is not properly formed. The binary encoder session information exceeded the maximum size quota ({0}). To increase this quota, use the MaxSessionSize property on the BinaryMessageEncodingBindingElement. The binding ('{0}','{1}') for contract ('{2}','{3}') is configured with SecureConversation, but the authentication mode is not able to provide the request/reply-based integrity and confidentiality required for the negotiation. The contract operation '{0}' requires Windows identity for automatic impersonation. A Windows identity that represents the caller is not provided by binding ('{1}','{2}') for contract ('{3}','{4}'. 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. Contract does not allow Session, but Binding '{0}' does not support Datagram or is not configured properly to support it. Contract requires Duplex, but Binding '{0}' doesn't support it or isn't configured properly to support it. Contract requires OneWay, but Binding '{0}' doesn't support it or isn't configured properly to support it. Contract requires Request/Reply, but Binding '{0}' doesn't support it or isn't configured properly to support it. Contract requires Session, but Binding '{0}' doesn't support it or isn't configured properly to support it. Contract requires TwoWay (either request-reply or duplex), but Binding '{0}' doesn't support it or isn't configured properly to support it. Fail to load binding {0} from config. Error:{1}. Binding type {0} instance {1} not found in config. The required binding keyword was not specified or is not valid. The binding for scheme '{0}' specified in the protocol mapping does not exist and must be created. DeliveryRequirementsAttribute disallows QueuedDelivery, but binding for the endpoint with contract '{0}' supports it. DeliveryRequirementsAttribute requires QueuedDelivery, but binding for the endpoint with contract '{0}' doesn't support it or isn't configured properly to support it. The path variable '{0}' in the UriTemplate must be bound to a non-empty string value. The body writer does not support writing more than once because it is not buffered. The body writer returned from OnCreateBufferedCopy was not buffered. The security binding element for bootstrap security was not specified on '{0}'. Unable to finish reading Base64 data as the given buffer quota has been exceeded. Buffer quota: {0}. Consider increasing the MaxReceivedMessageSize quota on the TransportBindingElement. Please note that a very high value for MaxReceivedMessageSize will result in buffering a large message and might open the system to DOS attacks. Context cached at the channel layer cannot be changed after the channel is opened. The service cannot cache the negotiation state as the capacity '{0}' has been reached. Retry the request. The item cannot be added. The maximum cache size is ({0} items). The incoming message with action '{0}' contains a callback context header with name '{1}' and namespace '{2}'. Callback context headers are not expected in incoming messages at the client. The outgoing message with action '{0}' contains a callback context message property. Callback context cannot be transmitted in outgoing messages at the server. The message contains a callback context message property. Callback context can be transmitted only when the ContextBindingElement is configured with ContextExchangeMechanism of ContextSoapHeader. The message contains a callback context header with an endpoint reference for AddressingVersion '{0}'. Callback context can only be transmitted when the AddressingVersion is configured with 'WSAddressing10'. Cannot access directory {0}. Cannot add two items with the same key to SynchronizedKeyedCollection. Cannot authenticate the other party. The channeloption intrinsic object cannot be created because the channel builder is not initialized. Unable to create a bi-directional (request-reply or duplex) channel for security negotiation. Please ensure that the binding is capable of creating a bi-directional channel. Cannot detect WS-Addressing version. EndpointReference does not start with an Element. 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). Cannot find the X.509 certificate using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}'. Cannot find The X.509 certificate using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}' for target '{4}'. Cannot find the correlation state for applying security to reply at the responder. The token's crypto collection does not support algorithm '{0}'. Cannot find the negotiation state for the context '{0}'. Cannot find the security session with the ID '{0}'. Interface {0} has a null namespace or name. The {0}.{1} operation references a message element [{2}] that has already been exported from the {3}.{4} operation. You can change the name of one of the operations by changing the method name or using the Name property of OperationContractAttribute. Alternatively, you can control the element name in greater detail using the MessageContract programming model. 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. PrivacyNotice element must have a Version attribute. The policy to import a process cannot import a binding for contract ({0},{1}). The protection requirements for the binding are not compatible with a binding already imported for the contract. You must reconfigure the binding. Security policy import failed. The security policy contains supporting token requirements at the operation scope. The contract description does not specify the action for the request message associated with this operation. 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. Cannot issue the token type '{0}'. Cound not load type '{0}' from the assemblies in current AppDomain. Cannot determine the key size of the issued token. The service was unable to verify the cipher strengths negotiated as part of the SSL handshake. Impersonation using the client token is not possible. The binding ('{0}', '{1}') for contract ('{2}', '{3}') uses the Username Security Token for client authentication with a Membership Provider registered. Use a different type of security token for the client. The binding ('{0}','{1}') for contract ('{2}','{3}') supports impersonation only on Windows 2003 Server and newer version of Windows. Use SspiNegotiated authentication and a binding with Secure Conversation with cancellation enabled. 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 result cannot be represented as a nodeset. Only results of type XPathResultType.NodeSet can be represented as nodesets. The type for the '{0}' parameter in '{1}' within the namespace '{2}' cannot not be resolved. The 'Name' property cannot be set on an invalid InstanceKey. The security token authenticator '{0}' cannot validate a token of type '{1}'. Cannot create channel for a contract that requires request/reply and a binding that requires manual addressing but only supports duplex communication. Can't infer an external reference for '{0}' token type. Certificate-based client authentication is not supported in TransportCredentialOnly security mode. Select the Transport security mode. The binding does not contain a ChannelDemuxerBindingElement. The current channel does not support closing the output session as this channel does not implement ISessionChannel<IDuplexSession>. A call to IChannelFactory.CreateChannel made on an object of type {0} failed because Open has not been called on this object. At least one operation on the '{0}' contract is configured with the TransactionFlowAttribute attribute set to Mandatory but the channel's binding '{1}' is not configured with a TransactionFlowBindingElement. The TransactionFlowAttribute attribute set to Mandatory cannot be used without a TransactionFlowBindingElement. A newly accepted connection did not receive initialization data from the sender within the configured ChannelInitializationTimeout ({0}). As a result, the connection will be aborted. If you are on a highly congested network, or your sending machine is heavily loaded, consider increasing this value or load-balancing your server. Internal Error: The InnerChannel property is null. Channel context management cannot be enabled or disabled after the channel is opened. The session channel must be opened before the session ID can be accessed. The channel is not open. Cannot modify channel parameters because the {0} is in the {1} state. This operation is only supported in the Created state. 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. The specified channel type {0} is not supported by this channel manager. The XML element {0} does not have a child of type {1}. The claimType cannot be an empty string. Invalid CleanupInterval value of {0}; it must be greater than zero The certificate for the client has not been provided. The certificate can be set on the ClientCredentials or ServiceCredentials. The client certificate is not provided. Specify a client certificate in ClientCredentials. The client certificate is not provided. Specify a client certificate in ServiceCredentials. ClientCredentials cannot create a local token provider for token requirement {0}. ClientCredentialType.None is not valid for the TransportWithMessageCredential security mode. Specify a message credential type or use a different security mode. The ClientOperation '{0}' requires Formatter, since SerializeRequest and DeserializeReply are not both false. The client's security session did not receive a 'close response' message from the service within the configured timeout ({0}). Client is unable to finish the security negotiation within the configured timeout ({0}). The current negotiation leg is {1} ({2}). The client's security session was not able to close its output session within the configured timeout ({0}). Client is unable to request the security session within the configured timeout ({0}). An error occurred when creating the WebSocket with the factory of type '{0}'. See the inner exception for details. An error occured when getting the WebSocketVersion from the WebSocket factory of type '{0}'. See the inner exception for details. The WebSocket returned by the factory of type '{0}' has the SubProtocol '{1}' that doesn't match the requested SubProtocol value '{2}'. WebSocket creation failed. The '{0}' returned a WebSocket that is either null or not opened. The WebSocketVersion returned by the WebSocket factory of type '{0}' is either null, empty or invalid. Clone() was not implemented properly by '{0}'. The cloned object was '{1}'. 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. The object with CLSID '{0}' does not support the required IPersistStream interface. The CLSID specified in the service file is not configured in the specified application. (The CLSID is {0}, the AppID is {1}.) The CLSID specified in the service file does not have a service element in a configuration file. (The CLSID is {0}.) CLSID of type {0} does not match the CLSID on PersistStreamTypeWrapper which is {1}. Generating manifest file {0} failed with {1}. The communication object, {0}, cannot be used for communication because it has been Aborted. The communication object, {0}, cannot be used for communication because it has been Aborted: {1} The communication object, {0}, has overridden the virtual function {1} but it does not call version defined in the base class. The communication object, {0}, cannot be modified unless it is in the Created state. The communication object, {0}, cannot be modified while it is in the {1} state. The communication object, {0}, is in the {1} state. Communication objects cannot be used for communication unless they are in the Opened state. The communication object, {0}, cannot be used due to an error that occurred during close. The communication object, {0}, cannot be used for communication because it is in the Faulted state. The communication object, {0}, cannot be used for communication because it is in the Faulted state: {1} 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. From: {0}\nAppId: {1}\nClsId: {2}\nIncoming TransactionId: {3}\nRequesting Identity: {4} This InstanceContext requires a valid Message to obtain the instance. From: {0}\nAppId: {1}\nClsId: {2}\nIid: {3}\nAction: {4}\nInstance Id: {5}\nManaged Thread Id: {6}\nUnmanaged Thread Id: {7}\nRequesting Identity: {8} A Windows hotfix or later service pack is required on Windows XP and Windows Server 2003 to use WS-AtomicTransaction and COM+ Integration Web service transaction functionality. See the Microsoft .NET Framework release notes for instructions on installing the required hotfix. AppId: {0}\nClsId: {1}\n AppId: {0} Iid: {0}\nType Library ID: {1} Configuration files are not supported. The remote endpoint sent conflicting requests to create a reliable session. The remote endpoint requested both a one way and a two way session. The reliable session has been faulted. Content Type {0} was sent to a service expecting {1}. The client and service bindings may be mismatched. The context-id={0} (generation-id={1}) is already registered with SecurityContextSecurityTokenAuthenticator. The context-id={0} (no key generation-id) is already registered with SecurityContextSecurityTokenAuthenticator. ContextBindingElement cannot provide channel factory for the requested channel shape {0}. ContextBindingElement cannot provide channel listener for the requested channel shape {0}. EndpointAddress: {0}, Via:{1} Context cached at the channel cannot be set or retrieved when the context management is disabled at the channel layer. Ensure context channel property 'IContextManager.Enabled' is set to true. There is no SecurityContextSecurityToken with context-id={0} (generation-id={1}) registered with SecurityContextSecurityTokenAuthenticator. There is no SecurityContextSecurityToken with context-id={0} (no key generation-id) registered with SecurityContextSecurityTokenAuthenticator. The Address, Binding and Contract keywords are required. 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. 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 contract type name in the configuration file was not in the form of an interface identifier. (The string is \"{0}\".) The '{0}' can only be used with HTTP (or HTTPS) transport. Failed to copy the HTTP header '{0}' with value '{1}' to '{2}'. There is no namespace binding for prefix '{0}' in scope. A message with action {0} could not be parsed. Channel type '{1}' was requested, but Binding '{0}' doesn't support it or isn't configured properly to support it. 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. Couldn't find required attribute of type {0} on {1}. Creation time must be before expiration time. The NTLM authentication scheme was specified, but the target credential does not allow NTLM. The endpoint at {0} processes duplex sessions. The create sequence request must contain an offer for a return sequence. This is likely caused by a binding mismatch. The endpoint at {0} processes input sessions. The create sequence request must not contain an offer for a return sequence. This is likely caused by a binding mismatch. The endpoint at {0} processes reply sessions. The create sequence request must contain an offer for a return sequence. This is likely caused by a binding mismatch. The message is not a valid SOAP message. The body contains more than 1 root element. The remote endpoint replied to a request for a two way session with an offer for a one way session. This is likely caused by a binding mismatch. The channel could not be opened. The client requested creation of a two way session. A one way session was created. The session cannot continue without as a one way session. This is likely caused by a binding mismatch. A return sequence was not offered by the create sequence request. The create sequence response cannot accept a return sequence. A return sequence was offered by the create sequence request but the create sequence response did not accept this sequence. The supporting token in the renew message has a different generation '{0}' than the current session token's generation '{1}'. 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. The custom crypto algorithm '{0}' obtained using CryptoConfig is not a valid or supported asymmetric signature algorithm. The custom crypto algorithm '{0}' obtained using CryptoConfig is not a valid or supported hash algorithm. Unable to decrypt an encrypted data block. Please verify that the encryption algorithm and keys used by the sender and receiver match. (Default) Delayed security application has already been completed. The '{0}' list created by the Func '{1}' is invalid because it contains one or more null items. The '{0}' list is invalid because the property '{1}' of '{2}' is not null. The WS-RM policy under the namespace {0} requires the wsrmp:ExactlyOnce, wsrmp:AtLeastOnce, or wsrmp:AtMostOnce assertion. The {1} element under the {2} namespace was found. The WS-RM policy under the namespace {0} requires the wsrmp:ExactlyOnce, wsrmp:AtLeastOnce, or wsrmp:AtMostOnce assertion. Nothing was found. Derived Key Token cannot derive key from the secret. The received derived key token has a invalid generation value specified. Value: {0}. The value should be greater than or equal to zero. The received derived key token has a invalid offset value specified. Value: {0}. The value should be greater than or equal to zero. The Implicit derived key clause '{0}' specifies a derivation key length ({1}) which exceeds the allowed maximum length ({2}). DerivedKey length ({0}) exceeds the allowed settings ({1}). The number of derived keys in the message has exceeded the maximum allowed number '{0}'. The derived key has not been computed for the security token. Both offset and generation cannot be specified for Derived Key Token. Either offset or generation must be specified for Derived Key Token. 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. The length ('{0}' bytes) of the derived key's Label exceeds the maximum length ('{1}' bytes) allowed. The length ('{0}' bytes) of the derived key's Nonce exceeds the maximum length ('{1}' bytes) allowed. The derived key's Offset ('{0}' bytes) exceeds the maximum offset ('{1}' bytes) allowed. DerivedKeyToken requires a reference to a token. The impersonation level '{0}' was specified, yet HTTP Digest authentication can only support 'Impersonation' level when used with an explicit credential. The DispatchOperation '{0}' requires Formatter, since DeserializeRequest and SerializeReply are not both false. 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. 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. 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 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. No DNS entries exist for host {0}. The document formatter must be configured with a document. Cannot map Windows user '{0}' to a UserPrincipalName that can be used for S4U impersonation. Duplex channel to {0} was aborted during the open process. No duplex session listener was listening at {0}. This could be due to an incorrect via set on the client or a binding mismatch. 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. Duplicate contract XmlQualifiedNames are not supported.\r\nAnother ContractDescription with the Name: {0} and Namespace: {1} has already been exported. The IssuedSecurityTokenProvider cannot support the FederatedClientCredentialsParameters. The FederatedClientCredentialsParameters has already provided the '{0}' parameter. The '{0}' id occurred twice in the message that is supplied for verification. A property with the name '{0}' already exists. A peer registration with the service address {0} already exists. A policy document was ignored because a policy expression with that ID has already been imported.\r\nPolicy ID:{0} A policy expression was ignored because another policy expression with that ID has already been read in this document.\r\nXPath:{0} A registration already exists for URI '{0}'. More than one Timestamp element was present in security header. Could not duplicate the token (error=0x{0:X}). The remote endpoint has errantly sent a TerminateSequence protocol message before the sequence finished. The valid from time is greater than the valid to time. The {0}:{1} element requires a {2}:{3} child element but has the {4} child element under the {5} namespace. The {0}:{1} element requires a {2}:{3} child element but has no child elements. Element to sign must have id. An empty value was found for the required base-64 attribute name '{0}', namespace '{1}'. Element {0} cannot be empty. Cannot process contentType. 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 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. Unrecognized charSet '{0}' in contentType. Unrecognized contentType ({0}). Expected: {1}. 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 Encrypted Header and the Security Header '{0}' attribute did not match. Encrypted Header: {1}. Security Header: {2}. The Header ('{0}', '{1}') was encrypted but not signed. All encrypted headers outside the security header should be signed. An encrypted header must have an id. The EncryptedKey clause was not wrapped with the required encryption token '{0}'. EncryptedKey with ReferenceList is not allowed according to the current settings. The encryption method is missing in encrypted data. Encryption not expected for this message. 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. 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}'. An endpoint configured for the COM+ CLSID {0} is not a configured interface on the class. (The contract type is {1}.) 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 ServiceEndpoint with name '{0}' could not be exported to WSDL because the Binding property is null. To fix this, set the Binding property to a valid Binding instance. The issuer cannot provide a computed key in key entropy mode '{0}'. The issuer cannot provide key entropy or a proof token in key entropy mode '{0}'. The client cannot provide key entropy in key entropy mode '{0}'. The issuer must provide a computed key in key entropy mode '{0}'. The issuer must provide key entropy in key entropy mode '{0}'. The issuer must provide a proof token in key entropy mode '{0}'. The client must provide key entropy in key entropy mode '{0}'. Envelope Version '{0}' is not supported. Unrecognized envelope version: {0}. There was an error creating the security key identifier clause from the security token XML. Please see the inner exception for more details. There was an error deserializing the security token XML. Please see the inner exception for more details. Importing metadata from issuer '{0}' failed with error '{1}'. Error in line {0} position {1}. An error was encountered when parsing a DateTime value in the XML. An error was encountered when parsing the document's XML. Refer to the inner exception for more details. An error was encountered when parsing the feed's XML. Refer to the inner exception for more details. An error was encountered when parsing the item's XML. Refer to the inner exception for more details. There was an error serializing the security token. Please see the inner exception for more details. The policy expression was not fully imported because it exceeded the maximum allowable complexity. The import stopped at element '{0}' '{1}'. The policy expression was not fully imported because its normalized form was too large. Element '{0}' with namespace '{1}' not found. Expected element '{0}' or element '{1}' (from namespace '{2}'). The Infocard token created during channel intialization has expired. Please create a new channel to reacquire token. Security policy export failed. The binding contains a TransportSecurityBindingElement but no transport binding element that implements ITransportTokenAssertionProvider. Policy export for such a binding is not supported. Make sure the transport binding element in the binding implements the ITransportTokenAssertionProvider interface. 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\". The Authentication Scheme \"Basic\" does not support Extended Protection. Please use a different authentication scheme or disable the ExtendedProtectionPolicy on the Binding or BindingElement by creating a new ExtendedProtectionPolicy with a PolicyEnforcement value of \"Never\". CustomChannelBindings are not supported. Please remove the CustomChannelBinding from the ExtendedProtectionPolicy\". The name of the extension element must be specified. Additional XML content is present in the fault detail element. Only a single element is allowed. At least one security token in the message could not be validated. The request for security token could not be satisfied because authentication failed. The processing of the WSDL parameter failed. Error: {0} The required outer proxy could not be created. Ensure that the service moniker is correctly installed and registered. The signature verification failed. Please see inner exception for fault details. Secure channel cannot be opened because security negotiation with the remote endpoint has failed. This may be due to absent or incorrectly specified EndpointIdentity in the EndpointAddress used to create the channel. Please verify the EndpointIdentity specified or implied by the EndpointAddress correctly identifies the remote endpoint. Failed to convert type library to assembly Failed to create a typed proxy for type '{0}' The issued token accompanying the WS-AtomicTransaction coordination context was invalid or corrupt. Failed to load type library Security negotiation failed because the remote party did not send back a reply in a timely manner. This may be because the underlying transport connection was aborted. {0} returned false from OnTryCreateException, but returned a non-null Exception (See InnerException for details). {0} returned false from OnTryCreateFaultMessage, but returned a non-null fault message. {0} returned true from OnTryCreateException, but did not return an Exception. {0} returned true from OnTryCreateFaultMessage, but did not return a fault message. The fault does not have detail information. The feed's authors were not serialized as part of serializing the feed in RSS 2.0 format. The feed's contributors were not serialized as part of serializing the feed in RSS 2.0 format. The feed created a null category. =The feed created a null item. The feed created a null person. The syndication feed formatter must be configured with a syndication feed. The feed being deserialized has non-contiguous sets of items in it. This is not supported by '{0}'. The feed's id was not serialized as part of serializing the feed in RSS 2.0 format. The feed's links were not serialized as part of serializing the feed in RSS 2.0 format. The IMessageFilterTable created for a Filter cannot be a MessageFilterTable or a subclass of MessageFilterTable. Value cannot be negative. Could not compile the XPath expression '{0}' with the given XsltContext. Parameter value cannot be an empty string. The filter already exists in the filter table. Invalid attribute on the XPath. When present, the dialect attribute must have the value '{0}'. Required inner element '{0}' was not found. Multiple filters matched. The number of XML infoset nodes inspected by the navigator has exceeded the quota ({0}). NodeQuota must be greater than 0. XmlReader not positioned at a start element. Session filter's isStrictMode differs from filter table's isStrictMode. The MessageFilterTable state is corrupt. The requested lookup cannot be performed. The type of IMessageFilterTable created for a particular Filter type must always be the same. The prefix '{0}' is not defined. An internal error has occurred. Unexpected error modifying filter table. Object type must be an enum with the flag attribute. '{0}' is not an enum - or the flag attribute is not set. Please use an enum type with the flag attribute instead. Cannot write to a buffer which is currently being flushed. For replay detection to be done ProtectionLevel must be Sign or EncryptAndSign. Found multiple X.509 certificates using the following search criteria: StoreName '{0}', StoreLocation '{1}', FindType '{2}', FindValue '{3}'. Provide a more specific find value. 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 request did not have any signatures but the reply has signature confirmations. An attempt was made to decode a value after the framing stream was ended. Content Type {0} was not supported by service {1}. The client and service bindings may be mismatched. The framing content type size ({0}) exceeds the quota. Content type '{0}' is too long to be processed by the remote host. See the server logs for more details. Error while reading message framing format at position {0} of stream (state: {1}) The framing fault size ({0}) exceeds the quota. Server faulted with code '{0}'. The maximum message size quota for incoming messages has been exceeded for the remote channel. See the server logs for more details. Framing mode {0} is not supported. The .Net Framing mode being used is not supported by '{0}'. See the server logs for more details. More data was expected, but EOF was reached. Expected record type '{0}', found '{1}'. Specified size is too large for this implementation. 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). The value cannot be accessed because it has not yet been fully decoded. Framing major version {0} is not supported. The .Net Framing version being used is not supported by '{0}'. See the server logs for more details. The framing via ({0}) is not a valid URI. The framing via size ({0}) exceeds the quota. Via '{0}' is too long to be processed by the remote host. See the server logs for more details. The Binding with name {0} failed validation because it contains a BindingElement with type {1} which is not supported in partial trust. Consider using BasicHttpBinding or WSHttpBinding, or hosting your application in a full-trust environment. The WSHttpBinding with name {0} failed validation because it contains a BindingElement with type {1} which is not supported in partial trust. Consider disabling the message security and reliable session options, using BasicHttpBinding, or hosting your application in a full-trust environment. The Binding with name {0} failed validation because the Binding type {1} is not supported in partial trust. Consider using BasicHttpBinding or WSHttpBinding, or hosting your application in a full-trust environment. There was an error verifying some XML Schemas generated during export:\r\n{0} GenericCallbackException Could not get token information (error=0x{0:X}). The message header with name '{0}' and namespace '{1}' is not present in the set of understood headers. The message header with name '{0}' and namespace '{1}' is already present in the set of understood headers. SecurityVersion.WSSecurityJan2004 does not support header decryption. Use SecurityVersion.WsSecurity11 and above or use transport security to encrypt the full message. SecurityVersion.WSSecurityJan2004 does not support header encryption. Header with name '{0}' and namespace '{1}' is configured for encryption. Consider using SecurityVersion.WsSecurity11 and above or use transport security to encrypt the full message. There is not a header with name {0} and namespace {1} in the message. Envelope Version '{0}' does not support adding Message Headers. The BaseUriWithWildcard object has invalid fields after deserialization. This service requires ASP.NET compatibility and must be hosted in IIS. Either host the service in IIS with ASP.NET compatibility turned on in web.config or set the AspNetCompatibilityRequirementsAttribute.AspNetCompatibilityRequirementsMode property to a value other than Required. Setting minFreeMemoryPercentageToActivateService requires full trust privilege. Please change the application's trust level or remove this setting from the configuration file. The protocol binding '{0}' does not conform to the syntax for '{1}'. The following is an example of valid '{1}' protocol bindings: '{2}'. The protocol binding '{0}' is not valid for '{1}'. This might be because the port number is out of range. The '{0}' protocol binding '{1}' specifies an invalid port number '{2}'. '{0}' is an absolute address. The supported relativeAddress formats are \"[subfolder/]filename\" or \"~/[subfolder/]filename\". There is no compatible TransportManager found for URI '{0}'. This may be because you have used an absolute address that points outside of the virtual application. Please use a relative address instead. There is no compatible TransportManager found for URI '{0}'. This may be because you have used an absolute address that points outside of the virtual application, or the binding settings of the endpoint do not match those that have been set by other services or endpoints. Note that all bindings for the same protocol should have the same settings in the same application. The protocol '{0}' is not supported. '{0}' cannot be invoked within the current hosting environment. This API requires that the calling application be hosted in IIS or WAS. Registered relativeAddress '{0}' in configuration file is not a valid one. Possible causes could be : You specified an empty addreess or an absolute address (i.e., starting with '/' or '\\'), or the address contains invalid character[s]. The supported relativeAddress formats are \"[folder/]filename\" or \"~/[folder/]filename\". The requested service, '{0}' could not be activated. See the server's diagnostic trace logs for more information. The value for the Service attribute was not provided in the ServiceHost directive. VirtualPathExtension is not allowed to be removed. 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. HTTP request streaming cannot be used in conjunction with HTTP authentication. Either disable request streaming or specify anonymous HTTP authentication. The HTTP request with client authentication scheme '{0}' failed with '{1}' status. The HTTP request is unauthorized with client authentication scheme '{0}'. The authentication header received from the server was '{1}'. The HTTP request was forbidden with client authentication scheme '{0}'. The HTTPS listener factory was configured to require a client certificate and the '{0}' authentication scheme. However, only one form of client authentication can be required at once. 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. 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 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 ({0}) occurred while parsing the content type of the HTTP request. The content type was: {1}. An HTTP Content-Type header is required for SOAP messaging and none was found. ContextBindingElement of binding {0}:{1} is configured with ContextExchangeMode.HttpCookie but the configuration of this binding's HttpTransportBindingElement prevents upper channel layers from managing cookies. Please set the HttpTransportBindingElement.AllowCookies property to false or change the ContextExchangeMechanism of ContextBindingElement to SoapHeader. Binding {1}:{2} is configured with ContextExchangeMechanism.HttpCookie which is not compatible with the transport type {0}. Please modify the ContextExchangeMechanism or use HTTP or HTTPS transport. 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. Unable to start the HTTP listener. The URI provided, '{0}', is invalid for listening. Check the base address of your service and verify that it is a valid URI. The value of MaxPendingAccepts should not be larger than {0}. '{0}' cannot return a null '{1}' instance. Please ensure that '{0}' returns a valid '{1}' instance. The config element '{0}' is invalid because the attribute '{1}' and the sub element '{2}' were both specified. These are mutually exclusive items and cannot be used simultaneouly. This '{0}' object cannot be used to generate configuration because it was created with the constructor that takes a '{1}' as the paramter. This functionality is not supported through configuration files. Please use a different constructor if you wish to generate a configuration file. Invalid type: '{0}'. It must inherit from base type '{1}', cannot be abstract, and must expose a public default constructor. The remote HTTP server did not satisfy the mutual authentication requirement. {0}. This often indicates that the HTTP client has prematurely closed the underlying TCP connection. {0}. This often indicates that a service that HTTP.SYS depends upon (such as httpfilter) is not started. The message property '{0}' is missing in the HttpRequestMessage. Please make sure this property not removed or changed from the properties of the HttpRequestMessage. If you are creating a new HttpRequestMessage, please copy this property from the old message to the new one. The message property '{0}' inside the HttpRequestMessage is not with expected type '{1}'. Please make sure this property not removed or changed from the properties of the HttpRequestMessage. If you are creating a new HttpRequestMessage, please copy this property from the old message to the new one. The property '{0}' is not supported when building a ChannelFactory. The property value must be null when calling BuildChannelFactory. The HTTP response message should not be null. Please ensure your '{0}' instance returns a non-null '{1}' object. HTTP pipeline operation cancelled. 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. 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. HTTP could not register URL {0}. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details). HTTP could not register URL {0}. Another application has already registered this URL with HTTP.SYS. HTTP could not register URL {0} because the MaxEndpoints quota has been exceeded. To correct this, either close other HTTP-based services, or increase your MaxEndpoints registry key setting (see http://go.microsoft.com/fwlink/?LinkId=70352 for details). HTTP could not register URL {0} because TCP port {1} is being used by another application. The HTTP request to '{0}' was aborted. This may be due to the local channel being closed while the request was still in progress. If this behavior is not desired, then update your code so that it does not close the channel while request operations are still in progress. 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 '{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. The HTTP request context was aborted while writing the response. As a result, the response may not have been completely written to the network. This can be remedied by gracefully closing the request context rather than aborting it. 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. An error occurred while making the HTTP request to {0}. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. 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. The HTTPS channel factory does not support explicit specification of an identity in the EndpointAddress unless the authentication scheme is NTLM or Negotiate. The endpoint identity specified when creating the HTTPS channel to '{0}' contains multiple server certificates. However, the HTTPS transport only supports the specification of a single server certificate. In order to create an HTTPS channel, please specify no more than one server certificate in the endpoint identity. The SOAP action specified on the message, '{0}', does not match the action specified on the HttpRequestMessageProperty, '{1}'. The SOAP action specified on the message, '{0}', does not match the action specified in the content-type of the HttpRequestMessageProperty, '{1}'. The SOAP action specified on the message, '{0}', does not match the HTTP SOAP Action, '{1}'. The SPN for the responding server at URI '{0}' could not be determined. 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. The entry found in AuthenticationManager's CustomTargetNameDictionary for {0} does not match the requested identity of {1}. 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}'. An error ({0}) occurred while transmitting data over the HTTP channel. The policy being imported for contract '{0}:{1}' contains multiple HTTP authentication scheme assertions. Since at most one such assertion is allowed, policy import has failed. This may be resolved by updating the policy to contain no more than one HTTP authentication scheme assertion. ID0020: The collection is empty. ID0023: Failed to create an instance of '{0}' from configuration. A custom configuration element was specified, but the method LoadCustomConfiguration was not implemented. Override LoadCustomConfiguration to handle custom configuration loading. ID2004: IAsyncResult must be the AsyncResult instance returned from the Begin call. The runtime is expecting '{0}', and the actual type is '{1}'. ID3002: WSTrustServiceContract could not create a SecurityTokenService instance from WSTrustServiceContract.SecurityTokenServiceConfiguration. ID3004: Cannot obtain the schema for namespace: '{0}'. ID3022: The WSTrustServiceContract only supports receiving RequestSecurityToken messages. If you need to support more message types, override the WSTrustServiceContract.DispatchRequest method. ID3023: The WSTrustServiceContract only supports receiving RequestSecurityToken messages asynchronously. If you need to support more message types, override the WSTrustServiceContract.BeginDispatchRequest and EndDispatchRequest. ID3097: ServiceHost does not contain any valid Endpoints. Add at least one valid endpoint in the SecurityTokenServiceConfiguration.TrustEndpoints collection. ID3112: Unrecognized RequestType '{0}' specified in the incoming request. ID3113: The WSTrustServiceContract does not support receiving '{0}' messages with the '{1}' SOAP action. If you need to support this, override the ValidateDispatchContext method. ID3114: The WSTrustServiceContract cannot deserialize the WS-Trust request. ID3137: The TrustVersion '{0}', is not supported, only 'TrustVersion.WSTrust13' and 'TrustVersion.WSTrustFeb2005' is supported. ID3138: The RequestSecurityTokenResponse that was received did not contain a SecurityToken. ID3139: The WSTrustChannel cannot compute a proof key. The KeyType '{0}' is not supported. Valid proof key types supported by the WSTrustChannel are WSTrust13 and WSTrustFeb2005. ID3140: Specify one or more BaseAddresses to enable metadata or set DisableWsdl to true in the SecurityTokenServiceConfiguration. ID3141: The RequestType '{0}', is not supported. If you need to support this RequestType, override the corresponding virtual method in your SecurityTokenService derived class. ID3144: The PortType '{0}' Operation '{1}' has Message '{2}' is expected to have only one part but contains '{3}'. ID3146: WsdlEndpointConversionContext.WsdlPort cannot be null. ID3147: WsdlEndpointConversionContext.WsdlPort.Service cannot be null. ID3148: WsdlEndpointConversionContext.WsdlPort.Service.ServiceDescription cannot be null. ID3149: Cannot find an input message type for PortType '({0}, {1})' for operation '{2}' in the given ServiceDescription. ID3150: Cannot find an output message type for PortType '({0}, {1})' for operation '{2}' in the given ServiceDescription. ID3190: The WSTrustChannel cannot compute a proof key without a valid SecurityToken set as the RequestSecurityToken.UseKey when the RequestSecurityToken.KeyType is '{0}'. ID3191: The WSTrustChannel received a RequestedSecurityTokenResponse message containing an Entropy without a ComputedKeyAlgorithm. ID3192: The WSTrustChannel cannot compute a proof key. The received RequestedSecurityTokenResponse does not contain a RequestedProofToken and the ComputedKeyAlgorithm specified in the response is not supported: '{0}'. ID3193: The WSTrustChannel cannot compute a proof key. The received RequestedSecurityTokenResponse indicates that the proof key is computed using combined entropy. However, the response does not include an entropy. ID3194: The WSTrustChannel cannot compute a proof key. The received RequestedSecurityTokenResponse indicates that the proof key is computed using combined entropy. However, the request does not include an entropy. ID3269: Cannot determine the TrustVersion. It must either be specified explicitly, or a SecurityBindingElement must be present in the binding. ID3270: The WSTrustChannel does not support multi-leg issuance protocols. The RSTR received from the STS must be enclosed in a RequestSecurityTokenResponseCollection element. ID3285: The WS-Trust operation '{0}' is not valid or unsupported. ID3286: The 'inner' parameter must implement the 'System.ServiceModel.Channels.IChannel' interface. ID3287: WSTrustChannelFactory does not support changing the value of this property after a channel is created. ID4008: '{0}' does not provide an implementation for '{1}'. ID4039: A custom ServiceAuthorizationManager has been configured. Any custom ServiceAuthorizationManager must be derived from IdentityModelServiceAuthorizationManager. ID4041: Cannot configure the ServiceHost '{0}'. The ServiceHost is in a bad state and cannot be configured. ID4053: The token has WS-SecureConversation version '{0}'. Version '{1}' was expected. ID4072: The SecurityTokenHandler '{0}' registered for TokenType '{1}' must derive from '{2}'. ID4101: The token cannot be validated because it is not a SamlSecurityToken or a Saml2SecurityToken. Token type: '{0}' ID4192: The reader is not positioned on a KeyInfo element that can be read. ID4240: The tokenRequirement must derived from 'RecipientServiceModelSecurityTokenRequirement' for SecureConversationSecurityTokens. The tokenRequirement is of type '{0}'. ID4244: Internal error: sessionAuthenticator must support IIssuanceSecurityTokenAuthenticator. ID4245: Internal error: sessionAuthenticator must support ICommunicationObject. ID4268: MergeClaims must have at least one identity that is not null. ID4271: No IAuthorizationPolicy was found for the Transport security token '{0}'. ID4274: The Configuration property of this SecurityTokenHandler is set to null. Tokens cannot be read or validated in this state. Set this property or add this SecurityTokenHandler to a SecurityTokenHandlerCollection with a valid Configuration property. ID4285: Cannot replace SecurityToken with Id '{0}' in cache with new one. Token must exist in cache to be replaced. ID4287: The SecurityTokenRequirement '{0}' doesn't contain a ListenUri. ID5004: Unrecognized namespace: '{0}'. The identity check failed for the incoming message. The expected identity is '{0}' for the '{1}' target endpoint. The identity check failed for the outgoing message. The expected identity is '{0}' for the '{1}' target endpoint. Ignoring invalid part in wsdl:message name='{0}' from targetNamespace='{1}'. Reason: {2} Ignoring invalid SOAP fault extension in wsdl:operation name='{0}' from targetNamespace='{1}'. Reason: {2} Ignoring invalid SOAP header extension in wsdl:operation name='{0}' from targetNamespace='{1}'. Reason: {2} Could not impersonate the anonymous user (error=0x{0:X}). The authentication modes using Kerberos do not support the impersonation level '{0}'. Specify identification or impersonation. Because base ServiceContract '{0}' has a CallbackContract '{1}', derived ServiceContract '{2}' must also specify either '{1}' or a derived type as its CallbackContract. 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 MSDTC transaction manager has disabled incoming transactions. For this security protocol, the incoming signing token must be an EncryptedKey. TransactedBatchingBehavior cannot be used when ReceiveContext is being used. Incoming binary negotiation has invalid ValueType {0}. Security Support Provider Interface (SSPI) authentication failed. The server may not be running in an account with identity '{0}'. If the server is running in a service account (Network Service for example), specify the account's ServicePrincipalName as the identity in the EndpointAddress for the server. If the server is running in a user account, specify the account's UserPrincipalName as the identity in the EndpointAddress for the server. Policy chain contains self issued URI or a managed issuer in the wrong position. Cannot open ChannelFactory as the inner channel factory was not set during the initialization process. The Inner listener factory of {0} must be set before this operation. The input {0} must be a '{1}' object. The input handler list cannot be empty. The ServiceHost must be configured with either a serviceType or a serviceInstance. Both of these values are currently null. Insufficient memory avaliable to complete the operation. Credentials specified are not sufficient to carry requested operation. Please specify a valid value for {0}. The binding's PeerTransportSecuritySettings can not be supported under the current system security configuration. Provided information is Insufficient to create a valid connection to the resolver service. Could not find interface in the Assembly Interface {0} not found in configuration. Interface Not Registered An unexpected error has occurred. The SequenceAcknowledgement violates the cumulative acknowledgement invariant. Security negotiation message has incorrect action '{0}'. 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. Invalid async End method signature for method {0} in ServiceContract type {1}. Your end method must take an IAsyncResult as the last argument. Expecting all chars - c - of id to be in set [Char.IsLetter(c), Char.IsNumber(c), '.', '_', '-'], found '{0}'. Expecting first char - c - to be in set [Char.IsLetter(c) && c == '_', found '{0}'. The ('{0}', '{1}') signed header contains the ('{2}', '{3}') attribute. The expected attribute is ('{4}', '{5}'). The binding ('{0}', '{1}') uses an Issued Token with Bearer Key Type in a invalid context. The Issued Token with a Bearer Key Type can only be used as a Signed Supporting token or a Signed Encrypted Supporting token. See the SecurityBindingElement.EndpointSupportingTokenParameters property. 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. The client credential entered was invalid. A security session close response was received with an invalid action '{0}', The value '{0}' is not a valid content type. Context channel received a message with context which does not match the current context cached at the channel. Ensure service does not change context after it was originally set or disable context management by setting channel property 'IContextManager.Enabled' to false. Value '{0}' specified for 'name' attribute of ContextMessageProperty is either null or has invalid character(s). Please ensure value of 'name' is within the allowed value space. The transaction identifier element in the coordination context is invalid. Invalid decoder state machine. The value of argument '{0}' ({1}) is invalid for Enum type '{2}'. Unexpected internal enum value: {0}. Object type must be an enum with the flag attribute and may only contain powers of two for the flags enum values or a combination of such values. Please use an enum type according to these rules. Cannot read the Identity element. The Identity type is not supported or the Identity element is empty. The isolation level for component {0} is invalid. (The value was {1}.) The issued token has an invalid key size '{0}'. The key length '{0}' requested is invalid. The specified key size {0} is invalid. The key size must be between {1} and {2}. The username/password Membership provider {0} specified in the configuration is invalid. No such provider was found registered under system.web/membership/providers. Cannot specify 'ContextMessageProperty' in message when using context channel with context management enabled. Ensure the message does not have 'ContextMessageProperty' or disable context management by setting channel property 'IContextManager.Enabled' to false. An internal error has occurred. Invalid MessageState. The Type of object passed as parameter '{0}' is not derived from {1}. Ensure that the type of object passed is either of type {1} or derived from {1}. The nonce is invalid or replayed. The message could not be processed because the action '{0}' is invalid or unrecognized. The type {0} registered as a policy extension does not implement IPolicyImportExtension The OLE Transactions propagation token received in the message could not be used to unmarshal a transaction. It may be invalid or corrupt. The QName is invalid. The XmlReader used for the body of the message must be positioned on an element. The context identifier element in the registration header is invalid. The token identifier element in the registration header is invalid. The transaction identifier element in the registration header is invalid A security session renew response was received with an invalid action '{0}'. The request for security token has invalid or malformed elements. Specified PeerResolverMode value {0} is invalid. Please specify either PeerResolveMode.Auto, Default, or Pnrp. The RoleProvider {0} specified in the configuration is invalid. No such provider was found registered under system.web/roleManager/providers. The RequestSecurityToken has an invalid or unspecified RequestType '{0}'. The SecurityContextSecurityToken has an invalid Cookie. The following error occurred when processing the Cookie: '{0}'. An error occurred when verifying security for the message. An error occurred when processing the security tokens in the message. The Security Support Provider Interface (SSPI) negotiation failed. The token provider of type '{0}' did not return a token of type '{1}'. Check the credential configuration. The specified method handle is incorrect for the proxy of type '{0}' The provided URI scheme '{0}' is invalid; expected '{1}'. Value '{0}' provided for '{1}' from namespace '{2}' is an invalid absolute URI. The interface with IID {0} cannot be exposed as a web service The parameter named {0} of type {1} on method {2} of interface {3} cannot be serialized. The return value of type {0} on method {1} of interface {2} cannot be serialized. The WS-AtomicTransaction extended information included in the OLE Transactions propagation token was invalid or corrupt. The specified WSAT protocol version is invalid. The type {0} registered as a WSDL extension does not implement IWsdlImportExtension. The remote endpoint responded to the {0} request with a response with action {1}. The response must be a {0}Response with action {2}. The channel could not be opened. The remote endpoint responded to the {0} request with a response with action {1}. The response must be a {0}Response with action {2}. The channel was faulted. Invalid binary representation of an X.509 certificate. Expected XML qualified name, found '{0}'. The received transaction has an isolation level of '{0}' but the service is configured with a TransactionIsolationLevel of '{1}'. The isolation level for received transactions and the service must be the same. The binding ('{0}', '{1}') has been configured with a security algorithm suite '{2}' that is incompatible with the issued token key size '{3}' specified on the binding. The security token parameters to use for the issued token are not set on '{0}'. The IssuedToken security authentication mode requires the issued token to contain a symmetric key. The issued token cache was not specified on '{0}'. The service does not accept issued tokens. The key length '{0}' is not a multiple of 8 for symmetric keys. The context for building the issuer channel was not specified on '{0}'. The channel behaviors configured for the issuer address '{0}' cannot contain a behavior of type '{1}'. There is no handler registered for session token issuance event. The item's authors were not serialized as part of serializing the feed in RSS 2.0 format. {0} is only available in a deserialized RequestSecurityToken. {0} is only available in a deserialized RequestSecurityTokenResponse. The item's content was not serialized as part of serializing the feed in RSS 2.0 format. The item's contributors were not serialized as part of serializing the feed in RSS 2.0 format. The item's copyrights were not serialized as part of serializing the feed in RSS 2.0 format. The item created a null category. The item created a null person. Item does not exist in SynchronizedKeyedCollection. The syndication item formatter must be configured with a syndication item. The item's last updated time was not serialized as part of serializing the feed in RSS 2.0 format. The item's links were not serialized as part of serializing the feed in RSS 2.0 format. {0} is not available in deserialized RequestSecurityToken. {0} is not available in deserialized RequestSecurityTokenResponse. No value found for a keyword. This SecurityKeyIdentifier does not have any clause that can create a key. This SecurityKeyIdentifierClause does not support key creation. Key length '{0}' is not a multiple of 8 for symmetric keys. The key effective and expiration times must be bounded by the token effective and expiration times. The key rollover interval cannot be greater than the key renewal interval. The value for wsrm:MessageNumber exceeds the value of the MessageNumber accompanying a LastMessage element in this Sequence. The length of this argument must be greater than 0. The callback address already has a context header in it. The specified channel listener at '{0}' is not registered with this transport manager. A listen URI must be specified in order to open this {0}. The localId cannot be empty. Specify a valid 'localId'. Cannot claim lock within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout. Internal SSL error (refer to Win32 status code for details). Check the server certificate to determine if it is capable of key exchange. Binding validation failed because the TransportBindingElement's ManualAddressing property was set to true on a binding that is configured to create reliable sessions. This combination is not supported and the channel factory or service host was not opened. Manual addressing is enabled on this factory, so all messages sent must be pre-addressed. For TransferMode.Buffered, MaxReceivedMessageSize and MaxBufferSize must be the same value. MaxBufferSize must not exceed MaxReceivedMessageSize. The recursive policy fetching limit has been reached. Check to determine if there is a loop in the federation service chain. 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. This factory buffers messages, so the message sizes must be in the range of an integer value. The maximum message size quota for outgoing messages ({0}) has been exceeded. ... stream ... ... A body element was not found inside the message envelope. Operation '{0}' is not valid in message body state '{1}'. The body reader is in ReadState '{0}' and cannot be consumed. ... Error reading body: {0}: {1} ... MessageBuffer is closed. Message is closed. A problem occurred while reading a message. See inner exception for details. This message cannot support the operation because it has been copied. This message cannot support the operation because it has been read. This message cannot support the operation because it has been written. The value of the addressHeaders argument is invalid because the collection contains null values. Null is not a valid value for the AddressHeaderCollection. The version of the header(s) ({0}) differs from the version of the message ({1}). The '{0}' header cannot be added because it does not support the specified message version '{1}'. The body of the message cannot be read because it is empty. For sending a message on server side composite duplex channels, the message must have either the 'Via' property or the 'To' header set. Message with id {0} was not in a locked state. The maximum value for wsrm:MessageNumber has been exceeded. Message part specification must be made constant before being set. The MessagePropagationFilter threw an exception. Please refer to InnerException. The array passed does not have enough space to hold all the properties contained by this collection. A property with the name '{0}' is not present. The IMessageProperty could not be copied. CreateCopy returned null. The received message does not meet the required message protection order '{0}'. Manual addressing is not supported with message level security. Configure the binding ('{0}', '{1}') to use transport security or to not do manual addressing. Message security verification failed. SecurityVersion must be WsSecurity10 or WsSecurity11. This Factory buffers messages, so the message sizes must be in the range of a int value. The text encoding '{0}' used in the text message format is not supported. The 'To' header on the message is set to Anonymous Uri '{0}'. Please set the 'To' header to a non-anonymous address as message cannot be addressed to anonymous Uri on server side composite duplex channels. Validity of message with id {0} has expired. 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. Support for {0} and {1} can not be enabled with {2} when the {3} of the {4} is '{5}'. Ensure the {4} used with the binding has a {3} of '{6}'. Unrecognized message version. The 'Via' property on the message is set to Anonymous Uri '{0}'. Please set the 'Via' property to a non-anonymous address as message cannot be addressed to anonymous Uri on server side composite duplex channels. The message is not encrypted with a key derived from the encryption token. The binding's token parameter '{0}' requires key derivation. The message is not encrypted with a key derived from the encrypted key. The binding's token parameter '{0}' requires key derivation. The message was not encrypted with the required encryption token. There is a problem with the XML that was received from the network. See inner exception for more details. Method {0} given in config was not found on interface {1}. Binding '{0}' was not found in config. The config file must be present and contain a binding matching the one specified in the moniker. The incoming message was signed with a token which was different from what used to encrypt the body. This was not expected. The receiver returned an error indicating that the content type was missing on the request to {0}. See the inner exception for more information. X509CertificateValidationMode.Custom requires a CustomCertificateValidator. Specify the CustomCertificateValidator property. UserNamePasswordValidationMode.Custom requires a CustomUserNamePasswordValidator. Specify the CustomUserNamePasswordValidator property. Id is missing in encrypted item in security header. The KeyInfo clause is missing or empty in EncryptedKey. UserNamePasswordValidationMode.MembershipProvider requires a MembershipProvider. Specify the MembershipProvider property. Request Message is missing a MessageID header. One is required to correlate a reply. The wsa:MessageId header must be present on a wsrm:{0} message. Missing Quote in value {0}. The wsa:ReplyTo header must be present on a wsrm:{0} message. Address not specified. Binding namespace not specified. Binding not specified. None of the contract in metadata matched the contract specified. Contract not specified. Failed to do mex retrieval:{0}. Invalid serializer specified. The only valid values are 'xml' and 'datacontract'. Multiple server identity keywords were specified. Ensure that at most one identity keyword is specified. Only one type of server identity can be specified. Mex address not specified. Mex binding section name attribute not specified. Moniker Missing Colon The contract does not have an endpoint supporting the binding specified. 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 RequestSecurityTokenResponseCollection received has more than one RequestSecurityTokenResponse element. Only one RequestSecurityTokenResponse element was expected. More than one SecurityBindingElement found in the binding ('{0}', '{1}) for contract ('{2}', '{3}'). Only one SecurityBindingElement is allowed. More than one supporting signature was encountered using the same supporting token '{0}'. MessageVersion '{0}' not supported by MTOM encoder. The AuthenticationManager cannot be added to the binding parameters because the binding parameters already contains a AuthenticationManager '{0}'. If you are configuring a custom AuthenticationManager for the service, please first remove any existing AuthenticationManagers from the behaviors collection before adding the custom AuthenticationManager. The AuthenticationSchemes cannot be added to the binding parameters because the binding parameters already contains AuthenticationSchemes '{0}'. If you are configuring custom AuthenticationSchemes for the service, please first remove any existing AuthenticationSchemes from the behaviors collection before adding custom AuthenticationSchemes. Calling IWsdlExportExtension.ExportContract twice with the same ContractDescription is not supported. More than one '{0}' objects were found in the BindingParameters of the BindingContext. This is usually caused by having multiple '{0}' objects in a CustomBinding. Remove all but one of these elements. The '{0}' contains multiple '{1}' objects, which is invalid. At most one '{1}' should be specified. The callback address contains multiple context headers. There can be at most one context header in a callback address. Multiple correlation tokens were found in the security correlation state. The extensions cannot contain an Identity if one is supplied as a constructor argument. Policy for multiple issuer endpoints was retrieved from '{0}' but the relying party's policy does not specify which issuer endpoint to use. One of the endpoints was selected as the issuer endpoint to use. If you are using svcutil, the other endpoints will be available in commented form in the configuration as <alternativeIssuedTokenParameters>. Check the configuration to ensure that the right issuer endpoint was selected. The token's crypto collection has multiple objects of type '{0}'. 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. Multiple headers with name '{0}' and namespace '{1}' found. Multiple headers with name '{0}' and namespace '{1}' and role '{2}' found. Multiple RelatesTo headers with relationship '{0}' found. Only one is allowed per relationship. 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. The ServiceCredentials cannot be added to the binding parameters because the binding parameters already contains a SecurityCredentialsManager '{0}'. If you are configuring custom credentials for the service, please first remove any existing ServiceCredentials from the behaviors collection before adding the custom credential. 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. 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. concrete PeerResolver implementation must override Initialize to accept metadata about resolver service. Registration with zero addresses detected. Please call Register with more than zero addresses. The cNamedArgs parameter is not supported and must be 0. An attempt to load the native type library '{0}' was made. Native type libraries cannot be loaded. Transport security negotiation failed due to an underlying IO error: {0}. The negotiation has already completed. The negotiation has not yet completed. There are too many active security negotiations or secure conversations at the service. Please retry later. Negotiation state already exists for context '{0}'. No AppliesTo element is present in the deserialized RequestSecurityToken/RequestSecurityTokenResponse. There is no pending asynchronous write on this stream. Ensure that there is pending write on the stream or verify that the implementation does not try to complete the same operation multiple times. No binary negotiation was received from the other party. There is no binary negotiation to send to the other party. 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 binding ('{0}', '{1}') has been configured with a MutualCertificateDuplexBindingElement that requires a client certificate. The client certificate is currently missing. The RequestSecurityToken must specify a CloseTarget. Could not find a compatible transport manager for URI '{0}'. The SecurityContextSecurityToken does not have a cookie. No correlation token was found in the security correlation state. No encryption message parts were specified for messages with the '{0}' action. 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. The keyword '{0}' has no equal sign following it. Ensure that each keyword is followed by an equal sign and a value. The object does not support the interface '{0}'. No IPEndpoints were found for host {0}. No clause of type '{0}' was found in the SecurityKeyIdentifier. The KeyInfo value was not found in the encrypted item to find the decrypting token. No KeyInfo in signature to find verification token. RequestedSecurityToken not specified in RequestSecurityTokenResponse. The fault reason does not contain any text translations. The specified nonce is too short. The minimum required nonce length is 4 bytes. The ReplayWindow and ClockSkew cannot be the maximum possible value when replay detection is enabled. There is no negotiation message to send. None of the methods were found for interface {0}. The translation set cannot contain nulls. The action {0} is not supported by this endpoint. Only WS-ReliableMessaging February 2005 messages are processed by this endpoint. No outgoing EndpointAddress is available to check the identity on a message to be sent. No outgoing EndpointAddress is available to check the identity on a received reply. No signature was created because not part of the message matched the supplied message part specification. No primary signature available for supporting token signature verification. No custom principal is specified in the authorization context. The RequestSecurityToken must specify a RenewTarget. No RequestSecurityTokenResponse elements were found. Unable to find a SecurityBindingElement. The SecurityContextSecurityToken does not have a context-id. The server's X509SecurityTokenProvider cannot be null. Final RSTR from other party does not contain a service token. No session token was present in the message. No signature is available in the security header to provide the nonce for replay detection. No signature message parts were specified for messages with the '{0}' action. No signing token is available to do an incoming identity check. The binding ('{0}','{1}') supports streaming which cannot be configured together with message level security. Consider choosing a different transfer mode or choosing the transport level security. 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}. CLSID {0} is not allowed. Not all the signatures in the request message were confirmed in the reply message. An event notification threw an exception. Please refer to InnerException. No timestamp is available in the security header to do replay detection. No Infocard token was found in the ChannelParameters. Infocard requires that the security token be created during channel intialization. There is no transaction in the context of the operation. Could not find an appropriate transport manager for listen URI '{0}'. The security policy expert failed. The provided transport token assertion of type '{0}' did not create a transport token assertion to include the sp:TransportBinding security policy assertion. The operation: {0} is not valid while the object is in closed state. The operation: {0} is not valid while the object is in open state. No type library available for interface Cannot find usable policy alternatives. The required UserNameSecurityToken was not provided. No value. A transaction vote request was completed, but there was no outstanding vote request. The server challenged this request and streamed requests cannot be resubmitted. To enable HTTP server challenges, set your TransferMode to Buffered or StreamedResponse. Could not formulate request message for security session operation '{0}'. The {0} object has been disposed. Object is read-only. Cannot dequeue a '{0}' object while in the Created state. The specified offset exceeds the upper bound of the buffer ({0}). The specified offset exceeds the buffer size ({0} bytes). The OLE Transactions header was invalid or corrupt. 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. A one-way header was expected on this message and none was found. It is possible that your bindings are mismatched. Binding '{0}' is not configured properly. OneWayBindingElement requires an inner binding element that supports IRequestChannel/IReplyChannel or IDuplexSessionChannel. The one-way operation returned a fault message. The reason for the fault was '{0}'. The one-way operation returned a fault message with Action='{0}'. The one-way operation returned a non-null message with Action='{0}'. One way operation {0} cannot not specify a reply action. A response was received from a one-way send over the underlying IRequestChannel. Make sure the remote endpoint has a compatible binding at its endpoint (one that contains OneWayBindingElement). Only body return values are supported currently for protection, MessagePartDescription was specified. The provided SafeArray parameter was passed by value. SafeArray parameters must be passed by reference. Only malformed Messages are supported. Multi-dimensional SafeArray parameters cannot be used. The symmetric security protocol can either be configured with a symmetric token provider and a symmetric token authenticator or an asymmetric token provider. It cannot be configured with both. A VARIANT parameter was passed by value. VARIANT parameters must be passed by reference. The elements of the SafeArray must be of the type VARIANT. The lower bound of the SafeArray was not zero. SafeArrays with a lower bound other than zero cannot be used. Could not open the process token (error=0x{0:X}). Could not open the thread token (error=0x{0:X}). 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. Operation was aborted while establishing a connection to {0}. This operation cannot be done after processing is started. The service operation '{0}' that belongs to the contract with the '{1}' name and the '{2}' namespace does not allow impersonation. This operation is not valid until security negotiation is complete. The method '{0}' could not be found. Ensure that the correct method name is specified. Operation property of OperationAttributeGenerationContext is required to generate an attribute based on settings. The optional WSDL extension element '{0}' from namespace '{1}' was not handled.\r\nXPath: {2} The outer element name must be specified. The outer name of the element extension cannot be empty. Send cannot be called when the session does not expect output. The package full name '{0}' is invalid. The parameter cannot be empty. Unable to log messages. Application may be running in partial trust. Either disable message logging or configure the application to run in full trust. Access to performance counters is denied. Application may be running in partial trust. Either disable performance counters or configure the application to run in full trust. The Service with name '{0}' could not be constructed because the application does not have permission to construct the type: both the Type and its default parameter-less constructor must be public. The Method with name '{1}' in Type '{0}' could not be invoked because the application does not have permission to invoke the method: both the Method and its containing Type must be public. Access to windows management instrumentation (WMI) is denied. Application may be running in partial trust. Either disable WMI or configure the application to run in full trust. There are too many pending secure conversations on the server. Please retry later. QueryInterface succeeded but the persistable type wrapper was null. A metadata section containing policy did not have an identifier so it cannot be referenced. An exception was thrown in a call to a policy export extension.\r\nExtension: {0}\r\nError: {1} An exception was thrown in a call to a policy import extension.\r\nExtension: {0}\r\nError: {1} The type {0} registered as a policy extension does not have a public default constructor. Policy extensions must have a public default constructor ContextBindingElementImporter cannot import policy because PolicyImportContext.BindingElements collection is null. Unreachable policy detected.\r\nA WS-Policy element embedded in WSDL is missing a fragment identifier. This policy cannot be referenced by any WS-PolicyAttachment mechanisms.\r\nXPath:{0} A policy reference was ignored because the URI of the reference was empty. A policy reference was ignored because the required {0} attribute was missing. Message security policy for the '{0}' action requires confidentiality without integrity. Confidentiality without integrity is not supported. Application {0} is marked Pooled. Pooled applications are not supported under COM+ hosting. You have tried to create a channel to a service that does not support .Net Framing. 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 channel demuxer Open failed previously with exception '{0}'. The primary signature must be encrypted. Primary signature must be computed before supporting token signatures. The primary signature is not signed with a derived key. The binding's primary token parameter '{0}' requires key derivation. The primary signature is not signed with a key derived from the encrypted key. The binding's token parameter '{0}' requires key derivation. PrivacyNotice element Version attribute must have an integer value. The proof token was not wrapped correctly in the RequestSecurityTokenResponse. The proof token XML element is not expected in the response. The required '{0}' property on the '{1}' security protocol factory is not set or has an invalid value. The protocol factory cannot create a protocol. Security protocol must be '{0}', type is: '{1}'.; '{0}' protocol can only be used by the Initiator. '{0}' protocol can only be used at the Recipient. The NetworkCredentials provided for the Kerberos Token does not have a valid UserName. The 'provider' argument to the InstanceKey constructor must be a non-empty string which identifies the source of the key data. The 'provider' argument can be null, in which case the default correlation provider name is used. The HTTP proxy authentication credential specified an mutual authentication requirement ({0}) that is stricter than the requirement for target server authentication ({1}). The HTTP proxy authentication credential specified an impersonation level restriction ({0}) that is stricter than the restriction for target server authentication ({1}). The PSHA1 key length '{0}' is invalid. The public key is not an RSA key. Positioned after last element. Positioned before first element. The string value can't be determined because the XPathNodeIterator has been moved past the first node. Context node is not supported in node sequences. The argument to an IXsltContextFunction could not be converted to a string. IXsltContextFunction return type '{0}' not supported. An internal error has occurred. Item already exists. The XPathNodeIterator has been invalidated. XPathNodeIterators passed as arguments to IXsltContextFunctions are only valid within the function. They cannot be cached for later use or returned as the result of the function. XPathNavigator must be a SeekableXPathNavigator. The function '{0}' is not implemented. XPathNavigator positions cannot be compared. IXsltContextVariables cannot return null. IXsltContextVariable type '{0}' not supported. The receive context, {0}, is in the {1} state. Receive contexts cannot be used for sending delayed acks unless they are in the Received state. The receive context, {0}, cannot be used for sending delayed acks because it is in the Faulted state. The receive context, {0}, is in an unsupported state '{1}'. This indicates an internal error in the implementation of that receive context. The request message in the request context received from channel '{0}' is null. The {0}Response was received when the {0} request had not been sent. This is a WS-ReliableMessaging protocol violation. The reliable session cannot continue. Receive request on local address {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout. Receive request timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. The channel received an unexpected fault input message while closing. The fault reason given is: '{0}' 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. 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. Receive on local address {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout. Receive timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. Receive timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. Application {0} has recycling enabled. Recycling of applications is not supported under COM+ hosting. The requested resouce has not changed and should be taken from cache. RedirectionType 'Cache' does not allow any RedirectionLocation objects be passed into the constructor. The requested resource has been moved. {0} {0} ({1}) At least one RedirectionLocation must be provided for this RedirectionType. The requested resource has moved to one of the following locations:\n{0} The requested resource must be accessed through one of the following intermediary service locations:\n{0} Invalid RefreshInterval value of {0}; it must be greater than zero The following remote identity failed verification: '{0}'. Stream Security is required at {0}, but no security context was negotiated. This is likely caused by the remote endpoint missing a StreamSecurityBindingElement from its binding. The renew security session message does not have the session token as a supporting token. There is no handler registered for session token renew event. Repeated moniker keyword. A reply has already been sent from this RequestContext. The reply was not signed with the required signing token. 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 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. The requestContext has been aborted. This collection holds response headers and cannot contain the specified request header '{0}'. The initialization process of the request message timed out after {0}. To increase this quota, use the '{1}' property on the '{2}'. A reply message cannot be created because the request message does not have a MessageID. The RequestSecurityToken message does not match the endpoint filters the service '{0}' is expecting incoming messages to match. This may be because the RequestSecurityToken was intended to be sent to a different service. 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. The interface with IID {0} is not configured in the COM+ catalog and cannot be exposed as a web service. The interface with IID {0} has no methods configured in the COM+ catalog and cannot be exposed as a web service. Attribute '{0}' is required on element '{1}'. The '{0}' required message part was not encrypted. The '{0}', '{1}' required message part was not encrypted. The '{0}' required message part was not signed. The '{0}', '{1}' required message part was not signed. The security header element '{0}' with the '{1}' id must be signed. The '{0}' security token with the '{1}' attachment mode must be encrypted. The '{0}' security token with the '{1}' attachment mode must be signed. The signature must be in the security header. Required timestamp missing in security header. The required WSDL extension element '{0}' from namespace '{1}' was not handled. The '{0}' binding with the '{1}' namespace is configured to issue cookie security context tokens. COM+ Integration services does not support cookie security context tokens. The Peer resolver threw an exception. Please refer to InnerException. Resolving an External reference token requires appropriate SecurityTokenParameters to be specified. 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}'. The content type {0} of the message is not supported by the encoder. This collection holds request headers and cannot contain the specified response header '{0}'. The requested resource is available. Failed to revert impersonation. {0} The reverting operation failed with the exception '{0}'. The endpoint at {0} has stopped accepting wsrm sessions. AcceleratedTokenAuthenticator does not expect RequestSecurityTokenResponse from the client. The negotiation RequestSecurityTokenResponse has a different context from the authenticator RequestSecurityTokenResponse. The RequestSecurityTokenResponse CombinedHash is incorrect. The authenticator was not included in the final leg of negotiation. The RequestSecurityTokenResponse has multiple RequestedSecurityToken elements. The RequestSecurityTokenResponse has multiple RequestedProofToken elements. KeySize element not present in RequestSecurityTokenResponse. DispatchOperation requires Invoker. On DuplexSecurityProtocolFactory, the same protocol factory cannot be set for the forward and reverse directions. There was a validation error on a schema generated during export:\r\n Source: {0}\r\n Line: {1} Column: {2}\r\n Validation Error: {3} Context protocol was unable to parse the context header. Nodes disallowed by the context header schema were found inside the context header. The 'scopeName' argument to the InstanceKey constructor must be a non-empty string which indicates the scope of uniqueness for the key. Durable services use the service namespace and name as the scope of uniqueness. Error decoding the Cookie element of SecurityContextSecurityToken. Issuing cookie SecurityContextSecurityToken is not supported. The SecurityContextSecurityToken's Cookie element either does not contain '{0}' or has a wrong value for it. Error parsing SecurityContextSecurityToken Cookie XML. Could not establish secure channel for SSL/TLS with authority '{0}'. Cannot create security binding element based on configuration data. The secure conversation bootstrap requires another secure conversation which is not supported. A secure conversation cancellation is not allowed by the binding. The configured SecureConversation version does not support sessions. Use WSSecureConversationFeb2005 or above. Cannot create security binding element based on the configuration data. When secure conversation authentication mode is selected, the secure conversation bootstrap binding element must also be specified. Security channel or listener factory creation failed. Secure conversation security token parameters do not specify the bootstrap security binding element. The security algorithm suite was not specified on '{0}'. The '{0}' dynamic link library (dll) failed to load. SecurityAuditBehavior is not supported on the channel factory. Writing audit messages to the Security log is not supported by the current platform. You must write audit messages to the Application log. A security policy was imported for the endpoint. The security policy contains requirements that cannot be represented in a Windows Communication Foundation configuration. Look for a comment about the SecurityBindingElement parameters that are required in the configuration file that was generated. Create the correct binding element with code. The binding configuration that is in the configuration file is not secure. This SecurityProtocol instance was not set up to process incoming messages. This SecurityProtocol instance was not set up to process outgoing messages. The SecurityBinding for the ('{0}','{1}') binding for the ('{2}','{3}') contract only supports the OneWay operation. 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. ExtendedProtectionPolicy specified a PolicyEnforcement of 'Always' and a ChannelBinding was not found. This prevents the ExtendedProtectionPolicy from being enforced. Change the binding to make a ChannelBinding available, for StandardBindings use a SecurityMode of TransportWithMessageCredential and a ClientCredential type of Windows. For CustomBindings use SspiNegotiationOverTransport or KerberosOverTransport. Alternatively, specify a PolicyEnforcement of 'Never'. ExtendedProtectionPolicy specified a PolicyEnforcement of 'Always' which is not supported for the authentication mode requested. This prevents the ExtendedProtectionPolicy from being enforced. For StandardBindings use a SecurityMode of TransportWithMessageCredential and a ClientCredential type of Windows. For CustomBindings use SspiNegotiationOverTransport or KerberosOverTransport. Alternatively, specify a PolicyEnforcement of 'Never'. The security channel listener was not specified on '{0}'. Cannot start impersonation because the SecurityContext for the UltimateReceiver role from the request message with the '{0}' action is not mapped to a Windows identity. The SecurityContextSecurityToken with context-id={0} (key generation-id={1}) has expired. The SecurityContextSecurityToken with context-id={0} (no key generation-id) has expired. The SecurityContextSecurityToken with Context-id={0} (generation-id={1}) has expired. The SecurityContextSecurityToken with Context-id={0} (no key generation-id) has expired. SecurityContext for the UltimateReceiver role is missing from the SecurityContextProperty of the request message with action '{0}'. The SecurityContextSecurityToken with context-id={0} (key generation-id={1}) is not registered. Server '{0}' sent back a fault indicating it is in the process of shutting down. Please see the inner exception for fault details. Security header is empty. The listener is not accepting new secure conversations because it is closing. The server is not accepting new secure conversations currently because it is closing. Please retry later. The security negotiation with '{0}' cannot be initiated because the confidential endpoint address header ('{1}', '{2}') cannot be encrypted during the course of the negotiation. The security negotiation message with action '{0}' is larger than the maximum allowed buffer size '{1}'. If you are using a streamed transport consider increasing the maximum buffer size on the transport. The security protocol '{0}' cannot do replay detection. Duplex security is not supported by the security protocol factory '{0}'. Request-reply security is not supported by the security protocol factory '{0}'. The security protocol factory must be set before this operation is performed. The SecurityContextSecurityToken's key needs to be renewed. Server '{0}' sent back a fault indicating it is too busy to process the request. Please retry later. Please see the inner exception for fault details. The security session was terminated This may be because no messages were received on the session for too long. The security session with id '{0}' is already pending. The receiver sent back a security session fault message. Retry the request. The security session id '{0}' is already present in the filter table. The session key must be renewed before it can secure application messages. Cannot create a security session. Retry later. No security session listener was found for message with action '{0}'. No security session with id '{0}' is pending. Security session protocol factory must be set before this operation is performed. The security session requires a security token authenticator that implements '{0}'. '{1}' does not implement '{0}'. Security sessions require all messages to be signed. The security session requires a security token resolver that implements '{1}'. The security token resolver '{0}' does not implement '{1}'. The security settings lifetime manager was not specified on '{0}'. The security standards manager was not specified on '{0}'. The DataProtectionSecurityStateEncoder is unable to decode the byte array. Ensure that a 'UserProfile' is loaded, if this is a 'web farm scenario' ensure all servers are running as the same user with the roaming profiles or provide a custom SecurityStateEncoder'. The DataProtectionSecurityStateEncoder is unable to encode the byte array. Ensure that a 'UserProfile' is loaded, if this is a 'web farm scenario' ensure all servers are running as the same user with the roaming profiles or provide a custom SecurityStateEncoder'. A security token ('{0}', '{1}') was found outside the security header. The message may have been altered in transit. The security token manager cannot create a token authenticator for requirement '{0}'. The security token manager cannot create a token provider for requirement '{0}'. The security token manager cannot create a token serializer for security token version '{0}'. The SecurityTokenProvider '{0}' could not resolve the token. The CloneCore method of {0} type returned an invalid result. The binding ('{0}', '{1}') is configured with a security token parameter '{2}' that has an incompatible security token inclusion mode '{3}'. Specify an alternate security token inclusion mode (for example, '{4}'). When authentication schemes 'Basic' and also '{0}' are enabled, the value of IncludeWindowsGroups for Windows ('{1}') and UserName authentication ('{2}') must match. Please consider using the same value in both places. The token requirement does not contain a property '{0}'. The token requirement has an unexpected type '{1}' for property '{0}'. The expected property type is '{2}'. The binding ('{0}','{1}') for contract ('{2}','{3}') has been configured with an incompatible security version that does not support unattached references to EncryptedKeys. Use '{4}' or higher as the security version for the binding. The SecurityVersion '{0}' does not support signature confirmation. Use a later SecurityVersion. The '{0}','{1}' binding for the '{2}','{3}' contract is configured with a security version that does not support external references to X.509 tokens using the certificate's thumbprint value. Use '{4}' or higher as the security version for the binding. A filter has attempted to access the body of a Message. Use a MessageBuffer instead if body filtering is required. XML unique ID not supported. The position is not valid for this navigator. Cannot call '{0}' on a non-atomized navigator. Not allowed to override prefix '{0}'. You cannot Send messages on a channel after CloseOutputSession has been called. Security token parameters must be specified with supporting tokens for each message. Unexpected code path for server security application, sending outgoing message on Recipient. Sending to via {0} timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout. The Sequence is closed and cannot accept new messages. The RM Source could not transfer the last message within the timeout the user specified. The server received a TerminateSequence message before all reply sequence messages were acknowledged. This is a violation of the reply sequence acknowledgement protocol. The wsrm:TerminateSequence protocol message was transmitted before the sequence was successfully completed. The inactivity timeout of ({0}) has been exceeded. The user specified maximum retry count for a particular message has been exceeded. Because of this the reliable session cannot continue. All of the reply sequence's messages must be acknowledged prior to closing the request sequence. This is a violation of the reply sequence's delivery guarantee. The session cannot continue. The necessary size to buffer a sequence message has exceeded the configured buffer quota. Because of this the reliable session cannot continue. A reply message was received with no acknowledgement. The wsrm:LastMsgNumber value is too small. A message with a larger sequence number has already been received. The RM destination received an acknowledgement message. The RM destination does not process acknowledgement messages. The RM source received an AckRequested message. The RM source does not process AckRequested messages. The RM source received an CloseSequence message. The RM source does not process CloseSequence messages. The RM destination received an CloseSequenceResponse message. The RM destination does not process CloseSequenceResponse messages. The RM source received a CreateSequence request. The RM source does not process CreateSequence requests. The RM destination received multiple CreateSequence requests with different OfferId values over the same session. The RM destination received a CreateSequenceResponse message. The RM destination does not process CreateSequenceResponse messages. The RM source received multiple CreateSequenceResponse messages with different sequence identifiers over the same session. The RM source received a TerminateSequence message. The RM source does not process TerminateSequence messages. The RM destination received a TerminateSequenceResponse message. The RM destination does not process TerminateSequenceResponse messages. An unknown error occurred while trying to add a sequence message to the window. The RM source does not support an RM destination initiated termination since messages can be lost. The reliable session cannot continue. The serialized token version {0} is unsupported. The recipient did not provide its certificate. This certificate is required by the TLS protocol. Both parties must have access to their certificates. {0}.OnCloseMessageReceived when state == Created. The server at {0} rejected the session-establishment request. The server rejected the upgrade request. Server '{0}' is too busy to process this request. Try again later. Operation Action={0} The service certificate is not provided for target '{0}'. Specify a service certificate in ClientCredentials. The service certificate is not provided. Specify a service certificate in ServiceCredentials. At least one operation on the '{0}' contract is configured with the TransactionFlowAttribute attribute set to Mandatory but the channel's binding '{1}' is not configured with a TransactionFlowBindingElement. The TransactionFlowAttribute attribute set to Mandatory cannot be used without a TransactionFlowBindingElement. Service '{0}' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element. Operations marked with IsOneWay=true must not declare output parameters, by-reference parameters or return values. The service's security session was not able to close its output session within the configured timeout ({0}). The service's security session did not receive a 'close' message from the client within the configured timeout ({0}). The COM+ string in the .svc file was formatted incorrectly. (The string is \"{0}\".) 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}'. The session was closed before message transfer was complete. Cannot renew the security session key. Session Key Renewal is not supported. The session security token provider returned a token of type '{0}'. The token type expected is '{1}'. The session security token authenticator returned a token of type '{0}'. The token type expected is '{1}'. The session token was not closed by the server. The Session value '{0}' is invalid. Please specify 'CurrentSession','ServiceSession' or a valid non-negative Windows Session Id. The operations {0} and {1} have the same action ({2}). Every operation must have a unique action value. Cannot create a typed message due to action mismatch, expecting {0} encountered {1} Part {1} in message {0} cannot be exported with RPC or encoded since its type is anonymous. The IAsyncResult returned from Begin and the IAsyncResult supplied to the Callback are on different objects. These are required to be the same object. 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. Method '{0}' in class '{1}' has bad parameter metadata: a pass-by-value parameter is marked with the 'out' parameter mode. There was a problem reading the MetadataSet argument: a MetadataSection instance with identifier '{0}' and dialect '{1}' has a Metadata property whose type does not match the dialect. The expected Metadata type for this dialect is '{2}' but was found to be '{3}'. The URL supplied to ServiceMetadataBehavior via the ExternalMetadataLocation property or the externalMetadataLocation attribute in the serviceMetadata section in config was a relative URL and there is no base address with which to resolve it. '{0}' was specified. The URI supplied to ServiceMetadataBehavior via the ExternalMetadataLocation property or the externalMetadataLocation attribute in the serviceMetadata section in config must be a relative URI or an absolute URI with an http or https scheme. '{0}' was specified, which is a absolute URI with {1} scheme. When calling the CreateFromPolicy method, the policy argument must be an XmlElement instance with LocalName '{1}' and NamespaceUri '{0}'. This XmlElement has LocalName '{3}' and NamespaceUri '{2}'. Metadata contains a reference that cannot be resolved: '{0}'. The TransactionProtocol setting was not understood. A supported protocol must be specified. The binding specified to do metadata exchange does not contain a TransportBindingElement. The binding (Name={0}, Namespace={1}) does not contain a TransportBindingElement. Binding name cannot be null or empty. The binding associated with ServiceMetadataBehavior or ServiceDebugBehavior is not supported. The inner binding elements used by this binding must support IReplyChannel. Verify that HttpGetBinding/HttpsGetBinding (on ServiceMetadataBehavior) and HttpHelpPageBinding/HttpsHelpPageBinding (on ServiceDebugBehavior) are supported. The scheme '{0}' used by binding {1} does not match the required scheme '{2}'. Body object cannot be null in message {0} Type {0} cannot inherit from any class other than object to be used as body object in RPC style. Type {0} implements interface {1} which is not supported for body object in RPC style. 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. 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 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. The dispatch instance for duplex callbacks cannot be activated - you must provide an instance. ServiceHostBase's AddBaseAddress method cannot be called after the InitializeDescription method has completed. Cannot make a call on this channel because a call to Open() is in progress. The MetadataExchangeClient can only get metadata from http and https MetadataLocations. It cannot get metadata from '{0}'. The MetadataExchangeClient can only get metadata from absolute addresses. It cannot get metadata from '{0}'. The configured policy specifies more than one TransactionProtocol across the operations. A single TransactionProtocol for each endpoint must be specified. The MetadataExchangeClient can only get metadata from http or https addresses when using MetadataExchangeClientMode HttpGet. It cannot get metadata from '{0}'. Generating message contract since the operation {0} is neither RPC nor document wrapped. Generating message contract since the wrapper name ({1}) of message {0} does not match the default value ({2}) Generating message contract since the wrapper namespace ({1}) of message {0} does not match the default value ({2}) Generating message contract since element name {0} from namespace {1} is not marked nillable Headers are not supported in RPC encoded format. Headers are ignored in message {0}. Generating message contract since message {0} has headers Generating message contract since the operation {0} has untyped Message as argument or return type Generating message contract since message {0} requires protection. Generating message contract since message part namespace ({0}) does not match the default value ({1}) Generating message contract since the operation has multiple return values. There are two contracts listening on the same binding ({2}) and address with conflicting settings. Specifically, the contract '{0}' specifies SessionMode.NotAllowed while the contract '{1}' specifies SessionMode.Required. You should either change one of the SessionMode values or specify a different address (or ListenUri) for each endpoint. This collection does not support setting extensions by index. Please consider using the InsertItem or RemoveItem methods. This ChannelDispatcher is not currently attached to the provided ServiceHost. Cannot add a ChannelDispatcher to more than one ServiceHost. Cannot open ChannelDispatcher because it is not attached to a ServiceHost. Cannot open ChannelDispatcher because it is does not have a MessageVersion set. The ChannelDispatcher at '{0}' is unable to open its IChannelListener as there are no endpoints for the ChannelDispatcher. The ChannelDispatcher at '{0}' with contract(s) '{1}' is unable to open its IChannelListener. ApplyConfiguration requires that the Endpoint property be initialized. Either provide a valid ServiceEndpoint in the CreateDescription method or override the ApplyConfiguration method to provide an alternative implementation. 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. The Address property on ChannelFactory.Endpoint was null. The ChannelFactory's Endpoint must have a valid Address specified. 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 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. The type argument passed to the generic ChannelFactory class must be an interface type. 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. 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. Close process timed out waiting for service dispatch to complete. Array of type {0} is not supported. Can only store into ArgBuilder or LocalBuilder. Got: {0}. Expecting End {0}. {0} is not assignable from {1}. No conversion possible to {0}. Internal Error: Unrecognized constant type {0}. CODEGEN: {0} This collection does not support setting items by index. This operation is not supported because the collection is read-only. The collection of type {0} does not support values of type {1}. Could not find endpoint element with name '{0}' and contract '{1}' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element. Could not find default endpoint element that references contract '{0}' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element. The endpoint configuration section for contract '{0}' with name '{1}' could not be loaded because more than one endpoint configuration with the same name and contract were found. Please check your config and try again. An endpoint configuration section for contract '{0}' could not be loaded because more than one endpoint configuration for that contract was found. Please indicate the preferred endpoint configuration section by name. The ConfigurationName property must be a non-empty string. Top level XML element with name {0} in namespace {1} cannot reference {2} type because it already references a different type ({3}). Use a different operation name or MessageBodyMemberAttribute to specify a different name for the Message or Message parts. Duplicate top level XML Schema type with name {0} in namespace {1}. The value of OperationContext.Current is not the OperationContext value installed by this OperationContextScope. ContractDescription's Name must be a non-empty string. ContractDescription '{0}' has zero IsInitiating=true operations; a contract must have at least one IsInitiating=true operation. ContractDescription '{0}' has zero operations; a contract must have at least one operation. 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. 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. SynchronizedReadOnlyCollection's CopyTo only works if the underlying list implements ICollection. 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. The InstanceContext provided to the ChannelFactory contains a UserObject that does not implement the CallbackContractType '{0}'. 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. 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. This CreateChannel overload cannot be called on this instance of DuplexChannelFactory, as the InstanceContext provided to the DuplexChannelFactory does not contain a valid UserObject. 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 CustomBinding on the ServiceEndpoint with contract '{0}' lacks a TransportBindingElement. Every binding must have at least one binding element that derives from TransportBindingElement. The Scheme cannot be computed for this binding because this CustomBinding lacks a TransportBindingElement. Every binding must have at least one binding element that derives from TransportBindingElement. DataContractSerializer does not support collection specified on element '{0}' Invalid OperationFormatUse specified in the OperationFormatStyle of operation {0}, DataContractSerializer supports only Literal. The formatter threw an exception while trying to deserialize the message: {0} This operation is not possible since the dictionary is empty. 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. In operation '{0}', cannot return null from methods that return Message. The DispatchRuntime.EnsureOrderedDispatch property is set to true, but the DispatchRuntime.ConcurrencyMode is not set to Single. EnsureOrderedDispatch requires the use of ConcurrencyMode.Single. Fault could not be loaded as the Use setting is Encoded and it references a schema definition using Element attribute. To fix the problem, change the Use setting to Literal. 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. <P class='intro'><B>C#</B></P> The service encountered an error. Use the 'client' variable to call operations on the service. Always close the client. You have created a service.<P class='intro'>To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:</P> You have created a service.<P class='intro'>To test this service, you will need to create a client and use it to call the service; however, metadata publishing via ?WSDL is currently disabled. This can be enabled via the service's configuration file. </P> This will generate a configuration file and a code file that contains the client class. Add the two files to your client application and use the generated client class to call the Service. For example:<BR/> You can also access the service description as a single file: {0} Service Service Note: the service name must match the configuration name for the service implementation. Add the following endpoint. Note: your service must have an http base address to add this endpoint. Add the following element to your service behavior configuration. This is a Windows&#169; Communication Foundation service.<BR/><BR/><B>Metadata publishing for this service is currently disabled.</B><BR/><BR/>If you have access to the service, you can enable metadata publishing by completing the following steps to modify your web or application configuration file:<BR/><BR/>1. Create the following service behavior configuration, or add the &lt;serviceMetadata&gt; element to an existing service behavior configuration: 2. Add the behavior configuration to the service: Note: the service name must match the configuration name for the service implementation.<BR/><BR/>3. Add the following endpoint to your service configuration: Note: your service must have an http base address to add this endpoint.<BR/><BR/>The following is an example service configuration file with metadata publishing enabled: For more information on publishing metadata please see the following documentation: <a href=\"http://go.microsoft.com/fwlink/?LinkId=65455\">http://go.microsoft.com/fwlink/?LinkId=65455</a>. <P class='intro'><B>Visual Basic</B></P> This service has multiple endpoints listening at '{0}' which share the same initiating action '{1}'. As a result, messages with this action would be dropped since the dispatcher would not be able to determine the correct endpoint for handling the message. Please consider hosting these Endpoints at separate ListenUris. Message part {0} in namespace {1} appears more than once in Message. The endpoint's address is not specified. The IEndpointBehavior '{0}' cannot be used on the server side; this behavior can only be applied to clients. The endpoint's binding is not specified. The endpoint's contract is not specified. This EndpointDispatcher is not currently attached to the provided ChannelDispatcher. Cannot add EndpointDispatcher to more than one ChannelDispatcher. Could not find a base address that matches scheme {0} for the endpoint with binding {1}. Registered base address schemes are [{2}]. Error creating a reader for the MTOM message Server returned an invalid SOAP Fault. Please see InnerException for more details. There was an error in deserializing one of the headers in message {0}. Please see InnerException for more details. Error in deserializing body of reply message for operation '{0}'. Error in deserializing body of reply message for operation '{0}'. {1} Error in deserializing body of request message for operation '{0}'. Error in deserializing body of request message for operation '{0}'. {1} An error occurred while loading attribute '{0}' on method '{1}' in type '{2}'. Please see InnerException for more details. An error occurred while loading attribute '{0}' on parameter {1} of method '{2}' in type '{3}'. Please see InnerException for more details. An error occurred while loading attribute '{0}' on type '{1}'. Please see InnerException for more details. An error occurred while loading attribute '{0}'. Please see InnerException for more details. There was an error in serializing body of message {0}: '{1}'. 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. --- End of inner ExceptionDetail stack trace --- An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: Internal Error: Message must be a valid IMethodCallMessage. The specified ContractDescription could not be exported to WSDL because the Type property of the MessagePartDescription with name '{1}' in the OperationDescription with name '{0}' is not set. The Type property must be set in order to create WSDL. Fault named {0} in operation {1} cannot be imported. {2} In operation {0}, more than one fault is declared with detail type {1} In operation {0}, more than one fault is declared with element name {1} in namespace {2} {0}: {1} (Fault Detail is equal to {2}). The creator of this fault did not specify a Reason. In operation {0}, the schema type corresponding to the fault detail type {1} is anonymous. Please set Fault name explicitly to export anonymous types. Only a '{0}' using '{1}' or '{2}' is supported in this scenario. Header name cannot be null or empty. 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. 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. 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. 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 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. Message {0} must not have headers to be used in RPC encoded style. This value cannot be changed after the ChannelFactory has opened. This value cannot be changed after the first ClientBase of type '{0}' has been created. This value cannot be changed after the ServiceHost has opened. {0} cannot be changed after the ServiceHost has opened. Operation {0} binding {1} has extra part {2} that is not present in other bindings Style {1} on header {0} does not match expected style {2}. All parts of message in operation {0} must either contain type or element. Style {1} inferred from messages in operation {0} does not match expected style {2} specified via bindings. Bindings for operation {0} cannot specify different use and style values. Binding {1} specifies use {2} and style {3} while binding {4} specifies use {5} and style {6}. Extensions for operation {0} in binding {1} cannot specify different use values. Fault bindings for operation {0} in binding {1} cannot specify different use values. Message bindings for operation {0} in binding {1} cannot specify different use values. MessageVersion '{0}' is not supported in this scenario. Only MessageVersion '{1}' is supported. AllowInitializationUI was set to false for this channel, but the channel is configured to use the '{0}' as an interactive initializer. 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. Service implementation object invoked with wrong number of input parameters, operation expects {0} parameters but was called with {1} parameters. Service implementation object invoked with null input parameters, but operation expects {0} parameters. The InstanceContext has no provider for creating Service implementation objects. This OperationContextScope is being disposed out of order. 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. 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. IAsyncResult's State must be the state argument passed to your Begin call. The CallbackContract {0} is invalid because it is not an interface type. IAsyncResult not provided or of wrong type. Invalid IContextChannel passed to OperationContext. Must be either a server dispatching channel or a client proxy channel. This OperationContextScope is being disposed on a different thread than it was created. 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}' The OperationFormatter could not deserialize any information from the Message because the Message is empty (IsEmpty = true). There was an error while trying to deserialize parameter {0}:{1}. Please see InnerException for more details. There was an error while trying to deserialize parameter {0}:{1}. The InnerException message was '{2}'. Please see InnerException for more details. There was an error while trying to serialize parameter {0}:{1}. The InnerException message was '{2}'. Please see InnerException for more details. 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. MessageHeaderArrayAttribute found on member {0} is not a single dimensional array. 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='*'. 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='*'. XmlSerializer attribute {0} is not valid in {1}. Only SoapElement attribute is supported. 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>. For request in operation {0} to be a stream the operation must have a single parameter whose type is Stream. For response in operation {0} to be a stream the operation must have a single out parameter or return value whose type is Stream. 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. Buffer size must be at least {0} bytes. The PrimitiveOperationFormatter was given a parameter or return type which it does not support. The WSDL binding named {0} is not valid because no match for operation {1} was found in the corresponding portType definition. The WSDL binding named {0} is not valid because an operation binding doesn't have a name specified. XmlSerializer attribute {0} is not valid in {1}. Only XmlElement, XmlArray, XmlArrayItem and XmlAnyElement attributes are supported in MessageContract when IsWrapped is false. XmlSerializer attribute {0} is not valid in {1}. Only XmlElement, XmlArray, XmlArrayItem, XmlAnyAttribute and XmlAnyElement attributes are supported when IsWrapped is true. {0} must contain either a single ServiceKnownTypeAttribute that refers to a method or a set of ServiceKnownTypeAttributes, each specifying a valid type The return type of method {1} in type {2} must be IEnumerable<Type> to be used by ServiceKnownTypeAttribute in {0} ServiceKnownTypeAttribute in {0} refers to a method {1} that does not exist in type {2} KnownType cannot be null in operation {0} The MaximumResolvedReferences property of MetadataExchangeClient must be greater than or equal to one. '{0}' was specified. Cannot create a typed message from type '{0}'. The functionality only valid for types decorated with MessageContractAttribute. 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. The message cannot be deserialized into MessageContract type {0} since it does not have a default (parameterless) constructor. MessageOperationFormatter cannot serialize faults. Instance of MessagePartDescription Name='{0}' Namespace='{1}' cannot be used in this context: required 'Type' property was not set. The MetadataExchangeClient could not create an IChannelFactory for: address='{0}', dialect='{1}', and identifier='{2}'. The MetadataExchangeClient instance could not be initialized because no Binding is available for scheme '{0}'. You can supply a Binding in the constructor, or specify a configurationName. The MetadataExchangeClient could not create an HttpWebRequest for: address='{0}', dialect='{1}', and identifier='{2}'. The MetadataExchangeClient was not supplied with a MetadataReference or MetadataLocation from which to get metadata. You must supply one to the constructor, to the GetMetadata method, or to the BeginGetMetadata method. The value '{0}' is not valid for the Location property. The Location property must be a valid absolute or relative URI. The MetadataResolver cannot recieve an empty contracts argument to the Resolve or BeginResolve methods. You must supply at least one ContractDescription. The contracts argument to the Resolve or BeginResolve methods cannot contain a null ContractDescription. The ContractDescriptions in contracts must all have unique Name and Namespace pairs. More than one ContractDescription had the pair Name='{0}' and Namespace='{1}'. 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. ServiceHost implementation type {0} does not implement ServiceContract {1}. 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. A DispatchOperation (or ClientOperation) can only be added to its parent DispatchRuntime (or ClientRuntime). No Action header was found with namespace '{0}' for the given message. The callback passed to operation '{0}' was called more than once. This indicates an internal error in the implementation of that operation. Calling Post() on '{0}' resulted in multiple callbacks. This indicates a problem in '{0}'. A ServiceContract has more the one operation with an Action of \"*\". A ServiceContract can have at most one operation an Action = \"*\". The Service contains multiple ServiceEndpoints with different ContractDescriptions which each have Name='{0}' and Namespace='{1}'. Either provide ContractDescriptions with unique Name and Namespaces, or ensure the ServiceEndpoints have the same ContractDescription instance. Part {1}:{0} is repeating and is not supported in Soap Encoding. Method {0} in type {1} has more than one header part of type array of XmlElement. The SetTransactionComplete method was wrongly called more than once in the operation '{0}' on contract '{1}'. The SetTransactionComplete method can only be called once. This is an invalid scenario and the current transaction was aborted. The Name property must be a non-empty string. Cannot handle invocation of {0} on interface {1} because the OperationSelector on ClientRuntime is null. TransactedBatchingBehavior validation failed. Service cannot be started. Transacted batching requires ServiceBehavior.ReleaseServiceInstanceOnTransactionComplete to be false. TransactedBatchingBehavior validation failed. Service or client cannot be started. Transacted batching is not supported for session contracts. Remove transacted batching behavior from the endpoint or define a non-sessionful contract. 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. 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. 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 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 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. The '{0}' service is configured with EnsureOrderedDispatch set to true, but the ConcurrencyMode is not set to Single. EnsureOrderedDispatch requires the use of ConcurrencyMode.Single. The WS-Addressing \"none\" value is not valid for the August 2004 version of WS-Addressing. An object that is not an exception was thrown. The operation '{0}' cannot be the first operation to be called because IsInitiating is false. The service implementation object was not initialized or is not available. There was no CLR type specified for parameter {0}, preventing the operation from being generated. Extension {0} prevented call to operation '{1}' from replying by setting the reply to null. Formatter {0} returned a null reply message for call to operation '{1}'. The one-way operation '{1}' on ServiceContract '{0}' is configured for transaction flow. Transactions cannot be flowed over one-way operations. 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. OperationBehaviorAttribute can only go on the service class, it cannot be put on the ServiceContract interface. Method '{0}' on type '{1}' violates this. The ReleaseInstanceMode property on OperationBehaviorAttribute can only be set on non-callback operations. Method '{0}' violates this. 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. Method '{1}' has {0}, but enclosing type '{2}' does not have ServiceContractAttribute. {0} can only be used on methods in ServiceContractAttribute types. OperationDescription's Name must be a non-empty string. OperationDescription '{0}' is invalid because its Messages property contains an invalid number of MessageDescription instances. Each OperationDescription must have one or two messages. 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 'parameters' argument must be an array of one element. The 'parameters' argument must be an array that contains a single Message object. All parameter names used in operations that make up a service contract must not be null. The 'parameters' argument must be either null or an empty array. Message part name {0} is not unique in an RPC Message. In operation '{0}', cannot pass null to methods that take Message as input parameter. Required message property '{0}' is missing from the IncomingProperties collections of the received message. Ensure that when the receive context is enabled on the binding, the created channel ensures that '{0}' is present on all received messages. The contract '{0}' has at least one operation annotated with '{1}', but the binding used for the contract endpoint at address '{2}' does not support required binding property '{3}'. Please ensure that the binding used for the contract supports the ReceiveContext capability. The contract name '{0}' could not be found in the list of contracts implemented by the service '{1}'. In order to add an endpoint to the service '{0}', a non-empty contract name must be specified. The contract name 'IMetadataExchange' could not be found in the list of contracts implemented by the service {0}. Add a ServiceMetadataBehavior to the configuration file or to the ServiceHost directly to enable support for this contract. An endpoint for type '{0}' could not be added because the ServiceHost instance was not initialized properly. In order to add endpoints by Type, the CreateDescription method must be called. If you are using a class derived from ServiceHost, ensure that the class is properly calling base.CreateDescription. A reply message was received for operation '{0}' with action '{1}'. However, your client code requires action '{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. The request message has FaultTo='{0}' but IContextChannel.RemoteAddress is '{1}'. When ManualAddressing is false, these values must be the same, null, or EndpointAddress.AnonymousAddress because sending a reply to a different address than the original sender can create a security risk. If you want to process such messages, enable ManualAddressing. The request message has From='{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 From on the message. The request message has From='{0}' but IContextChannel.RemoteAddress is '{1}'. When ManualAddressing is false, these values must be the same, null, or EndpointAddress.AnonymousAddress because sending a reply to a different address than the original sender can create a security risk. If you want to process such messages, enable ManualAddressing. 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 request message has ReplyTo='{0}' but IContextChannel.RemoteAddress is '{1}'. When ManualAddressing is false, these values must be the same, null, or EndpointAddress.AnonymousAddress because sending a reply to a different address than the original sender can create a security risk. If you want to process such messages, enable ManualAddressing. 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.\" 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. 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. Required runtime property '{0}' is not initialized on DispatchRuntime. Do not remove ServiceBehaviorAttribute from ServiceDescription.Behaviors or ensure that you include a third-party service behavior that supplies this value. The MetadataExchangeClient has resolved more than MaximumResolvedReferences. The 'result' argument must be of type Message. Could not revert impersonation on current thread. Continuing would compromise system security. Terminating process. RPC Message {1} in operation {0} has an invalid body name {2}. It must be {3} RPC Message {1} in operation {0} must have a single MessageBodyMember. There was a problem loading the XSD documents provided: a reference to a schema element with name '{0}' and namespace '{1}' could not be resolved because the element definition could not be found in the schema for targetNamespace '{1}'. Please check the XSD documents provided and try again. There was a problem loading the XSD documents provided: a reference to a schema type with name '{0}' and namespace '{1}' could not be resolved because the type definition could not be found in the schema for targetNamespace '{1}'. Please check the XSD documents provided and try again. Schema with target namespace '{0}' could not be found. SecurityContextProperty is missing from the request Message, this may indicate security is configured incorrectly. 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. 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. 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 contract type {0} is not attributed with ServiceContractAttribute. In order to define a valid contract, the specified type (either contract interface or service class) must be attributed with ServiceContractAttribute. In order to generate configuration information using the GenerateServiceEndpoint method, the ServiceContractGenerator instance must have been initialized with a valid Configuration object. Endpoints cannot be added after the ServiceHost has been opened/faulted/aborted/closed. Endpoints cannot be added before the Description property has been initialized. ApplyConfiguration requires that the Description property be initialized. Either provide a valid ServiceDescription in the CreateDescription method or override the ApplyConfiguration method to provide an alternative implementation. InitializeRuntime requires that the Description property be initialized. Either provide a valid ServiceDescription in the CreateDescription method or override the InitializeRuntime method to provide an alternative implementation. LoadConfigurationSection requires that the Description property be initialized. Provide a valid ServiceDescription in the CreateDescription method. InitializeDescription must be called with a serviceType or singletonInstance parameter. ServiceHost only supports class service types. The ChannelDispatcher with ListenUri '{0}' has endpoints with the following contracts: {1}. Metadata endpoints cannot share ListenUris. The conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config. The HttpGetEnabled property of ServiceMetadataBehavior is set to true and the HttpGetUrl property is a relative address, but there is no http base address. Either supply an http base address or set HttpGetUrl to an absolute address. The HttpsGetEnabled property of ServiceMetadataBehavior is set to true and the HttpsGetUrl property is a relative address, but there is no https base address. Either supply an https base address or set HttpsGetUrl to an absolute address. {0} must be a relative URI or an absolute URI with scheme '{1}'. '{2}' is an absolute URI with scheme '{3}'. Service implementation type is an interface or abstract class and no implementation object was provided. This property sets EnableFaults on the client. To set EnableFaults on the server, use ChannelDispatcher's EnableFaults. This property sets ManualAddressing on the client. To set ManualAddressing on the server, use ChannelDispatcher's ManualAddressing. Header properties cannot be set in MessageHeaderAttribute of {0} as its type is MessageHeader<T>. An exception has been thrown when reading the stream. The message containing this stream has been closed. Note that request streams cannot be accessed after the service operation returns. The message containing this stream has been closed. Throttle limit must be greater than zero. To disable, set to Int32.MaxValue. The timeout value provided was not of a recognized format. Please see InnerException for more details. Timeout must be greater than or equal to TimeSpan.Zero. To disable timeout, specify TimeSpan.MaxValue. Timeouts larger than Int32.MaxValue TotalMilliseconds (approximately 24 days) cannot be honored. To disable timeout, specify TimeSpan.MaxValue. Cannot create a unique part name for {0}. An unrecognized element was encountered in the XML during deserialization which was ignored. TransactedBatchingBehavior validation failed. The service endpoint cannot be started. TransactedBatchingBehavior requires a binding that contains a binding element ITransactedBindingElement that returns true for ITransactedBindingElement.TransactedReceiveEnabled. If you are using NetMsmqBinding or MsmqIntegrationBinding make sure that ExactlyOnce is set to true. The transaction under which this method call was executing was asynchronously aborted. The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false and the InstanceContextMode is not set to PerSession. TransactionAutoComplete set to false requires the use of InstanceContextMode.PerSession. The operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false but SessionMode is not set to Required. TransactionAutoComplete set to false requires SessionMode.Required. The operation '{0}' on callback contract '{1}' is configured with TransactionAutoComplete set to false. TransactionAutoComplete set to false cannot be used with operations on callback contracts. The service '{0}' is configured with TransactionAutoCompleteOnSessionClose set to true and with an InstanceContextMode not set to PerSession. TransactionAutoCompleteOnSessionClose set to true requires an instancing mode that uses sessions. The incoming transaction cannot be deserialized. The transaction header in the message was either malformed or in an unrecognized format. The client and the service must be configured to use the same protocol and protocol version. The following exception occurred: {0} The binding for the endpoint at address '{0}' is configured with both the MsmqTransportBindingElement and the TransactionFlowBindingElement. These two elements cannot be used together. The service operation requires a transaction to be flowed. The transaction header '{0}' within the namespace '{1}' was not understood by the service. The client and the service must be configured to use the same protocol and protocol version ('{2}'). The SetTransactionComplete method was called in the operation '{0}' on contract '{1}' when TransactionAutoComplete was set to true. The SetTransactionComplete method can only be called when TransactionAutoComplete is set to false. This is an invalid scenario and the current transaction was aborted. The service '{0}' is configured with a TransactionIsolationLevel but no operations are configured with TransactionScopeRequired set to true. TransactionIsolationLevel requires at least one operation with TransactionScopeRequired set to true. TThe operation '{1}' on contract '{0}' is configured with TransactionAutoComplete set to false and with ConcurrencyMode not set to Single. TransactionAutoComplete set to false requires ConcurrencyMode.Single. The '{0}' service is configured with ReleaseServiceInstanceOnTransactionComplete set to true, but the ConcurrencyMode is not set to Single. The ReleaseServiceInstanceOnTransactionComplete requires the use of ConcurrencyMode.Single. The service '{0}' is configured with ReleaseServiceInstanceOnTransactionComplete but no operations are configured with TransactionScopeRequired set to true. The ReleaseServiceInstanceOnTransactionComplete property requires at least one operation with TransactionScopeRequired set to true. Remove the ReleaseServiceInstanceOnTransactionComplete property from the service if this is the case. The service does not support concurrent transactions. The service '{0}' is configured with TransactionAutoCompleteOnSessionClose, but no operations are configured with TransactionScopeRequired set to true. The TransactionAutoCompleteOnSessionClose property requires at least one operation with TransactionScopeRequired set to true. Remove the TransactionAutoCompleteOnSessionClose property from the service if this is the case. The service '{0}' is configured with a TransactionTimeout but no operations are configured with TransactionScopeRequired set to true. TransactionTimeout requires at least one operation with TransactionScopeRequired set to true. The flowed transaction could not be unmarshaled. The following exception occurred: {0} An attempt was made to add more than one transaction to a message. At most one transaction can be added. Internal Error: The instance of the MessageContract cannot be null in {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 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. 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}'. This fault did not provide a matching translation: {0} This fault did not provide a reason (MessageFault.Reason was null). This fault did not provide a reason (MessageFault.Reason.Translations.Count was 0). Parameter value '{0}' is an invalid URI. Value '{0}' provided for {1} property is an invalid URI. User operation '{0}.{1}' threw an exception that is unhandled in user code. This exception will be rethrown. If this is a recurring problem, it may indicate an error in the implementation of the '{0}.{1}' method. Parameter '{0}' requires additional schema information that cannot be captured using the parameter mode. The specific attribute is '{1}'. Cannot add outgoing headers to message as MessageVersion in OperationContext.Current '{0}' does not match with the header version of message being processed '{1}'. In order to use one of the ServiceHost constructors that takes a service instance, the InstanceContextMode of the service must be set to InstanceContextMode.Single. This can be configured via the ServiceBehaviorAttribute. Otherwise, please consider using the ServiceHost constructors that take a Type argument. When multiple endpoints on a service share the same ListenUri, those endpoints must all have the same Identity in their EndpointAddress. The endpoints at ListenUri '{0}' do not meet this criteria. Wrapper element name cannot be empty. Wrapper type for message {0} cannot be projected as a data contract type since it has multiple namespaces. Consider using the XmlSerializer Service description message '{1}' from target namespace '{2}' does not contain part named '{0}'. The wsdl operation {0} in portType {1} contains a fault that does not reference a message. This is either because the message attribute is missing or empty. The wsdl operation input {0} in portType {1} does not reference a message. This is either because the message attribute is missing or empty. The wsdl operation output {0} in portType {1} does not reference a message. This is either because the message attribute is missing or empty. WSDL part {0} in message {1} from namespace {2} must have either an element or a type name XmlArrayAttribute cannot be used in repeating part {1}:{0}. Could not find XmlSerializer for type {0}. The service endpoint failed to listen on the URI '{0}' because access was denied. Verify that the current user is granted access in the appropriate allowAccounts section of SMSvcHost.exe.config. The service endpoint failed to listen on the URI '{0}' because the shared memory section was not found. Verify that the '{1}' service is running. failed to grant the PROCESS_DUP_HANDLE access right to the target service's account SID '{0}'. The TransportManager failed to listen on the supplied URI using the {0} service: {1}. the URI is already registered with the service failed to retrieve the UserSid of the current process failed to create a data connection to the service failed to establish a data connection to the service failed to establish the data connection because of an I/O error the service failed to listen failed to retrieve the LogonSid of the service process ({0}) the URI is too long the protocol is not supported the quota was exceeded failed to read the service's endpoint with native error code {0}. See inner exception for details failed to look up the service process in the SCM ({0}) the service failed the security checks failed to look up the service SID in the SCM ({0}) failed to start the service ({0}). Refer to the Event Log for more details failed to start the service because it is disabled. An administrator can enable it by running 'sc.exe config {0} start= demand'. failed to start the service. Refer to the Event Log for more details failed to retrieve the UserSid of the service process ({0}) the version is not supported by the service The message could not be dispatched to the service at address '{0}'. Refer to the server Event Log for more details The endpoint address for the NT service '{0}' read from shared memory is empty. The message could not be dispatched because the service at the endpoint address '{0}' is unavailable for the protocol of the address. The message could not be dispatched because the transport manager has been stopped. This can happen if the application is being recycled or disabled. Shutdown request was not received. The signature token '{0}' is not the same token as the encryption token '{1}'. The configured SecurityVersion does not support signature confirmation. Use WsSecurity11 or above. The protocol factory must support Request/Reply security in order to offer signature confirmation. Signature confirmation is not expected in the security header. The signature confirmation elements cannot occur after the primary signature. Signature confirmation was expected to be present in the security header. A signature is not expected for this message. Signature verification failed. A signed supporting token is not expected in the security header in this context. 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). The signing token {0} has no key that supports the algorithm suite {1}. Signing without primary signature requires timestamp. The DeliveryRequirementsAttribute on contract '{0}' specifies that the binding must support ordered delivery (RequireOrderedDelivery). This condition could not be verified because the configured binding does not implement IBindingDeliveryCapabilities. The DeliveryRequirementsAttribute may only be used with bindings that implement the IBindingDeliveryCapabilities interface. The DeliveryRequirementsAttribute on contract '{0}' specifies a QueuedDeliveryRequirements constraint. This condition could not be verified because the configured binding does not implement IBindingDeliveryCapabilities. The DeliveryRequirementsAttribute may only be used with bindings that implement the IBindingDeliveryCapabilities interface. A single WSDL document could not be generated for this service. Multiple service contract namespaces were found ({0}). Ensure that all your service contracts have the same namespace. The specified size exceeds the remaining buffer space ({0} bytes). SOAP security negotiation failed. See inner exception for more details. SOAP security negotiation with '{0}' for target '{1}' failed. See inner exception for more details. 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. 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. A graceful close was attempted on the socket, but the other side ({0}) is still sending data. 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. The socket connection has been disposed. The socket listener has been disposed. The socket listener is not listening. The incoming transaction cannot be unmarshaled because the source MSDTC transaction manager has either disabled outbound transactions or disabled its WS-AtomicTransaction protocol service. The space needed for encoding ({0} bytes) exceeds the message frame offset. The Security Support Provider Interface does not support Impersonation level 'None'. Specify Identification, Impersonation or Delegation level. The asynchronous result object used to end this operation was not the object that was returned when the operation was initiated. Read is not supported on this stream. Seek is not supported on this stream. It is likely that certificate '{0}' may not have a private key that is capable of key exchange or the process may not have access rights for the private key. Please see inner exception for detail. The certificate '{0}' must have a private key. The process must have access rights for the private key. The cipher key negotiated by SSL is too small ('{0}' bits). Keys of such lengths are not allowed as they may result in information disclosure. Please configure the initiator machine to negotiate SSL cipher keys that are '{1}' bits or longer. SSL protocol negotiation failed. Requested '{0}' but was offered '{1}'. The remote certificate is invalid according to the validation procedure. Either the client credential was invalid or there was an error collecting the client credentials by the SSPI. SecuritySessionServerSettings.CreateAcceptor, channelAcceptor must be null, can not create twice. The token Serializer cannot serialize '{0}'. If this is a custom type you must supply a custom serializer. Standards manager of filter does not match that of filter table. Can not have two different filters. The operation cannot be completed because the stream is closed. TimeoutStream requires an inner Stream that supports timeouts; its CanTimeout property must be true. An error occurred while transmitting data. The remote server did not satisfy the mutual authentication requirement. The StreamUpgradeProvider {0} does not support the specified ChannelBindingKind ({1}). StringNullOrEmpty The address of the security token issuer is not specified. An explicit issuer address must be specified in the binding for target '{0}' or the local issuer address must be configured in the credentials. The binding to use to communicate to the federation service at '{0}' is not specified. The algorithm '{0}' is not accepted for operation '{1}' by algorithm suite {2}. 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. The '{0}' addressing mode is not supported. The supporting signature is not signed with a derived key. The binding's supporting token parameter '{0}' requires key derivation. The supporting token provided for parameters '{0}' was not encrypted. The supporting token provided for parameters '{0}' did not endorse the primary signature. The supporting token provided for parameters '{0}' was not signed as part of the primary signature. A supporting token that satisfies parameters '{0}' and attachment mode '{1}' was not provided. Supporting token signatures not expected. The length of the symmetric key specified is too short ({0} bytes). SymmetricSecurityBindingElement cannot build a channel or listener factory. The ProtectionTokenParameters property is required but not set. Binding element configuration: {0} 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 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. 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. 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. A value of type '{0}' cannot be added to the generic collection, because the collection has been parameterized with a different type. A null value cannot be added to the generic collection, because the collection has been parameterized with a value 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, 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. 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. 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. 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 target service address was not specified on '{0}'. Target object does not support IPersistStream. Target type is an interface but corresponding type is not PersistStreamTypeWrapper. 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 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. 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 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. The task was cancelled. Client side task-based asynchronous method must not have any out or ref parameters. Any data that would have been returned through an out or ref parameter should instead be returned as part of the TResult in the resulting task. The use of '{0}' on the task-based asynchronous method is not supported. There is already a listener on IP endpoint {0}. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. Could not connect to {0}. TCP error code {1}: {2}. Could not connect to {0}. The connection attempt lasted for a time span of {3}. TCP error code {1}: {2}. 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. 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}'. 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}'. The local IP address and port is {1}. The remote IP address and port is {2}. 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. 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. The local IP address and port is {1}. The remote IP address and port is {2}. Insufficient winsock resources available to complete socket connection initiation. A TCP error ({0}: {1}) occurred while listening on IP Endpoint={2}. 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. A TCP error ({0}: {1}) occurred while transmitting data. A TCP error ({0}: {1}) occurred while transmitting data. The local IP address and port is {2}. The remote IP address and port is {3}. An IPv4 address was specified ({0}), but IPv4 is not enabled on this machine. An IPv6 address was specified ({0}), but IPv6 is not enabled on this machine. Directory {0} not found. The DeliveryRequirementsAttribute on contract '{0}' specifies a QueuedDeliveryRequirements value of NotAllowed. However, the configured binding for this contract specifies that it does support queued delivery. A queued binding may not be used with this contract. The ServiceMetadataExtension instance could not be added to the ServiceHost instance because it has already been added to another ServiceHost instance. The ServiceMetadataExtension instance could not be removed from the ServiceHost instance because it has not been added to any ServiceHost instance. The ServiceMetadataExtension instance could not be removed from the ServiceHost instance because it has already been added to a different ServiceHost instance. The message could not be transferred within the allotted timeout of {0}. There was no space available in the reliable channel's transfer window. The time allotted to this operation may have been a portion of a longer timeout. The close 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 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 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 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. The send 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. Opening the channel timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. Opening the {0} channel timed out after {1}. The time allotted to this operation may have been a portion of a longer timeout. TimeSpan cannot be less than TimeSpan.Zero. TimeSpan must be greater than TimeSpan.Zero. A timestamp element has already been set for this security header. The security timestamp is invalid because its creation time ('{0}') is greater than or equal to its expiration time ('{1}'). 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 security timestamp is stale because its expiration time ('{0}') is in the past. Current time is '{1}' and allowed clock skew is '{2}'. The timestamp must occur first in this security header layout. The timestamp must occur last in this security header layout. The timestamp element added to security header to sign has no id. 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}'. An error occurred communicating with the distributed transaction manager. The security token manager requires the security binding element to be specified in order to create a token authenticator for requirement '{0}'. The token provider '{0}' does not support token cancellation. A symmetric crypto could not be created from token '{0}'. The key size requirements for the '{0}' algorithm suite are not met by the '{1}' token which has key size of '{2}'. '{0}' does not support '{1}' creation. The supplied token manager cannot create a token reference. Security token manager could not parse token with name '{0}', namespace '{1}', valueType '{2}'. The SecurityTokenParameters and SecurityToken tuple specified for use in the security header must both be null or must both be non-null. Received security header contains unexpected token '{0}'. The token provider cannot get tokens for target '{0}'. The security token manager requires the security binding element to be specified in order to create a token provider for requirement '{0}'. TokenProvider returned token of incorrect type '{0}'. The token provider '{0}' was unable to provide a security token. The token provider '{0}' was unable to renew the security token. The token provider '{0}' does not support token renewal. 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 security token serializer must be specified on the security token provider. The operation cannot be performed after the communications channel has been created. Too many attributes of type {0} on {1}. A leg of the federated security chain contains multiple IssuedSecurityTokenParameters. The InfoCard system only supports one IssuedSecurityTokenParameters for each leg. There are too many renewed session keys that have not been used. Authorize Activating message received. An async callback threw an exception! Begin method execution. The given schema cannot be imported in this format. Channel connection was dropped Created: {0} Disposed: {0} Sent a message over a channel Prepared message for sending over a channel Aborted '{0}'. Failed to abort {0} Closed {0} Failed to close {0} Closing {0} Created {0} Disposing {0} Faulted {0} CommunicationObject faulted due to exception. Opened {0} Failed to open {0} Opening {0} The configuration is read-only. Extension type is not configured. The connection has been abandoned. An exception occurred while closing the connections in this connection pool. A connection has exceeded the idle timeout of this connection pool ({0}) and been closed. A connection has exceeded the connection lease timeout of this connection pool ({0}) and been closed. MaxOutboundConnectionsPerEndpoint quota ({0}) has been reached, so connection was closed and not stored in this connection pool. Connection information. ContextChannel created. A new ContextChannel was accepted. Context added to Message. Context retrieved from Message. No matching <service> tag was found. Default endpoints added. Failed to trace a message InstanceContext cached for InstanceId {0}. InstanceContext for InstanceId {0} removed from cache. Did not understand message header. A response message was received, but there are no outstanding requests waiting for this message. The message is being dropped. The type of the element does not match the configuration type. End method execution. Endpoint listener closed. Endpoint listener opened. Error invoking user code Configuration evaluation context not found. Starting Security ExportChannelBinding Finished Security ExportChannelBinding The extension collection does not exist. The extension collection is empty. Extension element not associated with an extension collection. The extension element already exists in the collection. Extension type not found. An attempt to reuse a pooled connection failed. Another attempt will be made with {0} remaining in the overall timeout. Failed to set an activity id header on an outgoing message An incoming channel was disposed because there was an error while attempting to open it. Failed to read an activity id header on a message Evaluating message logging filter against the message exceeded the node quota set on the filter. Get BehaviorElement. Get ChannelEndpointElement. Get machine.config common behaviors. Get configuration section. Get configured binding. Get configured endpoint. Get default configured binding. Get default configured endpoint. Get ServiceElement. The HTTP SOAPAction header and the wsa:Action SOAP header did not match. Authentication failed for HTTP(S) connection The HTTP concurrent receive quota was reached. Failed to lookup a channel to receive an incoming message. Either the endpoint or the SOAP action was not found. Failed to send request message over HTTP Failed to send response message over HTTP Received bad HTTP response HTTP response was received Client certificate is invalid. Client certificate is invalid with native error code {0} (see http://go.microsoft.com/fwlink/?LinkId=187517 for details). Client certificate is required. No certificate was found in the request. This might be because the client certificate could not be successfully validated by the operating system or IIS. For information on how to bypass those validations and use a custom X509CertificateValidator in WCF please see http://go.microsoft.com/fwlink/?LinkId=208540. Starting Security ImportChannelBinding Finished Security ImportChannelBinding An existing incompatible transport manager was found for the specified URI. Initiating Named Pipe connection. Initiating TCP connection. DurableInstance's InstanceContext refcount incremented. DurableInstance's InstanceContext refcount decremented. The IssuanceTokenProvider has started a new security negotiation. The IssuanceTokenProvider has completed the security negotiation. The IssuanceTokenProvider applied a redirection header. The IssuanceTokenProvider removed the expired service token. IssuanceTokenProvider pruned service token cache. The IssuanceTokenProvider used the cached service token. Listener created Listener disposed The system hit the limit set for the '{0}' throttle. Throttle value can be changed by modifying {0} property on {1}. Maximum number of inbound session channel has been reached. Maximum number of pending connections has been reached. A message was closed A message was closed again A message was copied Reached the limit of messages to log. Message logging is stopping. Message not logged because its size exceeds configured quota Switched threads while processing a message. A message was read Received a message over a channel. Sent a message over a channel. A message was written The MetadataExchangeClient received a reply. The MetadataExchangeClient is sending a request for metadata. NegotiationTokenAuthenticator was attached. NegotiationTokenProvider was attached. No existing transport manager was found for the specified URI. Transport is listening at base URI. The configuration system has detected a duplicate key in a different configuration scope and is overriding with the more recent value. A performance counter failed to load. Some performance counters will not be available. Failed to load the performance counter '{0}'. Some performance counters will not be available There was an error while updating the performance counter '{0}'. This performance counter will be disabled. Loading performance counters for the service failed. Performance counters will not be available for this service. Unloading the performance counters failed. A null Message (signalling end of channel) was received from a datagram channel, but the channel is still in the Opened state. This indicates a bug in the datagram channel, and the demuxer receive loop has been prematurely stalled. Switched threads while processing a message for Contract '{0}' at Address '{1}'. ConcurrencyMode for service is set to Single/Reentrant and the service is currently processing another message. Switched threads while processing a message for Contract '{0}' at Address '{1}'. Waiting for the completion of ReceiveContext acknowledgement. If your service seems to be not processing the message ensure that the channel implementation of receive context completes the operation. Switched threads while processing a message for Contract '{0}' at Address '{1}'. Cannot process more than one transaction at a time and the transaction associated with the previous message is not yet complete. Ensure that the caller has committed the transaction. Switched threads while processing a message for Contract '{0}' at Address '{1}'. UseSynchronizationContext property on ServiceBehaviorAttribute is set to true, and SynchronizationContext.Current was non-null when opening ServiceHost. If your service seems to be not processing messages, consider setting UseSynchronizationContext to false. Behavior type already exists in the collection Received reply over request channel RequestContext aborted A failure occured while performing a security related operation. An active security session was removed by the server. A failure occurred while writing to the security audit log. The security audit log is written successfully. The security protocol verified the incoming message. The security protocol secured the outgoing message. The security protocol cannot secure the outgoing message. The security protocol cannot verify the incoming message. Close message was received by client security session.TraceCodeSecurityClientSessionKeyRenewed=Client security session renewed session key. Close response message was sent by client security session. A Close message was sent by the client security session. The client security session renewed the session key. The client security session discarded the previous session key. The SecurityContextSecurityToken cache is full. Identity cannot be determined for an EndpointReference. Identity was determined for an EndpointReference. The HostName portion of an endpoint address cannot be normalized. Identity verification failed. Identity verification succeeded. Security impersonation failed at the server. Security Impersonation succeeded at the server. An inactive security session was faulted by the server. Service security negotiation processing failure. A new security session key was issued by the server. A pending security session was activated by the server. A pending security session was added to the server. The pending security session was closed by the server. Server security session sent session aborted fault to client. The server security session received a close message from the client. Server security session received Close response message from client. The security session key was updated by the server. The server security session sent a key renewal fault to the client. Client security session received session aborted fault from server. Failure sending security session aborted fault to client. The client security session received a closed reponse from the server. A failure occurred when sending a security session Close response to the client. The server security session sent a close response to the client. The incoming message is not part of an existing security session. The client security session received a key renewal fault from the server. The client security session was redirected. A failure occurred when sending a renewal fault on the security session key to the client. The client security session operation failed. The security session operation completed successfully at the client. A security session operation was started at the client. The security session operation failed at the server. Failure sending security session Close to client. Server security session sent Close to client. The ServicePrincipalName could not be mapped to a SecurityIdentifier. Security Token Authenticator was closed. Security Token Authenticator was opened. Security Token Provider was closed. Security Token Provider was opened. MaxOutboundConnectionsPerEndpoint quota ({0}) has been reached, so the connection was closed and not reused by the listener. ServiceChannel information. ServiceDurableInstance '{0}' deleted from persistence store. ServiceDurableInstance '{0}' disposed. ServiceDurableInstance loaded from persistence store. ServiceDurableInstance saved to persistence store. ServiceHost base addresses. Create ServiceHost. ServiceHost error on calling ReleasePerformanceCounters. ServiceHost faulted. ServiceHost close operation timedout. Replying to an operation threw a exception. The Request/Reply operation {0} has no Reply Message. The Request/Reply operation {0} has no IRequestContext to use for the reply. Service security negotiation completed. The system hit the limit set for throttle '{0}'. Limit for this throttle was set to {1}. Throttle value can be changed by modifying attribute '{2}' in serviceThrottle element or by modifying '{0}' property on behavior ServiceThrottlingBehavior. The system hit an internal throttle limit. Limit for this throttle was set to {0}. This throttle cannot be configured. The shared memory for the endpoint of the service '{0}' does not exist. The service may not be started. Behavior type is not of expected type SocketConnection aborted SocketConnection aborted under Close SocketConnection close SocketConnection create Client's outgoing SSPI negotiation. SpnegoTokenProvider completed SSPI negotiation. Service's outgoing SSPI negotiation. SpnegoTokenAuthenticator completed SSPI negotiation. SqlPersistenceProvider.Open() parameters. Sql execution complete. Sql execution started. The remote SSL client failed to provide a required certificate. The stream security upgrade was accepted successfully. SynchronizationContextWorkflowSchedulerService - Timer {0} cancelled. SynchronizationContextWorkflowSchedulerService - Timer {0} created for InstanceId {1}. Reading of a syndication feed started. Reading of a syndication feed completed. Writing of a syndication feed started. Writing of a syndication feed completed. Reading of a syndication item started. Reading of a syndication item completed. Writing of a syndication item started. Writing of a syndication item completed. Syndication XML node of type '{0}' with name '{1}' and namespace '{2}' ignored on read. Syndication element with name '{0}' and namespace '{1}' was not written. Syndication element with name '{0}' and namespace '{1}' is invalid. Reading of a categories document started. Reading of a categories document completed. Reading of a syndication feed started. Reading of a syndication feed completed. Reading of a syndication item started. Reading of a syndication item completed. Reading of a service document started. Reading of a service document completed. Writing of a categories document started. Writing of a categories document completed. Writing of a syndication feed started. Writing of a syndication feed completed. Writing of a syndication item started. Writing of a syndication item completed. Writing of a service document started. Writing of a service document completed. The operating system's timer resolution was detected as {0} ticks, which is about {1} milliseconds. Received a message over TCP channel Failed to receive a message over TCP channel The TCP connect operation failed. Listen at '{0}'. The transaction '{0}' was asynchronously aborted. The transaction '{0}' was aborted because it was uncompleted when the session was closed and the TransactionAutoCompleteOnSessionClose OperationBehaviorAttribute was set to false. The transaction '{0}' for operation '{1}' was completed due to asynchronous abort. The transaction '{0}' for operation '{1}' was completed due to the TransactionAutoComplete OperationBehaviorAttribute member being set to true. The transaction '{0}' for operation '{1}' was completed due to an unhandled execution exception. The transaction '{0}' for operation '{1}' was completed due to a call to SetTransactionComplete. The transaction '{0}' was completed when the session was closed due to the TransactionAutoCompleteOnSessionClose ServiceBehaviorAttribute member. The transaction '{0}' for operation '{1}' remains attached to the InstanceContext. The OleTransactions protocol negotiation failed for coordination context '{0}'. The service instance was released on the completion of the transaction '{0}' because the ReleaseServiceInstanceOnTransactionComplete ServiceBehaviorAttribute was set to true. The transaction '{0}' was received for operation '{1}' from an InstanceContext transaction. The transaction '{0}' for operation '{1}' was newly created. The transaction '{0}' was received for operation '{1}' from a transacted transport, such as MSMQ. The transaction '{0}' was flowed to operation '{1}'. Existing transaction '{0}' being used for operation '{1}'. Understood message header. No service available to handle this action Unhandled exception in user operation '{0}.{1}'. The ServiceDebugBehavior Help Page is enabled at a relative address and cannot be created because there is no base address. Webhost could not activate service Webhost couldn't compile service Incoming HTTP request with URI '{0}' does not match any operation. Incoming HTTP request with URI '{0}' matched operation '{1}'. HTTP query string parameter with name '{0}' was ignored. Setting a value via WMI. WorkflowDurableInstance aborted. WorkflowDurableInstance '{0}' activated. WorkflowDurableInstance '{0}' loaded. Work item enqueued. Fault Sent for InstanceId {0}. Reply sent for InstanceId {0}. WorkflowServiceHost created. A non-critical error or warning occurred during WSDL Export A non-critical error or warning occurred in the MetadataExchangeClient during WSDL Import This could result in some endpoints not being imported. An invalid create sequence message was received. An invalid WS-RM message was received. An incoming create sequence request was rejected because the maximum pending channel count was reached. A message in a WS-RM sequence has been dropped because it could not be buffered. WS-RM SequenceAcknowledgement received. WS-RM Last Sequence message received. WS-RM Sequence message received. WS-RM SequenceAcknowledgement sent. WS-RM Last Sequence message sent. WS-RM Sequence message sent. A WS-RM sequence has faulted. OnAuthorizeRequest Failed. OnAuthorizeRequest Succeeded. Invalid TransactionFlowOption value. In order to flow a transaction, flowing issued tokens must also be supported. Transfer mode {0} is not supported by {1}. Transferring to ComPlus logical thread {0}. 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 binding does not contain a TransportBindingElement. The '{0}'.'{1}' binding for the '{2}'.'{3}' contract is configured with an authentication mode that requires transport level integrity and confidentiality. However the transport cannot provide integrity and confidentiality. 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. This operation is only valid after the transport manager has been opened. This property cannot be changed after the transport manager has been opened. More than one 'To' header specified in a message secured by Transport Security. The message received over Transport security was missing the 'To' header. Transport secured messages should have the 'To' header specified. Unable to create Attached or Unattached reference for '{0}'. The configured WS-Trust version does not support issued tokens. WS-Trust February 2005 or later is required. The configured Trust version does not support sessions. Use WSTrustFeb2005 or above. Could not establish trust relationship for the SSL/TLS secure channel with authority '{0}'. Type load for contract interface ID {0} failed with Error:{1}. The '{0}' user-defined type could not be found. Ensure that the correct type and type library are registered and specified. Cannot create an ICrypto interface from the '{0}' token for signature verification. Unable to create Key Type element for the Key Type '{0}'. This might be due to a wrong version of MessageSecurityVersion set on the SecurityBindingElement. Cannot create the '{0}' symmetric algorithm from the token. Unable to create token reference. There was no channel that could accept the message with action '{0}'. KeyInfo clause '{0}' resolved to token '{1}', which does not contain a Symmetric key that can be used for derivation. A policy reference was ignored because the policy with ID '{0}' could not be found. Security processor was unable to find a security header with actor '{0}' in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This can occur if the service is configured for security and the client is not using security. Security processor was unable to find a security header in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This can occur if the service is configured for security and the client is not using security. Cannot find a token authenticator for the '{0}' token type. Tokens of that type cannot be accepted according to current security settings. Failed to impersonate client identity during serialization of the response message. The following Policy Assertions were not Imported:\r\n Cannot load the X.509 certificate identity specified in the configuration. Cannot load library {0}. Ensure that WCF is properly installed. Cannot locate operation {0} in Contract {1}. Obtaining metadata from issuer '{0}' failed with error '{1}'. Cannot renew the security session key. The data reference '{0}' could not be resolved in the received message. Cannot resolve the host name of URI \"{0}\" using DNS. Cannot resolve KeyInfo in derived key token for resolving source token: KeyInfoClause '{0}'. Cannot resolve KeyInfo for decryption: KeyInfo '{0}', available tokens '{1}'. Cannot resolve KeyInfo for unwrapping key: KeyInfo '{0}', available tokens '{1}'. Cannot resolve KeyInfo for verifying signature: KeyInfo '{0}', available tokens '{1}'. The token resolver is unable to resolve the security key reference '{0}'. Cannot resolve reference URI '{0}' in signature to compute digest. The token resolver is unable to resolve the token reference '{0}'. Unable to retrieve IUnknown for object. MemoryStream's internal buffer cannot be accessed. Unbound prefix used in qualified name '{0}'. A feed containing items that are not buffered (i.e. the items are not stored in an IList) cannot clone its items. Buffer the items in the feed before calling Clone on it or pass false to the Clone method. The remote endpoint sent an unexpected ack. Simplex servers do not process acks. The remote endpoint sent an unexpected request for an ack. Simplex clients do not send acks and do not process requests for acks. Expected binary secret of type {0} but got secret of type {1}. The remote endpoint sent an unexpected close sequence message. Simplex clients do not process this message. The remote endpoint sent an unexpected close sequence response message. Simplex servers do not process this message. The remote endpoint sent an unexpected request to create a sequence. Clients do not process requests for a sequence. The remote endpoint sent inconsistent requests to create the same sequence. The OfferId values are not identical. The remote endpoint sent an unexpected create sequence response. Servers do not process this message. The remote endpoint sent inconsistent responses to the same create sequence request. The sequence identifiers are not identical. '{0}' from namespace '{1}' is not expected to appear more than once '{0}' from namespace '{1}' is not expected. Expecting element '{2}' from namespace '{3}' The '{0}' from the '{1}' namespace is empty and does not specify a valid identity claim. Unexpected encrypted element in security header. Unexpected end of file. The remote server returned an unexpected response: ({0}) {1}. The security session received an unexpected close from the other party. The security session received an unexpected close response from the other party. Connection was not accepted because the SecurityContext contained tokens that do not match the current security settings. The remote endpoint sent an unexpected terminate sequence message. Simplex clients do not process this message. The remote endpoint sent an unexpected terminate sequence response message. Simplex servers do not process this message. Unexpected threading model. WCF/COM+ integration only supports STA and MTA threading models. XML child node {0} of type {1} is unexpected for element {2}. XPath:{0}\r\n Assertions: Cannot find a unique port number that is available for both IPv4 and IPv6. The computed key algorithm '{0}' is not supported. The element with name '{0}' and namespace '{1}' is not an allowed document format. Unrecognized encoding occurred while reading the binary security token. The element with name '{0}' and namespace '{1}' is not an allowed feed format. Unknown filter type: '{0}'. The contract ('{0}','{1}') contains some unknown header ('{2}','{3}') which cannot be secured. Please choose ProtectionLevel.None for this header. The ICrypto implementation '{0}' is not supported. The element with name '{0}' and namespace '{1}' is not an allowed item format. The listener at Uri '{0}' could not be initialized because it was created for an unrecognized channel type. Could not find keyword {0}. The value of wsrm:Identifier is not a known Sequence identifier. The remote endpoint has sent a message containing an unrecognized sequence identifier. The reliable session was faulted. Unrecognized supporting token '{0}' was encountered. Unknown token attachment mode: {0}. An unrecognized token authenticator '{0}' was used for token processing. An unrecognized WSDL extension of Type '{0}' was not handled. The WS-AtomicTransaction protocol service could not unmarshal the flowed transaction. The following exception occured: {0} The remote endpoint replied to the request for a sequence with a response that could not be parsed. See inner exception for details. The channel could not be opened. WsdlImporter encountered unrecognized policy assertions in ServiceDescription '{0}': The ClaimType '{0}' is not recognized. Expected ClaimType '{1}'. The remote endpoint has sent an unrecognized fault with namespace, {0}, name {1}, and reason {2}. The channel could not be opened. Invalid HostNameComparisonMode value: {0}. Unrecognized identity property type: '{0}'. Unrecognized identity type Name='{0}', Namespace='{1}'. The \"{0}\" namespace is not a recognized WS-Policy namespace. Unrecognized policy element {0} in namespace {1}. An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. The message received over Transport security has unsigned 'To' header. Binary encoding {0} is not supported. The '{0}' binding element does not support cloning. The value '{1}' is not supported in this context for the binding property '{0}'. Cannot import the policy. The value of the attribute '{0}' must be either 'true', 'false', '1' or '0'. The following error occurred: '{1}'. Canonicalization algorithm '{0}' is not supported. Channel interface type '{0}' is not supported. The conversion between the client parameter type '{0}' to the required server parameter type '{1}' cannot be performed. Crypto algorithm {0} not supported in this context. The {0} binding element requires envelope version '{1}' It doesn't support '{2}'. Issuer entropy is not BinarySecretSecurityToken or WrappedKeySecurityToken. Key derivation algorithm '{0}' is not supported. Symmetric Key length {0} is not supported by the algorithm suite '{1}'. The type {0} is not a supported result type. The '{0}' username token has an unsupported password type. \"{0}\" is not a supported WS-Policy document root element. The Rss20Serializer does not support RSS version '{0}'. Cannot import the security policy. The protection requirements for the secure conversation bootstrap binding are not supported. Protection requirements for the secure conversation bootstrap must require both the request and the response to be signed and encrypted. An unsupported security policy assertion was detected during the security policy import: {0} The value '{1}' is not supported in this context for the binding security property '{0}'. The protection level '{0}' was specified, yet SSL transport security only supports EncryptAndSign. The value '{1}' for the '{0}' property is not supported in Windows Store apps. Token inclusion mode '{0}' is not supported. The TrustVersion '{0}', is not supported, only 'TrustVersion.WSTrust13' and 'TrustVersion.WSTrustFeb2005' is supported. The StreamUpgradeAcceptor specified ({0}) is not supported by this IStreamUpgradeChannelBindingProvider implementation. The most likely cause of this is passing a StreamUpgradeAcceptor that was not created by the StreamUpgradeProvider associated with this IStreamUpgradeChannelBindingProvider implementation. 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. Unsupported WSDL, only one message part is supported for fault messages. This fault message references zero or more than one message part. If you have edit access to the WSDL file, you can fix the problem by removing the extra message parts such that fault message references just one part. Unsupported WSDL, the fault message part must reference an element. This fault message does not reference an element. If you have edit access to the WSDL document, you can fix the problem by referencing a schema element using the 'element' attribute. Protocol Type {0} was sent to a service that does not support that type of upgrade. .Net Framing upgrade request for {0} was sent to a service that is not setup to receive upgrades. The scheme parameter must not be empty. URI {0} could not be set because its size ({1}) exceeds the max supported size ({2}). The given URI must be absolute. You cannot specify an explicit Proxy Address as well as UseDefaultWebProxy=true in your HTTP Transport Binding Element. The username cannot be empty. The username is not provided. Specify username in ClientCredentials. Changing an inline default value with information from the additional default values is not supported; the default value to the variable '{0}' was already provided as part of the UriTemplate '{1}'. See the documentation for UriTemplate for more details. baseAddress must an absolute Uri. The BindByName method of UriTemplate was called with an empty name in the collection of arguments for the bind. Note that the NameValueCollection or the Dictionary passed to BindByName cannot contain an empty (or null) name as a key. See the documentation of UriTemplate for more details. UriTemplate '{0}' contains no variables; yet the BindByPosition method was called with {1} values. UriTemplate '{0}' contains {1} path variables and {2} query variables but {3} values were passed to the BindByPosition method. The number of values passed to BindByPosition should be greater than or equal to the number of path variables in the template and cannot be greater than the total number of variables in the template. The UriTemplate contains a literal value for query key '{0}', but that key also is present in the NameValueCollection. Either remove that key from the NameValueCollection, or else change the UriTemplate to not have a query literal for that key. UTCSR - Lookup was called before match The default values of UriTemplate are immutable; they cannot be modified after the construction of the UriTemplate instance. See the documentation of UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate compound path segment '{1}' provides a default value to variable '{2}'. Note that UriTemplate doesn't support default values to variables in compound segments. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the path variable '{1}', defined as part of a compound path segment has been provided with a default value as part of the additional defaults. Note that UriTemplate doesn't support default values to variables in compound segments. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate variable declaration '{1}' provides a default value to query variable '{2}'. Note that UriTemplate doesn't support default values to query variables. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the query variable '{1}' has been provided a default value as part of the additional defaults. Note that UriTemplate doesn't support default values to query variables. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; UriTemplate does not support two adjacent variables with no literal in compound segments, such as in the segment '{1}'. The UriTemplate '{0}' is not valid; the UriTemplate variable declaration '{1}' provides an empty default value to path variable '{2}'. Note that UriTemplate path variables cannot be bound to a null or empty value. See the documentation for UriTemplate for more details. UriTemplate does not support '{0}' as a valid format for a segment or a query part. The UriTemplate '{0}' is not valid; the UriTemplate variable declaration '{1}' isn't a valid variable construct. Note that UriTemplate variable definitions are either a simple, non-empty, variable name or a 'name=value' format, where the name must not be empty and the value provides a default value to the variable. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the wildcard ('{1}') cannot appear in a variable name or literal, unless as a construct for a wildcard segment. Note that a wildcard segment, either a literal or a variable, is valid only as the last path segment in the template; the wildcard can appear only once. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the additional default value '{1}' has a null value as default value. Note that null default values must be only provided to concrete path variables. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate path variable '{1}' has a null default value while following path variable '{2}' has no defaults or provides a non-null default value. Note that UriTemplate path variable with null default value must be followed only with other path variables with null defaulted values. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate path variable '{1}' has a null default value while the following path segment '{2}' is not a variable segment with a null default value. Note that UriTemplate path variable with null default values must be followed only with other path variables with null defaulted value. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate path variable '{1}' has a null default value while the template is finished with a wildcard. Note that UriTemplate path variable with null default values must be followed only with other path variables with null defaulted value. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the query string cannot end with '&amp;'. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; each portion of the query string must be of the form 'name=value', when value cannot be a compound segment. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; each portion of the query string must be of the form 'name' or of the form 'name=value'. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; each portion of the query string must be of the form 'name' or of the form 'name=value', where name is a simple literal. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; each portion of the query string must be of the form 'name' or of the form 'name=value', where each name is unique. Note that the names are case-insensitive. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate last path segment '{1}' provides a default value to final star variable '{2}'. Note that UriTemplate doesn't support default values to final star variable. See the documentation for UriTemplate for more details. The UriTemplate '{0}' is not valid; the UriTemplate final star variable '{1}' has been provides a default value as part of the additional defaults information. Note that UriTemplate doesn't support default values to final star variable. See the documentation for UriTemplate for more details. UriTemplateTable does not support '{0}' and '{1}' since they are not equivalent, but cannot be disambiguated because they have equivalent paths and the same common literal values for the query string. See the documentation for UriTemplateTable for more detail. BaseAddress must an absolute uri. BaseAddress has not been set. Set the BaseAddress property before calling MakeReadOnly, Match, or MatchSingle. Cannot change BaseAddress after calling MakeReadOnly. UriTemplateTable (with allowDuplicateEquivalentUriTemplates = false) does not support both '{0}' and '{1}', since they are equivalent. Call MakeReadOnly with allowDuplicateEquivalentUriTemplates = true to use both of these UriTemplates in the same table. See the documentation for UriTemplateTable for more detail. KeyValuePairs must have at least one element. An invalid template '{0}' was passed as the key in a pair of template and its associated object. UriTemplateTable Key-Value pairs must always contain a valid UriTemplate object as key; note that UriTemplateTable doesn't support templates that are ignoring the trailing slash in respect to matching. See the documentation for UriTemplateTable for more details. There were multiple UriTemplateMatch results, but MatchSingle was called. Parameter 'baseAddress' must an absolute uri. A null UriTemplate was passed as the key in a pair of template and its associated object. UriTemplateTable Key-Value pairs must always contain a valid UriTemplate object as key. See the documentation for UriTemplateTable for more details. UriTemplateTable does not support multiple templates that have equivalent path as template '{0}' but have different query strings, where the query strings cannot all be disambiguated via literal values. See the documentation for UriTemplateTable for more detail. The UriTemplate '{0}' is not valid; the UriTemplate variable named '{1}' appears multiple times in the template. Note that UriTemplate variable names are case-insensitive. See the documentation for UriTemplate for more details. The value of this argument must be greater than 0. The value of this argument must fall within the range {0} to {1}. The value of this argument must be non-negative. The value of this argument must be positive. Parameter at index {0} is null. WaitForMessage timed out after {0}. The time allotted to this operation may have been a portion of a longer timeout. Similar ServiceEndpoints were exported. The WSDL export process was forced to suffix wsdl:binding names to avoid naming conflicts.\r\n Similar ServiceEndpoints means different binding instances having the Name: {0} and Namespace: {1} and either the same ContractDescription or at least the same contract Name: {2}. An operation was skipped during export because the property '{0}' is set to '{1}'. This operation should be used for server only and should not be exposed from WSDL. \r\nContract Name:{2}\r\nContract Namespace:{3}\r\nOperation Name:{4} An operation was skipped during export because it has a wildcard action. This is not supported in WSDL.\r\nContract Name:{0}\r\nContract Namespace:{1}\r\nOperation Name:{2} Specified argument was out of the range of valid values. The parameter '{0}' cannot be an empty string. Enumeration has either not started or has already finished. Specified value has invalid Control characters. Specified value has invalid CRLF characters. Specified value has invalid HTTP Header characters. Specified value has invalid non-ASCII characters. HttpChannelFactory cannot create the channel with shape '{0}' when the {1} of {2} was set as '{3}'. The server didn't accept the connection request. It is possible that the client side message encoding format or message transfer mode doesn't match the setting on the server side. Please check your binding settings. The server didn't accept the connection request. It is possible that the client side message encoding format doesn't match the setting on the server side. Please check your binding settings. WebSocket object cannot be accessed directly. Invalid value for the {0} type. The type '{1}' does not derive from the appropriate base class '{2}' or is abstract. This service does not support WebSocket connections. This service only supports WebSocket connections. The value specified ('{0}') contains more than one subprotocol which is not supported. Empty string is not a valid subprotocol value. Please use \"null\" to specify no value. The subprotocol '{0}' is invalid because it contains the invalid character '{1}'. The subprotocol '{0}' was not requested by the client - no '{1}' header was included in the request. The subprotocol '{0}' was not requested by the client. The client requested the following subprotocol(s): '{1}'. Maximum number of pending WebSocket connections ({0}) has been reached. Consider increasing the '{1}' quota on the '{2}' property of the transport. The WebSocketModule is not loaded. Check if the WebSocket feature is installed and the WebSocketModule is enabled in the list of IIS modules (see http://go.microsoft.com/fwlink/?LinkId=231398 for details). This method is not supported for this HTTP content. The opening handshake properties associated with the current WebSocket connection are not available. The most likely cause is that the property '{0}' on the '{1}' object returned from the custom '{2}' is not set. The '{0}' operation timed out after '{1}'. The time allotted to this operation may have been a portion of a longer timeout. 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. This platform does not support client side WebSockets natively. Support for client side WebSockets can be enabled on this platform by providing an implementation of {0}. 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. WebSockets are not supported in the classic pipeline mode. Consider using the integrated pipeline mode for the application pool. This platform does not support server side WebSockets. Cannot write to the stream because the end of the stream marker was already written. 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}'. A WebSocket error occurred. The name of the policy being imported for contract '{0}:{1}' is invalid:'{2}'. It should be either '{3}', '{4}' or '{5}'. Unexpected WebSocket close message received when receiving a message. WebSocket upgrade request failed. Received response status code '{0} ({1})', expected: '{2} ({3})'. WebSocket upgrade request failed. The header '{0}' is missing in the response. Unexpected response - the server accepted the upgrade request but specified the subprotocol '{0}' when no subprotocol was requested. WebSocket upgrade request failed. The value of header '{0}' is '{1}'. The expected value is '{2}'. 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}'). WMI GetObject Query: {0} WMI PutInstance Class: {0} The number of encrypted keys in the message has exceeded the maximum allowed number '{0}'. An asynchronous write was called on the stream without a free buffer. An asynchronous write is pending on the stream. Ensure that there are no uncompleted asynchronous writes before attempting the next write. The identity of the security session renew message does not match the identity of the session token. The WS-AtomicTransaction header was invalid or corrupt. The WS-AT messaging library failed to initialize. The MSDTC transaction manager's WS-AtomicTransaction protocol service '{0}' is disabled and cannot unmarshal incoming transactions. A client-side channel to the WS-AT protocol service could not be created. The WS-AtomicTransaction transaction formatter could not read the registry value '{0}'. A registration service address could not be created from MSDTC whereabouts information. A previous call to this WsdlExporter left it in a faulted state. It is no longer usable. A WSDL import extension threw an exception during the BeforeImport call: {0}\r\nError: {1} An exception was thrown in a call to a WSDL export extension: {0}\r\n contract: {1} An exception was thrown in a call to a WSDL export extension: {0}\r\n Endpoint: {1} An exception was thrown while running a WSDL import extension: {0}\r\nError: {1} The type {0} registered as a WSDL extension does not have a public default constructor. WSDL extensions must have a public default constructor. The ContractDescription argument to ImportEndpoints must be contained in the KnownContracts collection. A previous call to this WsdlImporter left it in a faulted state. It is no longer usable. There was an error importing a {0} that the {1} is dependent on.\r\nXPath to {0}: {2} Cannot import {0}\r\nDetail: {2}\r\nXPath to Error Source: {1} A previous attempt to import this {0} already failed. The sequence has been terminated by the remote endpoint. {0} The reliable session was faulted. An error occurred while processing a message. {0} The remote endpoint has responded to a {0} request message with an invalid reply. The reply has a wsa:RelatesTo header with an unexpected identifier. The reliable session cannot continue. The wsrm:{0} request message's wsa:ReplyTo address containing a URI which is not equivalent to the remote address. This is not supported. The reliable session was faulted. The RM server requires the use of WS-ReliableMessaging 1.1 protocol. This is likely caused by a binding mismatch. 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} X509Chain does not have any valid certificates. Cannot find '{0}' value in dictionary string. An internal error has occurred. The XML buffer is not in the correct state to perform the operation. The size necessary to buffer the XML content exceeded the buffer quota. Context protocol was unable to parse the callback context header. Context protocol was unable to parse the context header. cdata '{0}' comment '{0}' element '{0}' from namespace '{1}' end element '{0}' from namespace '{1}' end of file node {0} text '{0}' The value '{0}' cannot be parsed as the type '{1}'. Stream returned by OperationStreamProvider cannot be null. Required xml:lang attribute value is missing. Line {0}, position {1}. Start element expected. Found {0}. XPath:{0} \"XPath Unavailable\" Missing required '{0}' attribute. Specified file length was too large for the file system. Index was out of range. Must be non-negative and less than the size of the collection. Index and count must refer to a location within the buffer. Non-negative number required. An item with the same key has already been added. IDN labels must be between 1 and 63 characters long. Invalid IDN encoded string. Decoded string is not a valid IDN name. Invalid Unicode code point found at index {0}. String contains invalid Unicode code points. Insufficient memory to continue the execution of the program. Assertion failed. ---- DEBUG ASSERTION FAILED ---- ---- Assert Long Message ---- ---- Assert Short Message ---- Fail: {0} The file '{0}' already exists. Unable to find the specified file. Could not find file '{0}'. Could not find a part of the path. Could not find a part of the path '{0}'. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. A URI scheme name '{0}' already has a registered custom parser. Invalid URI: The Authority/Host could not be parsed. Invalid URI: The Authority/Host cannot end with a backslash character ('\\'). Invalid URI: The format of the URI could not be determined. Invalid URI: The hostname could not be parsed. Invalid URI: Invalid port specified. Invalid URI: The URI scheme is not valid. Invalid URI: There is an invalid sequence in the string. An invalid Unicode character by IDN standards was specified in the host. Invalid URI: The username:password construct is badly formed. A relative URI cannot be created because the 'uriString' parameter represents an absolute URI. Invalid URI: The URI is empty. The value '{0}' passed for the UriKind parameter is invalid. Invalid URI: A Dos path must be rooted, for example, 'c:\\'. The URI parser instance passed into 'uriParser' parameter is already registered with the scheme name '{0}'. This operation is not supported for a relative URI. UriComponents.SerializationInfoString must not be combined with other UriComponents. A derived type '{0}' has reported an invalid value for the Uri port '{1}'. Invalid URI: The Uri scheme is too long. Invalid URI: The Uri string is too long. A derived type '{0}' is responsible for parsing this Uri instance. The base implementation must not be used. Access to the path is denied. Access to the path '{0}' is denied. Unknown error '{0}'. The base type '{0}' cannot be abstract. The base type '{0}' cannot be sealed. The base type '{0}' must have a public parameterless constructor. The type '{0}' must be an interface, not a class. Invalid number of rows of Assembly table: {0}. Base reader must be a full metadata reader. Blob is to large. Can't emit a branch, the current encoder not created with a branch builder. The operation is not valid on this builder as it has been linked with another one. Builder must be aligned to 4 byte boundary. Can't get a heap offset for a virtual heap handle EnCMap table not sorted or has missing records. Expected list of size {0}. Expected non-empty list. Handle belongs to a future generation Hash must be at least {0}B long. The limit on the size of {0} heap has been exceeded. Illegal tables in compressed metadata stream. Image is too small. Image is either too small or contains an invalid byte offset or count. Invalid coded index. Invalid compressed integer. Invalid constant value. Value of type '{0}' is not a constant. Invalid COR header size. The value of field Characteristics in debug directory entry must be zero. Invalid directory relative virtual address. Invalid directory size. Invalid document name. Invalid entry point token: 0x{0:8X} Invalid handle. Invalid import definition kind: {0}. Invalid local signature token: 0x{0:X8} Invalid metadata section span. Invalid Metadata stream format. Invalid method header: 0x{0:X2} Invalid method header: 0x{0:X2} 0x{1:X2} Invalid relative virtual address (RVA): 0x{0:X8} Invalid number of sections in declared in PE header. The path must be padded with NUL characters. Invalid PE signature. Invalid row count: {0} Invalid section name Invalid SEH header: 0x{0:X2} Invalid serialized string. Invalid signature. Invalid token. Invalid type size. Specified label doesn't belong to the current builder. Little-endian architecture required. Metadata header too small. Metadata image doesn't represent an assembly. Invalid COR20 header signature. The MetadataStringDecoder instance used to instantiate the Metadata reader must have a UTF8 encoding. Metadata table header too small. Metadata table 0x{0:x2} not sorted. Metadata tables too small. Missing data directory. Invalid number of rows of Module table: {0}. {0} must not return null. Negative byte count or offset. The Debug directory was not of type CodeView. Not enough space for Blob stream. Not enough space for GUID stream. Not enough space for Metadata stream. Not enough space for stream header name. Not enough space for String stream. Not enough space for version string. Specified handle is not a valid metadata heap handle. Specified handle is not a valid metadata table or UserString heap handle. Specified handle is not a TypeDefinitionHandle or TypeRefererenceHandle. Specified handle is not a TypeDefinitionHandle, TypeRefererenceHandle, or TypeSpecificationHandle. Read out of bounds. Write out of bounds. PE image does not have metadata. PE image not available. Specified readers must be minimal delta metadata readers. The size of the builder returned by {0}.{1} is smaller than requested. Row ID or heap offset is too large. Section too small. Sequence point value is out of range. Can't add vararg parameters to non-vararg signature. Signature provider returned invalid signature. Signature type sequence must have at least one element. Standalone debug metadata image doesn't contain Module table. Stream header too small. Stream must support read and seek operations. Stream length minus starting position is too large to hold a PEImage. Table row count space to small. There are too many subnamespaces. Unable to read metadata file. Unexpected CodeView data signature value. Unexpected handle kind: {0}. Unexpected op-code: {0}. Expected signature header for '{0}', but found '{1}' (0x{2:x2}). Expected signature header for '{0}' or '{1}', but found '{2}' (0x{3:x2}). Unexpected SignatureTypeCode: (0x{0:x}). Unexpected stream end. Unknown file format. Unknown PE Magic value. Unknown section name: '{0}'. Unknown tables: 0x{0:x16}. Value must be multiple of {0}. Value is too large. Missing mscorlib reference in AssemblyRef table. Value must be positive. Index was out of range. Must be non-negative and less than the size of the collection. The specified length exceeds the maximum value of {0}. '{0}' must be greater than zero. Non-negative number required. StartIndex cannot be less than zero. An item with the same key has already been added. FrameworkName is invalid. FrameworkName version component is invalid. FrameworkName version component is missing. FrameworkName cannot have less than two components or more than three components. Illegal characters in path. '{0}' cannot be greater than {1}. Path cannot be the empty string or all whitespace. The given path's format is not supported. URI formats are not supported. Destination array is not long enough to copy all the items in the collection. Check array index and length. Search pattern cannot contain \"..\" to move up directories and can be contained only internally in file/directory names, as in \"a..b\". Second path fragment must not be a drive or UNC name. Paths that begin with \\\\?\\GlobalRoot are internal to the kernel and should not be opened by managed applications. The path is not of a legal form. The UNC path should be of the form \\\\server\\share. Cannot create '{0}' because a file or directory with the same name already exists. The file '{0}' already exists. Unable to find the specified file. Could not find file '{0}'. Could not find a part of the path. Could not find a part of the path '{0}'. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. The process cannot access the file '{0}' because it is being used by another process. The process cannot access the file because it is being used by another process. The parameter '{0}' cannot be an empty string. Access to the path is denied. Access to the path '{0}' is denied. Unknown error '{0}'. Value cannot be empty. Non-negative number required. maximumThreshold cannot be less than initialThreshold. maximumThreshold cannot be less than initialThreshold. Non-negative number required. Handle collector count overflows or underflows. The number must be greater than or equal to zero. Format specifier was invalid. With the AllowHexSpecifier bit set in the enum bit field, the only other valid bits that can be combined into the enum value must be a subset of those in HexNumber. An undefined NumberStyles value is being used. The parameter must be a BigInteger. The value is too large to be represented by this format specifier. BigInteger cannot represent infinity. Value was either too large or too small for a Decimal. Value was either too large or too small for an Int32. Value was either too large or too small for an Int64. The value is not a number. The value could not be parsed. Value was either too large or too small for a UInt32. Value was either too large or too small for a UInt64. Property 'Order' in DataMemberAttribute attribute cannot be a negative number. Serialization error. Buffer cannot be null. Cannot set the length of a stream to a negative value. Enum value was out of legal range. The specified value is not a valid member of the InputStreamOptions enumeration. Cannot seek to an absolute stream position that is negative. The length cannot be greater than the capacity. '{0}' must be greater than zero. Non-negative number required. Length must be non-negative. Stream length must be non-negative and less than 2^31 - 1 - origin. UnmanagedMemoryStream length must be non-negative and less than 2^63 - 1 - baseAddress. The UnmanagedMemoryStream capacity would wrap around the high end of the address space. The buffer size for a Windows Runtime stream adapter may not be negative. Use a positive buffer size or 0 to disable buffering. The specified buffer index is not within the buffer capacity. The specified useful data length exceeds the capacity of this buffer. The specified index is out of bounds of the specified array. The specified Windows Runtime stream supports the IRandomAccessStream interface and its CanRead property returns TRUE, however it does not implement the IInputStream interface. Windows Runtime streams with such inconsistent capabilities cannot be converted to managed Stream objects. IRandomAccessStream instances whose CanRead property returns TRUE must implement the IInputStream interface. The specified Windows Runtime stream supports the IRandomAccessStream interface and its CanWrite property returns TRUE, however it does not implement the IOutputStream interface. Windows Runtime streams with such inconsistent capabilities cannot be converted to managed Stream objects. IRandomAccessStream instances whose CanWrite property returns TRUE must implement the IOutputStream interface. The specified array does not contain the specified number of elements starting at the specified offset. The specified buffer capacity is not sufficient to hold data of the specified length. The specified source buffer does not contain the specified number of elements starting at the specified offset. The specified destination buffer is not large enough to hold the specified number of bytes starting at the specified offset. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Offset and length were greater than the size of the SafeBuffer. Invalid seek origin. Cannot convert the specified Stream object to a Windows Runtime stream because it does not have sufficient capabilities. In order to convert a System.IO.Stream instance to a Windows Runtime stream at least one of the properties CanRead, CanWrite, CanSeek must return TRUE; however, none of these properties returns TRUE for the specified Stream. The specified object cannot be converted to a System.IO.Stream instance because it is not a Windows Runtime stream. In order to convert an object to a Stream instance it must implement at least one of the following 3 Windows Runtime stream interfaces: IInputStream, IOutputStream, IRandomAccessStream. The specified relative path may not consist of white spaces only The specified stream position is beyond the end of the stream. The specified AsyncResult does not correspond to any outstanding IO operation. The specified Windows Runtime stream does not support reading nor writing. Windows Runtime streams with such capabilities cannot be converted to managed Stream objects. Use a Windows Runtime stream that can support reading, writing or both. Not enough space available in the buffer. Empty. Unmanaged memory stream position was beyond the capacity of the stream. The method cannot be called twice on the same instance. The state of this object does not permit invoking this method. Cannot convert the specified Windows Runtime stream to a managed System.IO.Stream object with the specified buffer size because this Windows Runtime stream has been previously converted to a managed Stream object with a different buffer size. Ensure that the 'bufferSize' argument matches the existing buffer or use the '{0}'-overload without the 'bufferSize' argument to convert the specified Windows Runtime stream to a Stream object with the same buffer size as previously. Cannot convert the specified Windows Runtime stream to a managed System.IO.Stream object without a buffer because this Windows Runtime stream has been previously converted to a managed Stream object with a buffer. Ensure that the 'bufferSize' argument matches the existing buffer or use the '{0}'-overload without the 'bufferSize' argument to convert the specified Windows Runtime stream to a Stream object with the same buffer size as previously. Cannot call GetResults on this asynchronous info because the underlying operation has not completed. The 'Completed' handler delegate cannot be set more than once, but this handler has already been set. Cannot set the size of this stream because it cannot be written to. The specified state transition is illegal for the current state of this object. The asynchronous operation could not be completed. A callback for the same asynchronous IO operation was invoked more than once. Send is not supported in the Windows Runtime SynchronizationContext The Task provider delegate specified for this IAsyncInfo instance returned a Task object that was not started. Task instances must be run immediately upon creation. This AsyncResult or Task corresponds to a different asynchronous operation ID than the one that invoked the completion callback. The specified underlying Task is not started. Task instances must be run immediately upon creation. Cannot seek to an absolute stream position that is larger than 2^63 - 1 bytes. (2^63 - 1 = 0x7FFFFFFFFFFFFFFF = Int64.MaxValue). This Windows Runtime stream is backed by a .NET Stream; its size cannot be set to a value that is larger than 2^63 - 1 bytes. (2^63 - 1 = 0x7FFFFFFFFFFFFFFF = Int64.MaxValue). Unable to expand length of this stream beyond its capacity. An IO error occurred in the Windows runtime system. An attempt was made to move the position before the beginning of the stream. Stream was too long. This Stream is backed by a Windows Runtime stream with a length that exceeds 2^63 - 1 bytes. Operations related to the stream's length or position cannot be performed on streams when the length exceeds 2^63 - 1 bytes. (2^63 - 1 = 0x7FFFFFFFFFFFFFFF = Int64.MaxValue = approx. 8000 PetaBytes.) A native library routine was not found: {0}. Cannot use the specified Stream as a Windows Runtime IInputStream because this Stream is not readable. Cannot use the specified Stream as a Windows Runtime IRandomAccessStream because this Stream does not support seeking. Cannot use the specified Stream as a Windows Runtime IOutputStream because this Stream is not writable. This stream does not support read access. This stream does not support seeking. This stream does not support the Length property because it is not seekable. This stream does not support the Position property because it is not seekable. Cannot write to a BufferedStream while the read buffer is not empty if the underlying stream is not seekable. Ensure that the stream underlying this BufferedStream can seek or avoid interleaving read and write operations on this BufferedStream. This stream does not support write access. This IRandomAccessStream does not support the {0} method because it requires cloning and this stream does not support cloning. This operation is not supported for an UnmanagedMemoryStream created from a SafeBuffer. Stream does not support reading. Stream does not support seeking. Stream does not support writing. The Windows Runtime stream that underlies this System.IO.Stream object has invoked an IO completion callback and specified null for the IAsyncInfo instance that describes the completed IO operation. This behavior is not supported because results cannot be retrieved from a null operation. Either the underlying Windows Runtime stream has a faulty implementation, or you are using a Windows Runtime object in an unsupported runtime environment. The task provider delegate used to create this asynchronous operation returned null, but a valid Task object was expected. The requested invocation is not permitted because this IAsyncInfo instance has already been closed. The requested operation cannot be performed because this stream has already been disposed. Cannot access a closed Stream. MemoryStream's internal buffer cannot be accessed. An error has occurred. Invalid value for {0} property on CornerRadius. Invalid argument. The element is not available. The element is not enabled. A cycle occurred while laying out the GUI. XAML parsing failed. Actor cannot be set so that circular directed graph will exist chaining the subjects together. The Claim '{0}' was not able to be removed. It is either not part of this Identity or it is a claim that is owned by the Principal that contains this Identity. For example, the Principal will own the claim when creating a GenericPrincipal with roles. The roles will be exposed through the Identity that is passed in the constructor, but not actually owned by the Identity. Similar logic exists for a RolePrincipal. Buffer cannot be null. Non-negative number required. Positive number required. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. The OID value was invalid. Value was invalid. Error occurred during a cryptographic operation. Object contains only the public half of a key pair. A private key must also be provided. The specified curve '{0}' or its parameters are not valid for this platform. The hash algorithm name cannot be null or empty. The specified key parameters are not valid. Q.X and Q.Y are required fields. Q.X, Q.Y must be the same length. If D is specified it must be the same length as Q.X and Q.Y for named curves or the same length as Order for explicit curves. The specified Oid is not valid. The Oid.FriendlyName or Oid.Value property must be set. The specified Characteristic2 curve parameters are not valid. Polynomial, A, B, G.X, G.Y, and Order are required. A, B, G.X, G.Y must be the same length, and the same length as Q.X, Q.Y and D if those are specified. Seed, Cofactor and Hash are optional. Other parameters are not allowed. The specified named curve parameters are not valid. Only the Oid parameter must be set. The specified prime curve parameters are not valid. Prime, A, B, G.X, G.Y and Order are required and must be the same length, and the same length as Q.X, Q.Y and D if those are specified. Seed, Cofactor and Hash are optional. Other parameters are not allowed. Specified initialization vector (IV) does not match the block size for this algorithm. Specified key is not a valid size for this algorithm. Specified key is a known semi-weak key for '{0}' and cannot be used. Specified key is a known weak key for '{0}' and cannot be used. Specified padding mode is not valid for this algorithm. Specified padding mode is not valid for this algorithm. The specified RSA parameters are not valid; both Exponent and Modulus are required fields. The string contains a character not in the 7 bit ASCII character set. The cipher mode specified requires that an initialization vector (IV) be used. TransformBlock may only process bytes in block sized increments. Key is not a valid private key. Key is not a valid public or private key. Cannot open an invalid handle. The input data is not a complete block. Salt is not at least eight bytes. Algorithm is unavailable or is not supported for this operation. The Initialization vector should have the same length as the algorithm block size in bytes. EffectiveKeySize value must be at least 40 bits. KeySize value must be at least as large as the EffectiveKeySize value. Attempt to transform beyond end of buffer. CNG provider unexpectedly terminated encryption or decryption prematurely. '{0}' is not a known hash algorithm. Unknown padding mode used. The specified PaddingMode is not supported. Method not supported. Derived class must override. Buffer cannot be null. Non-negative number required. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. The keys from both parties must be the same size to generate a secret agreement. Keys used with the ECDiffieHellmanCng algorithm must have an algorithm group of ECDiffieHellman. Keys used with the ECDsaCng algorithm must have an algorithm group of ECDsa. DeriveKeyMaterial requires an ECDiffieHellmanCngPublicKey. Keys used with the RSACng algorithm must have an algorithm group of RSA. This key is for algorithm '{0}'. Expected '{1}'. The specified curve '{0}' or its parameters are not valid for this platform. XML serialization of an elliptic curve key requires using an overload which specifies the XML format to be used. The hash algorithm name cannot be null or empty. The algorithm group '{0}' is invalid. The algorithm name '{0}' is invalid. Specified cipher mode is not valid for this algorithm. The specified Oid is not valid. The Oid.FriendlyName property must be set, or be determined from Oid.Value. Specified initialization vector (IV) does not match the block size for this algorithm. The key blob format '{0}' is invalid. Specified key is not a valid size for this algorithm. Specified padding mode is not valid for this algorithm. The provider name '{0}' is invalid. The specified RSA parameters are not valid; both Exponent and Modulus are required fields. The hash algorithm is not supported for signatures. Only MD5, SHA1, SHA256,SHA384, and SHA512 are supported at this time. Key Blob not in expected format. The cipher mode specified requires that an initialization vector (IV) be used. TransformBlock may only process bytes in block sized increments. This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. Key is not a valid private key. Key is not a valid public or private key. The CNG key handle being opened was detected to be ephemeral, but the EphemeralKey open option was not specified. Cannot open an invalid handle. The input data is not a complete block. The specified cryptographic algorithm is not supported on this platform. EffectiveKeySize must be the same as KeySize in this implementation. The TLS key derivation function requires both the label and seed properties to be set. Attempt to transform beyond end of buffer. CNG provider unexpectedly terminated encryption or decryption prematurely. '{0}' is not a known hash algorithm. Unknown padding mode used. The specified PaddingMode is not supported. Specified key is a known weak key for this algorithm and cannot be used. Method not supported. Unsupported hash algorithm. RSACng currently supports only MD5, SHA1, SHA256, SHA384 and SHA512. Index was out of range. Must be non-negative and less than the size of the collection. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Only single dimensional arrays are supported for the requested action. No OID value matches this name. The OID value is invalid. Non-negative number required. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. Value was invalid. Stream was not readable. Stream was not writable. Error occurred during a cryptographic operation. Accessing a hash algorithm by manipulating the HashName property is not supported on this platform. Instead, you must instantiate one of the supplied subtypes (such as HMACSHA1.) FlushFinalBlock() method was called twice on a CryptoStream. It can only be called once. Specified block size is not valid for this algorithm. Specified cipher mode is not valid for this algorithm. Specified initialization vector (IV) does not match the block size for this algorithm. Specified key is not a valid size for this algorithm. Specified padding mode is not valid for this algorithm. Setting the hashname after it's already been set is not supported on this platform. Stream does not support reading. Stream does not support seeking. Stream does not support writing. Index was out of range. Must be non-negative and less than the size of the collection. Value of flags is invalid. The value of 'nameType' is invalid. Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection. The OID value was invalid. Array may not be empty or null. String cannot be empty or null. Illegal enum value: {0}. Invalid handle. Non-negative number required. Only single dimensional arrays are supported for the requested action. Cannot remove the specified item because it was not found in the specified Collection. The certificate has invalid policy. Unable to get file status. The chain context handle is invalid. Invalid directory permissions. The directory '{0}' must be readable, writable and executable by the owner. Invalid file permissions. The file '{0}' must readable and writable by the current owner and by no one else, and the permissions could not be changed to meet that criteria. {0} is an invalid handle. Object identifier (OID) is unknown. The store handle is invalid. The string contains a character not in the 7 bit ASCII character set. The string contains an invalid X500 name attribute key, oid, value or delimiter. The owner of '{0}' is not the current user. Unix LocalMachine X509Stores are read-only for all users. Unix LocalMachine X509Store is limited to the Root and CertificateAuthority stores. The {0} value cannot be set on Unix. X509ContentType.SerializedCert and X509ContentType.SerializedStore are not supported on Unix. The certificate export operation failed. The parameter should be an X509Extension. Invalid content type. Invalid find type. Invalid find value. The public key of the certificate does not match the value specified. Cannot find the original signer. The X509 certificate could not be added to the store because all candidate file names were in use. The specified X509 certificate store does not exist. The X509 certificate store has not been opened. The X509 certificate store is read-only. Enumeration has not started. Call MoveNext. Cannot obtain public key from X509Certificate. Public Key ASN.1 is in an unexpected format. CryptoApi ECDsa keys are not supported. Only one certificate with a private key can be exported in a single PFX. Only asymmetric keys that implement ICspAsymmetricAlgorithm are supported. The certificate key algorithm is not supported. The X509 Basic Constraints extension with OID 2.5.29.10 is not supported. The home directory of the current user could not be determined. The {0} value was invalid. Unknown error. Array cannot be null. Too many characters. The resulting number of bytes is larger than what can be returned as an int. Too many bytes. The resulting number of chars is larger than what can be returned as an int. Index was out of range. Must be non-negative and less than the size of the collection. Index and count must refer to a location within the string. Index and count must refer to a location within the buffer. Non-negative number required. Valid values are between {0} and {1}, inclusive. {0} is not a supported code page. Must complete Convert() operation or call Encoder.Reset() before calling GetBytes() or GetByteCount(). Encoder '{0}' fallback '{1}'. The output byte buffer is too small to contain the encoded data, encoding '{0}' fallback '{1}'. The output char buffer is too small to contain the decoded characters, encoding '{0}' fallback '{1}'. String contains invalid Unicode code points. Recursive fallback not allowed for character \\u{0:X4}. Recursive fallback not allowed for bytes {0}. Insufficient memory to continue the execution of the program. Western European (Mac) Japanese (Mac) Chinese Traditional (Mac) Korean (Mac) Arabic (Mac) Hebrew (Mac) Greek (Mac) Cyrillic (Mac) Chinese Simplified (Mac) Romanian (Mac) Ukrainian (Mac) Thai (Mac) Central European (Mac) Icelandic (Mac) Turkish (Mac) Croatian (Mac) IBM EBCDIC (Turkish Latin-5) IBM Latin-1 IBM EBCDIC (US-Canada-Euro) IBM EBCDIC (Germany-Euro) IBM EBCDIC (Denmark-Norway-Euro) IBM EBCDIC (Finland-Sweden-Euro) IBM EBCDIC (Italy-Euro) IBM EBCDIC (Spain-Euro) IBM EBCDIC (UK-Euro) IBM EBCDIC (France-Euro) IBM EBCDIC (International-Euro) IBM EBCDIC (Icelandic-Euro) Central European (Windows) Cyrillic (Windows) Western European (Windows) Greek (Windows) Turkish (Windows) Hebrew (Windows) Arabic (Windows) Baltic (Windows) Vietnamese (Windows) Korean (Johab) Chinese Traditional (CNS) TCA Taiwan Chinese Traditional (Eten) IBM5550 Taiwan TeleText Taiwan Wang Taiwan Western European (IA5) German (IA5) Swedish (IA5) Norwegian (IA5) T.61 ISO-6937 IBM EBCDIC (Germany) IBM EBCDIC (Denmark-Norway) IBM EBCDIC (Finland-Sweden) IBM EBCDIC (Italy) IBM EBCDIC (Spain) IBM EBCDIC (UK) IBM EBCDIC (Japanese katakana) IBM EBCDIC (France) IBM EBCDIC (Arabic) IBM EBCDIC (Greek) IBM EBCDIC (Hebrew) IBM EBCDIC (Korean Extended) IBM EBCDIC (Thai) Cyrillic (KOI8-R) IBM EBCDIC (Icelandic) IBM EBCDIC (Cyrillic Russian) IBM EBCDIC (Turkish) IBM Latin-1 Japanese (JIS 0208-1990 and 0212-1990) Chinese Simplified (GB2312-80) Korean Wansung IBM EBCDIC (Cyrillic Serbian-Bulgarian) Ext Alpha Lowercase Cyrillic (KOI8-U) Central European (ISO) Latin 3 (ISO) Baltic (ISO) Cyrillic (ISO) Arabic (ISO) Greek (ISO) Hebrew (ISO-Visual) Turkish (ISO) Estonian (ISO) Latin 9 (ISO) Europa IBM EBCDIC (US-Canada) Hebrew (ISO-Logical) OEM United States IBM EBCDIC (International) User Defined Japanese (JIS) Japanese (JIS-Allow 1 byte Kana) Japanese (JIS-Allow 1 byte Kana - SO/SI) Korean (ISO) Chinese Simplified (ISO-2022) Chinese Traditional (ISO-2022) IBM EBCDIC (Japanese and Japanese Katakana) IBM EBCDIC (Japanese and US-Canada) IBM EBCDIC (Korean and Korean Extended) IBM EBCDIC (Simplified Chinese) IBM EBCDIC (Traditional Chinese) IBM EBCDIC (Japanese and Japanese-Latin) Japanese (EUC) Chinese Simplified (EUC) Korean (EUC) Chinese Simplified (HZ) Chinese Simplified (GB18030) ISCII Devanagari ISCII Bengali ISCII Tamil ISCII Telugu ISCII Assamese ISCII Oriya ISCII Kannada ISCII Malayalam ISCII Gujarati ISCII Punjabi Arabic (ASMO 708) Arabic (DOS) Greek (DOS) Baltic (DOS) Western European (DOS) Central European (DOS) OEM Cyrillic Turkish (DOS) OEM Multilingual Latin I Portuguese (DOS) Icelandic (DOS) Hebrew (DOS) French Canadian (DOS) Arabic (864) Nordic (DOS) Cyrillic (DOS) Greek, Modern (DOS) IBM EBCDIC (Multilingual Latin-2) Thai (Windows) IBM EBCDIC (Greek Modern) Japanese (Shift-JIS) Chinese Simplified (GB2312) Korean Chinese Traditional (Big5) Could not find a resource entry for the encoding codepage '{0} - {1}' No data is available for encoding {0}. Alternation conditions do not capture and cannot be named. Alternation conditions cannot be comments. Cannot include class \\{0} in character range. Start index cannot be less than 0 or greater than input length. Capture number cannot be zero. Capture group numbers must be less than or equal to Int32.MaxValue. Count cannot be less than -1. Enumeration has either not started or has already finished. Illegal conditional (?(...)) expression. Illegal \\ at end of pattern. Illegal {x,y} with x > y. Incomplete \\p{X} character escape. Internal error in ScanRegex. Invalid group name: Group names must begin with a word character. Length cannot be less than 0 or exceed input length. parsing '{0}' - {1} Malformed \\k<...> named back reference. (?({0}) ) malformed. Malformed \\p{X} character escape. Missing control character. Nested quantifier {0}. Result cannot be called on a failed Match. Not enough )'s. This operation is only allowed once per object. Quantifier {x,y} following nothing. The RegEx engine has timed out while trying to match a pattern to an input string. This can occur for many reasons, including very large inputs or excessive backtracking caused by nested quantifiers, back-references and other factors. Replacement pattern error. [x-y] range in reverse order. A subtraction must be the last element in a character class. Insufficient hexadecimal digits. Too many | in (?()|). Too many )'s. Reference to undefined group number {0}. Reference to undefined group name {0}. (?({0}) ) reference to undefined group. Unexpected opcode in regular expression generation: {0}. Unimplemented state. Unknown property '{0}'. Unrecognized control character. Unrecognized escape sequence \\{0}. Unrecognized grouping construct. Unterminated [] set. Unterminated (?#...) comment. 'handle' has already been bound to the thread pool, or was not opened for asynchronous I/O. 'handle' has been disposed or is an invalid handle. 'overlapped' has already been freed. 'overlapped' was not allocated by this ThreadPoolBoundHandle instance. 'preAllocated' is already in use. NativeOverlapped cannot be reused for multiple operations. The postPhaseAction failed with an exception. The participantCount argument must be a positive value. Adding participantCount participants would result in the number of participants exceeding the maximum number allowed. The participantCount argument must be non-negative and less than or equal to 32767. The barrier has been disposed. This method may not be called from within the postPhaseAction. The participantCount argument must be less than or equal the number of participants. The participantCount argument is greater than the number of participants that haven't yet arrived at the barrier in this phase. The participantCount argument must be a positive value. The specified timeout must represent a value between -1 and Int32.MaxValue, inclusive. The number of threads using the barrier exceeded the total number of registered participants. The barrier has no registered participants. The operation was canceled. Invalid attempt made to decrement the event's count below zero. The increment operation would cause the CurrentCount to overflow. The event is already signaled and cannot be incremented. A read lock may not be acquired with the write lock held in this mode. Recursive read lock acquisitions not allowed in this mode. Recursive upgradeable lock acquisitions not allowed in this mode. Recursive write lock acquisitions not allowed in this mode. Upgradeable lock may not be acquired with read lock held. Upgradeable lock may not be acquired with write lock held in this mode. Acquiring Upgradeable lock gives the ability to read along with an option to upgrade to a writer. Write lock may not be acquired with read lock held. This pattern is prone to deadlocks. Please ensure that read locks are released before taking a write lock. If an upgrade is necessary, use an upgrade lock in place of the read lock. The lock is being disposed while still being used. It either is being held by a thread and/or has active waiters waiting to acquire the lock. The read lock is being released without being held. The upgradeable lock is being released without being held. The write lock is being released without being held. Number must be no greater than the value specified in BoundedCapacity. Number must be positive. Number must be either non-negative and less than or equal to Int32.MaxValue or -1 BoundedCapacity must be Unbounded or -1 for this dataflow block. The argument must be false if no source from which to consume is specified. The DataflowMessageHeader instance does not represent a valid message header. To construct a DataflowMessageHeader instance, either pass a non-zero value or use the parameterless constructor. This block must only be used with the source from which it was created. Greedy must be true for this dataflow block. The SyncRoot property may not be used for the synchronization of concurrent collections. Block {0} completed as {1}. {2} Block of type {0} instantiated with Id {1}. Source {0} linked to target {1}. Source {0} unlinked from target {1}. {1} task launched from block {0} with {2} message(s) pending. The source completed without providing data to receive. The target block failed to consume a message it had successfully reserved. The target does not have the message reserved. This member is not supported on this dataflow block. The block is intended for a specific purpose that does not utilize this member. Break was called after Stop was called. This method is not supported. Stop was called after Break was called. The Partitioner source returned a null enumerator. This method requires the use of an OrderedPartitioner with the KeysNormalized property set to true. The Partitioner used here must support dynamic partitioning. The Partitioner used here returned a null partitioner source. One of the actions was null. Array cannot be null. Index was out of range. Must be non-negative and less than the size of the collection. Index and count must refer to a location within the string. Index and count must refer to a location within the buffer. Non-negative number required. Valid values are between {0} and {1}, inclusive. Conversion buffer overflow. The output byte buffer is too small to contain the encoded data, encoding '{0}' fallback '{1}'. String contains invalid Unicode code points. Unable to translate Unicode character \\u{0:X4} at index {1} to specified code page. Invalid byte was found at index {0}. The '{0}' value for the 'dateTimeOption' parameter is not an allowed value for the 'XmlDateTimeSerializationMode' enumeration. The parameter entity replacement text must nest properly within markup declarations. The string '{0}' is not a valid {1} value. The string was not recognized as a valid Uri. String must be exactly one character long. Value '{0}' was either too large or too small for {1}. Xml type 'List of {0}' does not support a conversion from Clr type '{1}' to Clr type '{2}'. The String '{0}' cannot be represented as an XmlQualifiedName. A namespace for prefix '{1}' cannot be found. The QName '{0}' cannot be represented as a String. A prefix for namespace '{1}' cannot be found. An asynchronous operation is already in progress. '{0}', hexadecimal value {1}, is an invalid attribute character. Invalid syntax for a decimal numeric entity reference. Unexpected DTD declaration. Invalid syntax for a hexadecimal numeric entity reference. The '{0}' character, hexadecimal value {1}, cannot be included in a name. Invalid namespace declaration. Name cannot begin with the '{0}' character, hexadecimal value {1}. Cannot bind to the reserved namespace. Cannot resolve entity reference '{0}'. Cannot resolve entity reference '{0}' because the DTD has been ignored. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method. Cannot resolve external DTD subset - public ID = '{0}', system ID = '{1}'. Cannot resolve '{0}'. WriteStartDocument cannot be called on writers created with ConformanceLevel.Fragment. Cannot write XML declaration. XML declaration can be only at the beginning of the document. ']]>' is not allowed in character data. Invalid value of a character entity reference. The Writer is closed or in error state. The XmlReader is closed or in error state. '{0}' is an unqualified name and cannot contain the character ':'. Make sure that the ConformanceLevel setting is set to ConformanceLevel.Fragment or ConformanceLevel.Auto if you want to write an XML fragment. An XML error has occurred. BaseUri must be specified either as an argument of XmlReader.Create or on the XmlParserContext. If it is specified on both, it must be the same base URI. DTD must be defined before the document root element. The DTD has already been written out. DTD is prohibited in this XML document. For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method. DTD is not allowed in XML fragments. '{0}' is a duplicate attribute name. Cannot write XML declaration. WriteStartDocument method has already written it. Element '{0}' was not found. Element '{0}' with namespace name '{1}' was not found. The empty string '' is not a valid local name. The empty string '' is not a valid name. Entity replacement text must nest properly within markup declarations. Enumeration data type required. An error has occurred while opening external DTD '{0}': {1} An error has occurred while opening external entity '{0}': {1} An error occurred while parsing EntityName. Line {0}, position {1}. Expecting an attribute type. Expected DTD markup was not found. Expecting an external identifier or an entity value. Expecting external ID, '[' or '>'. Expecting a system identifier or a public identifier. Conditional sections must specify the keyword 'IGNORE' or 'INCLUDE'. '{0}' is an unexpected token. Expecting white space. White space not allowed before '?', '*', or '+'. Expecting '?', '*', or '+'. Expecting 'PCDATA'. Expecting an internal subset or the end of the DOCTYPE declaration. External entity '{0}' reference cannot appear in the attribute value. Standalone document declaration must have a value of 'no' because an external entity '{0}' is referenced. Fragment identifier '{0}' cannot be part of the system identifier '{1}'. Cannot change conformance checking to {0}. Make sure the ConformanceLevel in XmlReaderSettings is set to Auto for wrapping scenarios. Incomplete DTD content. Incomplete entity contents. XmlWriterSettings.{0} can contain only valid XML white space characters when XmlWriterSettings.CheckCharacters and XmlWriterSettings.NewLineOnAttributes are true. An internal error has occurred. '{0}' is an invalid attribute type. '{0}' is not a valid Base64 text sequence. '{0}' is not a valid BinHex text sequence. '{0}' is not a valid BinHex text sequence. The sequence must contain an even number of characters. '{0}', hexadecimal value {1}, is an invalid character. Invalid character in the given encoding. XmlWriterSettings.{0} can contain only valid XML text content characters when XmlWriterSettings.CheckCharacters is true. {1} An XML comment cannot contain '--', and '-' cannot be the last character. A conditional section is not allowed in an internal subset. Invalid content model. Invalid name character in '{0}'. The '{1}' character, hexadecimal value 0x{2}, cannot be included in a name. Invalid NmToken value '{0}'. '{0}' is an invalid XmlNodeType. Operation is not valid due to the current state of the object. A parameter entity reference is not allowed in internal markup. '{0}' is an invalid name for processing instructions. The current position on the Reader is neither an element nor an attribute. The {0} method is not supported on node type {1}. If you want to read typed content of an element, use the ReadElementContentAs method. The {0} method is not supported on node type {1}. The ReadValueAsChunk method is not supported on node type {0}. Data at the root level is invalid. Invalid high surrogate character (0x{0}). A high surrogate character must have a value from range (0xD800 - 0xDBFF). The surrogate pair is invalid. Missing a low surrogate character. The surrogate pair (0x{0}, 0x{1}) is invalid. A high surrogate character (0xD800 - 0xDBFF) must always be paired with a low surrogate character (0xDC00 - 0xDFFF). Invalid text declaration. Version number '{0}' is invalid. The Whitespace or SignificantWhitespace node can contain only XML white space characters. '{0}' is not an XML white space character. Syntax for an XML declaration is invalid. '{0}' is an invalid xml:space value. The input document has exceeded a limit set by {0}. {0} Line {1}, position {2}. There is no Unicode byte order mark. Cannot switch to Unicode. Root element is missing. ReadElementContentAs() methods cannot be called on an element that has child elements. ReadContentAsBase64 and ReadContentAsBinHex method calls cannot be mixed with calls to ReadElementContentAsBase64 and ReadElementContentAsBinHex. ReadValueChunk calls cannot be mixed with ReadContentAsBase64 or ReadContentAsBinHex. ReadContentAsBase64 and ReadContentAsBinHex method calls cannot be mixed with calls to ReadChars, ReadBase64, and ReadBinHex. Cannot have multiple DTDs. There are multiple root elements. Prefix '{0}' cannot be mapped to namespace name reserved for 'xml' or 'xmlns'. XmlReaderSettings.XmlNameTable must be the same name table as in XmlParserContext.NameTable or XmlParserContext.NamespaceManager.NameTable, or it must be null. Only white space characters should be used. Document does not have a root element. There was no XML start tag open. The buffer is not large enough to fit a surrogate pair. Please provide a buffer of size at least 2 characters. Not the same name table. Cannot use a prefix with an empty namespace. {0} method is not supported on this XmlReader. Use CanReadBinaryContent property to find out if a reader implements it. Content cannot be converted to the type {0}. Set XmlReaderSettings.Async to true if you want to use Async Methods. The '{0}' property is read only and cannot be set. ReadSubtree() can be called only if the reader is on an element node. ReadValueChunk method is not supported on this XmlReader. Use CanReadValueChunk property to find out if an XmlReader implements it. General entity '{0}' references itself. Parameter entity '{0}' references itself. The prefix '{0}' cannot be redefined from '{1}' to '{2}' within the same start element tag. The second character surrogate pair is not in the input buffer to be written. Cannot open '{0}'. The Uri parameter must be a file system relative or absolute path. The '{0}' start tag on line {1} position {2} does not match the end tag of '{3}'. There is an unclosed conditional section. There is an unclosed literal string. Reference to undeclared entity '{0}'. The '{0}' namespace is not defined. ']]>' is not expected. Unexpected end tag. Unexpected end of file while parsing {0} has occurred. Unexpected end of file has occurred. Unexpected end of file has occurred. The following elements are not closed: {0} '{0}' is an unexpected token. The expected token is '{1}'. '{0}' is an unexpected token. The expected token is '{1}' or '{2}'. System does not support '{0}' encoding. '{0}' is an undeclared namespace. Reference to unparsed entity '{0}'. Object type is not supported. {0} Set XmlWriterSettings.Async to true if you want to use Async Methods. Token {0} in state {1} would result in an invalid XML document. Unexpected XML declaration. The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. Prefix 'xmlns' is reserved for use by XML. Prefix 'xml' is reserved for use by XML and can be mapped only to namespace name 'http://www.w3.org/XML/1998/namespace'. An attribute cannot be added to content. A node of type {0} cannot be added to content. Non white space characters cannot be added to content. The argument cannot be converted to a string. '{0}' is an invalid expanded name. '{0}' is an invalid name for a processing instruction. '{0}' is an invalid prefix. The argument must be derived from {0}. The prefix '{0}' cannot be bound to the empty namespace name. The prefix 'xml' is bound to the namespace name 'http://www.w3.org/XML/1998/namespace'. Other prefixes must not be bound to this namespace name, and it must not be declared as the default namespace. The prefix 'xmlns' is bound to the namespace name 'http://www.w3.org/2000/xmlns/'. It must not be declared. Other prefixes must not be bound to this namespace name, and it must not be declared as the default namespace. An XObject cannot be used as a value. This instance cannot be deserialized. This operation would create an incorrectly structured document. Duplicate attribute. The XmlReader state should be EndOfFile after this operation. The XmlReader state should be Interactive. The XmlReader must be on a node of type {0} instead of a node of type {1}. This operation was corrupted by external code. A common ancestor is missing. The parent is missing. The root element is missing. The XmlReader should not be on a node of type {0}. The XmlReader cannot resolve entity references. An attribute cannot be written after content. This XmlWriter does not support base64 encoded data. This XmlWriter does not support entity references. Cannot create node of type {0}. The XmlReader passed in to construct this XmlValidatingReaderImpl must be an instance of a System.Xml.XmlTextReader. Type is incompatible. The reference node must be a child of the current node. An 'Attributes' collection can only contain 'Attribute' objects. The 'Attribute' node cannot be inserted because it is already an attribute of another element. The attribute local name cannot be empty. The namespace declaration attribute has an incorrect 'namespaceURI': '{0}'. The 'InnerText' of a 'Document' node is read-only and cannot be set. This document already has an 'XmlDeclaration' node. This document already has a 'DocumentElement' node. This document already has a 'DocumentType' node. The prefix of an element name cannot start with 'xml'. The local name for elements or attributes cannot be null or an empty string. 'EntityReference' nodes have no support for setting value. The 'InnerText' of an 'Entity' node is read-only and cannot be set. The element list has changed. The enumeration operation failed to continue. Cannot import nodes of type '{0}'. Cannot import a null node. The index being passed in is out of range. Cannot create an 'EntityReference' node with a name starting with '#'. '{0}' does not represent any 'XmlNodeType'. The document to be loaded could not be found. There is no reader from which to load the document. The named node is from a different document context. 'Entity' and 'Notation' nodes cannot be cloned. Cannot insert a node or any ancestor of that node as a child of itself. The current node cannot contain other nodes. The node to be inserted is from a different document context. Cannot insert the node in the specified location. The reference node is not a child of this node. The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type. This node is read-only. It cannot be modified. Cannot create a node without an owner document. The node to be removed is not a child of this node. The current node cannot contain other nodes, so the node to be removed is not its child. Cannot set a value on node type '{0}'. The document does not have a root element. Cannot set the 'InnerXml' for the current node because it is either read-only or cannot have children. Wrong value for the XML declaration standalone attribute of '{0}'. The 'Text' node is not connected in the DOM live tree. No 'SplitText' operation could be performed. Wrong XML version information. The XML must match production \"VersionNum ::= '1.' [0-9]+\". The string for white space contains an invalid character. The string '{0}' is not a valid {1} value. Non-CLS Compliant Exception. The '{0}' character, hexadecimal value {1}, cannot be included in a name. Name cannot begin with the '{0}' character, hexadecimal value {1}. Cannot bind to the reserved namespace. The Writer is closed. The Writer is closed or in error state. Cannot write XML declaration. WriteStartDocument method has already written it. The empty string '' is not a valid name. Cannot have ']]>' inside an XML CDATA block. '{0}', hexadecimal value {1}, is an invalid character. An XML comment cannot contain '--', and '-' cannot be the last character. Indentation value must be greater than 0. Invalid name character in '{0}'. Invalid name character in '{0}'. The '{1}' character, hexadecimal value {2}, cannot be included in a name. Operation is not valid due to the current state of the object. Cannot have '?>' inside an XML processing instruction. Prefixes beginning with \"xml\" (regardless of whether the characters are uppercase, lowercase, or some combination thereof) are reserved for use by XML. Invalid XML attribute quote character. Valid attribute quote characters are ' and \". Invalid high surrogate character (0x{0}). A high surrogate character must have a value from range (0xD800 - 0xDBFF). The surrogate pair is invalid. Missing a low surrogate character. The surrogate pair (0x{0}, 0x{1}) is invalid. A high surrogate character (0xD800 - 0xDBFF) must always be paired with a low surrogate character (0xDC00 - 0xDFFF). '{0}' is an invalid xml:space value. Cannot set the namespace if Namespaces is 'false'. Only white space characters should be used. Document does not have a root element. There was no XML start tag open. NotInWriteState. WriteStartDocument needs to be the first call. Resolving of external URIs was prohibited. Cannot use a prefix with an empty namespace. Relative URIs are not supported. The second character surrogate pair is not in the input buffer to be written. Reference to undeclared parameter entity '{0}'. The '{0}' namespace is not defined. An undefined prefix is in use. Unexpected XmlNodeType: '{0}'. Object type is not supported. XmlResolver can be set only by fully trusted code. Token {0} in state {1} would result in an invalid XML document. The 'xmlns' attribute is bound to the reserved namespace 'http://www.w3.org/2000/xmlns/'. Only TypeKind.Root can be set for typeof(object) which is never value type. Cannot remove the specified item because it was not found in the specified Collection. Array of type {0} is not supported. {0} is not assignable from {1}. No conversion possible to {0}. Type {0} cannot inherit from any class other than object to be used as body object in RPC style. Type {0} implements interface {1} which is not supported for body object in RPC style. Error in deserializing body of reply message for operation '{0}'. Error in deserializing body of request message for operation '{0}'. There was an error in serializing body of message {0}: '{1}'. Please see InnerException for more details. In operation {0}, the schema type corresponding to the fault detail type {1} is anonymous. Please set Fault name explicitly to export anonymous types. XmlSerializer attribute {0} is not valid in {1}. Only XmlElement, XmlArray, XmlArrayItem and XmlAnyElement attributes are supported in MessageContract when IsWrapped is false. XmlSerializer attribute {0} is not valid in {1}. Only XmlElement, XmlArray, XmlArrayItem and XmlAnyElement attributes are supported when IsWrapped is true. KnownType cannot be null in operation {0} RPC Message {1} in operation {0} must have a single MessageBodyMember. XmlArrayAttribute cannot be used in repeating part {1}:{0}. Internal Error: Unrecognized constant type {0}. The specified type is abstract: name Cannot include anonymous type '{0}'. The element '{0}' has been attributed with duplicate XmlAnyElementAttribute(Name Ambiguous types specified for member '{0}'. Items '{1}' and '{2}' have the same type. Please consider using {3} with {4} instead. '{0}.{1}' already has attributes. The top XML element '{0}' from namespace '{1}' references distinct types {2} and {3}. Use XML attributes to specify another XML name or namespace for the element or types. The global XML item '{0}' from namespace '{1}' has mismatch default value attributes: '{2}' and '{3}' and cannot be mapped to the same schema item. Use XML attributes to specify another XML name or namespace for one of the items, or make sure that the default values match. The global XML attribute '{0}' from namespace '{1}' references distinct types {2} and {3}. Use XML attributes to specify another XML name or namespace for the attribute or types. Enum values in the XmlChoiceIdentifier '{0}' have to be unique. Value '{1}' already present. Ambiguous choice identifier. There are several members named '{0}'. Missing '{0}' member needed for serialization of choice '{1}'. You need to add {0} to the '{1}' member. Type of choice identifier '{0}' is inconsistent with type of '{1}'. Please use array of {2}. Value '{0}' of the choice identifier '{1}' does not match element '{2}' from namespace '{3}'. Type of choice identifier '{0}' is inconsistent with type of '{1}'. Please use {2}. Choice identifier '{0}' must be an enum. Value of {0} mismatches the type of {1}; you need to set it to {2}. Type {0} is missing enumeration value '##any:' corresponding to XmlAnyElementAttribute. Type {0} is missing enumeration value '{1}' for element '{2}' from namespace '{3}'. A circular reference was detected while serializing an object of type {0}. The type '{0}' cannot be serialized because its parameterless constructor is decorated with declarative security permission attributes. Consider using imperative asserts or demands in the constructor. {0} cannot be serialized because it does not have a parameterless constructor. The string '{0}' is not a valid {1} value. '{0}' is an invalid value for the {1} property. {0} cannot be converted to {2}. Negative values are prohibited. The XML attribute '{0}' from namespace '{1}' is already present in the current scope. Use XML attributes to specify another XML name or namespace for the attribute. The XML element '{0}' from namespace '{1}' is already present in the current scope. Use XML attributes to specify another XML name or namespace for the element. Illegal namespace declaration xmlns:{0} This element was named '{0}' from namespace '{1}' but should have been named '{2}' from namespace '{3}'. There was an error reflecting field '{0}'. There was an error generating the XML document. {0}.{1}() must return a valid type name. You must implement public static {0}({1}) method on {2}. '{0}' is an invalid language identifier. Method {0}.{1}() specified by {2} has invalid signature: return type must be compatible with {3}. Member {0}.{1} of type {2} hides base class member {3}.{4} of type {5}. Use XmlElementAttribute or XmlAttributeAttribute to specify a new name. Cannot serialize member of type {0}: XmlAnyElementAttribute attribute is used incorrectly. XmlArray and XmlArrayItem cannot be used in conjunction with XmlAttribute, XmlElement, XmlText, or XmlAnyElement. Member '{0}' cannot be encoded using the XmlText attribute. You may use only the XmlText attribute to encode certain types such as primitives, enumerations, or arrays of strings. For non-array types, you may use the following attributes: XmlAttribute, XmlText, XmlElement, or XmlAnyElement. XmlAttribute cannot be used to encode array of {1}, because it is marked with FlagsAttribute. XmlAttribute cannot be used in conjunction with XmlElement, XmlText, XmlAnyElement, XmlArray, or XmlArrayItem. Cannot serialize member '{0}' of type {1}. XmlAttribute/XmlText cannot be used to encode complex types. Cannot serialize member '{0}' of type {1}. XmlAttribute/XmlText cannot be used to encode types implementing {2}. XmlElement, XmlText, and XmlAnyElement cannot be used in conjunction with XmlAttribute, XmlArray, or XmlArrayItem. Cannot serialize object of type '{0}' because it has multiple XmlText attributes. Consider using an array of strings with XmlTextAttribute for serialization of a mixed complex type. XmlText may not be used on multiple parameters or return values. Cannot serialize object of type '{0}'. Base type '{1}' has simpleContent and can only be extended by adding XmlAttribute elements. Please consider changing XmlText member of the base class to string array. Cannot serialize member '{0}' of type {1}. SoapAttribute cannot be used to encode complex types. The type for {0} may not be specified for primitive types. {0} cannot be used as: 'xml {1}'. Cannot serialize object of type '{0}'. Consider changing type of XmlText member '{0}.{1}' from {2} to string or string array. Internal error. Internal error: {0}. Internal error: missing generated method for {0}. SOAP-ENC:arrayType could not handle '{1}' as the length of the array. Invalid wsd:arrayType syntax: '{0}'. {0} may not be used on parameters or return values when they are not wrapped. XML attributes may not be specified for the type {0}. Cannot assign object of type {0} to an object of type {1}. Cannot assign object of type {0} to an object of type {1}. The error occurred while reading node with id Char is not a valid schema primitive and should be treated as int in DataContract Invalid or missing value of the choice identifier '{1}' of type '{0}[]'. Only XmlEnum may be used on enumerated constants. '{0}' is an invalid value for the {1} property. The property may only be specified for primitive types. Value '{0}' cannot be converted to {1}. The encoding style '{0}' is not valid for this call. Valid values are '{1}' for SOAP 1.1 encoding or '{2}' for SOAP 1.2 encoding. The encoding style '{0}' is not valid for this call because this XmlSerializer instance does not support encoding. Use the SoapReflectionImporter to initialize an XmlSerializer that supports encoding. The Form property may not be 'Unqualified' when an explicit Namespace property is present. Identifier '{0}' is not CLS-compliant. IsNullable may not be 'true' for value type {0}. Please consider using Nullable<{0}> instead. IsNullable may not be set to 'false' for a Nullable<{0}> type. Consider using '{0}' type or removing the IsNullable property from the {1} attribute. Cannot assign null value to an object of type {1}. The return value must be the first member. The type {0} may not be used in this context. To use {0} as a parameter, return type, or member of a class or struct, the parameter, return type, or member must be declared as type {0} (it cannot be object). Objects of type {0} may not be used in untyped collections. Member '{0}' of type {1} cannot be serialized. Members with names ending on 'Specified' suffix have special meaning to the XmlSerializer: they control serialization of optional ValueType members and have to be of type {2}. XmlRoot and XmlType attributes may not be specified for the type {0}. The type {0} may not be used in this context. Invalid namespace attribute: xmlns:{0} Member '{0}.{1}' hides inherited member '{2}.{3}', but has different custom attributes. Value '{0}' cannot be used for the {1} property. The datatype '{2}' is missing. This mapping was not crated by reflection importer and cannot be used in this context. The XML element '{0}' from namespace '{1}' references a method and a type. Change the method's message name or change the type's root element using the XmlRootAttribute. The method for enum {0} is missing. Invalid serialization assembly: Required type {0} cannot be found in the generated assembly '{1}'. {0}. {1} already has attributes. Cannot serialize object of type '{0}' because it has multiple XmlNamespaceDeclarations attributes. XmlNamespaceDeclarations may not be used on multiple parameters or return values. The node must be either type XmlAttribute or a derived type. To be XML serializable, types which inherit from {2} must have an implementation of Add({1}) at all levels of their inheritance hierarchy. {0} does not implement Add({1}). Cannot write a node of type XmlAttribute as an element value. Use XmlAnyAttributeAttribute with an array of XmlNode or XmlAttribute to write the node as an attribute. You must implement a default accessor on {0} because it inherits from ICollection. An internal error has occurred: Code in one or more assemblies referenced by the XmlSerializer cannot be called. Cannot serialize object of type '{0}'. The object does not have serializable members. Type '{0}' is not serializable. There was an error reflecting property '{0}'. Could not deserialize {0}. Parameterless constructor is required for collections and enumerators. Cannot deserialize type '{0}' because it contains property '{1}' which has no public setter. There was an error reflecting '{0}'. Input or output values of an rpc\\literal method cannot have maxOccurs > 1. Provide a wrapper element for '{0}' by using XmlArray or XmlArrayItem instead of XmlElement attribute. XmlAttribute cannot be used with rpc\\literal SOAP, you may use the following attributes: XmlArray, XmlArrayItem, or single XmlElement. XmlText, XmlAnyElement, or XmlChoiceIdentifier cannot be used with rpc\\literal SOAP, you may use the following attributes: XmlArray, XmlArrayItem, or single XmlElement. {0} {0} Multiple accessors are not supported with rpc\\literal SOAP, you may use the following attributes: XmlArray, XmlArrayItem, or single XmlElement. Input or output values of an rpc\\literal method cannot have an XmlNamespaceDeclarations attribute (member '{0}'). There was an error processing type '{0}'. Type member '{1}' declared in '{2}' is missing required '{3}' property. If one class in the class hierarchy uses explicit sequencing feature ({3}), then its base class and all derived classes have to do the same. Inconsistent sequencing: if used on one of the class's members, the '{0}' property is required on all particle-like members, please explicitly set '{0}' using XmlElement, XmlAnyElement or XmlArray custom attribute on class member '{1}'. If multiple custom attributes specified on a single member only one of them have to have explicit '{0}' property, however if more that one attribute has the explicit '{0}', all values have to match. Explicit sequencing may not be used on parameters or return values. Please remove {0} property from custom attributes. '{1}' values must be unique within the same scope. Value '{0}' is in use. Please change '{1}' property on '{2}'. Only XmlRoot attribute may be specified for the type {0}. Please use {1} to specify schema type. Type '{0}' from namespace '{1}' declared as derivation of type '{2}' from namespace '{3}, but corresponding CLR types are not compatible. Cannot convert type '{4}' to '{5}'. Type '{0}' from namespace '{1}' does not have corresponding IXmlSerializable type. Please consider adding {2} to '{3}'. There is an error in the XML document. There is an error in XML document ({0}, {1}). Cannot serialize member '{0}' of type '{1}', see inner exception for more details. {0} is an unsupported type. Please use [XmlIgnore] attribute to exclude members of this type from serialization graph. XmlNamespaceDeclarations attribute cannot be used in conjunction with any other custom attributes. Cannot deserialize attribute as element {0}:{1}. Invalid array type {0}. Cannot serialize a cycle in a literal object graph with type {0}. 'Add' method is required for collection type '{0}'. Invalid data type: '{0}'. Cannot deserialize element as attribute {0}:{1}. 'Add' method is required for type {0} {1} of {2}. Unexpected attribute type: '{0}'. Invalid choice direction. Invalid data type: '{0}'. Invalid sequence type {0}. Invalid text type {0}. Invalid Href format: '{0}'. Enum is missing {0}. Could not deserialize array of element {0}:{1}. No repeating element accessor for {0}:{1}. The identifier {0} cannot appear more than once. There can only be one default member value. Duplicated mapping for {0}. Unexpected two any elements for {0}:{1}. Could not find accessor for type {0}. Unexpected type of '{0}' value. Referenced identifier #{0} not found in document. Unknown prefix: '{0}'. Invalid type for XmlAnyAttributeAttribute: '{0}'. Invalid array type for XmlAnyElementAttribute: '{0}'. Cannot assign object of type {0} to an object of type {1}. Invalid location for an XmlNamespaceDeclarationAttribute. {0} is inaccessible due to its protection level. Only public types can be processed. There was an error reflecting type '{0}'. Types '{0}' and '{1}' both use the XML type name, '{2}', from namespace '{3}'. Use XML attributes to specify a unique XML name and/or namespace for the type. {0} cannot be serialized. Static types cannot be used as parameters or return types. The type, {0}, is undeclared. Namespace prefix '{0}' is not defined. Unexpected type: '{0}'. The XML element '{0}' from namespace '{1}' was not expected. The XML element name and namespace must match those provided via XmlAnyElementAttribute(s). Instance validation error: '{0}' is not a valid value for {1}. {0} was not expected. The specified type was not recognized: name The type {0} is not supported because it implements IDictionary. Cannot serialize member {0} of type {1}, because it implements IDictionary. Using {0} as a base type for a class is not supported by XmlSerializer. Cannot serialize interface {0}. Cannot serialize member {0} of type {1} because it is an interface. Type {0} is not supported because it has unbound generic parameters. Only instantiated generic types can be serialized. Cannot serialize object of type {0}. Multidimensional arrays are not supported. The type {0} may not be serialized with SOAP-encoded messages. Set the Use for your message to Literal. {0} is an unsupported type. The type {0} may not be serialized. The type {0} was not expected. Use the XmlInclude attribute to specify types that are not known statically. Cannot use XmlNamespaceDeclarations attribute on member '{0}' of type {1}. This attribute is only valid on members of type {2}. '{0}' is not a valid BinHex text sequence. '{0}' is not a valid BinHex text sequence. The sequence must contain an even number of characters. Invalid name character in '{0}'. Invalid NmToken value '{0}'. Operation is not valid due to the current state of the object. Type '{0}' cannot be serialized by XmlSerializer, serialization code for the type is missing. Consult the SDK documentation for adding it as a root serialization type. http://go.microsoft.com/fwlink/?LinkId=613136 Using the Scheduler.{0} property is no longer supported due to refactoring of the API surface and elimination of platform-specific dependencies. Please include System.Reactive.PlatformServices for your target platform and use the {0}Scheduler type instead. If you're building a Windows Store app, notice some schedulers are no longer supported. Consider using Scheduler.Default instead. OnCompleted notification doesn't have a value. Disposables collection can not contain null values. Disposable has already been assigned. Failed to start monitoring system clock changes. Heap is empty. Observer has already terminated. Reentrancy has been detected. This scheduler operation has already been awaited. {0} cannot be called when the scheduler is already running. Try using Sleep instead. Could not find event '{0}' on object of type '{1}'. Could not find event '{0}' on type '{1}'. Add method should take 1 parameter. The second parameter of the event delegate must be assignable to '{0}'. Event is missing the add method. Event is missing the remove method. The event delegate must have a void return type. The event delegate must have exactly two parameters. Remove method should take 1 parameter. The first parameter of the event delegate must be assignable to '{0}'. Remove method of a WinRT event should take an EventRegistrationToken. Sequence contains more than one element. Sequence contains more than one matching element. Sequence contains no elements. Sequence contains no matching element. The WinRT thread pool doesn't support creating periodic timers with a period below 1 millisecond. The current thread has no Dispatcher associated with it. No current Window object found to obtain a CoreDispatcher from.