I have a website with an index.html file (that contains an html/javascript application) that leverages a json rest api(asp.net webapi in the same website) for data. Periodically, IIS will start returning 500 errors when someone tries to hit the root of the site (index.html).

Oddly enough, the api is still 100% responsive to requests from fiddler while IIS refuses to serve that index file.

Any ideas as to what would cause this strange behavior? It would make sense if the whole site would become un-responsive but I just can't see why iis would suddenly stop serving index.html. Thoughts?

  • Is there anything in the event log? – jao Sep 22 '14 at 19:25
  • @jao Unfortunately, there isn't anything helpful there... Since this happened I have just had to restart the website and it seems to be more stable now... Not exactly re-assuring as I have no idea what caused/solved the problem. – theMothaShip Sep 23 '14 at 19:50
  • Could you elaborate your issue please, 1) Which version of IIS is you are using? What is the server OS? 2) Do you have multiple websites hosted on this server? If yes, I have you seen the same issue for another sites as well? 3) Please can you copy the exact error message and past it here? The error 500 can be because of various issues. 4) Please check if the below article is relevant to your issue, support.microsoft.com/kb/311766 5) Please get the IIS log files and paste it here. The location of logs files is 'C:\Windows\System32\LogFiles\W3SVC1 '. Also let me know the date and time th – Livin Jose Sep 25 '14 at 9:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.