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

Batch Stop Processing Errors

As a general rule, Exchange Web Services tries to fulfill as much of a batched request as possible. Of course, schema invalid requests and requests that fail SOAP header parsing result in SOAP faults being returned. You may encounter another class of conditions that cause a given batch to stop processing. They are called batch stop processing errors.

Batch stop processing errors occur while an item within a given batch is being operated on. This means that the request has already been schema validated and the contents of the SOAP headers have been accepted, but conditions arise such that Exchange Web Services realizes that it cannot continue processing the other items within the batch. When an item fails due to a batch ...

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