Handheld contact sync stopped

Are you using the Zimbra Connector for BlackBerry? Post your comments and questions here.
Post Reply
mernisse
Posts: 2
Joined: Sat Sep 13, 2014 1:50 am

Handheld contact sync stopped

Post by mernisse »

I noticed the other day that contact sync has stopped to the handhelds on the BES server.
I followed the steps here: ZCB and BlackBerry Enterprise Server (BES) Common Issues - Zimbra :: Wiki and verfied that in fact Outlook on the BES server does see the contacts in the BlackBerryServer store on the system. I did notice several disturbing lines in the BES logs:
[30531] (02/11 22:17:22.861):{0x1760} {mernisse@letsgocoldvoid.org} Failed to enable sync for private folder - unable to open contact folder(Contacts ID:2) for user (0x80040107)
I am attaching the logs from the connector and the MAGT log from the latest session.
Google is not showing a ton of hits on this topic and I'm not really sure where to look next, any assistance would be appreciated. If it is of any note, I can read the IMAP folder 'Contacts' via a standard MUA without an issue.
zco-20110211T224054.418-BlackBerryAgent.exe-5944.log.bak_1.zip
jasondykstra
Posts: 2
Joined: Sat Sep 13, 2014 1:53 am

Handheld contact sync stopped

Post by jasondykstra »

Did you get anywhere with this?
I found this: http://www.blackberry.com/btsc/KB24873 seems to be a problem as I have 'emailed contacts' and 'suggested contacts' (you can change the last one to 'suggested' for example....)
looking now for a way to change the name of the 'emailed contacts' folder...
mernisse
Posts: 2
Joined: Sat Sep 13, 2014 1:50 am

Handheld contact sync stopped

Post by mernisse »

I ended up re-installing the BES and the ZCB after wiping the zdb stores and letting everything resync. It was not a particularly fun process.
jasondykstra
Posts: 2
Joined: Sat Sep 13, 2014 1:53 am

Handheld contact sync stopped

Post by jasondykstra »

Cheers, I was just setting to do the same...
nevets666
Posts: 3
Joined: Sat Sep 13, 2014 1:56 am

Handheld contact sync stopped

Post by nevets666 »

i have been having the same issue and have tried deleteing and formatting both the ubuntu server 10.04 TLS and reinstalling Zimbra network edition and windows server 2003 with BES Express 5.0.2.29 everything but the contacts sync works and i get the error
[30531] (04/11 16:08:16.796):{0x164C} {1234567890@DOMAINNAME.co.uk} Failed to enable sync for private folder - unable to open contact folder(Contacts ID:2) for user (0x80040107)
please has anyone else been able to find a solution for this

eg remove or rename the emailed contacts folder on the zimbra server
nevets666
Posts: 3
Joined: Sat Sep 13, 2014 1:56 am

Handheld contact sync stopped

Post by nevets666 »

i've been able to resolve the issue now
nevets666
Posts: 3
Joined: Sat Sep 13, 2014 1:56 am

Handheld contact sync stopped

Post by nevets666 »

hmmmmmmm maybe not

it was working for 1 day then stopped working again
xeon
Outstanding Member
Outstanding Member
Posts: 208
Joined: Fri Sep 12, 2014 11:50 pm

Handheld contact sync stopped

Post by xeon »

What version of ZCB are you using?
abhullar
Zimbra Alumni
Zimbra Alumni
Posts: 21
Joined: Fri Sep 12, 2014 10:17 pm

Handheld contact sync stopped

Post by abhullar »

Here is a KB by RIM on this issue:

KB23776-Unable to synchronize address book when "Contacts" check box in the "Private contact folders" is unchecked
The above link does provides the following Resolution:
Perform the following steps to resolve this issue:
Log into the BlackBerry Administration Service.

Under BlackBerry Solution Management expand User and click Manage users.

Select the affected BlackBerry Smartphone user from the list.

Click Default Configuration.

Select E-mail.

Click Edit user.

In the Private contact folders select the checkbox for the Contact.

Click Continue to user information edit.

Click Save all.
Please try the above steps to see if this resolves this issue.
The above error Indicates that BES has cached the entryid of the contacts folder but the ZDB has been regenerated since that point – hence the cached entry id is invalid.
This can happen is you delete the ZDB or perform an user move.
Zimbra recommended steps for resolution:
- Wipe BB device

- Remove user from BAS

- Re-provision user in BAS

- Re activate BB device
Post Reply