Red X when accepting meeting requests on Blackberry

[danton99]

I have found many forums out there regarding this without any real answers. Has this happened to anyone else? On all of our phones for the past week when a user accepts a meeting invite on their Blackberry (different models), and they choose to respond, it sends the response and shows a red X. It will show in the requestor's calendar that it was accepted but it won't go into your own calendar. I have looked at everything from cdo.dll to mapi32.dll version (all good) to a registry hack on the client pc but nothing fits our company. We have a BES and this has been running fine for years.
If anyone has encoutered this and resolved it, please share because I can't figure this one out.
Thanks!

[danton99]

Ah cmon guys, nobody has encountered/resolved this?

[MobileMadness002]

Just a quick question, are the affected users able to create their own cal events and are they able to envite other parties to their events. Sounds like a write error when trying to update the users cal. Do the logs on the BES show any blatant errors when trying to write to the affected calenders? Has their been any Microsoft updates applied to the Exchange server?

Wish I could offer more but I am not BES certified or trained, but I do know a fair bit questions to ask to try and pin point the error.

[danton99]

Thanks for responding Mobile. There have not been any issues creating Calendar events and inviting users as far as Outlook is concerned, just through the Blackberry. I think I have it though. Even thought the CDO.dll file versions on the BES and Exchange servers matched, I figured I would try to take the one on the Exchange server and paste it on the BES server, replacing the one that was there. I did that, restarted the Information Store and it is now working ok.

[dbovine]

I am getting this error now on a couple of phones now. Did a solution ever develop?

[michael47020]

I have seen it to - on BES 4 and 5, various devises.

We have support from O2 and they couldn't give us any advise other than raise with RIM and start testing this that and the other.

Mike