A couple of things:
a) IIS 7 doesn't display anything detailed when accessed remotely, unless you change a configuration to allow detailed error messages to be displayed remotely. Try accessing the service locally on the server, and see if you get something more detailed. b) IIS 7 has a Failed Request Tracing (you can google "FREB" and "Failed Request Tracing"). You need to enable this via a two-step process - google can help. This provides detailed tracing information for all request. Often you can get a .NET stack in the details of the module where the error failed c) Sometimes the error isn't in .NET - sometimes it's more fundamental. Httperr.log shows 500 errors that occur in http.sys (e.g. Invalid Host Name), and the System and Application logs show fundamental errors in IIS (e.g. a serious problem in IIS itself) Cheers Ken From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Tuesday, 4 January 2011 5:53 PM To: 'ozDotNet' Subject: 500 - Internal server error Folks, I've been trying for hours to deploy a WCF HTTP Web Service onto a Win2008 server. I've been through all of the configuration steps I can think of in IIS, which I've done many times before on other Win 2003 servers. This is my first attempt to install this thing on Win2008, but I can't imagine it would be much different. When I browse the URL and SVC file I get this: Server Error 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed. Absolutely nothing I do will give me anything but this error. Is there some trick I can pull to try and get more diagnostic information? Thanks Greg
