ASP.NET entity datasource control 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 Provider Manifest instance.

When you add an entity datasource control and you try to configure it you might get the following 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 Provider Manifest instance.
Error trying to configure Entity Datasource control

In order to fix this you have to open your edmx file with notepad, locate ProviderManifestToken and change it's value from 2012 to 2008 as shown in the picture below. Save, rebuild in Visual Studio and you are done.



Comments

  1. davoblog28 Apr 2015, 23:44:00

    It's very frustrating that this bug has been around so long and that Microsoft has basically said they do not intend to fix it. If they are not, and the bug is related to incompatible versions of VS and EF, they could at the very minimum publish a table of compatible components and features so that we don't need to spend hours futilely churning the web looking for threads of answers.

    ReplyDelete
  2. Anonymous9 May 2015, 19:12:00

    i love u man.....

    ReplyDelete
  3. Sabry29 Sept 2015, 07:34:00

    Thanks a million you saved my day

    ReplyDelete
  4. MPPRUTHVIRAJ KASHYAP25 Nov 2015, 10:02:00

    thank you so much dude. For the Quick and Simple solution

    ReplyDelete
  5. davoblog25 Nov 2015, 19:47:00

    I agree, its pathetic. Every newby who comes along stumbles into this and among the cloud of things needed to get a connection string right has to figure out this obscure bug. What is more disheartening is that Microsoft says that fixing it implies a significant change to their code. What sort of code architecture makes it difficult to fix a versioning bug?

    ReplyDelete
    Replies
    1. Antonis Tsalapakis26 Nov 2015, 09:48:00

      I agree it's so frustrating. In my current project I use Dapper. Maybe you would like to give it a try.

      Delete
  6. Muhammad Shawal10 Aug 2016, 15:02:00

    Thank u so much man.....

    ReplyDelete

Post a Comment

Popular posts from this blog

Convert Outlook EntryID to EwsID Exchange Web Services

I found myself trying to find an email in Exchange the other day, based on the EntryID I could retrieve from the email in Outlook (Exchange account). I was using Exchange Web Services EWS to access the mailbox the email was stored in. In EWS you can retrieve an item by providing its ID Dim item As Item = item.Bind(service, New ItemId(entryid))   Well quickly I found out that the EntryID of the email in Outlook was not what I wanted. After some reading I discovered the ConvertId function that converts ids from one format to another. The available formats are  EntryId EwsId EwsLegacyId HexEntryId OwaId StoreId   So I went on to do the obvious, convert my ID from EntryId to EwsId. I wish! Microsoft.Exchange.WebServices.Data.ServiceResponseException "The specified object was not found in the store." was what I got to my surprise! What actually was wrong was that the EntryID was not in EntryId format but i n HexEntryId format . The code that gets the job don
Read more

Freeze panes in BO Webi report like Excel

Image
Since the design of my first BO report a need kept coming up. The need for freeze panes. When there is a table that doesn't fit in the screen and you start scrolling, the moment the headers disappear you lose track of your data and start scrolling up and down, left and right again and again to see those headers. Well here it is what you need to do to add freeze pane capabilities to your report. For this example we have the crosstab table of the screenshots below: Headers disappeared The logic is quite simple. With the help of javascript we are going to move headers accordingly to the user's scrolling so as the user thinks the headers are pinned to the screen while the body of the table is moving. The problem is that if we see the structure of the crosstab it is actually an html table which means that we can not move header cells independently from body cells. HTML structure of the crosstab So we have to break the crosstab down to three independent
Read more