RE: 422 Unprocessable Entity when using two date clauses

[pcreehan@xxxxxxxxxxxxx (Patrick Creehan)]

Yes, for performance reasons we limit you to a 2 year range when querying 
using the start and end dates.
Patrick
Microsoft Enterprise Business Apps Messaging Development

--------------------
| Thread-Topic: 422 Unprocessable Entity when using two date clauses
| thread-index: Acbn0ldosjT4daDLQ5+eRXC2qFvtjQ==
| X-WBNR-Posting-Host: 195.2.133.104
| From: =?Utf-8?B?QW5keSBCcmFkZm9yZA==?= 
<AndyBradford@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References:  <662627C0-DDAB-4244-860F-E84FA98A484C@xxxxxxxxxxxxx>
| Subject: RE: 422 Unprocessable Entity when using two date clauses
| Date: Wed, 4 Oct 2006 09:30:02 -0700
| Lines: 2
| Message-ID: <8E2581DE-E846-47EB-8846-25752A8E47A9@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
|       charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.exchange.development
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.development:9091
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.exchange.development
| 
| SOLVED The start date was too far in the past it seems, when changed to a 
| more modern date the code works fine
|