Configuring crash diagnostics settings in Kaspersky Security Center

If a problem occurs when operating Kaspersky Security for Windows Server (for example, the application crashes), you can diagnose it. To do this, you can enable the creation of trace files and a dump file for the Kaspersky Security for Windows Server process and send these files for analysis to Kaspersky Technical Support.

Kaspersky Security for Windows Server does not send any trace or dump files automatically. Diagnostic data can only be sent by a user who has the required permissions.

Kaspersky Security for Windows Server writes information to trace files and the dump file in unencrypted form. The folder where files are saved is selected by the user and managed by the operating system configuration and Kaspersky Security for Windows Server settings. You can configure access permissions and allow only required users to access logs, trace files and dump files.

To configure crash diagnostics settings in Kaspersky Security Center:

1. In the Kaspersky Security Center Administration Console, open the Application settings window.
2. Open the Malfunction diagnosis section.
3. If you want the application to write debug information to a file, select the Write debug information to trace file check box.
4. In the field below, specify the folder where Kaspersky Security for Windows Server will save trace files.
5. Configure the level of detail of debug information.
   

   This drop-down list lets you select the level of detail of debug information that Kaspersky Security for Windows Server saves to the trace file.

   You can select one of the following detail levels:

   • Critical events – Kaspersky Security for Windows Server saves information only about critical events to the trace file.
   • Errors – Kaspersky Security for Windows Server saves information about critical events and errors to the trace file.
   • Important events – Kaspersky Security for Windows Server saves information about critical events, errors, and important events to the trace file.
   • Informational events – Kaspersky Security for Windows Server saves information about critical events, errors, important events, and informational events to the trace file.
   • All debug information – Kaspersky Security for Windows Server saves all debug information to the trace file.

   A Technical Support representative determines the detail level that needs to be set in order to resolve any issue that may arise.

   The default level of detail is set to All debug information.

   The drop-down list is available if the Write debug information to trace file check box is selected.

6. Specify the maximum size of trace files.
7. Specify the maximum number of files for one trace log.

   Kaspersky Security for Windows Server will create up to the maximum number of trace files for each component to be debugged.

8. Specify the components to be debugged. Component codes must be separated with a semicolon. The codes are case sensitive (see table below).

   Kaspersky Security for Windows Server subsystem codes

   Component Code	Name of component
   *	All components.
   gui	User interface subsystem, Kaspersky Security for Windows Server snap-in in Microsoft Management Console.
   ak_conn	Subsystem for integrating Network Agent and Kaspersky Security Center.
   bl	Control process, implements Kaspersky Security for Windows Server control tasks.
   wp	Work process, handles anti-virus protection tasks.
   blgate	Kaspersky Security for Windows Server remote management process.
   ods	On-Demand Scan subsystem.
   oas	Real-Time File Protection subsystem.
   qb	Quarantine and Backup subsystem.
   scandll	Auxiliary module for virus scans.
   core	Subsystem for basic anti-virus functionality.
   avscan	Anti-virus processing subsystem.
   avserv	Subsystem for controlling the anti-virus kernel.
   prague	Subsystem for basic functionality.
   updater	Subsystem for updating databases and software modules.
   snmp	SNMP protocol support subsystem.
   perfcount	Performance counter subsystem.

   The trace settings of the Kaspersky Security for Windows Server snap-in (gui) and the Administration Plug-in for Kaspersky Security Center (ak_conn) are applied after these components are restarted. The trace settings of the SNMP protocol support subsystem (snmp) are applied after the SNMP service is restarted. The trace settings of the performance counter subsystem (perfcount) are applied after all processes that use performance counters are restarted. Trace settings for other Kaspersky Security for Windows Server subsystems are applied as soon as the crash diagnostics settings are saved.

   By default, Kaspersky Security for Windows Server logs debug information for all Kaspersky Security for Windows Server components.

   The entry field is available if the Write debug information to trace file check box is selected.

9. If you want the application to create a dump file, select the Create dump file check box.
10. In the field below, specify the folder in which Kaspersky Security for Windows Server will save the dump file.
11. Click OK.

The configured application settings are applied on the protected device.