O'Reilly logo

Inside Microsoft® Exchange Server 2007 Web Services by Huw Upshall, Mark Taylor, Ben Spain, Michael Mainer, David Sterling

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

HTTP 500 Status Codes

As mentioned earlier in the chapter, you will sometimes encounter HTTP 500 status codes. You encounter these errors when something about your request causes the entire request to fail. Typically, such erroneous conditions occur before the first item in the request is processed. For instance, if you pass in a request that is not schema-compliant, you receive an HTTP 500 status code, and the response code of ErrorSchemaValidation is embedded in the detail node of the SOAP fault. Let’s see that in action. The invalid request is shown in Example 18-12.

Example 18-12. Schema invalid request

<CreateItem xmlns=".../messages"
            xmlns:t=".../types"
            MessageDisposition="SaveOnly">
  <Items>
    <t:Messagez> <t:Subject>I am batched message #1</t:Subject> ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required