I have a web service running on IIS that is rejecting data being send from ATG. It fails before it gets to my web service code, and the error message is badly formed XML.

I want to get logging started on the IIS front end so I can see the body of the request before it dies in the SOAP marshaller, but I can't seem to find the way to do it. I followed along with the brutal log process, but the recommended log parser 2.2 just spews out lots of message boxes and no text output.

This seems pretty straightforward in IIS 7 but in IIS6 it seems impossibly difficult. Am I missing something? Is there a simple, easy to use tool to turn it on in IIS 6, and easily view the results? I need to see the actual body of the XML not just the headers, so the logging in the properties tab of IIS Manager doesn't produce enough information.



One non-IIS way of doing this would be to install a packet capture program on the server, start a capture, wait until the problem occurs, stop the capture, and analyze the capture details. Microsoft Network Monitor will let you easily drill into the capture based on process, conversation, etc.

Your Answer

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.