In part 3 of this series, I will share some of the issues and resolutions I encountered during my BEMS implementation.

If you haven’t already, feel free to check out other parts of this series to get your BEMS implemented. I promise it will save you hours from reading all the documentation (though it never hurts for extra knowledge!)

• Part 1: Installation
• Part 2: Configuration
• Part 3: Troubleshooting (you are here!)

The installation itself is relatively pain-free.

Similar to the multi-subnet setup in UEM, I came across an issue within BEMS configuration to support the setup. Basically, below are the steps you need to do within BEMS:

• On each computer that hosts BEMS, open the Apache Karaf Web Console. Open a browser window and navigate to https://<BEMS instance hostname>:8443/system/console/configMgr.

• Scroll to and click com.good.server.core.datasource.
• In the jdbc.url field, add the following property to the end of the connection string:MultiSubnetFailover=true. For example, Jdbc:sqlserver://<Listener value>;databaseName=<database name>;integratedSecurity=true;MultiSubnetFailover=true;.
• Click Save

Somehow I get the below from time to time whether I enter domain\username or just username when prompted.

I also get this upon entering the URL from my local machine: “The requested page was not found. If you are not forwarded in 3 seconds to the Web Console, please click here” Essentially, it keeps directing me to https://servername:8443/system/console/bundles instead of https://servername:8443/system/console/configmgr.

This is incorrect and why does this happen?

We then reviewed the BEMS log located at D:\blackberry\bemslogs (or C drive depending on your environment.)

When the database hosted on SQL 2016 AAG is active in NY, we see the error in the log below. Also, pinging from NJ BEMS server to the SQL AAG listener doesn’t resolve properly.

Line 952: 2018-01-31T13:38:08.807-0500 CEF:1 | good | com.good.server.core.sqlserver-jdbc-driver-bundle | 0.11.3 | DEBUG | unknown | 3 | ID=79 THR=onsole/configmgr CAT=SQLServerException MSG=*** SQLException:ConnectionID:122 com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host SQLAAG, port 1433 has failed. Error: “connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.”. The TCP/IP connection to the host SQLAAG port 1433 has failed. Error: “connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.”.

Line 955: javax.security.auth.login.LoginException: Error has occured while retrieving credentials from database:Cannot create PoolableConnectionFactory (The TCP/IP connection to the host SQLAAG, port 1433 has failed. Error: “connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.”.)

2018-01-31T13:38:08.807-0500 CEF:1 | loginproviders | loginproviders | 0.11.3 | INFO | unknown | 5 | ID=90 THR=onsole/configmgr CAT=LoginUtil MSG=Login failed for user username

While the database is active in NJ, the connection is successful from the NJ BEMS server.

This issue wasn’t truly resolved at the time. As a workaround, I accessed the Apache Karaf Web Console of NJ BEMS server from the NY BEMS server while the database is active in NY.

During troubleshooting with Blackberry technical support, you may be asked to enable DEBUG logging for BEMS. Here’s a screenshot of what it looks like.