Community
Showing results for 
Search instead for 
Do you mean 
Reply

Getting a 500 error accessing API

Accepted Solution Solved
Bronze Elite Contributor
Posts: 2,115
Country: United_Kingdom
Accepted Solution

Getting a 500 error accessing API

Hiya got 17.2 installed on a Win8.1 VM + the Web API, but when I try and access http://localhost/act.web.api/ it returns a 500 error.

 

I've given IUSER Full Access Rights to the folder, I've turned UAC down to 1 notch above off, done a IISRESET, rebooted the VM but still no joy.

 

What am I doing wrong or have I missed?

Vivek Gargav
Caldere Associates Ltd.
www.caldere.com
vgargav@caldere.com
My Blog

Accepted Solutions
Solution
Accepted by topic author vivek
‎09-25-2015 03:20 AM
Bronze Elite Contributor
Posts: 2,115
Country: United_Kingdom

Re: Getting a 500 error accessing API

[ Edited ]

Thanks Xavier,

 

Looking into the logs I can see the following error:

 

Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

 

 

So I went off and had a look under the enabled options within Windows features (running this IIS on a Win8.1 VM) found I had not enabled .NET 4.5 Extensibility or the .NET 4.5 Framework for some reason!

 

Once activated all is well in the world.

 

Hopefully this info might help someone else in the same boat.

Vivek Gargav
Caldere Associates Ltd.
www.caldere.com
vgargav@caldere.com
My Blog

View solution in original post


All Replies
Employee
Posts: 236
Country: USA

Re: Getting a 500 error accessing API

Hi,

 

Have you gone through standard IIS failed request tracing troubleshooting steps, and generated a log?  That would be a great place to start.

 

HTH,

--Xavier

Solution
Accepted by topic author vivek
‎09-25-2015 03:20 AM
Bronze Elite Contributor
Posts: 2,115
Country: United_Kingdom

Re: Getting a 500 error accessing API

[ Edited ]

Thanks Xavier,

 

Looking into the logs I can see the following error:

 

Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

 

 

So I went off and had a look under the enabled options within Windows features (running this IIS on a Win8.1 VM) found I had not enabled .NET 4.5 Extensibility or the .NET 4.5 Framework for some reason!

 

Once activated all is well in the world.

 

Hopefully this info might help someone else in the same boat.

Vivek Gargav
Caldere Associates Ltd.
www.caldere.com
vgargav@caldere.com
My Blog
Employee
Posts: 236
Country: USA

Re: Getting a 500 error accessing API

Thanks for sharing that, I hope it does help others!