Does anyone else get this? If I run a custom report for, say, June 2005 selecting the range to be June 01 to June 31 (of course, there are 30 days in June), it barfs with the "our engineers have been informed of this error."
Ok, perhaps not a bug. Perhaps "an uncreative use of error catching and reporting" - will that suit you better? My point was that I saw a very generic catch-all error reported and wondered whether it was as a result of the invalid dates as I'd been seeing it at other times too (with valid dates). Our friend above was decent enough to offer constructive input and verify that he sees it too for invalid dates.