I tried something stupid that is mentioned by a few searches on this issue. It NEVER worked for me before but I added this to the Web.config out of desperation:
runAllManagedModulesForAllRequests="true" Now the routing is working, although the Swagger help comes up blank. Other articles hint that this setting is overkill and degrades performance, but I'll ignore that for now until I find a "real" fix. Since this setting never worked before for me, I'm guessing different IIS or OS versions are causing different behaviour. *GK* On 31 July 2017 at 16:08, David Burstin <[email protected]> wrote: > Reboot? ;) > > (Sorry, it's my goto fix for nearly everything Windows. And I wish I was > joking.) > > On 31 July 2017 at 15:55, Greg Keogh <[email protected]> wrote: > >> Folks, I deployed a WebApi to a Windows Server box that has never before >> had a REST style service installed on it. It has existing static sites, >> ASP.NET apps and SOAP services all running fine. Routing is not working >> for the WebApi and all you get for any request is: >> >> HTTP Error 404.0 - Not Found >> The resource you are looking for has been removed, had its name changed, >> or is temporarily unavailable. >> IIS Web Core >> MapRequestHandler >> StaticFile >> 0x80070002 >> >> I've had this before and I usually bumble around for an hour and find the >> Web.config file needs to add ExtensionlessUrlHandler-Integrated-4.0 with >> all verbs and the IIS role needs a few features installed, like Redirection >> (I think). So I usually stumble into getting it working, but this time I'm >> utterly blocked and nothing works. I've searched the whole Internet and >> tried every stupid thing I can think of. All the config and features are >> present, procmon reports no permission problems ... but I get nothing but >> the error above for the last 3 hours and I'm about to throw my box out the >> window. >> >> Is there something I've forgotten to try? >> >> *Greg K* >> >> >> >
