-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error activating IFilterProvider using binding from IFilterProvider to NinjectFilterAttributeFilterProvider #13
Comments
This is a very strange error message and it should not be possible to occur. The only active request is for IFilterProvider but it seems that it is already on the active bindings stack. I doubt that it is a problem of the MVC3 extension more likely it is a porblem in Ninject Core but I can't see any way such a behavior can occur yet. Can you debug the application? If so can you please break at Ninject\Activation\Context.cs:148 and tell me the values of Binding and Request.ActiveBindings? |
Fixed in 2.2.1.0 |
thx - will try it soon - was the fix in 49471e0 ? |
The commit fixing the issue is ebc359a |
fix works great - thx |
This exact error message still happens for us in very latest version of Ninject. We have 3 NuGet packages installed Ninject (3.0.1.10) I cant repeat that all the time, usually it happens after dozens of successful AJAX requests, and then this happens and entire application is broken. Right now this happening in MVC4 .NET 4.5 application, but we experienced the same error in MVC3 application as well Any help in understanding why this is happening will be really appreciated. Thanks Below exact stack trace. Error activating IFilterProvider using binding from IFilterProvider to NinjectFilterProvider Activation path:
Suggestions:
Exception Details: Ninject.ActivationException: Error activating IFilterProvider using binding from IFilterProvider to NinjectFilterProvider Activation path:
Suggestions:
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ActivationException: Error activating IFilterProvider using binding from IFilterProvider to NinjectFilterProvider Activation path:
Suggestions:
|
Same |
Can you confirm that you are not using any custom IDependencyResolver implementation but the one from Ninject.Web.MVC3? |
I just confirmed that I was using a custom IDependencyResolver. Switching to the one from the Ninject.Web.MVC3 assembly fixed my problem. Thanks for making me check and and sorry for the red herring :-) love the product. |
It hapened right now for me... It's a shame. I was using a custom implementation of IDependencyResolver and I have changed to Ninject.Web.Mvc.NinjectDependencyResolver. I'm testing with no errors. It seems to fixed. thank you |
I am also having this issue I am using following implementation to setup my implementation with interfaces in my mvc project. namespace MoftakSolutions.WebUI.Infrastructure
|
This exact error message still happens for me in the last version of Ninject |
A cyclical dependency was detected between the constructors of two services. Activation path: 1) Request for IFilterProvider
I keep getting this in a production server after a few hours of flawless execution. I don't see any other exceptions in the elmah logs and my current guess is that the server is reloading/restarting the app somehow and this leads to the exceptions. Of course, once those appear, the whole app is unusable.
I'm using Ninject 2.2.0.0 and Ninject.Web.Mvc 2.2.0.3 and extend NinjectHttpApplication in my Global.asax.cs (Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1; ASP.MVC 3)
Here's the full trace
The text was updated successfully, but these errors were encountered: