CDO.DLL = 6.5.7651.61 (same as Exchange)
BESX 4.0.6

Anyone ever see this error:

[40000] (08/28 08:59:45):{0x1980} CDO helper 044b4008 is not in memory
[40000] (08/28 08:59:45):{0x1980} Starting new CDO helper 044b4008
[40574] (08/28 08:59:45):{0x1A2C} CDO helper 044b4008 started
[30001] (08/28 08:59:46):{0x1A2C} CDOCalendar::GetAssociatedApptObj - Code = 800406ff, WCode = 04ff, Code meaning = IDispatch error #1279,
[30005] (08/28 08:59:46):{0x1A2C} Source = Collaboration Data Objects, Description = [Collaboration Data Objects - [MAPI_E_TOO_COMPLEX(80040117)]].
[40406] (08/28 08:59:46):{0x1A2C} {} CDOCalendar::GetRIMMeetingResp - Cannot get associated appt. Try searching for it. (0x80040117) failed.

Meh?

This behavior occurs because CDO is looking for the date/time values on the meeting response message, and when it does not find a date/time value on a property, it uses the current date/time value as the default value. The values are then compared with the date/time values that are stamped by the meeting recipient. This date/time value is too old, and the MAPI_E_TOO_COMPLEX error message is returned.

Stolen from: XCLN: MAPI_E_TOO_COMPLEX Error Is Returned When Using the GetAssociatedAppointment Method of CDO

So my monkey friend, any suggestion of resolution...? You know how often I actually ask for help, so leave it up to me to find one of those bunker busters, right?

(This isn't just a one-off issue - it's quite regular and quite widespread, although no actual impact has been reported as a result of the errors).

I'm off to the store to get some bananas; hopefully they'll inspire me with some insight ... I'm looking through 8 sets of logs now to see if I can find any correlation. I'll keep you posted ... as long as I don't kill myself after tonights Yankee / Sox game.

You Bostonians are funny.

Didn't find anything in set one; perusing another now.

... I'm a displaced New Yorker ... let that speak for itself. (time to duck and cover from penguin)

Maybe take a look at the user's calendar with something like MFCMAPI / MAPI Editor and see if any of the appointments look funny?

Crapilly I can't find anything to correlate with reported problems and can't find a damn thing in common with people generating these messages (besides being on the same Exchange & BES)

k, i will investigate next week when i get into the office. not a real issue from what i can see, but i am curious as to what's causing it so i can atleast fix it or write it off as a non-issue.

Del