
05-26-2009, 06:57 PM
|
 |
Proprietor
|
|
Join Date: Nov 2008
Posts: 2,237
|
|
KB02937 - How to download and manually update the cdo.dll file
KB02937 - How to download and manually update the cdo.dll file
Environment
- BlackBerry® Enterprise Server for Microsoft® Exchange®
- Windows® 2000
- Windows 2003
- Windows NT®
Overview
To download and manually update the cdo.dll file, complete the following tasks:
Note: Before applying the cdo.dll file, verify that the most recent service pack for the Microsoft Exchange System Manager is installed.
It is recommended that the cdo.dll and mapi32.dll be updated as part of Microsoft Windows updates or hotfixes, rather than being manually registered in this way.
Task 1
Download the cdo.dll file from the Microsoft Help and Support web site.
Note: To determine which version of the cdo.dll file you need, see the Additional Information section of this article.
There are two methods of downloading the cdo.dll file, depending on the version of Microsoft Exchange. Refer to the following Microsoft Support articles for the appropriate version of Microsoft Exchange.
Microsoft Exchange 5.5 and Microsoft Exchange 2000
Microsoft Exchange 2003
For more information about the cdo.dll file, search Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 on the Microsoft Help and Support web site.
Task 2
Register the cdo.dll file by completing the appropriate steps:
BlackBerry Enterprise Server software version 4.0 and 4.1
For Microsoft Exchange Server 5.5 with Windows 2000 or Windows NT, complete the following steps:
- Stop the BlackBerry Controller and BlackBerry Dispatcher services.
- Click Start > Run.
- Type regsvr32 "C:\exchsrvr\bin\cdo.dll"
- Click OK.
- Restart the BlackBerry Dispatcher service and then the BlackBerry Controller service.
For Microsoft Exchange Server 2000 and Microsoft Exchange Server 2003 with Windows 2000, or Microsoft Exchange Server 2003 with Windows 2003, complete the following steps:
- Stop the BlackBerry Controller and BlackBerry Dispatcher services.
- Click Start > Run.
- Type regsvr32 "C:\Program Files\Exchsrvr\bin\cdo.dll "
- Click OK.
- Restart the BlackBerry Dispatcher service and then BlackBerry Controller service.
BlackBerry Enterprise Server software version 3.6 or earlier
Complete the following steps:
- Click Start > Run.
- Type regsvr32 "cdo.dll"
- Click OK.
- Restart the BlackBerry Server <BlackBerry_Enterprise_Server_name> service.
Additional Information
Warning: The following procedure involves modifying the computer registry. This can cause substantial damage to the Microsoft Windows operating system. Document and back up the registry entries prior to implementing any changes.
To verify that the correct cdo.dll file version is being used, complete the following steps:
1. Check the version of the mapi32.dll file on the BlackBerry Enterprise Server.
2. Use the table below to check the corresponding version of the cdo.dll file.
Note: For instructions on how to locate the cdo.dll file and to verify that it is registered, see KB04912.
Microsoft Exchange Administration Tool | | | Microsoft Exchange 5.5 Administrator
| 5.5.2657.55
| 5.5.2653.12
| Microsoft Exchange 2000 System Manager
| 6.0.6487.2
| 6.0.6487.1
| 6.0.6603.0
| 6.0.6603.0
| Microsoft Exchange 2003 System Manager
| 6.5.6980.3
| 6.5.6944.0
| 6.5.7226.0
| 6.5.7226.0
| 6.5.7651.61
| 6.5.7638.1
| Important: To make sure that the Daylight Saving Time (DST) updates for the BlackBerry Enterprise Server function correctly in a Microsoft Exchange 2003 environment, use cdo.dll version 6.5.7651.61.
The most recent release of the DST patches for Exchange 2003 SP2 were made available in August 2008 (see Microsoft knowledge base article 956398) and this cdo.dll was version 6.5.7654.4.
For more information about thecompatibility and support for specific versions of cdo.dll and mapi32.dll please refer to the BlackBerry Enterprise Server Compatibility Matrix
BlackBerry - BlackBerry Enterprise Server Compatibility
__________________
http://blog.port3101.org/hdawg/
The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.
|