Skip to content
Help and manuals  >  Enterprise services  >  BlackBerry Enterprise Mobility Server  >  Installation and configuration: BEMS in a Good Control, Good Proxy environment

Appendix EBEMS Windows Event Log Messages

Message

Component

Level

Context

Error Node exceeded capacity (100%). <number of users including users over exceeded capacity>/<number of users for maximum capacity>

autodiscover/ewslistener

Error

This error occurs when the BEMS instance reaches maximum user capacity. BEMS features might not work as expected for any new users added to the BEMS instance. For example, notifications.

Warn Node close to exceed capacity (80%). <number of users>/<number of users for maximum capacity>

autodiscover/ewslistener

Warning

This warning occurs when the BEMS instance reaches 80% of user capacity or if one BEMS instance is working at overcapacity and one BEMS instance is working under capacity. BEMS automatically reassigns users between the two BEMS instances.

Error communicating with Good Proxy Server - HTTP code {}, Message {}

server-core/gd-core

Error

Could not connect to Good Proxy server while verifying authorization token (during Push Registration from G3 Mail context)

Failed to retrieve the list of Good Proxy servers - code {} - Reason {}

server-core/gd-core

Error

Used for high availability and load balancing of requests to Good Proxy server. The list of known Good Proxy servers are maintained in memory and requests are load-balanced through this list.

Failed to retrieve the list of Good Proxy servers

server-core/gd-core

Error

Used for high availability and load balancing of requests to Good Proxy server. The list of known Good Proxy servers are maintained in memory and requests are load-balanced through this list.

Incorrect Good Proxy Server configuration

server-core/gd-spring

Error

Communicate with Good Proxy server to verify Authorization token using HTTP(s) protocol. If URL is syntactically wrong or configuration error then error is logged in event log.

Autodiscover failed for {} users with exception {}

server-notifications/autodiscover

Warn

Failed to retrieve user’s settings through autodiscover. Needs administrator attention to fix the issue. The user will not receive notifications until issue is resolved. This is a batch request and the log only prints the number of users that failed auto discover.

Invalid syntax for property {}, must be a valid URL

server-notifications/autodiscover

Error

Server is configured with an invalid URL used for bypassing the steps to find the autodiscover end point. BEMS ignores this URL and follows the regular steps to perform autodiscover.

User {} being quarantined after {} attempts to perform autodiscover

server-notifications/autodiscover

Warn

BEMS can not autodiscover the user’s settings for configured number of attempts. The user mentioned is marked as ‘QUARANTINED’ and does not receive notifications. The status can be reset through karaf command (user:reset).

No response from server while performing autodiscover for user {}

server-notifications/autodiscover

Warn

Autodiscover failed for the user mentioned.

Autodiscover failed for user {}, error code: {}, Detail: {}

server-notifications/autodiscover

Warn

Autodiscover failed for the user mentioned.

Failed to retrieve user settings while performing autodiscover for user {}

server-notifications/autodiscover

Warn

Autodiscover failed for the user mentioned.

No valid EWS URL setting configured for the user {}

server-notifications/autodiscover

Warn

Autodiscover failed for the user mentioned.

Error communicating with Database server - {error msg}

server-notifications/autodiscover

Error

BEMS failed to connect to SQL database. Needs immediate attention.

Database Error - {error msg}

server-notifications/autodiscover

Error

BEMS failed to connect to SQL database. Needs immediate attention.

Lost connection with exchange server. Last known error {}

server-notifications/ewslistener

Erro

EWSListener: Lost connection with exchange server. This might be due to Exchange server\Autodiscover service down.

Error subscribing user {} with exchange server {}

server-notifications/ewslistener

Error

Subscribe to the user email address with exchange server to track modifications of user mailbox.

User {} marked for reautodiscover

server-notifications/ewslistener

Info

Does a database call to mark the user for reautodiscovery. This task is done every n interval of time.

Error communicating with Database server - {error details}

server-notifications/pushnotifydbmanager

Error

Bootstrap database connection.

{} is no longer the master (producer) since database server time {}

servernotifications/pushnotifyha-dbwatcher

Error

High availability System: Check whether the node itself is Producer or not. Prints the error in event log when the server has lost ownership of the high availability system (not master any more).

{} is the master (producer) since database server time {}

servernotifications/pushnotifyha-dbwatcher

Info

High availability System: Check whether the node itself is Producer or not. If it was not master before; the fail-over is happening.

Detected Server {} is inactive. Users will be load balanced to other active servers

servernotifications/pushnotifyha-dbwatcher

Error

High availability System: If server is detected as inactive\heartbeat fails, the users of the bad server are reassigned to other active server.

Error communicating with Database server - {error details}

servernotifications/pushnotifyprefs

Error

Database error due to server down\login error, etc.

{ Good Dynamic Proxy Server connection error details }

server-console/config

Error

Connect BlackBerry Dynamics Module – Test from dashboard with GP down, connection failure error.

Connection to Good Dynamic Proxy Server is successful

server-console/config

Info

Connect BlackBerry Dynamics – Test from dashboard when GP is up and running, successful test.

Connection Successful, Server: -{}: Database : {}

server-console/config

Info

Mail – DB – Test database configurations from dashboard. Connection successful.

Exception during connection test - {}

server-console/config

Error

Mail – DB – Test database configurations from dashboard. Connection issues due to bad password or user or host info.

Invalid configuration properties- {}

server-console/config

Error

Mail – DB – Test database configurations from dashboard. Validation of database configuration values.

{ Good Dynamic Proxy Server connection error details }

server-console/config

Error

Presence BlackBerry Dynamics – Test from dashboard with Good Proxy down, connection failure error.

Connection to Good Dynamic Proxy Server is successful

server-console/config

Info

Presence BlackBerry Dynamics – Test from dashboard when Good Proxy is up and running, successful test.

Lync Presence Provider Ping failed with error status {} and

reason - {}

server-presence/presencebundle

Error

Connection to Presence server. If response received, log the reason for failure.

Lync Presence Provider Ping failed with exception {}: {} - set status {}

server-presence/presencebundle

Error

Connection to Presence server. Most likely connection refused because down

Lync Presence Provider Ping failed, cause unknown

server-presence/presencebundle

Error

Connection to Presence server.

Presence Service failed to reset LPP, interrupted with error: {}

server-presence/presencebundle

Error

Reset all contacts presence status.

Presence Service failed to reset LPP, timed out with error: {}

server-presence/presencebundle

Error

Reset all contacts presence status. Timeout error.

Failed to reset LPP, {} with error: {}

server-presence/presencebundle

Error

Reset all contacts presence status.

Presence Service started

server-presence/presencebundle

Info

Presence service started.

Presence Service stopped

server-presence/presencebundle

Info

Presence service stopped.

Bad Lync Presence Provider Subscription URI: {}

server-presence/presencebundle

Error

Presence service provider subscription URI.

Bad Lync Presence Provider

Ping URI: {} Ping

server-presence/presencebundle

Error

Presence service provider subscription URI.

Redis Cache & Queue services are not available at the moment.

server-presence/presencebundle

Error

When cache provider is set to Redis and Redis service is unavilable.

GNP Relay Service not available

server-presence/presencebundle

Warn

GNP service which sends GNP notification is not available or down.

Installation icon Installation and configuration: BEMS in a Good Control, Good Proxy environment