The BlackBerry Administration Service Application Server continues to stop and restart

Article ID: KB18366

Type: Support Content

Last Modified: 12-15-2011

 

Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
  • BlackBerry Enterprise Server for IBM Domino
CollapseEnvironment
  • BlackBerry® Enterprise Server 5.0 and 5.0 SP1 for Microsoft® Exchange®
  • BlackBerry® Enterprise Server Express 5.0 SP1 and 5.0 SP2 for Microsoft® Exchange®
  • BlackBerry® Enterprise Server 5.0 and 5.0 SP1 for IBM® Lotus® Domino®
  • Windows® 
  • SDR251193
CollapseOverview

The BlackBerry® Administration Service Application Server (BAS-AS) continues to stop and restart. The following error appears when the administrator attempts to log in to the BlackBerry Administration Service:

Page cannot be displayed when opening the BlackBerry Administration Service.

The following log lines appear in the BAS-AS log file:

Caused by: java.lang.Exception: problem creating sockets
(bind_addr=server.domain.com/xx.xx.xx.xx, mcast_addr=null) at org.jgroups.protocols.UDP.start(UDP.java:372)
at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:571) ... 131 more
Caused by: java.net.BindException: Address already in use: Cannot bind at java.net.PlainDatagramSocketImpl.bind0(Native Method)

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---

ObjectName: jboss.cache:service=BASObjectVersioningCache
State: FAILED
Reason: org.jgroups.ChannelException: failed to start protocol stack
I Depend On:
jboss:service=Naming
jboss:service=TransactionManager
jboss.aop:service=AspectDeployer

CollapseCause

The BlackBerry Administration Service instances use User Datagram Protocol (UDP) multi-cast to communicate with each other. If the inbound default UDP ports are in use or not available, the service does not start correctly.

CollapseResolution

To resolve this issue, complete the following steps:

  1. Run netstat with the following switches so that you are able to confirm which ports are available. Open a command prompt and type netstat -a -b -n > C:\netstat.txt.
  2. Confirm that the following UDP ports are used by the BAS-AS.exe service and not another application: 48858, 48857, 48855, 45588.
  3. Confirm that the TCP (non-default) ports 49955 and 45599 are not in use by other applications.
  4. Enable TCPPing.

For instructions on enabling TCPPing on BlackBerry Enterprise Server 5.0.0, see KB19436.

For instructions on enabling TCPPing on BlackBerry Enterprise Server 5.0.1, see KB19654.

For instructions on enabling TCPPing on BlackBerry Enterprise Server 5.0.2, see KB17089.

CollapseWorkaround

Workaround 1

Reserve the port that is being used by the other application.

For instructions on reserving the ports that are required by BlackBerry Enterprise Server services, visit the Microsoft Help and Support site and search for "How to reserve a range of ephemeral ports on a computer that is running Windows® Server 2003 or Windows® 2000 Server."

Workaround 2

Stop the DNS Client and DNS Server Services and restart the BAS-AS service. Once the BAS-AS service has completely started, restart the two DNS services.

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.