Has anyone who is using BES 4.0 for GroupWise noticed that if you change the date of an appointment, either in the GroupWise client or on the BlackBerry itself, the change does not synchronize?

In some cases, you can't even change the time of an appointment or the location.

A colleague of mine who also uses BES for GroupWise is having the same problem and RIM has listed a known bug ( http://tinyurl.com/ea2u8 ) with no resolution time frame set yet.

We've applied service pack 3 and the 3 hotfixes but the problem remains.

I now have several chiefs calling for my scalp because they've missed important meetings and I have to get them back onto Palm.

The workaround is to delete and recreate appointments whenever you need to make a change but when your PA is changing 80% of your appointments every day this just isn't practical.

If you're not having this problem or have found a way to fix it, please let me know.

Thanks,

Jerem

I have this problem too, and you are correct, the only workaround is to delete and re-create the appointment. I hope that BES 4.1 will fix this.

Do you work in a hospital?

Hi. No, I don't work for a hospital or a university so I don't know how we ended up with GroupWise, but it beats Exchange.

I have good news for you. The GroupWise 6.5.6 client, installed on the BES, fixes the calendar sync problem.

You should install SP3 on the BES first if you haven't already and make sure you have the right Trusted Application Key to paste in during setup. It should be about 64 characters long. The one that you can find in ConsoleOne is only 32 characters long and your BES will not sync if you use it.

It's also a good idea to stop all the BlackBerry services in Windows before you upgrade the BES and again when you upgrade GroupWise.

Let me know how you get on.

Best,

Jerem

Works great now Now when an appointment is rescheduled, the new appointment appears on the BlackBerry Calendar immediately. The old appointment disappears within 15 minutes.

I remember when we called tSupport they told us to use the beta GWise client. We decided to wait untill the full version was released; I guess we forgot as 6.5.6 was released a month ago. Thanks for the heads up!!

I am still experiencing this problem. I am using the GW 6.5.6 client on the BES and am on BES 4.0 SP 3 HF 3.

I am only aware of this problem with one user who is using a 7100i.

Any suggestions would be appreciated.