I have a solution (WCF service) that has many Entity Framework modules in it. Each dll is named differently.
When I (and my co-workers) run this locally it all works fine. When we run the auto build and copy the files to a Dev Server it all works fine.
But when we copy the files to a Test Server I get an error:
Resolution of the dependency failed, type = "OrderManagementInterfaces.IOrderModel", name = "(none)".
Exception occurred while: Calling constructor OrderDAL.OrderEntities(System.String connectionString).
Exception is: MetadataException - Schema specified is not valid. Errors:
OrderDataModel.csdl(3,4) : error 0019: The EntityContainer name must be unique. An EntityContainer with the name 'OrderEntities' is already defined.
It then follows with all the parts of my schema saying that each was already defined. When I first got this error it was the same kind of error but for a different Entity Framework module. (Not sure if that is important or not.)
So my question is: Is there an IIS Setting that could cause this? Why would it work in my dev server and not my test server?
And what can I do to fix it.
NOTE: I have checked many times to see if I have a duplicate module or container name. There is only one module and container named OrderEntities.
I saw that sometimes this is a product of the metadata part of the connection string. My Connection String looks like this:
metadata=res://*/OrderDataModel.csdl|res://*/OrderDataModel.ssdl|res://*/OrderDataModel.msl;provider=...
All the others are the same except the Data Model name is different.
Note: when I deploy to IIS. I delete all files and only copy in the stuff from the auto build. (Same stuff to both locations.)
Turns out it was nothing to do with my code.
I had my Identity in my App Pool incorrectly set. Once that was switched to the right value, it all started working 🙂