-
Notifications
You must be signed in to change notification settings - Fork 418
Glimpse.EF6 issue with EF 6.1 (and some beta versions of 6.2) means I can no longer access the database #713
Comments
@avanderhoorn got any thoughts about this? |
Started getting a similar error after upgrading EF to 6.1.0-alpha1. Maybe it's the bug referred to here rearing its head again? |
@migill @mrnerdhair No idea from looking at the above. I'm not seeing any errors or anything out of the ordinary. Any chance that you could create a simple repro or add the glimpse source to your project and track it down a bit more? |
I am seeing the same problem with my project. Using the most up to date EF and ASP.NET Identity along with:
I get:
Stack trace:
Removing Glimpse solves my problem but also removes Glimpse (IYSWIM). Would be nice to find a workaround for this issue. I have a gut feeling that it may be something to do with ASP.NET identity but no idea what. |
This probably wont tell us much, but can you add this app setting and see what happens?
|
Tried that and no difference I'm afraid. |
I've been investigating further myself and apologies, it seems to be EntityFramework 6.1.0-beta1 that is causing the problem. I need to use this version as I've designed my application to use ASP.NET Identity 2.0 which is also prerelease at the moment. My app won't be released until after these products are out of beta. I've created a small repo which exhibits the problem. It's a VS2013 ASP.NET Web Application with all default settings. I then updated all packages to the latest stable versions and added Glimpse. All worked OK. Finally updated the EntityFramework package to 6.1.0-beta1 and anything that tries to hit the database (logging in) comes up with error. The repo is at https://github.com/coopermoto/MVC5EF6Glimpse |
I hate to be the guy that adds a "Me Too", but I am suffering the same fate. Everything works after removing Glimpse.EF6 Thanks, |
@coopermoto Huge thanks on creating the repro. In terms of narrowing down the problem, does the problem occur as soon as you update to 6.1.0? |
Also can the other people on the thread confirm that the problem they are having is with EF 6.1.0 as well? |
I was using 6.1 alpha1 On 3 March 2014 16:50, Anthony van der Hoorn notifications@github.comwrote:
|
@avanderhoorn yes it does. For the test repo all was working fine until I updated EntityFramework to 6.1.0-beta1. |
Fantastic! I'm going see if I can get some help from the EF team, hopefully they can fix it before they go RC/Live. |
That would be good if they can before release. It can't be too far away now. |
@coopermoto Did you manage to track the issue down to a specific place in the EF6.1.0-beta1 or Glimpse.EF6 code? The reason I ask is that I have a very similar setup using the same Glimpse.EF6, AspNet.Identity 2.0 and EF6.1.0-beta1 packages and querying the database is working. I've been following this thread for a while and the only differences I can see is I'm connecting to SQL2008 and I don't have the Glimpse.Mvc5 package installed, so I'm intrigued at what the issue might be and if I'll suddenly come across it... |
@PaulAtkins No I didn't. I'm not that familiar with Glimpse and was just trying to use it for the first time. |
Just as an update, I've sent off a message to the EF team, so I'm hoping On 3 March 2014 15:22, coopermoto notifications@github.com wrote:
|
Just confirming that my issue is in conjunction with EF 6.1.0 alpha 1 as On Mon, Mar 3, 2014 at 4:04 PM, Anthony van der Hoorn <
|
Great news everyone. Looks like the EF team have found the bug at their end and we should be able to put in a temporary workaround at our end to get around it till their fix goes live. I'll shot through more updates once I get the temp fix in place. |
Fantastic! Thanks for your efforts. |
Thanks (to all) for your efforts on this project, Just curious, was this actually fixed? I upgraded to EF 6.1 today after an extended weekend, and am now receiving the same error ... Unable to determine the provider name for provider factory ... Removing Glimpse does in fact allow the application to run :( Any ideas? |
Same problem as @AlonCG here! |
As a recap this isn't a Glimpse issues its a bug that EF introduced in 6.1+. Internally it looks like they have fixed the issue and all being equal it should got out with 6.1.1 and the next drop of 6.2. Unfortunately, at this point, there isn't much I can do. All I can recommend is that if you have to update to 6.1.0 or 6.2, you might have to remove the Glimpse.EF/ADO packages :( otherwise wait for 6.1.1 and the next drop of 6.2. Sorry that I can't do much more. |
Ok, I suspected it. Let's wait until the EF Team releases a new upgrade. Thanks! |
I can confirm this became an issue when I updated EF from 6.0.2 to 6.1.0. Downgrading back to 6.0.2 resolved the issue. You can downgrade simply be reinstalling 6.0.2 directly over 6.1.0:
|
@avanderhoorn ... understood that, just thought they caught the issue before they were releasing. No worries, I'll just reinstall Glimpse after EF is updated. Thanks! |
@AlonCG Note an issue... wish we had of got it in time, but looks like this is going to have to be a permeant note next to 6.1 :( |
@avanderhoorn You said that you would have a temporary fix. Are you going to be able to do that or are we just waiting for 6.1.1? |
I installed the nuget packages not even 15 minutes ago. this is the same error I was having last night with my Northwind solution. I have not yet retested the work solution (I will do that tomorrow morning). |
I have NOT downloaded the code. I am using nuget to get the packages. are these packages updated? or should I be downloading and building the source code? |
@jonathan305 The update hasn't been released to Nuget yet. I usually try and get a second verification first. To do this, if you could download the source and reference the projects in your solution that would be great! |
Ok, I'm going to get some some packages to you today to try out. Hopefully On 16 April 2014 09:37, jonathan305 notifications@github.com wrote:
|
I've packed up the fixes for this to the milestones feed - https://www.myget.org/gallery/glimpsemilestone - http://www.myget.org/F/glimpsemilestone/. Any chance someone could download the packages and try them out. When you do this, if you could remove all your existing glimpse packages and add all the new ones from this feed. |
I uninstalled all the Glimpse Nuget Packages then ran: Install-Package DiscoverPackageSources Congratulations! The following additional commands have been installed into your
This Url should show I am using the latest http://getglimpse.com/Version/Install/?Glimpse.Mvc5=1.5.3&Glimpse.AspNet=1.8.1&Glimpse.EF6=1.6.1&Glimpse.Ado=1.7.0&Glimpse=1.8.4 After reinstalling the Glimpse Nuget Packages to my Northwind project I still am unable to see the SQL Tab as you can see from the screenshot here: http://tinypic.com/r/2hdp768/8 My Glimpse.EF6 Runtime version is v4.0.30319 Can't figure out what I am doing wrong... |
@jonathan305 Just to make sure, but how did you locate the Glimpse packages to install? Did you searched for them in the new package source only or is it possible that you installed from nuget.org again? If you use the package manager console, make sure to select the correct package source at the left top and if you are using the NuGet UI, then make sure you don't select all but only the glimpsemilestone package source |
Keep in mind that the version number has not yet been increased, that is why the install page says you have the latest version. maybe enable glimpse logging to make sure their is no error that might be an indication why the SQL tab is not showing... If all is well and you have the latest source, then maybe the patch is not working? |
I get a big log file but no errors one warning about a missing in home/index 2014-04-17 19:18:37.3187 | DEBUG | Preloaded all referenced assemblies with System.Web.Compilation.BuildManager.GetReferencedAssemblies() | 2014-04-17 19:18:38.8299 | DEBUG | Discovered IInspector of type 'Glimpse.EF.Inspector.EntityFrameworkInspector' and added it to collection. | 2014-04-17 19:18:38.8455 | DEBUG | Discovered ITab of type 'Glimpse.Ado.Tab.SQL' and added it to collection. | So the Tab is added but it's not enabled... Meaning I can't click on it. I can see there is a SQL tab but the text color is black, the Session Tab and the ModelBinding Tabs are also black... all the other tabs have text color white... What else can I check? |
@jonathan305 Are you able to make the source for the solution available somewhere? Additionally, can anyone else check out the patch to see if it works or if they get the same thing? |
@jonathan305 Huge thanks for this!!! One last favour, any chance you can turn logging on and send through the log? When you turn it on, just go as far as replicating the - i.e. not seeing data in the SQL tab when you think you should (if it happens straight away thats great) and then send it through. |
@jonathan305 I think I've worked out your issue. I'm pretty sure the fix I did solved the original issue you where having. Looking at your solution, the reason you are not seeing the SQL tab enabling is that you aren't using the Ajax/History tabs. Since all the requests after the initial load are done via ajax, you need to use the Ajax/History tabs to view and 'inspect' these (note how the URL in the Glimpse title bar doesn't update as you navigate between pages). Playing with your sample, most pages don't show up in the Ajax tab, because RequireJS Text doesn't include the If you did want to fix things so that those calls do show up in the Ajax tab, @jrburke talks about how to do this here - https://github.com/requirejs/text#custom-xhr-hooks (requirejs/text#58). |
@MisinformedDNA @migill @AlonCG Any chance that one of you guys can test the package update from here https://www.myget.org/gallery/glimpsemilestone - http://www.myget.org/F/glimpsemilestone/ |
it works now. thank you! |
I will test it shortly. Give me an hour? Thanks for the reminder. |
Uninstalled all Glimpse packages. Added MyGet feed. Installed Glimpse.MVC5 and Glimpse.EF6. Upgraded to EF 6.1. All seems to be working just fine! w00t! |
Ya! Thanks guys. I'll try and wait for a couple more confirmations to come in before doing the release. I'm going to aim for Monday. |
I had this problem a while back and just removed the EF6 package. Today I decided to Google it and came across this, so installed the packages and it's working for me with EF6.1 as well. |
@hastarin Just to confirm you used the packages I had referenced from MyGet? |
Just confirming. I just (uninstalled and) installed from the MyGet feed and all appears to be working. (MVC5, EF6.1) Thanks for the fix!!! |
@avanderhoorn Yes confirmed it was the packages you referenced from MyGet. The ones on NuGet have the issue described. |
Thanks everyone for the feedback. I'm going to close this one off. |
Just letting you know that this has now gone live. Thanks to all involved in getting this fixed. |
Very timely, as I just started a new project yesterday and ran into this issue before going home for the day, only to find this thread today :) |
:D On 23 April 2014 18:38, tafs7 notifications@github.com wrote:
|
[ See also http://stackoverflow.com/questions/21333863 ]
I'm using Visual Studio 2013, ASP.NET MVC 5, and EF 6 (against a SQL Server 2012 database). I'm also using:
Glimpse Core 1.8.1
Glimpse ASP.NET 1.6
Glimpse MVC5 1.5.2
Glimpse ADO 1.7
Glimpse EF6 1.6
Everything is up-to-date at the time of writing.
When I add Glimpse.EF6 to my project, I get a System.NotSupportedException as soon as my code touches the database. If I remove Glimpse.EF6, it works again.
The exception is:
FYI, the
connectionStrings
part of my web.config looks like this:...and my
Application_Start
method looks like this:...and my context class looks like this:
Thanks in advance for any help...
Stack trace:
Glimpse log:
The text was updated successfully, but these errors were encountered: