[dcolpitts]

Has anyone else seen any calendar issues with BES Express 5.0.x and Exchange 2010 SP1 where calendar entries on the Blackberry simply disappear after say 24 hours (I can't confirm the time interval yet)? Resyncing using RSET from Calendar --> Options returns the calendar entries for another period of time. 5.0.1 and 5.0.2 are both exhibiting this issue in conjunction with Exchange 2010 SP1.

On our first server, we upgraded from Exchange 2010 RTM + Hotfix 4 to Exchange 2010 SP1, and then a couple of days later from 5.0.1 to 5.0.2 (5.0.1 and 2010 RTM had been fine for over 5 months). On the second server we are seeing the issue with, we migrated from Exchange 2007 SP2 directly to Exchange 2010 SP1, and were seeing this issue on 5.0.1, after which we upgraded to 5.0.2. I'm 99.9% sure the BESAdmin permissions are correct. This is not affecting all users, but most users.

Anyone have any ideas?

dcc

[bmwilson1978]

Hey there, I see E2K10 SP1 is still being assessed for compatibility by RIM as per the latest available compatibility matrix.

BlackBerry - BlackBerry Enterprise Server Compatibility

[dcolpitts]

Yeah - I know... Just a quick follow up. The removal of the calendar entries appears to occur every 6 hours.

[smartbrains]

Same story for me. Exchange 2010 + SP1, BESX 5.0.2. My calendar keeps disappearing, and I have to do RSET on my handheld and wait for a reload. Quite annoying. Please keep me posted.

[dcolpitts]

Just an update. We are opening a support call with RIM this afternoon (finally broke down and got a TSupport contract). However, in trial and error, we found the calendar issue appears to be related with the number of entries you have in your calendar. The magic number is somewhere between 500 & 600 items. I had 1999 items this morning when we found this.

I exported my calendar to a PST, then deleted everything older than January 1, 2010, leaving me with 146 items. My calendar never cleared after a BES reboot as it was doing previously. I then re-imported my 2009 entries, which put me at a count of 606 items, and upon BES reboot it wiped. One of the guys on my support team discovered this, and I know the number was over 500, but less than 600, but I don't recall the exact number he found to be the make / break number.

dcc

[smartbrains]

Please update us on your support case. I have over 600 calendar items, and it happens to me, but my brother has much much less and he is OK.

Mickey

[jnix99]

Do you have Public Folders turned on in your environment? Found some other posts online where this has worked for people.

I'm in the same boat btw. In the middle of an Exchange 2003-2010 SP1 migration and missed the fact BES doesn't support SP1 yet...

[dcolpitts]

Yup - Public Folders are on. RIM had us recreate the mapi configuration for BESAdmin this afternoon and it looked like that was gonna fix it, but after about 20 reboots of the BES, the handheld calendars wiped again.

[jnix99]

I know everyone has prob seen this too, maybe worth mentioning though

I can't post the link but if you google shudnow and exchange 2010 sp1 blackberry enterprise the link should be the first result. Discusses modifying the BESthrottling policy, however in the comments one guy had to apply the changes to his default throttling policy as well:

Get-ThrottlingPolicy | Set-ThrottlingPolicy -RCAPercentTimeInCAS:$null -RCAPercentTimeInMailboxRPC:$null -RCAMaxConcurrency:$null -RCAPercentTimeInAD:$null

[dcolpitts]

All RCA* settings are already null in both the default and the BES policies. You'll also note I've posted in the comments of that particular thread too...

[jnix99]

Oh that's funny, I did miss that. Let's hope RIM can figure out a workaround..

[MarkF]

Full support for E2010 comes with BES5.0 SP3 - no release date yet.

Thanks for the info on throttling, do those disappearing Calendar items seem to be the only issues with BES5 and E2010?

[dcolpitts]

Thus far - that is our only know issue with BES 5.0.2 and Exchange 2010 SP1, out of 275 mailboxes...

[smartbrains]

do they have an ETA on when they will release the update? or did they provide a workaround?

[MarkF]

thanks dcolpitts, we're just about to move into pilot with E2010 SP1 and according to test plan we won't hit 300 users (out of 80K) until mid Nov. Hopefully BES 5.0 SP3 will be released by then

[smartbrains]

FYI, I have 3 mailboxes and 1 is experiencing the calendar issue. It's not related to the quantity of mailboxes.

[opieharper]

So it would appear that in SP1, Microsoft introduced EWSFindCountLimit throttling. It will search for the first thousand entries, maybe on one user, or across all users, then respond to all subsequent find requests with an item not found message, which causes BES to think that the item has been deleted, and it tells the device to delete them. It will be fixed in SP3, but there is a workaround:
Set the EWSFindCountLimit to $null

1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
2. Type New-ThrottlingPolicy BESPolicy.
3. Type Set-ThrottlingPolicy BESPolicy -RCAMaxConcurrency $null -EWSFindCountLimit $null -EWSMaxConcurrency $null
4. Type Set-Mailbox "BESAdmin" -ThrottlingPolicy BESPolicy.

Good luck!

[Korbyn]

Do you happen to notice a pattern at all with the device code? I remember with moving several systems from E2003 to E2007 that the calendars would duplicate with any device running 4.3 code. Two of the users I'm having troubles with are running 5.0 code and I've stopped moving anyone else, peoples calendars are to important to them.

Shudnow found some pretty handy changes, but it would seem MS has buried something else somewhere to screw RIM over again. Mind you they screwed most of the backup vendors too, SP1 might as well been E2011, everything has to be updated yet again.

[Korbyn]

giving yours a try Opie. Thanks.

[MarkF]

Here's my issue. Our BESADMIN mailbox is on an E2K3 server so I can't apply the throttling policy to it as outlined in step 4:

4. Type Set-Mailbox "BESAdmin" -ThrottlingPolicy BESPolicy.

Seems very risky to migrate that mailbox to E2010 and have a chance at affecting the other 10K BB users with mailboxes still on E2K3.