Found this link of a BES 5.0 Service Pack 3 leaked admin guide: 5.0.3 The link was posted on CIO mag. I am curious to see what features will make the official release of version 5.0.3. I hope the TCPPing and JMS BAS jobs notification issues with BAS get resolved or at least minimized. [...]
Stack traces occur when an exception is encountered by a service (BlackBerry Administration Service, Sync Service) or process (Messaging Agent). With a basic understanding of stack trace, the culprit (s) may be isolated. For root cause, a dump needs to be taken usually with DebugDiag and the issue needs to be escalated to RIM Software [...]
4. Wiping and removing/re-adding a user from BES is a common shotgun approach to troubleshooting issues with EA or message flow. Admins will just remove/re-add users and re-activate users hoping that will resolve the issue at hand. There needs to be an investigation why the issue is occurring in order to find root cause and [...]
From SGriffin’s Blog there is a new release of MFCMapi. There is a new command line utility called MrMAPI which includes Property tag lookup and SmartView parsing.
The main points of failure for an Enterprise Activation are the following: Provisioning ETP delivery Exchange permissions for the BlackBerry service account IT Policy rejected by the handheld Policy and/or Synchronization services are non-responsive Slow Sync not completing 1. If a handheld is going to be activated on the full Enterprise BES or a wireless [...]
Here is the BlackBerry KB to check DST readiness: KB24267
On SGriffin’s MAPI Internals Blog, he reported the emsmdb32 hang the new MAPI CDO 1.2.1 package fixes which causes Calhelper to consume CPU on BES.
Below are log lines specific to the stages of an EA. BlackBerry Messaging Agent 1. After entering the email address and EA password on the device and clicking Activate, the enterprise activation ETP message arrives in the mailbox of a BlackBerry smartphone user and is picked up by the BlackBerry Enterprise Server. [40282] (10/27 08:07:40):{0×1114):{0x13B8} [...]
Microsoft’s new release of the MAPI/CDO 1.2.1 package last week corrects the High CPU usage experienced by Calhelper.exe on the BES for the previous version of MAPI/CDO bundle 6.5.8165.0 which resolved many of the issues experienced with MAPI shared heap corruption. The high CPU usage issue was casued by Emsmdb32.dll failing to unload cdo.dll properly [...]
BES logs (debug logs) provide valuable information concerning troubleshooting, benchmarking, capacity planning, and monitoring for BES issues. Most admins do not look at BES logs unless to delete them since they can grow quickly in large environments. By having a basic understanding how BlackBerry Services and processes write to the debug logs, an admin can [...]