Using the SMS Tracer Utility

This article was previously published under Q125452
This article has been archived. It is offered "as is" and will no longer be updated.
SUMMARY
The Microsoft Systems Management Server allows you to trace theactions performed by the SMS services. When tracing is enabled, eachservice makes log entries for actions that it performs or errors that itreceives in a log file. The log files are ASCII text and can be viewed witha text editor. However, SMS includes a Tracer utility that parses these logfiles and presents them in a clearer, more user-friendly manner than plaintext viewing. Tracer also allows interactive viewing of the SMS log filesas the services are writing to them.
MORE INFORMATION
There are currently two versions of this utility, TRACER.EXE andSMSTRACE.EXE

TRACER.EXE is a command line console-mode utility that reads changes madeto a text file in real time. This file is located in the PSSTOOL\<arch>directory on the SMS 1.0 and 1.1 CD-ROM. For SMS 1.2 it is located in theSUPPORT\DEBUG\<arch> directory on the CD-ROM.
   Usage: tracer <path to one of the SMS log files>				
SMSTRACE.EXE is a graphical user interface (GUI) multiple documentinterface (MDI) version and is included in the SITE.SRV\<arch>.BINdirectory.

SMSTRACE.EXE allows you to customize the display by selecting options suchas columns, filtering, and ignore new lines. You can also Cut and Paste andPrint from SMSTRACE. SMSTRACE.EXE also allows viewing of several log filessimultaneously.

To install SMSTRACE as an icon in the SMS group:

  1. Open the Systems Management Server group windows.
  2. From the Program Manager File menu, select New.
  3. Choose New Program Item. For the Command Line, enter:
    <drive>:\sms\site.srv\<arch>.BIN\SMSTRACE.EXE
    For the working directory, enter:
    <drive>:\sms\site.srv\<arch>.BIN
The SMS services log files are all located in the SMS\LOGS directory exceptfor the Site Configuration Manager log file SCMAN.LOG and the Bootstrap logfile BOOT.LOG.

The following is a list of the log files and the names of the componentthat writes to them:
SMS Alerter                   ALERTER.LOGApplications Manager          APPMAN.LOGBootstrap                     BOOT.LOG (in SMS root directory of Secondary                                        Site Servers)Client Configuration Manager  CLICFG.LOGInventory Dataloader          DATALODR.LOGDespooler                     DESPOOL.LOGSite Hierarchy Manager        HMAN.LOGInventory Agent               INVAGENT.LOGInventory Processor           INVPROC.LOGLAN Sender                    LANSEND.LOGRAS Sender                    RASSEND.LOGRAS Sender (asynchronous)     RASSYNC.LOGRAS Sender (ISDN)             RASISDN.LOGRAS Sender (X.25)             RASX25.LOGSNA Sender                    SNASEND.LOGSNA Sender (Batch)            SNABATCH.LOGSNA Sender (Interactive)      SNAINTER.LOGSNA Receiver                  SNARECV.LOGMaintenance Manager           MAINTMAN.LOGPackage Command Manager       PACMAN.LOGSMS Scheduler                 SCHED.LOGSite Configuration Manager    SCMAN.LOG (in root directory of SMS drive)Site Reporter                 SITEREP.LOGSMS Executive                 SMSEXEC.LOGSNMPTrap Filter               TRAPFLTR.LOGSMS Administrator             UI.LOG				
For more information on tracing Systems Management Server services, pleaserefer to the Systems Management Server 1.0 or 1.1 "System Guide," AppendixJ. If you are running Systems Management Server 1.2, please refer to theSystems Management Server 1.2 Resource Kit.
config sms prodsms tshoot troubleshooting
Properties

Article ID: 125452 - Last Review: 12/04/2015 11:01:18 - Revision: 2.2

Microsoft Systems Management Server 1.0 Standard Edition, Microsoft Systems Management Server 1.1 Standard Edition, Microsoft Systems Management Server 1.2 Standard Edition

  • kbnosurvey kbarchive kbhman kbinventory kbmaintman kbnetwork kbscheduler kbscman KB125452
Feedback