Geek Answers Handbook

How can I track IIS 500 errors created by my web service

I have deployed a new version of ASP.NET web service. The IIS log file reports error code 500 when this service is called by the client. My own (test) can use the service without any errors. I enabled errorlogging in my ASP.NET web service, but the error is not logged, which makes me think that the error was not selected by my code, but somewhere "earlier" on the stack. I also examined the httperr1.log file, but there was nothing there.

Question: how can I add more errors for IIS to investigate the error? I do not have access to the client.

[Updates] I am using IIS6. I checked the event log and found nothing.

+6
web-services iis error-code
source share
4 answers

Microsoft's DebugDiag 2.0 is the specific tool you want to use if you are using IIS6.

+3
source share

What version of IIS are you using?

In IIS7, you have extensive tracking capabilities.

Take a look at: Troubleshooting Tracing Errors in IIS 7.0

+5
source share

What format is your log file in? The IIS format often contains error messages from a specific request, but the default format does not.

0
source share

If you run webMethod from an automatically generated proxy on the local host, you can see a stack trace dump when it works.

0
source share

More articles:


All Articles