Creating the SMS Administrator Log File UI.LOG

Last reviewed: March 16, 1998
Article ID: Q125668

The information in this article applies to:
  • Microsoft Systems Management Server versions 1.0, 1.1, and 1.2

SUMMARY

SMS Administrator can log its activities to a log file (a process known as tracing). By default, tracing is turned on for SMS Administrator, but the log file does not get created until SQL Server tracing is turned on.

MORE INFORMATION

To turn on SQL Server tracing:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT or Microsoft SMS to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Start Registry Editor (REGEDT32.EXE) and select the HKEY_LOCAL_MACHINE subtree.

  2. Go to the following subkey:

          \SOFTWARE\MICROSOFT\SMS\TRACING
    

  3. From the parameter list, select SqlEnabled.

  4. From the Edit menu, choose DWORD.

  5. In the Data field, change the value from 0 to 1 and then choose OK.

  6. To verify that tracing is enabled for the SMS Administrator User Interface, go to the following HKEY_LOCAL_MACHINE key:

          \SOFTWARE\MICROSOFT\SMS\TRACING\SMS_USER_INTERFACE
    

    The parameter Enabled should be set to 1.

  7. Exit and restart SMS Administrator (SMS.EXE).

A UI.LOG file is created in the SMS\LOGS directory. The log file can be viewed using SMS Tracer (SMSTRACE.EXE). For more information on using SMS Tracer, query on the following words here in the Microsoft Knowledge Base:

   tracer


Additional query words: sms prodsms
Keywords : ntutil smsconfig kbnetwork
Version : 1.0 1.1 1.2
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 16, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.