OpenMsgStore (0x8004011d) and CDO failed Errors only some users

Brief History: We had BES 4.1.6 with exchange 2007 and we just migrated to exchange 2010. I migrated all users to bes express 5.0.2 and used Blackberry Transporter and everything was working fine before we moved to exchange 2010.

When moved to Exchange 2010 i applied all the permissions on the server from this link

I installed MapiCdo on both of our exchange servers and bes server. BESX has about 83 users and about 50 our working fine but the other 30 are not. I ran EMSTEST and see below for one of our users that is having this issue.

Also after running EMSTEST with a unsuccesful user i try to re-run it again and get a error

Re: OpenMsgStore (0x8004011d) and CDO failed Errors only some users

By default, Microsoft® Exchange 2010 uses client throttling policies to track the bandwidth that each Microsoft Exchange userconsumes and enforce bandwidth limits, as necessary. The policies affect the performance of the BlackBerry® Enterprise Servernegatively, so you should turn off client throttling for the Windows® account that has a Microsoft Exchange mailbox.Please check http://www.blackberry.com/btsc/KB20608

Re: OpenMsgStore (0x8004011d) and CDO failed Errors only some users

Have you had any luck with this yet? I have the same errors even though the throttling policy has been setup completely with $null on all the suggested connections, and is applied to the besadmin mailbox. Also, this is occuring on the only mailbox on Exchange 2010 and the first Blackberry device I've tried to add, so I don't think it's related to throttling policy. If you do get anything figured out, I'd appreciate hearing what your fix was.

Re: OpenMsgStore (0x8004011d) and CDO failed Errors only some users

Try looking at your MAPI CDO version, there are multiple versions of CDO 1.2.1. For my Exchange 2013 integration, I was getting this error without fail in the MAGT logs and IEMTEST utility only to find out I was using the CDO 1.2.1 that was time stamped from February 2013. Once I uninstalled and applied the May 2013 version and error is fixed.