The BlackBerry Enterprise Management Web Service fails to start following an upgrade of BlackBerry Enterprise Service 10

Article ID: KB34875

Type: Support Content

Last Modified: 09-22-2014

 

Product(s) Affected:

  • BlackBerry Enterprise Service 10
CollapseEnvironment
  • BlackBerry Enterprise Service 10 version 10.1.1 to 10.1.3
  • Oracle Java Runtime Environment
CollapseOverview

The BlackBerry Enterprise Web Management Service (EMWS) fails to start and the following is logged in the EMWS_err log:

SEVERE: Error initializing endpoint java.security.KeyStoreException: Key not supported

INFO: Initializing Coyote HTTP/1.1 on http-38084
Mar 19, 2014 10:02:30 AM org.apache.coyote.http11.Http11NioProtocol init
SEVERE: Error initializing endpoint
java.security.KeyStoreException: Key not supported
    at com.certicom.tls.interfaceimpl.TLSKeyStoreImpl.setKeyEntry(Unknown Source)
    at com.certicom.jsse.provider.jdk1_5.CerticomKeyManagerFactorySpi_jdk15.engineInit(Unknown Source)
    at javax.net.ssl.KeyManagerFactory.init(Unknown Source)
    at org.apache.tomcat.util.net.NioEndpoint.init(NioEndpoint.java:844)
    at org.apache.coyote.http11.Http11NioProtocol.init(Http11NioProtocol.java:136)
    at org.apache.catalina.connector.Connector.initialize(Connector.java:1022)
    at org.apache.catalina.core.StandardService.initialize(StandardService.java:703)
    at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:838)
    at org.apache.catalina.startup.Catalina.load(Catalina.java:538)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
    at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:276)
    at com.rim.mdm.tomcat.EMWSTomcatStartup.init(EMWSTomcatStartup.java:49)

Mar 19, 2014 10:02:30 AM org.apache.catalina.core.StandardService initialize
SEVERE: Failed to initialize connector [Connector[org.apache.coyote.http11.Http11NioProtocol-38444]]
LifecycleException:  Protocol handler initialization failed: java.security.KeyStoreException: Key not supported
    at org.apache.catalina.connector.Connector.initialize(Connector.java:1024)
    at org.apache.catalina.core.StandardService.initialize(StandardService.java:703)
    at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:838)
    at org.apache.catalina.startup.Catalina.load(Catalina.java:538)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)
    at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:276)
    at com.rim.mdm.tomcat.EMWSTomcatStartup.init(EMWSTomcatStartup.java:49)


The Windows Event Logs may also report Event IDs 4096 and 4098.

Starting the service manually will return error:

The BES10 - Enterprise Management Web Service on hostname started and then stopped. Some services stop automatically if they are not in use by other services or programs.

CollapseCause
The Java Runtime Environment (JRE) version installed has not been updated with the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files.
CollapseResolution

Update JRE with the JCE Unlimited Strength Jurisdiction Policy files.

Warning: System/database changes could potentially result in irreparable damage. Prior to making any system/database changes it is recommended that you perform a system/database backup.

  1. Obtain the Java JCE Jurisdiction Policy files from Oracle.
  2. Extract the local_policy.jar and US_export_policy.jar files from the Java JCE Jurisdiction Policy file package, and copy them to the following locations:
    • C:\Program Files (x86)\Java\jre1.7.0_21\lib\security
    • C:\Program Files\Java\jre1.7.0_21\lib\security

Note: These files already exist in the above locations, but should be replaced as a result of this step.

CollapseAdditional Information

To locate the correct Java path, open the Windows Registry and review the information in this key location:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BES - EMWS\Parameters\JVM Library]


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.