Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Mobility > Zimbra Connector for BlackBerry

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-09-2010, 09:03 AM
Active Member
 
Posts: 49
Default CDO_ in BES Mail Profile List

One of our BES has some strange mail profiles in the Mail control panel. In addition to the two expected, BlackberryServer and BlackberryManager, there are about 125 additional profiles. They take the form "CDO_username_hexnumber_hexnumber". There are multiple entries for each username with the only difference among them being the hex number? Any one seen this. This is BES 4.1 SP5. Connector is 5.0.2711.18

If I click on one of the CDO_ entries and try to view the mail account details, a dialog popup say MS Exchange is not available and asks if I want to work offline.

Last edited by kbigger; 06-09-2010 at 09:09 AM..
Reply With Quote
  #2 (permalink)  
Old 06-17-2010, 12:18 PM
Zimbra Employee
 
Posts: 187
Default

These temporary cdo profiles can be manually removed using procedure below:

- stop BB controller
- go to the list of the profiles (control panel->mail) and manually remove all 'CDO_....' profiles
- start BB controller

Most likely this happened because windows update overwrote ‘emsmdb32.dll’. This dll is heavily used by CalHelper and has to have the same version as BES connector. As highlighted in zcb installation document, customers must do zcb repair each time after windows update is finished. zcb repair will make sure that above mentioned dll has proper version.

In addition, the following bug fix was included in zcb 5.0.24:

Bug 35042 – Windows Update or Outlook repair can break BES functionality

This fix will automatically make sure that the version of dll in question is correct so that doing zcb repair is no longer necessary. That is why upgrading to zcb 5.0.24(or zcb 6.0.7) will eliminate possibility of this happening again.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.