Tips 'n' Tricks for BlackBerry Enterprise Server and BlackBerry Handheld devices.
[40000] (05/19 16:23:09):{0xF2C} SRPClient::ReceivePacket: Error receiving Header (10054)
[30155] (05/19 16:23:09):{0xF30} SRP connection dropped
[30357] (05/19 16:23:09):{0xF30} Connection with <SRP_address> lost
[40000] (05/19 16:23:09):{0xF3C} SRPClientReceiver thread stopped
[40000] (05/19 16:23:09):{0xF3C} [DIAG] EVENT=Unregister_thread, THREADID=0xF3C,
THREADNAME="SRPClientReceiver"
[30000] (05/19 16:23:09):{0xF30} [SRP] Connection lost
Cause: Network access issues occur when the BlackBerry Enterprise Server tries to connect to the BlackBerry Infrastructure through the default port on the firewall.
Resolution: Search the MAGT logs using the following phrase:
Connection with <SRP_address> lost
where <SRP_address> is the SRP address that the BlackBerry Enterprise Server uses to connect to the BlackBerry Infrastructure.
Cause: If the SRP Identifier attempts to connect to the BlackBerry Infrastructure five times in under one minute, the SRP Identifier is disabled from the BlackBerry Infrastructure.
Note: If the SRP Identifier connects and disconnects five times within one minute, it is disabled so that no one can use the same SRP Identifier or try to access the SRP Identifier and SRP Authentication Key. This is by design.
Resolution: Verify the following:
Note: If more than one BlackBerry Enterprise Server is using the same SRP Identifier and attempting to connect through the same proxy server, the connections will appear to be originating from one IP address. Stop all instances of the BlackBerry Enterprise Server and make sure that only one BlackBerry Enterprise Server instance attempts to connect to the BlackBerry Infrastructure.
The BlackBerry Enterprise Server depends on existing databases, such as the mail files and the IBM Lotus Domino directory, for its operation.
Corruption of a database design, form, document, view, or index can cause a number of issues with the BlackBerry Enterprise Server. To help correct these problems, an administrator can run maintenance tasks, such as Fixup, Updall and Compact.
Some issues that the maintenance tasks may correct are the following:
The BlackBerry Enterprise Server creates IBM Lotus Domino-designed databases, such as BlackBerryProfiles.nsf, BlackBerryOutbox.nsf, BBDir.nsf, BBStats.nsf, and a uniquely named BlackBerry state database for each user.
Note: These maintenance task can be performed either online or offline, as desired.
Complete the following steps to perform IBM Lotus Domino offline maintenance tasks on specific databases:
For online maintenance, the same set of commands can be run, except the "n" in front of the command is dropped, and the command Load is needed. The command is run from the Domino console.
Caution should be taken when running online maintenance as this can affect the performance of your server.
Before upgrading from BlackBerry Enterprise Server for Lotus Domino v4.0 to v4.1, see the BlackBerry Enterprise Server Installation Guide and the BlackBerry Enterprise Server System Administration Guide for BlackBerry Enterprise Server version 4.1 to verify your system requirements.
Make sure that BlackBerry Enterprise Server version 4.0 is upgraded to at least SP3 before upgrading to version 4.1.
Additionally, complete the checklists provided below.
Complete the following steps:
Complete the following steps:
At some point the BlackBerry Manager has closed unexpectedly, generating the message. The following error message appears every minute in the Lotus Domino console:
Process C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BBMgr\Server\bbmgrw32.exe
(7976/0x1F28) has terminated abnormally
Restarting BlackBerry Manager or the Lotus Domino console does not prevent the error message from appearing. The Domino Process Monitor causes the message to be repeatedly displayed.
Restarting the server, either a warm boot or cold boot, appears to resolve the issue temporarily.
To disable the Domino Process Monitor please review the Lotus Administrator help.
To identify why the error occurred originally, make sure the BlackBerry Manager's debug log level is at a minimum of 4. To verify the log level, complete the following steps:
IT policy keys are read from the GlobalSettings table in the configuration database each time the BlackBerry Policy Service needs to sign a policy. These keys let the BlackBerry smartphone confirm that the policy key came from its database.
The ServerConfigHistory table keeps a history of policy key changes, but it is periodically updated by a Structured Query Language (SQL) script that removes the oldest entries in the table after a specified number of days. Therefore, a query of the database does not recover a complete history of changes. Additionally, the ServerConfigHistory does not archive the previous versions of the policy key; it only records the current version.
When the BlackBerry Enterprise Server cannot access the active IT policy key, only users with the current policy key are able to receive IT Policies and applications on their BlackBerry smartphones.
During routine operations, the BlackBerry Enterprise Server references the active IT policy key in the SQL configuration database to confirm its authenticity. If it is unable to communicate with the configuration database, it generates a new policy key.
Note: This issue should occur infrequently, because when the Policy service fails to read the keys, it attempts to commit a new key to the database within a short period of time.
If running Microsoft SQL Server 2000, complete the following steps to confirm the policy key change:
SELECT * FROM ServerConfigHistory WHERE Details='PolicyPublicKey,PolicyPrivateKey'
If you are running Microsoft SQL Server Desktop Engine (MSDE), complete the following steps to confirm the policy key change:
osql -E -d <database_name> -q "SELECT ChangeDateTime FROM ServerConfigHistory
WHERE Details='PolicyPublicKey,PolicyPrivateKey'"
To reset a BlackBerry smartphone to factory defaults perform the following steps:
Warning: This will erase all data from the smartphone, please ensure that you back up the BlackBerry smartphone first.
Note: BlackBerry Desktop Manager 4.7 must be installed on the computer. The BlackBerry smartphone must be running BlackBerry Device Software versions 4.3 to 4.5.
SMS, Phone, and Email icons may be missing from the BlackBerry Bold 9000 smartphone after the following error message:
Uncaught Exception Error Appeared
© 2024 d-PIT Solutions