Issue:
This article describes the steps to generate fsdiag debug, also known as full logging, logs for PSB Computer Protection, PSB Server Protection, Client Security 14 and Server Security 14 and later. Debug diagnostic logs are needed in some instances by technical support to investigate problems in more detail.
Resolution:
When full debug logging is enabled, an Fsdiag will gather more in depth and additional log files, which help in some problem investigations.
Debug logging can be enabled directly from the F-Secure user interface in the following products: PSB Computer Protection, PSB Server Protection, SAFE, Internet Security and Client Security 15.10
Steps how to enable advanced debug logging (full logging) on a Windows system for:
- Open the F-Secure product user interface
- Select Settings (Cogwheel icon)
- Select Edit settings
- Click Yes on User Account Control prompt (provide admin credentials if requested)
- Select Support
- In the Tools section, enable debug logging by tapping the On/Off switch below Debug logging helps customer support to analyze issues.. -text
- Reproduce the steps that caused the original problem, take note of exact time of the problem
- Generate an FSDIAG diagnostic file by following the steps explained in this link: https://community.f-secure.com/common-home-en/kb/articles/5427-how-do-i-create-an-fsdiag-file
- Open the F-Secure product user interface
- Select Settings (Cogwheel icon)
- Select Edit settings
- Click Yes on User Account Control prompt (provide admin credentials if requested)
- Select Support
- In the Tools section, disable debug logging by tapping the On/Off switch below Debug logging helps customer support to analyze issues.. -text
In case the option described above is not available, follow the steps below:
- Download the debug tool from download.f-secure.com/support/tools/CCF-logging-tool/fsloglevel.exe
- Double click fsloglevel.exe
- Select Full Logging
- Click OK
- Restart the computer
- Reproduce the steps that caused the original problem, take note of exact time of the problem
- Generate an FSDIAG diagnostic file by following the steps explained in this link: https://community.f-secure.com/common-home-en/kb/articles/5427-how-do-i-create-an-fsdiag-file
- Run the fsloglevel.exe tool a second time after submitting the logs
- Click on Normal Logging to turn off the debug mode (debug mode slows down the machine slightly)
Article no: 000009164