KB17542 - How to reload missing BlackBerry smartphone data into the BlackBerry Manager
Environment
- BlackBerry® Enterprise Server Resource Kit version 4.1 SP6
- SDR95925
- SDR245373
- SDR253386
Overview
In some circumstances, BlackBerry smartphone specific fields like phone number and Hardware identification (ID) are not synchronized with the BlackBerry Manager User View. This causes issues with Administrators attempting to run audits within their environments.
Cause
The Handheld Agent may not have synchronized from the BlackBerry® smartphone to the BlackBerry® Enterprise Server.
Workaround
- Log in to the BES Server as the Windows Service Account for the BESAdmin.
- Download and unpack the BlackBerry Enterprise Server Resource Kit onto the BES Server. Note: Download the BlackBerry Enterprise Server Resource Kit User Guide located at BlackBerry - Enterprise Server Resource Kit and refer to pages 35-38.
- Create a list of PIN numbers (or email addresses) Note: For instructions to export BlackBerry smartphone user information from the BlackBerry Manager to a file see KB11477
- Import into Excel.
- Sort by Phone Number and remove all users with a valid Phone Number.
- Remove all columns except the PIN (or Email Address) column.
- Remove the first row/headings.
- Save this as a text file into the SyncRequest folder of the BRK for easy access.
- If you wish to test, create a short text file with a list of PIN numbers (or Email Addresses) and save in the same location.
- Open a command window and navigate to the SyncRequest folder.
- To submit a list of PIN numbers:
SyncRequest.exe -n -db -sync "Handheld Agent" -value_type pin -inputfile
- To submit a list of Email addresses:
SyncRequest.exe -n -db -sync "Handheld Agent" -value_type emailaddress -inputfile
- Restart the BlackBerry Synchronization Service.
To monitor its progress, the SYNC log will show the process with [SYNC-DSession] "headings" and "*** SLOWSYNC COMPLETE *** [username]" for each device/user.
Additional Information
There may be a delay in executing subsequent or repeat commands. My first test went almost immediately, but my second request seemed to stall in the “queue” for approximately 30 minutes.
This is informational only, in case it appears to be waiting for a long time with no apparent change in the BlackBerry Manager. Each user request may take a minute or two to complete. It is recommended to run a small batch test of 5 users.