Debugging Log
Create a debugging log to assist in diagnosing problems.
Details
If you are experiencing problems with Avatar Signature with Validation (version 4x or higher) or the Topaz pad, it is recommended that a debugging log be created to help in diagnosing the problem.
Steps
To enable the debugging log feature:
-
Create a blank file with the following file name:
DebugSignature.txt -
Save the file to the applicable location:
-
When running locally (thick-client), the file must be located in the \Windows directory. This will activate debugging for all users of this workstation only.
-
When running on Citrix or Terminal Services (thin-client), the file must be located in the \Windows directory that the user is mapped to; this is typically the user’s profile directory. This will activate debugging for all users who are mapped to this location.
Once activated, a debugging log is created in the same location that the DebugSignature.txt file was placed in, and has the following file name:
DebugSignature_%userid%_MMDDYYYY.log
where %userid% is the ID of the user who was logged in and created the log, and MMDDYYYY is the date that the log was created.
A new log is created for each day and each user for which the feature is activated. Records are appended to the current log for the same date/user. It is recommended that the debugging feature be deactivated when no longer needed, as it continues to generate logs and consume disk space.
To deactivate the debugging log feature, simply delete or rename the DebugSignature.txt file. Debugging logs are not required for running Avatar Signature with Validation and should only be utilized to resolve specific problems.