.NET Framework
- The SamlAuthorityBinding being read was found to contain an 'AuthorityKind' that was missing or of length 0. This is not ...
- The SamlSerializer does not contain a SecurityTokenSerializer capable of reading the SecurityKeyIdentifier. If you are using ...
- The SamlSerializer does not contain a SecurityTokenSerializer capable of serializing the given SecurityKeyIdentifier '{0}'. ...
- The SamlToken is not time valid. The current time '{0}' is outside the Effective '{1}' and Expiration '{2}' time of the token. ...
- The satellite assembly named "{1}" for fallback culture "{0}" either could not be found or could not be loaded. This is generally ...
- The schema could not be determined because one or more required properties has not been set. The required properties are ...
- The schema items collection cannot contain an object of type 'XmlSchemaInclude', 'XmlSchemaImport', or 'XmlSchemaRedefine'. ...
- The Scheme cannot be computed for this binding because this CustomBinding lacks a TransportBindingElement. Every binding ...
- The scope {0} cannot be matched using 'MatchByLdap' matching rule. To match the scopes using 'MatchByLdap' rule, the scope's ...
- The scope {0} cannot be matched using 'MatchByUuid' matching rule. To match the scopes using 'MatchByUuid' rule, the scope ...
- The script '{0}' failed to load. Check for: Inaccessible path. Script errors. (IE) Enable 'Display a notification about every ...
- The script '{0}' failed to load. Check for: Inaccessible path. Script errors. (IE) Enable 'Display a notification about every ...
- The script '{0}' has been referenced multiple times. If referencing Microsoft AJAX scripts explicitly, set the MicrosoftAjaxMode ...
- The script tag registered for type '{0}' and key '{1}' has invalid characters outside of the script tags: {2}. Only properly ...
- The second data source of a binary operator must be of type System.Linq.ParallelQuery rather than System.Collections.Generic.IEnumerable ...
- The section is marked as being protected, but it does not have the correct format. It should contain only the child node. ...
- The section is marked as being protected. However, the child node was not found in the section's node. Make sure that the ...
- The security capabilities of binding '{0}' do not match those of the generated runtime object. Most likely this means the ...
- The security configuration of this computer is incompatible with certain features used by this application. For more information, ...
- The security negotiation message with action '{0}' is larger than the maximum allowed buffer size '{1}'. If you are using ...
- The security negotiation with '{0}' cannot be initiated because the confidential endpoint address header ('{1}', '{2}') cannot ...
- The security object (Permission or PermissionSet) used for performing a Demand caused an error relating to serialization/deserialization. ...
- The security policy expert failed. The provided transport token assertion of type '{0}' did not create a transport token ...
- The Security Service Providers don't support extended protection. Please install the latest Security Service Providers update. ...
- The security session requires a security token resolver that implements '{1}'. The security token resolver '{0}' does not ...
- The Security Support Provider Interface does not support Impersonation level 'None'. Specify Identification, Impersonation ...
- 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 ...
- The security timestamp is stale because its creation time ('{0}') is too far back in the past. Current time is '{1}', maximum ...
- The security timestamp is stale because its expiration time ('{0}') is in the past. Current time is '{1}' and allowed clock ...
- The security token manager requires the security binding element to be specified in order to create a token authenticator ...
- The security token manager requires the security binding element to be specified in order to create a token provider for ...
- The SecurityKeyIdentifier that was found in the SamlSubject cannot be resolved to a SecurityToken. The SecurityTokenResolver ...
- The SecurityTokenParameters and SecurityToken tuple specified for use in the security header must both be null or must both ...
- The segment '{1}' in the request URI is not valid. Since the segment '{0}' refers to a primitive type property, the only ...
- The SELECT VALUE expression cannot be aliased in this context. SELECT VALUE expression can be aliased only when ORDER BY ...
- The SelectCountCommand on SqlDataSource '{0}' did not return a count of the rows in the data source. Please check the SelectCountCommand. ...
- The selected file is not a managed card file (.crd) or a Windows CardSpace backup file (.crds). Select a different file, ...
- The selected SamlSerializer is unable to deserialize this element {0}. Please register a custom SamlSerializer to deserialize ...
- The SelectedDates collection can be changed only in a multiple selection mode. Use the SelectedDate in a single selection ...
- The Send activity is configured with a request/reply Operation '{0}', however, there is no ReceiveReply activity paired with ...
- The send operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been ...
- The Send operation timed out after '{0}'. Increase the SendTimeout value on the Binding. The time allotted to this operation ...
- The sender's X.509 certificate was not found. The message cannot be sent. Ensure the certificate is available in the sender's ...
- The serialization failed because the serialization format '{0}' is not supported. The message cannot be sent or received. ...
- The serialized Capacity property of StringBuilder must be positive, less than or equal to MaxCapacity and greater than or ...
- The server cannot access the application directory {0}. This may be due to the presence of Unicode characters in the URL. ...
- The server certificate with name '{0}' failed identity verification because its thumbprint ('{1}') does not match the one ...
- The server challenged this request and streamed requests cannot be resubmitted. To enable HTTP server challenges, set your ...
- The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown ...
- The server didn't accept the connection request. It is possible that the client side message encoding format doesn't match ...
- The server didn't accept the connection request. It is possible that the client side message encoding format or message transfer ...
- The server didn't accept the connection request. It is possible that the WebSocket protocol version on your client doesn't ...
- The server didn't accept the connection request. It is possible that the WebSocket subprotocol sent by your client is not ...
- The server encountered an error processing the request. Please see the service help page for constructing valid requests ...
- The server encountered an error processing the request. Please see the service help page for constructing valid requests ...
- The server encountered an error processing the request. The exception message is '{0}'. See server logs for more details. ...
- The server received a TerminateSequence message before all reply sequence messages were acknowledged. This is a violation ...
- The server returned an address in response to the PASV command that is different than the address to which the FTP connection ...
- The server tag '{0}' is ambiguous. Please modify the associated registration that is causing ambiguity and pick a new tag ...
- The server was unable to process the request due to an internal error. For more information about the error, either turn ...
- The server was unable to process the request due to an internal error. For more information about the error, either turn ...
- The server was unable to process the request due to an internal error. For more information about the error, either turn ...
- The service '{0}' is configured with a TransactionIsolationLevel but no operations are configured with TransactionScopeRequired ...
- The service '{0}' is configured with a TransactionTimeout but no operations are configured with TransactionScopeRequired ...
- The service '{0}' is configured with ReleaseServiceInstanceOnTransactionComplete but no operations are configured with TransactionScopeRequired ...
- The service '{0}' is configured with ReleaseServiceInstanceOnTransactionComplete set to true but no operations are configured ...
- The service '{0}' is configured with TransactionAutoCompleteOnSessionClose set to true and with an InstanceContextMode not ...
- The service '{0}' is configured with TransactionAutoCompleteOnSessionClose set to true, but no operations are configured ...
- The service '{0}' is configured with TransactionAutoCompleteOnSessionClose, but no operations are configured with TransactionScopeRequired ...
- The service cannot be activated because it does not support ASP.NET compatibility. ASP.NET compatibility is enabled for this ...
- The service cannot be activated because it requires ASP.NET compatibility. ASP.NET compatibility is not enabled for this ...
- The service class of type {0} both defines a ServiceContract and inherits a ServiceContract from type {1}. Contract inheritance ...
- The service class of type {0} both defines a ServiceContract and inherits a ServiceContract from type {1}. Contract inheritance ...
- The Service contains multiple ServiceEndpoints with different ContractDescriptions which each have Name='{0}' and Namespace='{1}'. ...