Description of specific logs that are required for investigation of BlackBerry


Specific logs are required when you investigate BlackBerry single-user and device issues. The following information must be submitted to Microsoft Online Services Support regarding these issues:
  • Required log type
  • Required date logs
  • BlackBerry ticket number
Microsoft only makes BlackBerry logs available for break-fix issues. Additionally, a BlackBerry support ticket number is required.

More Information

The following list describes the type and organization of BlackBerry Enterprise Server (BES) logs. BES logs are stored on each server in separate folders for each day. Depending on the services that are running on the server, the log folder contains a subset of the following logs:
  • EWSA - EWS component log - New in Hosted BES
  • ACNV - BlackBerry Attachment Service attachment conversion
  • ALRT - BlackBerry Enterprise Server Alert Tool
  • ASCL - BlackBerry Attachment Service client
  • ASMN - BlackBerry Attachment Service attachment monitor
  • ASRV - BlackBerry Attachment Service component
  • BBAS-AS - BlackBerry Administration Service - Application Server
  • BBAS-NCC - BlackBerry Administration Service - Native Code Container
  • CBCK - backup connector
  • CEXC - Microsoft Exchange connector
  • CMNG - management connector
  • ConfigTool - BlackBerry Enterprise Server Express configuration tool
  • CONN - BlackBerry Synchronization Connector
  • CTRL - BlackBerry Controller
  • DBNS - BlackBerry database notification service
  • DISP - BlackBerry Dispatcher
  • EXTS - extension connector
  • HHCG - BlackBerry Configuration Panel
  • MAGT - BlackBerry Messaging Agent
  • MAST - BlackBerry Mail Store Service
  • POLC - BlackBerry Policy Service
  • ROUT - BlackBerry Router
  • SYNC - BlackBerry Synchronization Service
  • TAT - BlackBerry Threshold Analysis Tool

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.

Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.

Article ID: 2797774 - Last Review: Apr 1, 2016 - Revision: 1