How to troubleshoot Footprints 12.1.x using the footprints.log?

Version 8
    Share This:

    Currently when publishing containers in Footprints Service Core 12.1.x, you may not find enough details to identify and troubleshoot the problem or error. Additional details are stored in the Footprints.log file on the Footprints application server. Please follow these steps to review the log using the available log viewer.

     

    In Footprints 12.1.00.00x or before you will need to use these steps to access the log file and log viewer.

     

    1. Go to the Footprints Service Core application server

    2. Go to the C:\Program Files\BMC Software\FootPrints Service Core\web\default folder

    3. Launch the "fp-log-viewer.html" in a browser on the server. You may have to give it permissions to run and open pop-up windows

    4. Click the "Load Log" icon

    5. Change the "Minimum log level to load" to "Warn"

    6. Click the link to "Browse" to "Load from a file".

    7. Go to the C:\Program Files\BMC Software\FootPrints Service Core\logs and select "footprints.log"

    8. Double click to see full details of the error

     

    In Footprints 12.1.01 and 12.1.01.00x, there is a new option to download the Footprints.log file to your workstation and  launch the log viewer.

     

    Go to the Administration>System Management>System Settings>Server Configuration page.  At the top of the page are 2 new options.

     

    In Footprints 12.1.01 you have a link to download the Footprints.log or all log files.

     

    In Footprints 12.1.01.001 or higher, you have the download and log viewer option.

     

     

    The current option to use the log viewer from inside Footprints 12.1.01.001 requires 2 steps.

    1. Download the Footprints.log.zip file and unzip to a local folder on your workstation
    2. Launch the log viewer and load the log file from your local drive.

     

    The Footprints.log file will rename itself and start a new file when it reaches 10 MB in size, so you may need to look at an older file to find the time when the error happened.

     

    You can also use this tool to determine information from the incoming email debugging, publishing errors, business rule execution, or other occurrences that could be affecting Footprints 12.1.

     

    NOTE: A new feature in Footprints 12.1.01 summer release is the option to enable sending browser errors to the server log.  Please go into Administration>System Management>System Settings>Server Configuration page. If you are troubleshooting an error in the browser, enable the "Logging Configuration" setting to "Send browser error to the server log".

     

     

    I do not recommend turning on the "Custom Logging Configuration" unless you receive instructions from BMC Software Footprints support.

     

    NOTE: When turning on the "Email Debugging", for tracking incoming email processing, the data is written to the footprints.log file.  To turn on email debugging, go to the Administration>System Management>Email Settings>Incoming Email (System) page for the option at the bottom of the page to "Enable Email Debugging".