Troubleshoot issues with

UEM Notifications

Issue:

 I attempted to send a notification from the UEM user manager and it says the limit is 2000.

Possible causes:

 You selected more than the allowed number of recipients from the UEM user manager, which is 2000. If you want to alert more users in a single notification, use a group in the Notifications menu or send multiple notifications.

Issue:

I sent a notification to a large number of users inside a group and it failed.

Possible causes:

You can send a notification to a maximum of 30,000 users in a group.

Issue:

I sent a notification, but the end users did not receive it.

Possible causes:

The users do not exist in your
BlackBerry AtHoc
system.
The users exist in the
BlackBerry AtHoc
system, but do not have a Username or Mapping ID attribute in their profile.
The users exist in the
BlackBerry AtHoc
system, but do not have any of the selected delivery methods.

Issue:

I sent a notification to 1000 UEM users, but when I look at the notification report, it shows that the message was sent to only 990 users.

Possible cause:

Some of your UEM users are not mapped in your

BlackBerry AtHoc

system. Notification reports only reflect the users in the

BlackBerry AtHoc

system, not users in UEM.

Issue:

I want to send myself a test notification, but do not see the Send only to me option on the New notification screen.

Possible cause:

You are an operator in UEM, but you do not have a user profile in the

BlackBerry AtHoc

system.

Issue:

I can see the Notifications plug-in in the UEM console, but I cannot send notifications and I see errors when viewing settings and sent alerts.

Possible cause:

The UEM Notifications plug-in is not installed on the UEM core server. Go to

Settings

>

Infrastructure

>

Instances

. Expand the BlackBerry UEM instance and view the installed plug-ins and their versions in the

BlackBerry UEM - UEM Core

and

BlackBerry UEM - Management console

rows.

Issue:

I sent a stop sync request and it is taking a long time to complete.

Possible cause:

If you submit a stop sync request within 5 seconds of the sync start, the stop request processes quickly. If the stop sync request occurs after the sync request has been processing, the stop request takes longer because it needs to roll back the changes already made by the in-progress sync.

Issue:

User import through .csv file displays an error when more than 1000 users are imported.

Possible cause:

User import is restricted to 1000 users at a a time.