Vertigo Logging Options and Locations (Vertigo 1)

  • 7020321
  • 07-Sep-2010
  • 07-Aug-2017




What do the log options in Vertigo mean? Where is the location of the log files for Vertigo?


1) Vertigo uses log files to detail everything that is done in the program (logging in, copying a rule, deleting a signature etc...). It can also serve a purpose of troubleshooting when things are not connecting, or working.

By default Vertigo will enable logging on installation. If you wish to disable logging or re-enable logging:
a. Log into Vertigo

b.Click "Settings | Debugging |Enable .NET Tracing "
Note: You may also want to make sure that 'Trace Errors',' Trace Info', and 'Trace Warnings' are selected.  'Enable SOAP Tracing' is optional.

A check mark in front of the setting means it is enabled. No check mark means the log will no longer be updated.

Explanation of logging options:

Enable.NET Tracing:  This enables the Vertigo tracelog to be created ,and updated. (Recommended to be enabled)
Trace Errors:                This enables errors within Vertigo to be written in the logs. This is very helpful for troubleshooting purposes.
Trace Info:                    This provides standard information in the logs: queries to GroupWise, copying signatures, rules etc...
Trace Warnings:          This enables warning messages to be displayed within the log files.

It is highly recommended that each one of these settings be on at all times, especially if needing help from support.

Enable SOAP Tracing:  These are additional log files that help in troubleshooting Vertigo and GroupWise. This is mainly used by support, but can provide information about requests along the SOAP protocols.

2)  The location of the log files are:
If you are running Windows XP, 2000, or Server 2003 the log files will be located in:  C:\Documents and Settings\All Users\Application Data\GWAVA\Vertigo\Tracelogs
If you are running Windows 7, 2008 Server the log files will be located in: C:\ProgramData\GWAVA\Vertigo\Tracelogs

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 1846.