Last post May 27, 2014 05:25 AM by om1042
May 23, 2014 03:53 PM|DaveWI|LINK
Have a Web API service I am writing that will surface data to jQuery. Currently production site is SSL with wildcard cert. Service is developed using VS2013 Utlimate and used the MVC Web Api as the template. Controller works fine in debug mode, but when
deployed to the IIS 8.5 Win 2012 site, The Get function causes a 500 error. Testing has been with the domain, both on the IIS server and dev box. The Get(Id) works in production fine.
What I am I missing here? Any help would be appreciated.
_activeProjects = new
_dm = new
_activeProjects = _dm.ActiveProjects();
May 24, 2014 09:37 AM|Neodynamic|LINK
500 is a generic error that could be caused by many things. Try enabling error description in your web.config file to see what is the exact error in your code:
<httpErrors errorMode="Detailed" />
<customErrors mode="Off" />
<compilation debug="true" />
May 24, 2014 09:54 AM|Rion Williams|LINK
Do you have a StackTrace or any other details regarding this error?
A 500 error is fairly generic server-side error that could indicate a variety of things (compilation issues, exceptions etc). You might consider disabling custom errors within your web.config temporarily so that you can troubleshoot this issue.
Additionally, you might try using the Developer Tools (F12) within your browser and monitoring the Network traffic (this will allow you to see the Request / Response of your specific calls and look into them a bit deeper to check for errors).
Fiddler is also an excellent tool for troubleshooting issues like these.
May 27, 2014 05:25 AM|om1042|LINK
Rion is right. i just want add that you can add Route Debugger in your Web API. Nuget package is available for this. using this you can get know where your route is producing error. in addition to this you can add tracing to Web API.
for tracing in web api