We have a solution which consists of two projects - a console application project and a web application project. Each of these has an identical in schema, but differently named .edmx file used to access the same database.
The console application runs as a scheduled task on the same server as the web application is hosted. The web application contains a reference to the console application as certain actions within the web application lead to methods in the console application being called.
This combination has been running in our staging environment successfully for many months.
When released live we are seeing the following error message at least once a day:
Schema specified is not valid. Errors:
ProjectName.csdl(3,4) : error 0019: The EntityContainer name must be
unique. An EntityContainer with the name 'ProjectEntities' is already
defined. ProjectName.csdl(63,4) : error 0019: Each type name in a
schema must be unique. Type name 'ProjectModel.DataSource' was already
defined. ProjectName.csdl(75,4) : error 0019: Each type name in a
schema must be unique. Type name 'ProjectModel.Error' was already
defined.
This continues, listing all the type names in our schema.
This error can be fixed by recycling the application pool or restarting IIS.
Please note that the error does not occur until the web application has been running for a while - it is not occuring when we compile or the first time we access the application.
My initial theory was that the two Entity Containers are conflicting with each other because the web application references the console application, but they have different names, which makes the error "The EntityContainer name must be unique. An EntityContainer with the name 'ProjectEntities' is already defined" confusing.
Go to that bin folder and delete dll and pdb file manually.
When faced with this problem in the past, I've always created a third, shared library that contains the entity model - that way you know there's not going to be a name conflict, if you decide to add a new table/column/method to the model you only need to do so once, etc, etc.
Change the webconfig file entity connection string entry from this
metadata=res://*/App_Code.AAA.csdl|res://*/App_Code.AAA.ssdl|res://*/App_Code.AAA.msl;provider=System.Data.SqlClient;provider connection string="data source=XXX;initial catalog=XXX;user id=XXX;password=XXX;multipleactiveresultsets=True;App=EntityFramework""
providerName="System.Data.EntityClient
to
metadata=res://MyProject/App_Code.AAA.csdl|res://MyProject/App_Code.AAA.ssdl|res://MyProject/App_Code.AAA.msl;provider=System.Data.SqlClient;provider connection string="data source=XXX;initial catalog=XXX;user id=XXX;password=XXX;multipleactiveresultsets=True;App=EntityFramework""
providerName="System.Data.EntityClient
Just in case anyone else is desperate and not finding any answers - I accidentally ended up with a copy of my .edmx file included in the project in a second location. Both were being included in the build.
;-)
If this happened to you, fear not: You were not the first.
Well, in my case I'm working diferent software architecture, because I have diferent projects (dlls), they access to the same Database, but I have diferent entities inside. So, when I have references in a project that needs all or at least two of them, i get this error
If I change the Entity Container Name on each one, I solve the problem, but now my connection string are diferent and I have to include all the connection strings in the config file for each dll I refer.
This error occurs when you have more than one entity model.edmx files in a single DLL or class library project. Although the reason behind the error is not known to me , you can fix this by deleting the other model or moving the other model.edmx file to another class library .
Also dont forget to remove the references of the previous dll
Note when trying to rename a entity container to that of a previously deleted entity container, you will need to go into your web.config or app.config and delete the connection string out of the configuration section.
I fixed this issue in EntityFramework 6.0 by.
During creation of the models, I name the .edmx to the name of the entities. i.e. (MYDbEntities)
After creation i open the MYDbEntities.Context.cs and modified the "Entities" Class to "MYDbEntities".
- Open the App.Config and look for the connection string
- Open the MYDbEntities.Context.cs and change the connection string to Connection string from the config. example "MyDbConnection"
Make sure that the connection string is like this
metadata=res:///MYDbEntities.csdl|res:///MYDbEntities.ssdl|res://*/MYDbEntities.msl;provider=System.Data.SqlClient;provider connection string="data source=.;initial catalog=YourDb;persist security info=True;user id=sa;password=Sw0rdf!sh;multipleactiveresultsets=True;application name=EntityFramework"
Note: my entities resides in a separate DLL.
Hope this helps.
In my case none of the solutions worked. I finally recycled the IIS on my hosting to make it work.
Hope this helps someone :)
My Entities were in another class library (MyLibrary.Data). Changing below worked :
<add name="Entities" connectionString="metadata=res://*/;
 provider=MySql.Data.MySqlClient; .....
<add name="Entities" connectionString="metadata=res://MyLibrary.Data;
 provider=MySql.Data.MySqlClient;
