Hi Greg,

 

I ran into the same problem before.

 

Windows Server 2008 R2 is all ready for MVC/REST API.

 

But Windows server 2008 Standard is not.

 

There are a few things to do to get it to work. I can’t remember exactly what I 
had to do.

 

But have a google for Windows 2008 Standard MVC

https://www.google.com.au/search?q=Windows+2008+standard+MVC&rlz=1C1GGRV_enAU752AU754&oq=Windows+2008+standard+MVC&aqs=chrome..69i57j69i60.8935j0j7&sourceid=chrome&ie=UTF-8

 

There is the Quick Fix for extensionless URL’s

 

https://www.microsoft.com/en-us/download/details.aspx?id=11342

https://support.microsoft.com/en-us/help/980368/a-update-is-available-that-enables-certain-iis-7-0-or-iis-7-5-handlers

https://stackoverflow.com/questions/12495346/asp-net-4-5-mvc-4-not-working-on-windows-server-2008-iis-7#

 

Also you have to make sure you are using the integrated pipeline mode for the 
application pool.

 

That will hopefully get you up and running.

 

Regards

 

Adrian Halid

 

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On 
Behalf Of Greg Keogh
Sent: Tuesday, 1 August 2017 6:05 AM
To: ozDotNet <ozdotnet@ozdotnet.com>
Subject: Re: [OT] WebApi not working

 

 

What version of IIS are you running?

Also what is the OS?

 

It's Windows Server 2008 Standard SP2 6002, so I think that comes with IIS 7.5.

 

But anyway, I found a workaround by adding the "use all managed modules" 
setting, which isn't recommended. So one of my missions today is to find out 
just what this settings does, why it's discouraged and what a "real" fix might 
be.

 

GK

 

 

 

Regards

 

Adrian Halid

 

From: ozdotnet-boun...@ozdotnet.com <mailto:ozdotnet-boun...@ozdotnet.com>  
[mailto:ozdotnet-boun...@ozdotnet.com <mailto:ozdotnet-boun...@ozdotnet.com> ] 
On Behalf Of Greg Keogh
Sent: Monday, 31 July 2017 1:56 PM
To: ozDotNet <ozdotnet@ozdotnet.com <mailto:ozdotnet@ozdotnet.com> >
Subject: [OT] WebApi not working

 

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 
<http://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

 

 

Reply via email to