[Brendan42]

Thanks for this thread all. Having to rethink our upgrade to SP6 MR3. Some users already complaining about meetings going missing, can only imagine what would happen if things get worse.

A colleague found this doc to clarify MS stand on meeting request do/don'ts in Outlook:
http://office.microsoft.com/en-gb/ou...276781033.aspx

Has anybody checked if the delegates have full access to the Deleted Items folder on their delegator's (?) mailbox? I tend to use the "DelegateWasteBasketStyle" registry key (in WinXP, Outlook 2003), hence the need for this level of access.

Glad we're not the only ones experiencing this problem.

[DW747]

Hi Brendan42, yeh we've explicitly set the access to the deleted items folder after setting the "DelegateWasteBasketStyle" key. Made no difference (We are XP/O2K3).

stuwhite, nope not received the documentation as yet.... in fact had no reply from our vendor as yet but meeting with the account manager on Wednesday so may just push for some form of comms.

Anyway another fresh week to keep hacking away at this, will let you all know if anything new presents itself but I think from reading all the comments above we've covered just about everything and the problem must be programmatic as if we didnt know that already lol.

[stuwhite]

New week, new fun indeed . Release notes for MR3 are now up -

Livelink - Redirection

and our friend is in there -

"*SDR 217944
In BlackBerry Enterprise Server version 4.1 SP6 MR3, optimizations have been made to some MAPI calls related to wireless calendar synchronization."

[DW747]

Thanks for posting that stuwhite. I am reading through it now, hope the "optimizations" refer to we stopped losing calendar items as it is a rather broad term but if it resolves this issue.... I can get on with my life!

[MrDexterity]

Ok so I've upgraded to MR3 and also upgraded the device software from a user who repeatedly reported this problem (almost every day ).
Well as of now I haven't heard from him anymore, so I'm keeping my fingers crossed.

upgraded from 4.6.0.126 to 4.6.0.162 (Bold)

good luck everyone.

[DW747]

I've now installed MR3 on our Dev BES server and happy to report that another irritating problem (when you change re-direction on the "sent items" it remains regardless) has been resolved. So in about two weeks I will be able to give you all an update as to the impact of this on our live server (1500 users).

[sharestoys]

we are having this issue as well.. 4.1.6.13 (mr1)

Im racking my brains trying to solve this.. have a call with RIM senior, anyone need me to ask anything? (Keep it nice)

[BB_Fluster]

Has anyone found a solution to this yet?

[Highfall]

Looking to install MR3 this weekend and would like to know. Thanks!

[DW747]

Hey all,

Well we have now officially been running with MR3 for a week and just had the service desk pull up reports for the issue.... in the last week, not one single instance of the problem... where it used to be reported a number of times daily. Although RIM dont officially say this problem even exists, they seem to have fixed it with MR3 and I can now continue to slowly kill my brain cells with beer.

Good luck all and thanks for posting.

[dev]

Hi guys,

I've been running the TraitTool for over a month now...Just completed the 4.1.6 MR3 update lastnight.
I will let you'll know later on today if it resolves that annoying calendar issue.

[conniet]

Hope to hear further success stories surrounding the install of MR3. I have had users complaining about this issue for a while and I had concentrated on the addition of the regkey for keeping calendar item entry id's static, but this seemed to be a longshot at best and it is certainly not plausible that I could get all admins to agree to add it to all machines throughout our org.

Today, though, I had a Deputy Minister complain about this issue and threats were implied. I found this thread after some more searching (don't know how I missed it before!) - and will now plan to install MR3 without delay.

Fingers crossed. I'll report back success or failures in a week or so.

[DW747]

Hi All,

Further feedback... MR3 has now been running here since the 28th of Jan. So far only one person complained about a missing appointment however once we did some investigation we found that the appointment was created three weeks prior to us applying the pack and thus likely it disappeared ages ago and the user only noticed on the day of the meeting.

Anyway, I will stick to my guns I think this has solved the issue.

[CFSguy]

Hello everyone,

I was glad to find this thread, as the issues that you are discussing appear to be identical to what we are seeing. Our BES is on 4.1.6, and I applied MR3 on 1/14/09. We are running Exchange 2003 SP2. Our clients use Outlook 2003 SP3. The version of CDO on the BES and Exchange servers is 6.5.7651.61.

I am getting numerous reports of strange behavior surrounding Outlook calendaring and the use of Blackberry. We have only had our BES server since the first of the year, and have approximately 55 users converted to Blackberry (the 8330 Curve model). I am not convinced that MR3 has resolved these issues, as I still get reports of recent events.

In addition to missing calendar items, I have reports of recurring Outlook meeting reminders from appointments dismissed long ago. I am investigating KB957208 as a possible hotfix for this. The version of CDO on this hotfix is 6.5.7654.7. Has anyone installed this hotfix, and do you know whether it is compatible with BES?

We are also seeing attendees on meeting invitations show alias names instead of first & last name. This started showing up only after beginning our implementation of Blackberry.

We just purchased an annual support program with RIM, so as soon as I get my account information I will be opening an incident with them for all of the calendaring issues that we are having. It sounds like some of you have gone down this route also, without great success. Wish me luck!

[DW747]

Hi CFSGuy,

We have actually been running CDO version: 6.5.7654.8 for quite some time now as this was recommended by Microsoft when they were doing the initial investigation. So far we have had no problems with this version of the CDO components and all seems to be fine.