.NET Framework
- The element {1} in namespace {0} was unexpected for the root element. The expected Schema in one of the following namespaces: ...
- The elements of the AdjustmentRule array must not contain ambiguous time periods that extend beyond the DateStart or DateEnd ...
- The elements of the AdjustmentRule array must not contain Daylight Saving Time periods that overlap adjacent elements in ...
- The elements of the AdjustmentRule array must not contain Daylight Saving Time periods that overlap the DateStart or DateEnd ...
- The elements of the AdjustmentRule array must not contain invalid time periods that extend beyond the DateStart or DateEnd ...
- The embedded interop type '|1' does not contain a definition for '|2' since it was not used in the compiled assembly. Consider ...
- The encoding style '{0}' is not valid for this call because this XmlSerializer instance does not support encoding. Use the ...
- 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 endpoint address '{0}' has message headers and is being used with a binding that's configured for message version None. ...
- The endpoint at '{0}' does not have a Binding with Scheme 'http' or 'https'. '{1}' is only intended for use with WebHttpBinding ...
- The endpoint at '{0}' does not have a Binding with the None MessageVersion. '{1}' is only intended for use with WebHttpBinding ...
- The endpoint at {0} processes duplex sessions. The create sequence request must contain an offer for a return sequence. This ...
- The endpoint at {0} processes input sessions. The create sequence request must not contain an offer for a return sequence. ...
- The endpoint at {0} processes reply sessions. The create sequence request must contain an offer for a return sequence. This ...
- The endpoint configuration for the standard endpoint of kind '{0}' could not be loaded. Please verify that the endpoint configuration ...
- The endpoint configuration section for contract '{0}' with name '{1}' could not be loaded because more than one endpoint ...
- The endpoint identity specified when creating the HTTPS channel to '{0}' contains multiple server certificates. However, ...
- The endpoint only processes messages using the WS-ReliableMessaging protocol. The message sent to the endpoint does not have ...
- The endpoint processing requests to create a reliable session does not support sessions that use SSL. This is likely caused ...
- The endpoint processing requests to create a reliable session only supports sessions in which the AcksTo Uri and the Endpoint ...
- The endpoint processing requests to create a reliable session only supports sessions in which the AcksTo Uri and the ReplyTo ...
- The endpoint specified cannot be null or an empty string. Please specify a valid endpoint. Valid endpoint values can be found ...
- The enterprise level is the highest, describing security policy for an entire enterprise. Below that, machine policy applies ...
- The entity '{0}' in type '{1}' and the entity '{2}' in type '{3}' are incompatible because they do not share a common super-type. ...
- The entity of type '{0}' references the same complex object of type '{1}' more than once. Complex objects cannot be referenced ...
- The entity set '{0}' differs only in case from an existing entity set, and is not compatible with the current language option. ...
- The entity type '{0}' does not have any key properties. Please make sure the key properties are defined for this entity type. ...
- The EntityClassGenerator is only for use with EntityFrameworkVersions.Version1 and the schemas provided have newer versions ...
- The EntityCodeGenerator is not for targeting EntityFrameworkVersions.Version1. Consider using EntityClassGenerator or a template. ...
- The EntityCollection could not be initialized because the relationship manager for the object to which the EntityCollection ...
- The EntityContainer name could not be determined. The provided EntitySet name must be qualified by the EntityContainer name, ...
- The EntityParameter '{0}' must have a value from which the DbType can be inferred, or a supported DbType must be set as the ...
- The EntityReference could not be initialized, because the relationship manager for object to which the entity reference belongs ...
- The EntitySet '{0}' has both a Table or Schema attribute and a DefiningQuery element. The Table and Schema attributes on ...
- The EntitySet '{0}' includes function mappings for AssociationSet '{1}', but none exists in element '{2}' for type '{3}'. ...
- The EntitySet '{0}' used for creating the Ref expression does not match the EntitySet '{1}' declared on the AssociationSetEnd ...
- The EntitySet '{0}' with schema '{1}' and table '{2}' was already defined. Each EntitySet must refer to a unique schema and ...
- The EntitySet '{0}.{1}' differs only in case from an existing EntitySet, and is not compatible with the current language ...
- The EntitySet could not be determined for the specified entity type '{0}' because there is more than one EntitySet defined ...
- The EntitySet could not be determined for the specified entity type '{0}' because there is more than one EntitySet defined ...
- The EntitySet for the End '{0}' in AssociationSet '{1}' was not specified, and cannot be inferred because none of the EntitySet ...
- The EntitySet for the End '{0}' in AssociationSet '{1}'was not specified, and cannot be inferred because the EntitySet is ...
- The EntitySet name '{0}.{1}' from the entity's EntityKey does not match the expected EntitySet name '{2}.{3}' from the '{4}' ...
- The EntitySet name cannot be null or empty, and must be qualified with an EntityContainer name that is not null or empty. ...
- The EntitySet name could not be determined. To attach an object, supply a valid EntitySet name and make sure that the object ...
- The EntitySetMapping in EntityContainerMapping for entity container '{0}' contains a query view. Query views are not allowed ...
- The EntitySetMapping in EntityContainerMapping for EntityContainer '{0}' must contain only mapping fragments and no query ...
- The EntityState value passed for the entity is not valid. The EntityState value must be one of the following: Added, Deleted, ...
- The EntityState value passed for the relationship is not valid. The EntityState value must be one of the following: Added, ...
- The EntityType '{0}' specified is not the declared type '{1}' nor a derivation of the type of the EntitySet '{2}' for FunctionImport ...
- The EntityType '{0}' that the NavigationProperty '{1}' is declared on is not the same type '{4}' referred by the end '{3}' ...
- The EntityType or ComplexType '{0}' cannot be mapped by convention to the value type '{1}'. Value types are not allowed to ...
- The EntityTypeFilter type '{0}' is not assignable from the base type specified by the EntitySet '{1}'. The EntityTypeFilter ...
- The entry found in AuthenticationManager's CustomTargetNameDictionary for {0} does not match the requested identity of {1}. ...
- The enum member '%hs.%ls' has a value that cannot be expressed as a 32-bit integer. Type library enum members must be 32-bit ...
- The enumeration type '{0}' defined in the object layer does not have a member that corresponds to the member '{1}' whose ...
- The envelope version of the incoming message ({0}) does not match that of the encoder ({1}). Make sure the binding is configured ...
- The environment block used to start a process cannot be longer than 65535 bytes. Your environment block is {0} bytes long. ...
- The error message to be sent to the client when an unhandled exception occurs on the server. The property can be set declaratively ...
- The etag value '{0}' specified in one of the request headers is not valid. Please make sure only one etag value is specified ...
- The event that the trigger will hook up to determine whether to refresh the UpdatePanel. If the property is not set then ...
- The evidence collection already contains evidence of type '{0}'. Multiple pieces of the same type of evidence are not allowed. ...
- The execution of an InstancePersistenceCommand was interrupted because another valid InstanceHandle holds a lock on instance ...
- The execution of an InstancePersistenceCommand was interrupted because another valid InstanceHandle holds a lock on the instance, ...
- The execution of an InstancePersistenceCommand was interrupted because the instance '{0}' has already been persisted to the ...
- The execution of an InstancePersistenceCommand was interrupted because the instance '{0}' has become unlocked. This error ...
- The execution of an InstancePersistenceCommand was interrupted because the instance '{0}' has not yet been persisted to the ...
- The execution of an InstancePersistenceCommand was interrupted because the instance '{0}' is locked by a different instance ...
- The execution of an InstancePersistenceCommand was interrupted because the instance '{0}' is locked by a different instance ...
- The execution of an InstancePersistenceCommand was interrupted because the instance has already been persisted to the instance ...
- The execution of an InstancePersistenceCommand was interrupted because the instance has become unlocked. This error indicates ...
- The execution of an InstancePersistenceCommand was interrupted because the instance has not yet been persisted to the instance ...
- The execution of an InstancePersistenceCommand was interrupted because the instance is locked by a different instance owner. ...
- The execution of an InstancePersistenceCommand was interrupted because the instance key '{0}' has already been completed. ...
- The execution of an InstancePersistenceCommand was interrupted because the instance key '{0}' was not associated to an instance. ...