[jrice0309]

I'm running BES 4.1.4.15 for exchange 2003. There is one user that gets this error when he tries to accept meetings in his outlook 2007. I've traced the error to the BES I believe.

Does anyone know of any Hotfixes or updates I may need?

Let me know if you need anymore info, thanks for you help.

[knottyrope]

Remove user from BES and see if they acn accept meeting, if not might need to run a mailbox repair utility on the Exchange account.

[mattlane]

If you check the scheduling tab of the appointment. Is the person who is trying to accept the appointment changed to the organizer. (the attendee now appears twice, Once as the attendee and once as the organizer).

Can you also let me know what version of cdo.dll you are running on exchange and bes ?

[kendao]

I have been searching for a solution for someone and found this forum. hopefully someone can help me.

If you check the scheduling tab of the appointment. Is the person who is trying to accept the appointment changed to the organizer. (the attendee now appears twice, Once as the attendee and once as the organizer).

YES

Can you also let me know what version of cdo.dll you are running on exchange and bes ?

CDO.DLL locate in three different places in the machine running Outlook 2003 (not on Exchange Server)
1. C:\Program Files\Common Files\System\MSMAPI\1033 has version 6.5.7651.61

2. C:\Documents and Settings\username\My Documents\My Downloads\Microsoft Applications\Office 2003 Professional SP2\Data\FILES\PFILES\COMMON\SYSTEM\MSMAPI\1033 has version 6.5.7232.92

3. C:\WINNT\system32 has version 5.5.2448.0

[mattlane]

to work around the issue get the user to accept the meeting request on the blackberry. This changes the owner back to the correct owner. I am after the CDO.dll which is on your exchange server and your bes server. they should be identical. I still have not found a solution yet. As soon as i have got to the bottom of this I will let you know.

Q) Is this only affecting users who own 8300 devices.

[Kevin Stanley]

Was a solution identified for this issue? Someone in our Corporation has reported the same issue. They currently user a 8310