[Recursion20]

Accounts created in Groupwise and later deleted still appear in the Blackberries Addressbook 'lookup' function.

I am performing a "delete" on the groupwise object (not an expire). The user object does not seem to appear in the groupwise global calendar (groupwise desktop client can not find the user).

Several days / weeks later, the blackberries are still able to retrieve the users information.

This is a concern to me as in one case a users info was entered incorrectly. The account was deleted and recreated with proper information, but a search on his last name still reports two possible accounts.

Relevant info:
Groupwise 7.0
BES 4.1.0

Any ideas would be excellent,
Thanks.

[Zro]

in sql run the following on the BESMgmt database to clear the BES's lookup table

delete from mbaddresslookup

Once that is clear, use the sync system address book command in the BB Manager.

[Recursion20]

Clearing the mbaddresslookup table fixed the issue.
Thank you again!

I am surprised about the requirement to "physically" purge the records. I assumed BES would synchronize to the Groupwise system. Perhaps its part of the 'ugly' Groupwise API I hear so much about.

Again, thanks...
May I query you as to where learnt this? These are the "small" issues that let me understand I do not know the internal workings of the system. Perhaps formal training through RIM will illustrate the inner workings better..

Thanks.

[Zro]

BES 4.1.2 actually has a link under the sync system address book one that is a "clear and sync system address book"....makes things much easier.

Found out about this when I ran into the issue and was talking to RIM.

Speaking of 4.1.2, you may want to look at upgrading to it. There's two HUGE issues with 4.1 that become major pain in the butts.

First, if you have a temporary disruption between the BES and the POA, if any logins are attempted during this time it fails (obviously) but the BES doesn't try to re log in. So the users that are affected will not be able to send/receive email. To fix, you can remove/wipe/readd the user, or you can restart the BlackBerry Controller.

IF you restart the Controller you run into the second issue, message flow can take up to 3 hours to resume for everyone on the BES.

Zro

[|||||||]

And make sure you are running GroupWise client 6.5.7 release date Nov6/2006 (TID2974707)
Check out KB04614 for more info

[Recursion20]

I'm curious as to why you suggest the 6.5.7 groupwise client? Currently we are using the 7.0.1 client, and have not run into any issues (that anyone has noticed).

Thanks.

[|||||||]

The 7.x client isn't supported and specifically has issues with address book I have found.