Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry Enterprise Mobility Server 3.7
  3. BEMS Release Notes
  4. BEMS 3.7.9.9 and BEMS Cloud Release Notes
  5. Fixed issues in BEMS 3.7 and BEMS Cloud

Fixed issues in
BEMS
 3.7 and
BEMS
 Cloud

BEMS
 3.7.9.9 and
BEMS
 Cloud (February 2024)

When a user had a contact without an email address and they tried to retrieve the contact using the Contacts API, a 500 Server Error was logged in the
BEMS
 log file, and the contact was not retrieved. For more information on the Contact Service API, see the Contact Service API Reference content. (G3SERVER-11542)
After the on-premises
BEMS
 instance was upgraded to version 3.7.2.2, users were unable to send S/MIME encrypted email using
BlackBerry Work
. (FIRST-18103, G3SERVER-11573)
When you performed a repair installation on your on-premises
BEMS
 instance, the repair failed if your SSL certificate root domain only specified two characters (for example, test.example.ca). A "Host information" warning was displayed. (FIRST-18039, G3SERVER-11519)
If
BEMS
 was configured to use
Microsoft Graph
 to access
Microsoft Office 365
, email notifications may have been delayed. (FIRST-18022, G3SERVER-11458)
When
Mail
 was configured to use Passive Authentication and the device tried to access multiple resources (for example, https://outlook.office365.com and https://autodiscover-s.outlook.com/), users did not receive email notifications. The BEMS logs logged the error message:
Error subscribing user <
user email address
> with exchange server outlook.office365.com
. (FIRST-17986, G3SERVER-11540)
When the Docs service was configured for
Active Directory
 Rights Management Services (AD RMS), or
Entra
-IP RMS support and users tried to view a protected file, the file could not be viewed. The BEMS log files logged the error message:
Failed to execute RMS HTTP request because rmsHttpWrapper.exe is stopped
. (FIRST-17983, GEMSS-10259)

BEMS
 3.7.2.2 and
BEMS
 Cloud (December 2023)

If
BEMS
 was configured to use
Microsoft Graph
 to access
Microsoft Office 365
, when a user searched
Active Directory
, phone numbers (for example, work and mobile) were not returned in the results. (FIRST-18029, G3SERVER-11467)
In the
BEMS
 on-premises Dashboard, if you configured or changed the Docs Settings (Docs > Settings), you were required to complete all fields, or the changes were not saved. (FIRST-18026, G3SERVER-11422)
If
BEMS
 was configured to use
Microsoft Graph
 to access
Microsoft Office 365
, users with a large number of messages in their Inbox did not receive email notifications. (FIRST-18022, G3SERVER-11461)
If you used the
BlackBerry
 Contact API in your third-party apps, the user's email address was displayed in an incorrect format (for example, email addresses were returned as an ExchangeDN instead of an email address). (FIRST-17975, G3SERVER-11382)
In
BEMS
 on-premises System Settings > Troubleshooting > Upload Log Credentials, the
BlackBerry
 Online Portal link redirected to an incorrect webpage. (FIRST-15579, G3SERVER-11381)