CDO Helper Application Error
When logging onto the server where our BES is installed, using the BESAdmin user, we get the message that the CDO Helper Application has encountered an error and needs to close. This happens twice, we hit OK both times and everything works just fine. Can something be done about what causes errors?
Thanks a lot!
Getting the same error
Our setup is a BES 4.1 attached to Exchange 2003. Bothe servers are Windows Server 2003. CDO.DLL is the same servion on both machines.
Same thing here!!
Did you guys find any resolution to this?? I am getting the very same error...
Same issue here, wondering if anybody found a solution??? I have people that are having issues sending and I wonder if the two are related.
Thanks for any help
CDO Helper has encountered an error
CDO Helper Application - failure
Having the same issue. According to RIM CDO Helper is used to facilitate the "modification" of the calendar. We will get strange problems with our users where they are unable to send and recieve on the handhelds, reboot will resolve temporarily.. I have noticed that in the following registry location CDO__o_ profiles are building. Stop all BlackBerry services and DELETE the CDO__o_ entries and reboot the server.. be careful not to delete the BlackBerryManager and BlackBerryServer profiles, although, its not hard to fix if you do. Ill include a script to delete the CDO__o_ keys, use at your own risk. Obviously im not responsible for you environment.. test this first. This has saved my bacon on more than once. The information i am submitting doesnt prevent the issue, it just help to resolve the issue after its happening.. ANYONE KNOW WHY this is happening!?
Location of the CDO__o_ 's
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
'VBS to facilite deleting these.. TEST this first !
On Error Resume Next
Const HKEY_CURRENT_USER = &H80000001
strComputer = "."
strKeyPath = "Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles"
Set objRegistry = GetObject("winmgmts:\\" & _
strComputer & "\root\default:StdRegProv")
DeleteSubkeys HKEY_CURRENT_USER, strKeypath
Sub DeleteSubkeys(HKEY_CURRENT_USER, strKeyPath)
objRegistry.EnumKey HKEY_CURRENT_USER, strKeyPath, arrSubkeys
If IsArray(arrSubkeys) Then
For Each strSubkey In arrSubkeys
DeleteSubkeys HKEY_CURRENT_USER, strKeyPath & "\" & strSubkey
If InStr(strKeyPath & "\" & strSubkey, "CDO__o_") then
WScript.Echo strKeyPath & "\" & strSubkey
objRegistry.DeleteKey HKEY_CURRENT_USER, strKeyPath
Same issue here. Running BES v18.104.22.168 w/ 20 users. I too am on the hunt for a permanent solution. If anybody figures out the cause (and a resolution) please do chime in!
Update! Installing Exchange SP2 on the BES server seemed to correct this problem.
There are many reasons for this problem. Most are related to COD.dll.
luckey's solution seems like it was probably fixed in CDO code in MS Exchange SP2.
tc490225's script to remove the temporary _COD profiles is a great way to work around the problem, and other calendar related problems (ofter permissions related).
Anyone having this problem will have to give more details.
What is your BES version, what is the Exchagne System Manager version on the BES?
What is your backend Excahgne version?
Is full Exchange on the BES, or the Exchagne System Manager?
What Outlook versions do the users use? (or what is the highest version they may use?)
What is the cdo.dll version on the BES?
How many cdo.dlls are on the BES?
Which one is the registered one?
How To - Check if and where the CDO.dll file is registered
KB04912: BlackBerry Search Results
Determining which CDO version should be installed on the BlackBerry Enterprise Server
KB10197: BlackBerry Search Results
|All times are GMT -5. The time now is 11:02 AM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.