Locating Log Files

In the event of an issue, your Square 9 Support Technician may ask for a variety of logs to be sent over for analysis. Here are the types of logs they may ask for, what application they are associated with, and where to find them.

  1. GlobalSearch Error Log
    1. General, all-purpose error log that handles all faults in ssinterface.exe including login and REST issues.
    2. Found on both server and client applications
    3. Location: C:\Users\<USERNAME>\AppData\Local\Square_9_Softworks\GlobalSearch\ErrorLog.log
  2. GlobalCapture Engine Log
    1. This log is a transcription of all actions being taken in the GlobalCapture Engine.
    2. Found only on the Engine server. One log per engine exists.
    3. Location: C:\GetSmart\CaptureServices\GlobalCapture_<ENGINE#>\captureLog.log
  3. GlobalAction Log
    1. This log is a transcription of all actions being taken in the GlobalAction Engine.
    2. Found only on App Server
    3. Location: C:\GetSmart\Workflow.log for versions prior to 2.2 C:\GetSmart\ActionServices\GlobalAction_<ENGINE#>\actionlog for versions 2.2 and later.
  4. Mongo Log
    1. This log is a transactional log of everything happening in the Mongo Database. Records varying levels of data based on what logging level is enabled.
    2. Found only on App Server
    3. Location: C:\GetSmart\Mongodb\logs\mongo.log
  5. Catalina Log
    1. Captures issues related to the Tomcat server running GlobalForms.
    2. Found only on GlobalForms Server
    3. Logs may be separated by date
    4. Location: C:\GlobalForms<yourVersion>\tomcat\logs\catalina.log
  6. Frevvo Log
    1. Captures issues related to the Frevvo LiveForms application.
    2. Found only on GlobalForms Server
    3. Logs may be separated by date
    4. Location: C:\GlobalForms<yourVersion>\tomcat\logs\Frevvo.log
  7. IIS Log
    1. Logs application data related to IIS and all of it's app pools and subprocesses
    2. IIS Log files can be configured to log varying amounts of data, and can be turned on or off in Programs & Features
    3. Their location is configured within the IIS Web Management Console - MORE INFO HERE
    4. Default Location: C:\inetpub\logs
  8. License Manager Log
    1. Logs errors for SSLicenseClean service.
    2. Found only on App Server.
    3. Such as “The request failed with HTTP status 403: Forbidden.” That is caused by not having your SSLicenseClean config file updated when using SSL.  
    4. Default Location: C:\GetSmart\Square9LicenseManager.log (Version 5 and below)
    5. C:\Program Files\Square 9 Softworks\License manager\Square9LicenseManager.log (Version 6 and up)
  9. GlobalForms Log
    1. By default GlobalForms does not create any logs, and typically logging for GlobalForms is not as common as the output tends to be overly verbose.
      1. Logging for GlobalForms should only be enabled temporarily and should only be done for good reason.
    2. You can enable logging for GlobalForms by:
      1. Stop the GlobalForms service in the Windows Service manager interface
      2. Open a command prompt (command prompt, not a powershell window)
      3. In command prompt, Navigate to your GlobalForms directory (by default C:\GlobalForms)
      4. Start GlobalForms with all logging enabled using the following command:

        set DEBUG=* & node main

        To output this into log files. Only have this running into log files for troubleshooting.

      5. cd C:\GlobalForms set DEBUG=* 
      6. node main >> output.log 2> error.log
      7. Output.log will have what you see when you launch GF in console without debugging, error.log will have everything else.

  10. GlobalSearch Extensions Log
    1. Log.txt location example: C:\Users\JOE\AppData\Local\Square_9_Softworks\GlobalSearch_Extensions\log.txt

Some of these logs may be large and may need to be compressed to send over email.

Removing Log Files

In almost all cases, large log files can be deleted to free up space. It is recommended you keep the most recent logging, but old log files can take up unnecessary amounts of space and can be deleted without any repercussions relating to application function. A better, more non-destructive way to address this may be to zip up and compress these log files periodically, especially in the event the logs are required for future auditing.