CODEWITHSUNDEEP
asp.net.netowinkatanaasp.net-identity
graycrow
graycrow

Reputation: 3705

No owin.Environment item was found in the context

Microsoft recently introduced new ASP.NET Identity - replacement for old (Simple)Membership. Unfortunately, I can't use this new membership system in my old project because it throws System.InvalidOperationException: No owin.Environment item was found in the context. This is a known bug, but Microsoft keeps silence about this issue. The easiest way to reproduce this bug - it's to create a new web application (MVC, WebForms or WebApi - doesn't matter) in VS 2013 (with Web Tools 2013 Preview Refresh) and then go to the login page. It will work. Then change namespace in your application to anything else than original namespace and login page will throw that error. Changing namespace back to original (the one you used at the creation of a project) will solve this problem.

It looks like .net stores somewhere something related to the original namespace, but I can't find what and where, it's not in the project folder. I know that stackoverflow is not a place for a bug reports, I just hoping that someone already found a solution for this issue or maybe people involved in the development of ASP.NET Identity will see this.

Upvotes: 39

Views: 66694

Answers (14)

elena
elena

Reputation: 173

I have tried all of the above suggestions, without success; then reading the documentation at: https://learn.microsoft.com/en-us/aspnet/aspnet/overview/owin-and-katana/owin-startup-class-detection

I understood that the error was in the call to the assembly in the Startup.cs file:

wrong code:

[assembly: OwinStartupAttribute(typeof([AssemblyName].Startup))]

right code:

[assembly: OwinStartup(typeof([AssemblyName].Startup))]

so, I fixed the error removing the word Attribute from OwinStartupAttribute

Upvotes: 0

Frostrar
Frostrar

Reputation: 337

I experienced this error in an Optimizely (Episerver) solution where I had two feature branches using the same CMS database. In one feature branch I was working on a proof of concept using a visitor criterion. So I had created something like this:

    public class SomeVisitorCriterionSettings : CriterionModelBase
    {
        public override ICriterionModel Copy()
        {
            return base.ShallowCopy();
        }
    }



[VisitorGroupCriterion(
    Category = "Some category",
    DisplayName = "My visitor criterion")]
public class SomeVisitorCriterion : CriterionBase<SomeVisitorCriterionSettings>
{
    public override bool IsMatch(IPrincipal principal, HttpContextBase httpContext)
    {
        // match logic here..
    }
}

And within Episerver -> CMS -> Visitor Groups I had created an instance of this visitor criterion. After switching to the other branch where this code did not exist, but the instance in the database did, the Owin exception was thrown.

Deleting the visitor criterion in the CMS resolved the issue, but I honestly have no idea why this sort of exception is thrown. I would love to know though..

Upvotes: 0

Daniel
Daniel

Reputation: 1179

None of the above answers worked for me.

Turned out my project was missing the "Startup" class that contains the following:

using Microsoft.Owin;
using Owin;

[assembly: OwinStartupAttribute(typeof(NAMESPACE.Startup))]
namespace NAMESPACE
{
    public partial class Startup
    {
        public void Configuration(IAppBuilder app)
        {
            ConfigureAuth(app);
        }
    }
}

This file called "Startup.cs" is located on the root folder (~/) of your project.

My "Web.config" doesn't have any of this "Owin" configuration posted on the other replies.

Upvotes: 3

Dov Miller
Dov Miller

Reputation: 2058

I have no idea why this works but it did!

My problem was in VS2013. In the WebConfig, debug was set to true and I got that error. When I set it to false it worked fine and then I reset to true and it continued to work OK!

At first when debug was true before changing to false, I put a break point in my StartUp code and it wasn't reached at all. After changing to false pressing save and then back to true the StartUp code was called and the program works like it should.

Upvotes: 1

Zia UsafXai
Zia UsafXai

Reputation: 73

Had same problem. Thanks for the shared solutions. this.. 

<add key="owin.AppStartup" value="Namespace.Startup, Namespace"/>
<add key="owin:AutomaticAppStartup" value="false"/>

fixed for me

Upvotes: 1

David
David

Reputation: 1

adding default language to compilation in web.config did it for me!

Upvotes: -1

Drol
Drol

Reputation: 198

I had the exact same error, but as it turned out I had another configuration problem in my web.config. My web.config was missing the attribute defaultLanguage="c#" in the compilation element under system.web.

In this case it will default to VB. So unless you have your Startup class written in VB you should change the default language to C#.

Not correct:

<compilation debug="true" optimizeCompilations="true" targetFramework="4.6.1">

This is correct (unless you use VB):

<compilation debug="true" defaultLanguage="c#" optimizeCompilations="true" targetFramework="4.6.1">

Upvotes: 20

Mathi Rajan
Mathi Rajan

Reputation: 79

If you happened to have copied the below config from MVC4, you should remove it from web.config

<add key="owin:AutomaticAppStartup" value="false" />

Upvotes: 4

Gatis Bergšpics
Gatis Bergšpics

Reputation: 441

Cleaning ASP.NET temporary files helped me with this exact problem

Upvotes: 11

cesar-moya
cesar-moya

Reputation: 601

I had the same issue, it was fixed after making sure this line was in web.config:

<add key="owin:AutomaticAppStartup" value="true" />

Upvotes: 21

Ron Dow
Ron Dow

Reputation: 41

I tried everything mentioned on this page but nothing worked. Then I found out about a setting in IIS named owin:AutomaticAppStartup. You can find it in the Application Settings page of the IIS Manager for the Default Web Site. Check to see if that setting is true. If not set to true. This worked for me.

This is the website where I found the answer: http://gotoanswer.stanford.edu/?q=Microsoft.Owin.Host.SystemWeb+and+still+getting+No+owin.Environment+item+was+found+in+the+context

Upvotes: 4

user2697956
user2697956

Reputation: 139

I had this same issue. I fixed it with the web.config.

However I had changed the assembly name and namespace and did not find the original assembly name anywhere anymore.

I then discovered that clean was not removing the original assembly from the bin.

Aftter deleting the bin litter, I was able to remove the web.config OWIN entry.

Upvotes: 3

Luiz Bicalho
Luiz Bicalho

Reputation: 935

I created two new projects called TesteMvc5.2 and TesteMvc5.0 and both of them didn't work at start

this is because the default namespace is different from the assembly name. but after I put the line 

<add key="owin:AppStartup" value="TesteMvc5._2.Startup, TesteMvc5.2" />

on the web.config it worked fine.

Upvotes: 8

pranav rastogi
pranav rastogi

Reputation: 4154

Most likely it cannot find the OWIN Startup class. The default convention for the Startup class is [AssemblyName].Startup. If you're no longer following that convention you'll need to specify the full name of your Startup class in the Web.Config.

The next release of Microsoft.Owin.Host.SystemWeb package now throws detailed exception messages when the Startup class cannot be found.

Upvotes: 29

Related Questions