Unable to activate or enroll BlackBerry PlayBook or BlackBerry 10 smartphones due to port conflict on MDS-CS

Article ID: KB33663

Type: Support Content

Last Modified: 03-01-2013


Product(s) Affected:

  • BlackBerry 10 OS
  • BES10
  • BlackBerry PlayBook tablet
  • BlackBerry Device Service 6.2
  • BlackBerry PlayBook
  • BlackBerry 10

    Over The Air (OTA) Enterprise Activations of BlackBerry PlayBook tablets or BlackBerry 10 smartphones are failing with the error: The server could not be contacted. The Enterprise Web Management Service (EMWS) is properly started, is confirmed as running, and logs are generating.


    The MDS Connection Service is not fully functional. Review of the MDAT logs shows : 

    <DEBUG>:<LAYER = SRP, SRPID = S########[BDS-SERVER01:3200], EVENT = Authentication, PHASE = spec_2_1_1, MESSAGE = Succeeded>
    <ERROR>:<LAYER = SCM, LifecycleException:  Protocol handler initialization failed: java.net.BindException: Address already in use: bind>
    <ERROR>:<LAYER = SCM,       at org.apache.catalina.connector.Connector.initialize(Connector.java:1024)>
    <ERROR>:<LAYER = SCM,       at org.apache.catalina.startup.Embedded.start(Embedded.java:830)>
    <ERROR>:<LAYER = SCM,       at net.rim.application.ipproxyservice.TomcatThread.startTomcat(Unknown Source)>
    <ERROR>:<LAYER = SCM,       at net.rim.application.ipproxyservice.TomcatThread.run(Unknown Source)>

    The following log lines could be printed constantly in the EMWS debug log when attempting to enroll a device.

    [DEBUG] (02/12 13:34:48:552):{AsynchronousPushServiceThread} EMWS:Sent Poke to: http://SERVER.DOMAIN.COM:8080/push2 with query parameters: PORT=7875&DESTINATION=00PIN000&REQUESTURI=%27%27
    [DEBUG] (02/12 13:34:48:552):{AsynchronousPushServiceThread} EMWS:X-Rim-Push-Id: c987651-fdd7-487d-b127-39764e29253c
    [DEBUG] (02/12 13:34:48:552):{AsynchronousPushServiceThread} EMWS:Status Code was: 404
    [DEBUG] (02/12 13:35:48:525):{AsynchronousPushServiceThread} EMWS:Sent Poke to: http://SERVER.DOMAIN.COM:8080:8080/push2 with query parameters: PORT=7875&DESTINATION=00PIN000&REQUESTURI=%27%27
    [DEBUG] (02/12 13:35:48:525):{AsynchronousPushServiceThread} EMWS:X-Rim-Push-Id: c1234981-1c60-4aff-b2b1-82d75b9b935c
    [DEBUG] (02/12 13:35:48:525):{AsynchronousPushServiceThread} EMWS:Status Code was: 404

    The default ports used by MDS-CS are 8080 and 8443, and one of these ports are in use by another process.


    Confirm available ports on this server by opening a Command Window with Administrator rights and perform:

    netstat -abn > c:\ports.txt

    This will generate a text file of the ports in use and the process that is consuming that port.

    The WebServerListenPort (set to use port 8080 by default) and the WebServerListenSSLPort (set to use port 8443 by default) used in the MDS-CS component in BlackBerry Device Service may conflict with Tomcat and the Universal Device Service Console. It is recommended that both of these ports be updated to other values (such as 8099 and 8445 respectively); this is achieved by logging into the BlackBerry Administration Console and navigating here: BlackBerry Solution Topology > BlackBerry Domain > Component View > MDS Connection Service > Instance Name > General tab

    Refer to KB32547 on recommendations on how to install the BlackBerry Enterprise Service 10 package on the same physical server.


    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.