Entity Designer Errors

Artigo
02/21/2011

This topic lists common errors that the ADO.NET Entity Data Model Designer reports when validating an .edmx file and suggests ways to resolve the errors.

Note
When you add an empty .edmx file to your project and then begin adding entities and associations, some of the errors below may be reported as warnings. When you add storage model and mapping information to the .edmx file, the warnings will be reported as errors if problems still exist. For more information, see How to: Create a New .edmx File (Entity Data Model Tools) and How to: Generate a Database from a Conceptual Model (Entity Data Model Tools).

When you add an empty .edmx file to your project and then begin adding entities and associations, some of the errors below may be reported as warnings. When you add storage model and mapping information to the .edmx file, the warnings will be reported as errors if problems still exist. For more information, see How to: Create a New .edmx File (Entity Data Model Tools) and How to: Generate a Database from a Conceptual Model (Entity Data Model Tools).

Error 11007: Entity Type Is Not Mapped

This error occurs when an entity type in the conceptual model is not mapped to the data source. To resolve this error, map the entity type to the data source. For more information, see How to: Map Entities to Database Tables (Entity Data Model Tools).

Error 11008: Association Is Not Mapped

This error occurs when an association in the conceptual model is not mapped to the data source. To resolve this error, map the association to the data source. For more information, see How to: Create and Edit Association Mappings (Entity Data Model Tools).

Error 11009: Property Is Not Mapped

This error occurs when a property of an entity type in the conceptual model is not mapped to the data source. To resolve this error, map the property to the data source. For more information, see How to: Map Entities to Database Tables (Entity Data Model Tools).

Error 11010: Association End Is Not Mapped

This error occurs when an association end in the conceptual model is not mapped to the data source. To resolve this error, map the association end to the data source. For more information, see How to: Create and Edit Association Mappings (Entity Data Model Tools).

Error 11011: Association End key property <Property Name> is not mapped.

This error occurs when an association end in the conceptual model is a compound entity key and one or more of the key properties is not mapped. To resolve this error, map all properties of the association end. For more information, see How to: Create and Edit Association Mappings (Entity Data Model Tools).

Error 10019: This file contains a DataServices element and cannot be opened in the Entity Designer.

This error occurs when trying to open an .edmx file that is intended to be used with an application that is a WCF Data Services client. This file can be opened with the XML Editor. For more information, see .edmx File Overview (Entity Framework).

Error 11002: Entity type <Entity Type Name> has no entity set.

The error occurs when an entity type has no corresponding entity set. To resolve this error, open the .edmx file in the XML Editor and define an entity set for the entity type. For more information, see EntitySet Element (CSDL) and EntityType Element (CSDL).

Error 11003: Entity type <Entity Type Name> exists in multiple entity sets: <Entity Set Names>

This error occurs when an entity type exists in multiple entity sets. Although the Entity Framework supports models with multiple entity sets per type (MEST), such models cannot be opened in the Entity Designer. To edit this type of model, you must use a text editor such as XML Editor. For more information, see How to: Define a Model with Multiple Entity Sets per Type (Entity Framework).

Error 10018: Multiple EntityContainer elements were detected in namespace <Namespace Name>

This error occurs when more than one EntitySet element is defined in the conceptual model. To resolve the issue, open the .edmx file in the XML Editor and remove one of the EntitySet elements. For more information, see EntitySet Element (CSDL).

Error 11013: A circular complex type definition has been found for <Complex Type Name> complex type.

This error occurs when a complex type has a property that references a second complex type which, in turn, has a property that references the first complex type. Such circular references are not supported by the Entity Framework. To resolve the issue, open the .edmx file in the XML Editor and redefine the complex types. For more information, see ComplexType Element (CSDL).

Error 11004: Association <Association Name> has no association set.

This error occurs when an association is defined without a corresponding association set. To resolve the issue, open the .edmx file in the XML Editor and define an association set for the given association. For more information, see AssociationSet Element (CSDL) and Association Element (CSDL).

Error 11006: Using elements are not supported in the Entity Designer.

This error occurs when there is a Using element in the conceptual model. Although the Entity Framework supports the Using element in conceptual models, such models cannot be opened in the Entity Designer. For more information, see Using Element (CSDL).

Error 10023: Could not find the conceptual model to validate.

This error occurs when the Entity Designer cannot find the conceptual model. This can happen when the conceptual model is not defined according to the conceptual model schema. To resolve the issue, open the .edmx file in the XML Editor and correctly define the conceptual model. For more information, see .edmx File Overview (Entity Framework) and CSDL Specification.

Error 10024: Could not find the storage model to validate.

This error occurs when the Entity Designer cannot find the storage model. This can happen when the storage model is not defined according to the storage model schema. To resolve the issue, open the .edmx file in the XML Editor and correctly define the storage model. For more information, see .edmx File Overview (Entity Framework) and SSDL Specification.

Error 10025: Could not find the mapping model to validate.

This error occurs when the Entity Designer cannot find mapping information. This can happen when the mapping information is not defined according to the mapping schema. To resolve the issue, open the .edmx file in the XML Editor and correctly define the mapping information. For more information, see .edmx File Overview (Entity Framework) and MSL Specification.

Compartilhar via