Export (0) Print
Expand All

Startup Options

This section describes several different ways in which you can start Message Analyzer. Note that the first time you start Message Analyzer after installation, you are prompted by the Welcome to Message Analyzer dialog to opt-in or opt-out of automatic updates to Message Analyzer user Library item collections and other elements that appear on the Start Page. To understand what these options mean, refer to Syncing Items on First Startup.

Startup Methods
Message Analyzer startup methods consist of the following:

  • Click the Message Analyzer icon in the Start menu or on the system Taskbar.

  • Double-click a supported Message Analyzer file, such as a .matp or .matu file.

    Note  When you double-click a supported trace or log file to start Message Analyzer, or if you use the right-click method indicated next, the file’s message data is automatically loaded into the Analysis Grid viewer by default.

  • Right-click a supported Message Analyzer file and select the Open item from the context menu. Note that in some cases, you might need to select the Open with Message Analyzer item in the context menu, for example, with a .cap or .etl file.

  • Specify a startup command string at the command line prompt, as described ahead.

Note  For more information about supported Message Analyzer files, see Locating Data.

Command Line Startup
When you start Message Analyzer from the command line, you can do the following:

  • Launch Message Analyzer to the StartPage, without opening a trace or log file.

  • Start Message Analyzer while opening a specifed trace or log file, which displays data in the Analysis Grid viewer by default.

  • Start Message Analyzer while specifying various command line options associated with locating, logging, and compiling any custom OPN parsers that you have created for Message Analyzer use.

The basic syntax for starting Message Analyzer from the command line is the following:  MessageAnalyzer.exe [TraceFile|LogFile] [Options]

So for example, you could open Message Analyzer from the command line without specifying a trace file, log file, or any options, as follows:  “C:\Program Files\Microsoft Message Analyzer\MessageAnalyzer.exe”

You can also specify a trace or log to open, as indicated in the following example, but it must be in one of the supported file formats, as described in Locating Data:   “C:\Program Files\Microsoft Message Analyzer\MessageAnalyzer.exe” <TraceFile.matp>

Startup Switches
The command line switches that are available for starting Message Analyzer at a command prompt are described below. To view these options at the command line, specify the following help switch:  “C:\Program Files\Microsoft Message Analyzer\MessageAnalyzer.exe” /?

Important  With exception of the TraceFile argument and the Command Line Usage switch, the following list items enable you to locate, compile, log, and debug custom OPN parsers that you have created for use with Message Analyzer.

  • TraceFile — specifies the name and path to the trace or log file to open when Message Analyzer starts.

  • /? — displays these Command Line Usage instructions.

  • /OPNLoadPathOnly=<path> — specifies the only path from which you will load custom OPN parsers. If this switch is specified, the default OPN load path in Message Analyzer is ignored. Note that this switch cannot be used with the /OPNLoadPathMerge option.

  • /OPNLoadPathMerge=<path> — adds the specified path to the list of paths from which you will load custom OPN parsers. Note that this switch cannot be used with the /OPNLoadPathOnly option.

    Important  If you create a new path from which to load custom OPN parsers and you place a native Message Analyzer parser in this path, for example, a user-extended native parser with the same name, Message Analyzer will start improperly.

  • /LogMode=<log mode> — specifies the output of the compilation log for debugging OPN. The log mode enables you to redirect log messages in the following ways:

    • /LogMode=File — saves log messages to a log file. If you do not specify a <filename> value with the /LogPath switch, the log file will be created as %LOCALAPPDATA%\Microsoft\MessageAnalyzer\Parsers.log.

    • /LogMode=Console — redirects log messages to the console.

    • /LogMOde=ETW — redirects log messages to the Windows Event Trace system.

    • /LogMode=Default — redirects log messages to the Win32 debug output.

  • /LogPath=<file name> — creates a log file with the specified file name. This switch can be used only with the /LogMode-File option.

  • /CachePath=<path> — specifies a path to an alternate cache folder where custom OPN parser model and codec files will be written and read, so that the default compilation cache for OPN parsers provided with Message Analyzer is not overwritten. Message Analyzer will then point to this folder at startup.

  • /GenerateOPNSymbols — generates PDB (Program Database) files during OPN compilation for instrumentation and debugging. When a .pdb file is generated, you can attach Message Analyzer to a debugger to debug OPN-generated C# code.

  • /OptimizeOPN=<flag> — specifies whether or not OPN compilation should be optimized. Examples:

    • /OptimizeOPN=true — optimizes OPN compilation. True is the default value, if this switch is unspecified.

    • /OptimizeOPN=false — does not optimize OPN compilation. Makes it easier for OPN debugging, which is more difficult to perform when OPN code is optimized. Note that if you specify this flag, Message Analyzer will have to perform recompilation at startup time.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft