Hello, We are in an Exchange 2003 sp2/Outlook 2003 sp2 environment. When an internal user creates a meeting request that includes email addresses to external parties all the internal users who receive the meeting request receive just a plain email in the following format: When: Tuesday, June 26, 2007 4:00 PM-5:00 PM (GMT-06:00) Central Time (US & Canada). Where: Dial-In:north wing conferance room *~*~*~*~*~*~*~*~*~* i.e. no 'accept/deny' buttons. If a user creates a meeting request and includes only internal persons from our GAL, the meeting request is received by the internal persons w/ the correct accept/decline buttons. the user can then update their meeting request w/ the external parties and the external parties receive an email w/ the meeting info as above. All my searches have yielded articles about older Outlook clients or iCalendar format being selected, but this does not apply to us as all users are on Outlook 2003 sp2 and the iCalendar format is not even an option (it's greyed out, unchecked) when using an Exchange/Outlook set up (i.e. not pop). This has to be an issue on the server itself, right? Like the server is stripping the meeting request data? I've posted several entries to places like msexchange.org and the MS Exchange/Outlook newsgroups, all have yielded only client side resolutions (which did nothing for us). Any ideas on what else to check? Thanks in advance!

bumping...anyone?

so nothing?

Jim, Just wondering if you ever found a resolution to this issue. We're having the same issue on my end too. My issue start when someone at RIM was helping us out with a BES issue. Not sure what settings he went through. Whatever he did got the BlackBerry service working again but left us with the same issue youe having. Let me know if you found anything new. Thanks,TommyIRD

I imagine you guys have resolved this by now, but incase anyone else it looking here for clues... I ran in to this recently with Exchange 2007 , and Blackberry Enterprise Server 4.1 (running on seperate servers)More than likely, its an issue with CDO/MAPI.. in my case, I had installed Outlook 20003 with older CDO/MAPI on our blackberry server...I resolved this issue by re-installing the Collaboration Data Objects/MAPI 1.21 and rebooting.Stuart

OK - So now I've got a similar problem. The CDO/MAPI 1.21 - was this an installation on the BES server or the Exchange Server?JB