<
!-- Start Facets -->
!Unable to resolve assembly '{0}'.
>
INTERNAL ERROR: The parser found an error and cannot continue.
>
Unable to handle an unknown TypeCode {0} returned by Type {1}.
,Unable to find type '{0}' in assembly '{1}'.
/Unable to load the specified metadata resource.
0Internal .NET Framework Data Provider error {0}.
5Failed to start transaction at {0} with error: {1}{2}
Unable to load embedded resource '{1}' from assembly '{0}'.
?Unable to resolve to a specific overload of the function '{0}'.
@Unable to find ComplexType {0} in the current MetadataWorkspace.
An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure.
An error occurred while attempting to generate the body SQL of the stored procedure '{0}' for entity type '{1}'. This can happen if the entity type has both a self-referencing association and a store-generated key. See the inner exception for details.
An error occurred while saving entities that do not expose foreign key properties for their relationships. The EntityEntries property will return null because a single entity cannot be identified as the source of the exception. Handling of exceptions while saving can be made easier by exposing foreign key properties in your entity types. See the InnerException for details.
An error was reported while committing a database transaction but it could not be determined whether the transaction succeeded or failed on the database server. See the inner exception and http://go.microsoft.com/fwlink/?LinkId=313468 for more information.
Cannot scaffold the next migration because the target database was created with a version of Code First earlier than EF 4.3 and does not contain the migrations history table. To start using migrations against this database, ensure the current model is compatible with the target database and execute the migrations Update process. (In Visual Studio you can use the Update-Database command from Package Manager Console to execute the migrations Update process).
DUnable to insert or update an entity because the principal end of the '{0}' relationship is deleted.
EUnable to call public, instance method AddOrUpdate on derived IDbSet<
T>
type '{0}'. Method not found.
FXML parsing failed for mapping schema. Schema Error Information : {0}.
HAn error occurred while preparing definition of the function '{0}'. See the inner exception for details.
KAn error occurred while reading from the store provider's data reader. See the inner exception for details.
KTo enable migrations for '{0}', use Enable-Migrations -ContextTypeName {0}.
OAn error occurred while starting a transaction on the provider connection. See the inner exception for details.
OError retrieving values from ObjectStateEntry. See inner exception for details.
PThe query view generated for the EntitySet '{0}' is not valid. The query parser threw the following error : {1}.
PThe query view specified for the EntitySet '{0}' is not valid. The query parser threw the following error : {1}.
PXML Schema validation failed for mapping schema. Schema Error Information : {0}.
RAn error occurred while updating the entries. See the inner exception for details.
SAn error occurred while executing the command. See the inner exception for details.
TThere was an error parsing the Include path. An empty navigation property was found.
TUnable to set field/property {0} on entity type {1}. See InnerException for details.
The Entity Framework was already using a DbConfiguration instance before an attempt was made to add an 'Loaded' event handler. 'Loaded' event handlers can only be added as part of application start up before the Entity Framework is used. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
The changes to the database were committed successfully, but an error occurred while updating the object context. The ObjectContext might be in an inconsistent state. Inner exception message: {0}
The default DbConfiguration instance was used by the Entity Framework before an attempt was made to set an instance of '{0}'. The '{0}' instance must be set at application start before using any Entity Framework features or must be registered in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
The default DbConfiguration instance was used by the Entity Framework before the '{0}' type was discovered. An instance of '{0}' must be set at application start before using any Entity Framework features or must be registered in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=260883 for more information.
UError in Function '{0}'. Aggregate Functions should take exactly one input parameter.
UUnable to process the type '{0}', because it has no known mapping to the value layer.
Unable to calculate model hash because no mapping was found between conceptual model container '{0}' and store model container '{1}'. Ensure that the names match those defined in the EDMX or Code First model.
Unable to calculate model hash because the model contained more than one container. Choose the conceptual and store model containers to use by passing their names to the appropriate overload of the ComputeMappingHashValue method.
Unable to create a null constant value of type '{0}'. Only entity types, enumeration types or primitive types are supported in this context.
Unable to determine a composite foreign key ordering for foreign key on type {0}. When using the ForeignKey data annotation on composite foreign key properties ensure order is specified by using the Column data annotation or the fluent API.
Unable to determine a valid ordering for dependent operations. Dependencies may exist due to foreign key constraints, model requirements, or store-generated values.
Unable to determine composite primary key ordering for type '{0}'. Use the ColumnAttribute (see http://go.microsoft.com/fwlink/?LinkId=386388) or the HasKey method (see http://go.microsoft.com/fwlink/?LinkId=386387) to specify an order for composite primary keys.
Unable to determine the DbProviderFactory type for connection of type '{0}'. Make sure that the ADO.NET provider is installed or registered in the application config.
Unable to determine the principal end of an association between the types '{0}' and '{1}'. The principal end of this association must be explicitly configured using either the relationship fluent API or data annotations.
Unable to determine the provider name for provider factory of type '{0}'. Make sure that the ADO.NET provider is installed or registered in the application config.
Unable to generate an explicit migration because the following explicit migrations are pending: [{0}]. Apply the pending explicit migrations before attempting to generate a new explicit migration.
Unable to generate views because no mapping was found between conceptual model container '{0}' and store model container '{1}'. Ensure that the names match those defined in the EDMX or Code First model.
Unable to generate views because the model contained more than one container. Choose the conceptual and store model containers to use by passing their names to the appropriate overload of the GenerateViews method.
Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based migration or enable automatic migration. Set DbMigrationsConfiguration.AutomaticMigrationsEnabled to true to enable automatic migration.
VUnable to add the convention '{0}'. Could not find an existing convention of type '{1}' in the current convention set.
WUnable to cast the type '{0}' to type '{1}'. LINQ to Entities only supports casting EDM primitive or enumeration types.
WUnable to determine the principal end of the '{0}' relationship. Multiple added entities may have the same primary key.
YUnable to create a constant value of type '{0}'. Only primitive types or enumeration types are supported in this context.
Unable to determine application context. The ASP.NET application path could not be resolved.
Unable to determine rows affected. The value of parameter '{0}' is not convertible to '{1}'.
]An error occurred while closing the provider connection. See the inner exception for details.
^An error occurred while executing the command definition. See the inner exception for details.
^An error occurred while preparing the command definition. See the inner exception for details.