Zimbra

jeffw · #1 (**permalink**) 02-05-2008, 10:34 AM

Hi:

I have a user that reported that calendar syncing stopped (he says he's still getting mail) on his blackberry.

He created 2 appointments in the zimbra web client and one on his handheld. None are showing up in the other place.

The mailbox.log shows ZCB picking up the items:

Code:

2008-02-05 13:18:03,675 INFO  [btpool0-402] [name=jrober08@zstore.usg.tufts.edu;mid=8;ip=130.64.204.135;ua=ZimbraWebClient - FF2.0 (Win)/5.0.0_GA_1869.RHEL5;] CreateCalendarItem - <CreateCalendarItem folder=10> LC(mbox=deca4830-fbaf-4081-b07d-ef31791646fb, sessions=16832)
2008-02-05 13:18:04,465 INFO  [btpool0-396] [name=jrober08@zstore.usg.tufts.edu;aname=uit013@zstore.usg.tufts.edu;mid=8;ip=130.64.9.18;ua=ZimbraConnectorForBES/5.0.2428;] GetCalendarItem - <GetCalendarItem id=5566> LC(mbox=4d883e30-c081-4f2a-8662-ffd038de3377)
2008-02-05 13:19:25,004 INFO  [btpool0-396] [name=jrober08@zstore.usg.tufts.edu;aname=uit013@zstore.usg.tufts.edu;mid=8;ip=130.64.9.18;ua=ZimbraConnectorForBES/5.0.2428;] GetCalendarItem - <GetCalendarItem id=5566> LC(mbox=4d883e30-c081-4f2a-8662-ffd038de3377)
2008-02-05 13:20:09,121 INFO  [btpool0-402] [name=jrober08@zstore.usg.tufts.edu;mid=8;ip=130.64.204.135;ua=ZimbraWebClient - FF2.0 (Win)/5.0.0_GA_1869.RHEL5;] CreateCalendarItem - <CreateCalendarItem folder=10> LC(mbox=deca4830-fbaf-4081-b07d-ef31791646fb, sessions=16832)
2008-02-05 13:20:12,457 INFO  [btpool0-402] [name=jrober08@zstore.usg.tufts.edu;aname=uit013@zstore.usg.tufts.edu;mid=8;ip=130.64.9.18;ua=ZimbraConnectorForBES/5.0.2428;] GetCalendarItem - <GetCalendarItem id=5569> LC(mbox=4d883e30-c081-4f2a-8662-ffd038de3377)

What's my next step for troubleshooting?

alee · #2 (**permalink**) 02-05-2008, 10:39 AM

Quote:

Originally Posted by jeffw

Hi:

I have a user that reported that calendar syncing stopped (he says he's still getting mail) on his blackberry.

He created 2 appointments in the zimbra web client and one on his handheld. None are showing up in the other place.

The mailbox.log shows ZCB picking up the items:

Code:

2008-02-05 13:18:03,675 INFO  [btpool0-402] [name=jrober08@zstore.usg.tufts.edu;mid=8;ip=130.64.204.135;ua=ZimbraWebClient - FF2.0 (Win)/5.0.0_GA_1869.RHEL5;] CreateCalendarItem - <CreateCalendarItem folder=10> LC(mbox=deca4830-fbaf-4081-b07d-ef31791646fb, sessions=16832)
2008-02-05 13:18:04,465 INFO  [btpool0-396] [name=jrober08@zstore.usg.tufts.edu;aname=uit013@zstore.usg.tufts.edu;mid=8;ip=130.64.9.18;ua=ZimbraConnectorForBES/5.0.2428;] GetCalendarItem - <GetCalendarItem id=5566> LC(mbox=4d883e30-c081-4f2a-8662-ffd038de3377)
2008-02-05 13:19:25,004 INFO  [btpool0-396] [name=jrober08@zstore.usg.tufts.edu;aname=uit013@zstore.usg.tufts.edu;mid=8;ip=130.64.9.18;ua=ZimbraConnectorForBES/5.0.2428;] GetCalendarItem - <GetCalendarItem id=5566> LC(mbox=4d883e30-c081-4f2a-8662-ffd038de3377)
2008-02-05 13:20:09,121 INFO  [btpool0-402] [name=jrober08@zstore.usg.tufts.edu;mid=8;ip=130.64.204.135;ua=ZimbraWebClient - FF2.0 (Win)/5.0.0_GA_1869.RHEL5;] CreateCalendarItem - <CreateCalendarItem folder=10> LC(mbox=deca4830-fbaf-4081-b07d-ef31791646fb, sessions=16832)
2008-02-05 13:20:12,457 INFO  [btpool0-402] [name=jrober08@zstore.usg.tufts.edu;aname=uit013@zstore.usg.tufts.edu;mid=8;ip=130.64.9.18;ua=ZimbraConnectorForBES/5.0.2428;] GetCalendarItem - <GetCalendarItem id=5569> LC(mbox=4d883e30-c081-4f2a-8662-ffd038de3377)

What's my next step for troubleshooting?

this is a known problem:

Bug 21242 - BB: Appointments don't show up

please restart your BlackBerry Controller service and the user will start getting new appts on their device.
this problem normally happens if BES starts getting RPC or Maintenance Mode errors from the server. so until this bug is fixed, you might want to bounce this service whenever the server gets in this state.

jeffw · #3 (**permalink**) 02-05-2008, 10:40 AM

i just sent a test message to him, and then replied to it hoping that might trigger the calendar sync, but that didn't help.

jeffw · #4 (**permalink**) 02-05-2008, 10:50 AM

Quote:

Originally Posted by alee

this is a known problem:

Bug 21242 - BB: Appointments don't show up

please restart your BlackBerry Controller service and the user will start getting new appts on their device.
this problem normally happens if BES starts getting RPC or Maintenance Mode errors from the server. so until this bug is fixed, you might want to bounce this service whenever the server gets in this state.

Thanks. I'll see if I can get the service restarted. Any idea on a timeline for this fix?

-j

alee · #5 (**permalink**) 02-05-2008, 10:52 AM

Quote:

Originally Posted by jeffw

Thanks. I'll see if I can get the service restarted. Any idea on a timeline for this fix?

-j

this fix will probably come out in 5.0.3 since we missed the 5.0.2 train.

jeffw · #6 (**permalink**) 02-05-2008, 11:58 AM

I restarted the blackberry controller service, and the user in question is still not getting calendar changes.

Mine's working just fine, though.

Where should I look next?

alee · #7 (**permalink**) 02-05-2008, 02:24 PM

Quote:

Originally Posted by jeffw

I restarted the blackberry controller service, and the user in question is still not getting calendar changes.

Mine's working just fine, though.

Where should I look next?

are you talking about new appts or the old appts that should be there and still aren't there. the GIT problem that was outlined in the bug is bad because when that problem situation arises, calendar events are not sent to your device. when you restart BES and that problem goes away, you will still not get the old appts from when the problem was occuring but you should get new appts.

if they are having problesm with new appts but the user is still getting mail and you are getting new appts...then this is something that i've not seen before. please enable ZCB logging (fully with all options selected), and try the tests and then forward the logs along with the agent logs to support and we can take a look at what is going on.

in the meantime, you could try to delete/add the user to BES and have them reprovision their device. this brute force fix will trump most problems that you are seeing for this user.