[slimbim]

Whenever logging into the BES server, we get multiple windows error pop up messages whether to tell microsoft about the problem regarding the CDO Helper Application. Exact error message is: "CDO Helper Application encountered a problem and needed to close"

In the event log, I see Informational event that states:
Reporting queued error: faulting application CalHelper.exe, version 4.1.3.15, faulting module CalHelper.exe, version 4.1.3.15, fault address 0x0008d3f0.

What does this error exactly mean, and what is the cause and solution? I know this has something to do with the CDO and the calendar sync but is this something of a concern or does it just automatically resolve whatever the issue was?

Thanks.

[stuwhite]

Originally Posted by slimbim

Whenever logging into the BES server, we get multiple windows error pop up messages whether to tell microsoft about the problem regarding the CDO Helper Application. Exact error message is: "CDO Helper Application encountered a problem and needed to close"

In the event log, I see Informational event that states:
Reporting queued error: faulting application CalHelper.exe, version 4.1.3.15, faulting module CalHelper.exe, version 4.1.3.15, fault address 0x0008d3f0.

What does this error exactly mean, and what is the cause and solution? I know this has something to do with the CDO and the calendar sync but is this something of a concern or does it just automatically resolve whatever the issue was?

Thanks.

Embarassingly I don't actually know but I know that when we had the same error, a (already-scheduled) update to the next SP fixed it so maybe the CDO is corrupt. If you are about to patch your CDO anyway for DSt, might be worth waiting to see if that makes it run away.

[slimbim]

Thanks for your reply

I guess I'll endure the hold times and try asking T-support, though I never really had any luck getting a straight answer/solution for these kind of things with them...

[stuwhite]

Originally Posted by slimbim

Thanks for your reply

I guess I'll endure the hold times and try asking T-support, though I never really had any luck getting a straight answer/solution for these kind of things with them...

i fairly sure it doesn't affect anything as we had it for ages, so i would CDO patch for DST and if it still does it, try RIM after that.

[slimbim]

CDO patch for all our servers have already been rolled out two weeks ago, and the CDO.dll file matches the Exchange version... does it need to be manually re-registered when it gets updated by any chance?

[stuwhite]

Originally Posted by slimbim

CDO patch for all our servers have already been rolled out two weeks ago, and the CDO.dll file matches the Exchange version... does it need to be manually re-registered when it gets updated by any chance?

It only has to be done manually if you see issues. You can use this doc to check that the correct one is being used by BES.