Run the BlackBerry Thread Analyzer Tool from the command prompt

  • See Prepare to run the log analysis tools.
  • Copy any log files for the BlackBerry Enterprise Server components, except the log file for the BlackBerry MDS Connection Service, to the computer that hosts the BlackBerry Thread Analyzer Tool and BlackBerry Enterprise Server Log Analysis Tool
  1. On the computer that hosts the BlackBerry Thread Analyzer Tool, on the taskbar, click Start > All Programs > BlackBerry Enterprise Server Resource Kit > BlackBerry Analysis Monitoring and Troubleshooting Tools > BlackBerry Thread Analyzer Tool.
  2. In the command prompt window, type NoResponseCheck and the following parameter:

    Parameter

    Description

    -p E[xchange]

    -p D[omino]

    -p G[roupWise]

    This parameter specifies the messaging platform.

  3. Type any of the following optional parameters:

    Parameter

    Description

    -NoFP

    This parameter prevents the tool from checking for false positives.

    -type <abbreviation>

    You can use this parameter to limit the tool to checking the log files for a specific BlackBerry Enterprise Server component. Specify the abbreviation for the log files that you want to analyze. For example, type MAGT to analyze the log files for the BlackBerry Messaging Agent only.

    For more information about the abbreviations used for different components, visit www.blackberry.com/go/serverdocs to read the BlackBerry Enterprise Server Administration Guide.

    -MDS <abbreviation>

    This parameter specifies the abbreviation for the BlackBerry MDS Connection Service log files. If you do not specify an abbreviation, the tool uses MDAT.

    You require this parameter to bypass any reference to the BlackBerry MDS Connection Service log files in the log files for other BlackBerry Enterprise Server components. If the tool finds a reference to the BlackBerry MDS Connection Service log files, the tool stops running.

    -L <path>

    This parameter specifies the location of the log files that you want to analyze if the files are not in the same folder as the tool. If the path contains spaces, enclose the path in quotation marks ( " " ).

    -OL <path>

    This parameter specifies the folder where the tool writes the output files. If the path contains spaces, enclose the path in quotation marks ( " " ).

    -debug <filename.txt>

    This parameter specifies that the tool creates a more detailed output file for debugging purposes, and it specifies the name of the debugging file.

    If you do not specify a file name, the tool displays the debugging information on the screen.

Example: Producing detailed output for the BlackBerry Enterprise Server for IBM Lotus Domino log files

NoResponseCheck -p D -debug Detailed.txt -L C:\BRK\logs

NoResponseCheck -p E -NoFP -type MAGT -L C:\BRK\logs

  • If you want to view the help information for the tool, including the list of available parameters, in the command window, type NoResponseCheck -? or NoResponseCheck -help.
  • If you configured the tool to use a UAC-compliant file path, the output file is located at <drive>:\Users\<user_name>\AppData\Roaming\Research In Motion\AMT\ or <drive>:\Documents and Settings\user_name\Application Data\Research In Motion\AMT\. If you did not configure the tool to use a UAC-compliant file path, the output file is located in a file path relative to the current working directory, for example, <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server Resource Kit \BlackBerry AMT Tools.


Was this information helpful? Send us your comments.