Im having an issue with our blackberry server not starting up completely. I have only recently had it setup, and working with only a single blackberry for a few days, then suddenly it all stopped working.

I believe I have set it up correctly using the zimbra documentation since I had it working for a few days, but after doing some screwing around on the phone itself, it suddenly stopped working. No emails come in to the phone and no emails go out.

When I look at the services on the machine the following are running
Administration Service - Application Server
Administration Service - Native Code Container
Alert
Dispacher
MDS Connection Service
Router

When I start the controller service, the rest of the blackberry services start, then after a few seconds, they all stop.

The only thing I have done on the phone from when it was working to when it all fell apart was try to disable send email to handheld, and re-enable it, and also try to get the phone to sync sub folders of the mailbox.

So far on the server, I have recreated the outlook profiles again, and used the IEMSTest utility to open them up which seem to work ok. And I've changed the SRP keys on the server to a different one (I applied for 9 keys when I registered for the express server)

I also have tried the startup and shutdown service sequence, but when I start up the controller service, it automatically kicks up the remaining services, and then shuts them all down.

When I start the controller service, the following start up (in that order I think)

Mail Store Service
Synchronization Service
Policy Service

Then these services stop with the controller service.

I dont know if I am able to follow the guidelines on starting and stopping services when the controller services does these actions.

10-22-2010, 09:59 AM

eugener

Perhaps repair of zcb connector will help (Add/Remove programs->focus on zcb connector)->Repair.

10-24-2010, 10:38 PM

scasperson

Bang on! Thanks

That worked a treat! I was baning my head against a wall for hours trying to figure why it wasn't working. :)

01-13-2011, 05:59 AM

nexed

This works...

This solution works... but why?

Repairing the Zimbra BES connector each time the BlackBerry Controller fails to remain started is clearly a problem...

Any permenant fixes for this?

01-13-2011, 06:36 AM

ebory

Quote:

Originally Posted by scasperson

That worked a treat! I was baning my head against a wall for hours trying to figure why it wasn't working. :)

WOW ... me too !
thank !

04-14-2011, 06:28 AM

profion

OK, this is really serious problem..

Zimbra didn't fix that issue on old connector, and didn't fix that on new one for BES express...

WHY?!? - I spent today 3hrs for nothing.. All I had to do is repair connector..

Why this happend after 1.5month of smooth run?

:mad::mad::mad:

04-15-2011, 01:03 PM

xeon

Could have been a Windows Update that caused a change in the ZCB DLLs. Its recommended to turn off Windows Updates. Not sure if this is official word, but after I apply Windows Updates (in a maintenance window of course) I update/repair ZCB, just in case.