Client Submits an Invalid collblob

Client Submits an Invalid collblob

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. The collblob held by the client for a collection can become invalid under certain circumstances. A scenario under which the collblob held by a client can become invalid is when the collection is deleted and re-created with the same name as before on the server. In this instance, the collections, as known by the client and server, are different although the URL is the same. Under these circumstances, when the client requests an updated manifest by passing its previous collblob, the server detects that the collections are, in fact, different and returns an error 475 Invalid collblob.

Request

SEARCH /exchange/user0/inbox HTTP/1.1
Host: example.com
Content-type: text/xml
Content-length: {insert length here}

<?xml version="1.0"?>
<D:searchrequest xmlns:D="DAV:"
    xmlns:R="https://schemas.microsoft.com/repl/"
    xmlns:M="urn:schemas:mail:">
    <R:repl>
	<R:collblob>clientopaquedata</R:collblob>
    </R:repl>
    <D:sql>SELECT 'urn:schemas:mail:Size', 'urn:schemas:mail:Importance',
           'https://schemas.microsoft.com/repl/resourcetag'
           FROM SCOPE ('SHALLOW TRAVERSAL OF "/exchange/user0/inbox"')
    </D:sql>
</D:searchrequest>

Response

HTTP/1.1 475 Invalid collblob

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

This topic last updated: December 2004

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.