The provider did not return a ProviderManifest instance in VS 2013 and EntityFramework 6 - by chanmm

Status : 


Sign in
to vote
ID 806693 Comments
Status Active Workarounds
Type Bug Repros 8
Opened 10/27/2013 4:57:36 AM
Access Restriction Public


When I wanted to create the EntityDataSource the error:

The metadata specified in the connection string could not be loaded
Consider rebuilding the web project to build assemblies that may 
contain metadata. The following error(s) occurred:

The provider did not return a ProviderManifest instance
Sign in to post a comment.
Posted by Bixby Bob Pope on 7/22/2014 at 11:51 AM
I'm disappointed that you(Microsoft) aren't going to put some effort into correcting this. I read your reasons why and could only ask, why even keep the control deployed? It took a while to get to the information on this page and I'm hoping that it's not all there is to it but at this point, if I have to hand code the control (without any readily available example) I just have to wonder what is the point of using it?
Posted by listv on 7/13/2014 at 8:00 AM
Solution, proposed by bbnguyenbb really helped.
"Open the EDMX file ny notepad and change ProviderManifestToken="2012" to ProviderManifestToken="2008""
Posted by Rowan [MSFT] on 3/31/2014 at 1:32 PM
Hi All,
Given the workarounds seem to be resolving this issue for folks, and it would be a very large job for us to implement anything to resolve this issue, we are closing the issue. If we see folks hitting this issue where the workarounds are not acceptable then we reconsider a fix again in the future.
~EF Team
Posted by bbnguyenbb on 3/7/2014 at 10:37 AM
or you can do, Open the EDMX file ny notepad and change ProviderManifestToken="2012" to ProviderManifestToken="2008" hi. i found solution here, it's greatest
Posted by bbnguyenbb on 3/7/2014 at 10:27 AM
hi in my link!5777#cid=315D95D87E4676AF&id=315D95D87E4676AF!5778&v=3, you see some picture, you see path of picture in right hand. it's how file name of picture, or picture order by 1, 22, 33, 44 in left to right hi
Posted by Diego [MSFT] on 2/14/2014 at 3:17 PM
Thanks everyone for taking the time to provide information about this issue. We believe that there are at least two separate root causes that can lead to different exceptions:

1. The design-time components (a.k.a. the data source wizard) for the EntityDataSource and the EntityDataSource runtime control that is included in the .NET framework depend on older versions of EF runtime libraries included in .NET are not designed to work with EF6. We are shipping a new version of the EntityDataSource runtime control that has been updated to work with the EF6 runtime as a NuGet package (see, but we do not plan to create a new wizard, so the new EntityDataSource for EF6 can only be configured editing the control markup on the ASP.NET page.

2. When using VS 2013 (or with the new EF designer for EF6 in VS 2012) and the EntityDataSource wizard in a project that contains EF5, the EF Designer and the EntityDataSource wizard will try to load mismatching versions of the EntityFramework.dll assembly in the same Visual Studio AppDomain. While the EF Designer will generally kick-in first and succeed, the EntityDataSource wizard will try to do it while discovering the EF model in the project and will fail with an exception saying that the metadata for the model cannot be found. The workaround is again to edit the configuration of the EntityDataSource control in the markup of the page.

We are currently monitoring the incidence of the issue so if you have hit it and you cannot use the workaround I would encourage you to vote it up and add a comment explaining why you cannot use the workaround.

EntityFramework Team.
Posted by chanmm on 12/29/2013 at 7:39 PM
I do not see the 1.png, 22.png and so.
Posted by bbnguyenbb on 12/29/2013 at 1:49 PM
i'm fixed it (i use vs 2013)
first. you must be user "model first" in entity framework. add file entity framework, and after create connection string, but you must be choose entity framework 5 (don't choose entity framework 6.0 - i don't know why, if you choose 6 - it's not finished). if you user vs 2012, you alse must be choose 5.0

see picture in link!5777#cid=315D95D87E4676AF&id=315D95D87E4676AF!5778&v=3

file 1.png

after, you drap listview, gridview ro something else and choose entity datasource, sure error
see picture

you must update entyti framework by nuget in 6.0.2 or new

see picture

in the end, choose from menu build => rebuild solution.

And after close solution in menu file ( don't exit visual studio, only close solution)

now, open again and choose EntityDataSource again, it's successfuly.
see picture

hi, note, step by step carefully, if not it's error.

Posted by chanmm on 11/1/2013 at 6:35 PM
It does not work for Entity Framework 5 as well.

I attach 2 more pictures here.

Posted by Sara [MSFT] on 10/31/2013 at 1:39 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Sara [MSFT] on 10/29/2013 at 5:11 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested. We look forward to hearing from you with this information.
Posted by Sara [MSFT] on 10/28/2013 at 3:45 AM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please use the feedback tool to collect steps while you're reproducing the issue?

Visual Studio now has an extension called Microsoft Visual Studio 2013 Feedback Tool, available on the VS gallery(<>)

The extension allows you to
1. upload files
2. collect trace and dump files
3. collect steps while you're repro'ing the issue.
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.
Posted by Christian Nagel on 10/27/2013 at 8:14 AM
I think this is by design. The EntityDataSource is based on the ObjectContext (old namespace), and EntityFramework 6 creates DbContext derived data contexts.
Posted by Macy [MSFT] on 10/27/2013 at 5:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(