This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Track-It! 2018 R2
Where are Track-It! 2018 log files?
Where can I configure Track-It! 2018 Logging?
How can I debug Track-It! 2018?
How do I troubleshoot Track-It! 2018?
Does Track-It! 2018 have any advanced logging features?
Log files can be found on the Track-It! 2018 server at:
<Track-It! 2018 installation Drive>\Program Files (x86)\BMC\Track-It!\Logs
Note: Please see Knowledge Article 000147419 - Track-It! 2018 Log File and Component Descriptions for information on which log files should be referred to, for various components in Track-It! 2018.
How to adjust the level of logging using the Log Configuration Manager
All logging is enabled by default, but you may have to increase the level of logging depending on what you are troubleshooting.
The Log Manager Configuration window appears.
2. For each component, you can select one of the logging levels below.
Messages to indicate errors or critical failures, including runtime errors or unexpected conditions.
"Exception.message = divide by zero"
Messages to indicate potential problems, this may include non-critical failures.
"Password is blank", “login failed : invalid password”
Messages that show process flow without being too verbose.
"User logged in successfully", “Incident created”, etc.
Messages important to developers for debugging.
 2007-04-10 16:48:08 DEBUG 1828 MGCUserTrack SDESERVER1 sde MGCUserTrack CreateDBCommand strCmd: SELECT * FROM "_SMDBA_"."_ACTIVEUSERS_" WHERE APPSERVER = 'SDESERVER1/SDE'
More detailed messages that contain the data important to developers for debugging.
Note: BMC does not recommend using TRACE unless you are working directly with development or Field Engineering. Enabling TRACE for all components severely affects the performance of the application server.
 2007-04-10 16:46:23 TRACE 1828 MGCUserTrack SDESERVER1 sde 528259116 MGCUserTrack UserTouch Finish
WARNING: BMC does not recommend using TRACE unless you are working directly with development or Field Engineering. Enabling TRACE for all components will severely affect the performance of the application server.
3. Click Save.
- Logging changes are saved to the Windows registry and immediately take effect.
- If you had disabled logging for some components and then re-enabled, be aware that logging does not take effect immediately for the Metadata and FeatureInfo components. If the application server is running before logging is enabled for these two components, then the application server must be restarted to receive logging information from them or an IISRESET must be done on the application server.
NOTE: If the logging output does not take effect a metadata restart is required. Metadata restarts required ALL users log out of Track-It! 2018.