How to get IIS to recognize OWIN startup class?

Question

My OWIN web service runs beautifully in Visual Studio 2013, but when I publish it to a real IIS site, it acts as if the Configuration method in the startup class has not been run. I can do "normal" things like browse to the app and see the directory structure, but nothing that was supposedly set up with the IAppBuilder is functional. For example, I get a 404.0 error when I browse to a URL that was set up in Startup to issue an OAuth2 bearer token. It's as if Startup.Configuration(IAppBuilder app) was never run.

I'm using the [assembly: OwinStartup(typeof(MyNamespacedStartupClass))] attribute to designate the startup class.

I've used NuGet to get both Microsoft.Owin.Host.SystemWeb and Microsoft.Owin.Diagnostics per instructions I've seen, but that doesn't make a difference.

What more do I have to do?

Solution 1

1. Make sure your app pool is in v4.0 integrated mode.
2. Make sure you have bin placed Microsoft.Owin.Host.SystemWeb (I see you have installed it) - Just make sure its also in the bin folder.

This article will have more information on how an OWIN middleware runs on Integrated pipeline.

Solution 2

I also had to add an extra setting to my web.config

<configuration>    
    <system.webServer>
        <modules runAllManagedModulesForAllRequests="true" />       
    </system.webServer> 
</configuration>

From: https://katanaproject.codeplex.com/wikipage?title=Static%20Files%20on%20IIS

IIS has a native static file module that is optimize to skip other portions of the pipeline if it sees file paths that do not match other handlers (e.g. not aspx). This means that the directory browser middleware is likely to work, but then the static file middleware may be bypassed in favor of the native static file module.

This tells IIS not to skip the managed Asp.Net modules even if the native static file module thinks it has a match.

It also describes another step, but this was not needed for me:

Also, add the following stage marker AFTER your static file middleware (in namespace Microsoft.Owin.Extensions): app.UseStageMarker(PipelineStage.MapHandler);

Solution 3

Probably the reason if you upgraded at some point from an older MVC:

Make sure you don't have

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

in your web.config. It will suppress calling the startup

Instead change it to this

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

Somewhere along the line - when I upgraded to MVC 5 this got added (actually almost ironically it was a year ago tomorrow) and I never even knew what owin was until today when I tried to use it.

Solution 4

I also faced same problems when I migrated my already running MVC5 site to a new server. It gave me nightmares, just to recap I had to do all this to get it working

1. Add [assembly: OwinStartupAttribute(typeof([YourAssemblyName].Startup))] this to the Startup class (after the using statements and before the namespace declaration)

2. Add these keys to the <appSettings> section of web.config

   <add key="owin:AppStartup" value="[NamespaceForYourStartUpClass].Startup, [YourAssemblyName]" />
   <add key="owin:AutomaticAppStartup" value="true" />
   

3. And lastly as suggested by Martijn Evens add the following to <system.webserver> section in web.config

   <modules runAllManagedModulesForAllRequests="true" />
   

View more solutions