Saturday 14 September 2013

Blackberry Collaboration Service does not stay started

In this post i will discuss about an issue which i have faced today and how i have fixed it.

I have installed a windows media package and restarted the blackberry enterprise server. After the server restart in the blackberry stand by server, the blackberry collaboration service does not stay started. Even though manually i have started the collaboration service, it stops again.

I have checked the BBIM logs on server and found 


<DEBUG>:<LAYER = BBIM, [BBCS] Invoking remote OCSC method, configureConnectorProperties, by sending request:>

From BAS Console, i have changed the listening port for the server instance BBIM from 65061 to 65063

Blackberry Solution Topology > Blackberry Domain > Component view > Collaboration > Edit (BESServer_BBIM_InstanceNumber)

But it didn't work, then i have reverted the changes back. (Changed the port to 65061)

From command prompt i ran netstat -abn which showed me the list of listening connections with the services in which OCSConnector.exe is not listening to 65061.

I have restarted the Blackberry Controller Service, again i ran the netstat command and found the below info

  TCP    0.0.0.0:65061          0.0.0.0:0              LISTENING
 [OCSConnector.exe]

I have determined that the BlackBerry Collaboration Service could not start due to a port conflict.  By running the netstat command i am able to determine that port 65061 was currently bound to the BlackBerry Controller.  To resolve this issue i have restarted the BlackBerry Controller service first.  I have verified that the controller was using a different port this time and i was then able to successfully start the BlackBerry Collaboration Services.


Therefore I conclude that when the server was restarted after applying the windows patches the Controller service happened to grab the port that the collaboration service needed causing the conflict.  Restarting the controller caused it to use a different port allowing the collaboration service to use the port it required.

Reference Article: KB32042

No comments:

Post a Comment